Consent-Aware Privacy Firewall

The project addresses a practical and increasingly important AI safety problem: reducing accidental disclosure of sensitive information when interacting with LLMs. The focus on local-first processing and explicit user consent reflects good privacy-by-design principles, and the implementation demonstrates a functional end-to-end prototype.

As next steps, the project could:

-Expand the evaluation with standard metrics such as precision, recall, false positives, and false negatives across different categories of sensitive information.

-Conduct a small usability study to assess whether the consent prompts meaningfully reduce accidental disclosures while maintaining a smooth user experience.

I conditionally approve the project

The Consent-Aware Privacy Firewall (CAF) addresses a genuinely important and timely problem — users routinely share sensitive personal, medical, and financial information with LLMs like ChatGPT without understanding the privacy implications, and existing solutions detect information after the fact rather than intervening before submission. The project's core strength lies in its local-first architecture — all processing occurs entirely within the browser with no data transmitted externally — which is a principled and privacy-respecting design choice that aligns well with the consent-aware philosophy. The system is practical, deployable as a Chrome Manifest V3 extension, and covers a reasonable scope including prompt scanning, PDF/DOCX attachment scanning, risk scoring, and user-controlled masking. However, several significant weaknesses prevent full acceptance. The 76.67% detection coverage is concerning for a privacy/security tool, meaning roughly 1 in 4 sensitive items goes undetected — a gap that could give users a false sense of security. The detection engine is entirely rule-based (regex) with no ML or NLP component, limiting its ability to identify contextually sensitive information that doesn't match predefined patterns. The evaluation is extremely thin — no formal dataset description, no comparison against established tools like Microsoft Presidio or enterprise DLP systems, no precision/recall breakdown by entity type, and no statistical rigour. The literature review cites only a single reference, which is inadequate for establishing the novelty and positioning of the work. Additionally, there are no performance benchmarks (latency, memory usage), no user study to validate the consent workflow's usability, and the tool is limited to Chrome only. That said, the project demonstrates a viable proof-of-concept with a sound architectural philosophy, and with stronger evaluation, ML-augmented detection, cross-browser support, and proper benchmarking against baselines, this could become a meaningful contribution to AI safety tooling.

This project makes a practically useful contribution by implementing a browser‑native, local‑first “Consent‑Aware Privacy Firewall” that scans prompts and attachments for sensitive entities before they are sent to LLMs, giving users a risk score and masking options—directly addressing accidental disclosure risks common in everyday AI use, especially relevant in Global South contexts where WhatsApp‑style copy‑paste of medical/financial data into chatbots is rising.

The architecture (Chrome MV3 extension, local regex‑based detection, PDF/DOCX scanning, risk scoring, masking, dashboard) is clearly described, implemented, and demonstrated, with an overall reported detection coverage of ~77%, which is strong for a hackathon prototype, though evaluation appears limited in scope and relies on rule‑based detection with constrained contextual understanding.

The write‑up is concise and clear, with honest limitations (Chrome‑only, rule‑based patterns, small test set) and sensible future‑work directions such as LLM‑assisted context‑aware detection, multi‑platform support, and enterprise/regulatory integrations; the piece would be even stronger with more detail on the evaluation dataset and error analysis (false positives/negatives) to better substantiate the 76.67% coverage claim.