Privacy Policy

Draft — last updated: not yet published.

TODO: legal copy required before launch

The data inventory below reflects what the app currently stores, but the policy language still needs legal review and a published contact address.

1. Data we store

Account email, optional name/company/phone, subscription status and billing identifiers from our payment processor, activated browser records (an opaque device identifier, friendly name, first/last seen dates), and a log of listings processed (source, source listing ID, address, date, status).

TODO: Confirm this inventory matches the shipped extension's actual data collection.

2. What we do not store

We do not store card numbers — payments are handled by our payment processor. The extension's short-lived access credentials are held by your browser, and long-lived session tokens are stored only in hashed form on our servers.

TODO: Confirm final wording with counsel and with the extension's privacy disclosure in the Chrome Web Store listing.

3. Processors and sub-processors

Hosting, database/authentication, and payment processing are provided by third-party vendors.

TODO: List each vendor by name, location and purpose; add DPA references.

4. Retention and deletion

Placeholder: describe retention periods and how a user requests deletion of their account and usage history.

TODO: Define retention windows and the deletion request workflow.

5. Your rights

Placeholder: describe access, correction, portability and deletion rights and how to exercise them.

TODO: Add GDPR/CCPA specific language and a contact address.