Local-first by default
Saved MVP records are stored in the user's browser, not silently uploaded to a PrivacyTrace account database.
Security
Built around user control.
PrivacyTrace should help users reduce exposure without creating a new data misuse problem. These are the current protections and the remaining production work.
Local Mode
Users can choose Local Mode to avoid AI requests for assistant, scam-check, and removal-writing workflows that support it.
Explicit actions
The app should only send data when the user presses a button that clearly performs a scan, AI draft, or request action.
Delete controls
Users can delete locally stored privacy data from the app, and browser storage can be cleared at any time.
No background browsing collection
The browser extension scans the current tab only when the user presses scan. It is not designed to silently collect browsing history.
Production gap
The account vault foundation is in place. Field-level encryption, audit logs, and broker API integrations still need to be added before this becomes a full production service.
Before full production launch
The next production milestone should add field-level encryption, user export, rate limits, audit logging, and clear consent screens for every broker or AI submission.