Section 1

What we collect

We collect the account information you provide directly, including your display name, email address, chosen authentication method, and the usage metadata needed to keep the app secure and quota-aware.

If you sign in with Google OAuth, we use the verified email address, your name, and your Google profile photo to create and maintain your account. We do not request broader Google Drive or Gmail scopes for this experience.

Section 2

Cookies, consent, and analytics

Essential cookies keep sign-in, route protection, and theme preference working. Non-essential analytics stays blocked until you explicitly accept it through the cookie banner.

Rejecting optional analytics leaves the core application usable. Consent preferences can be revisited through the cookie policy flow or by clearing the stored cookie.

Section 3

Operational monitoring and product telemetry

We use PostHog for product analytics after consent and Sentry for operational error tracking. Error tracking helps us investigate failures, while analytics helps us improve workflows and understand feature usage.

Sensitive document content, annotation text, and private file names should not be sent in analytics payloads. Error payloads must be minimized and handled under the security and backend rules of the project.

Section 4

Retention, export, deletion, and restore

Users can request an export of their account data from Settings. Account deletion enters a 7-day grace period before permanent removal, and users may restore access during that window.

Audit records may be retained in limited or anonymized form to preserve platform integrity, investigate abuse, and satisfy legal obligations where required.

Section 5

User rights and legal review

TODO: lawyer review. This section should describe lawful bases, regional rights under frameworks such as GDPR and CCPA, cross-border data transfer language, and formal complaint channels.

Placeholder contact for the Data Protection Officer: privacy@example.com.