Privacy Policy

Last updated: March 24, 2026

1. Controller

The controller responsible for data processing on this website is:

For privacy-related requests, please use the contact details shown above.

2. Overview of Processing

We process personal data only to operate DocDocDoc, provide Google Docs editing functionality, protect data integrity, and handle support/security events. We do not sell personal data.

Important: most Google API requests are sent directly from your browser to Google during normal editor operation. Some limited flows, such as image delivery inside the editor and support/error handling, may pass through our server infrastructure.

3. Categories of Data We Process

• Account data: Google account identifiers (e.g., Google ID, email, name, profile picture URL, email verification status).
• Session/security data: encrypted OAuth session/token metadata in HTTP-only cookies and anti-CSRF/PKCE state cookies.
• App data: user settings, starred documents, document fingerprint hashes/signatures, terms acceptance metadata.
• Support and error data: support messages, technical error reports, context metadata (e.g., browser info, endpoint status, page URL).
• Usage analytics (optional): privacy-focused web analytics from Vercel, only after consent.
• Client-side storage: local/session storage for editor and UI preferences on your own device.

4. Purposes and Legal Bases (Art. 6 GDPR)

• Service operation and document sync (Google OAuth, Docs editing): Art. 6(1)(b) GDPR (contract/performance of requested service).
• Security, abuse prevention, reliability, and incident handling (error reports, logs, integrity controls): Art. 6(1)(f) GDPR (legitimate interests).
• Support processing (support requests you submit): Art. 6(1)(b) GDPR and/or Art. 6(1)(f) GDPR.
• Optional analytics (Vercel Web Analytics): Art. 6(1)(a) GDPR (consent).
• Device access/storage (cookies/local storage): Section 25 TDDDG; where required, only with consent; where strictly necessary, under the statutory exemption.

4A. Per-Processing Disclosures

A) Google OAuth session and authentication

• Data: OAuth session/token metadata, anti-CSRF/PKCE flow metadata, account email.
• Purpose: secure sign-in and authenticated API access.
• Legal basis: Art. 6(1)(b) GDPR; Section 25 TDDDG (strictly necessary storage/access).
• Recipients: Google, Vercel (hosting).
• Retention: state/PKCE cookies short-lived; OAuth session cookie up to 30 days unless deleted/revoked earlier.

B) Google Docs/Drive API processing for editor functionality

• Data: document/API payloads you trigger while loading, editing, and saving documents, and in limited cases image/media data needed to display existing document content in the editor.
• Purpose: loading, displaying, editing, and saving documents.
• Legal basis: Art. 6(1)(b) GDPR.
• Recipients: Google, Vercel (hosting).
• Retention: operationally processed; no permanent content database storage is intended as part of the normal editing flow. Certain transient server-side caches or request handling steps may temporarily process limited data where technically necessary.

C) User account profile and settings in Neon

• Data: Google ID/email/name/picture, role, terms acceptance metadata, user settings JSON.
• Purpose: account/session continuity, role-based features, settings persistence, legal-compliance records.
• Legal basis: Art. 6(1)(b) GDPR and Art. 6(1)(f) GDPR.
• Recipients: Neon (database processor), Vercel (hosting).
• Retention: while account remains active or until deletion request, unless legal obligations require longer.

D) Document fingerprints and starred documents in Neon

• Data: document IDs, hashed document fingerprint/signature metadata, and starred document metadata.
• Purpose: safe-load logic, known-document detection, and convenience features.
• Legal basis: Art. 6(1)(b) GDPR and Art. 6(1)(f) GDPR.
• Recipients: Neon, Vercel.
• Retention: while account is active or until deletion request.

We store hashed document fingerprints so that previously edited documents can be recognized across sessions and devices without storing full document content in our database for this purpose.

E) Support requests

• Data: subject/message, account email/role, optional document/tab/layout context and technical metadata.
• Purpose: handling support and feedback requests.
• Legal basis: Art. 6(1)(b) and/or Art. 6(1)(f) GDPR.
• Recipients: Neon, Vercel.
• Retention: as needed for support history and follow-up, then deletion when no longer necessary.

F) Error reports

• Data: technical error details (for example endpoint/method/status, document and tab metadata, page URL, user agent, contextual state, and limited request/response previews where relevant to the error).
• Purpose: reliability, debugging, abuse detection, incident response, and service hardening.
• Legal basis: Art. 6(1)(f) GDPR.
• Recipients: Neon, Vercel.
• Retention: retained for a reasonable debugging/security period and then deleted when no longer necessary, unless longer retention is required for abuse investigation or legal obligations.

G) Optional web analytics (Vercel)

• Data: aggregated visit/traffic metrics as provided by Vercel Web Analytics (for example: timestamp, URL/path patterns, referrer, coarse geolocation, OS/browser/device class).
• Purpose: product usage measurement and improvement.
• Legal basis: Art. 6(1)(a) GDPR (consent).
• Recipients: Vercel.
• Retention: according to Vercel Analytics retention/model and your consent status. Vercel describes visitor identification via short-lived request hashing and discarding of that visitor-session hash after 24 hours.

5. Google APIs and OAuth

We currently request Google OAuth scopes for:

• https://www.googleapis.com/auth/documents (load/edit/save document content)
• https://www.googleapis.com/auth/drive.file (per-file Drive actions such as safe-copy creation, picker-based file selection, and file-related operations needed by the editor)

Google API data is used only to provide editor functionality requested by you. We do not sell Google user data.

Access, Use, Storage, and Sharing of Google User Data

• Access: We access Google Docs/Drive API data only for documents/actions you explicitly initiate (open, edit, save, copy, picker selection, and related compatibility/sync features).
• Use: Data is used only to render/edit/sync documents and operate reliability/safety workflows.
• Storage: We do not intend to permanently store Google document content in our application database as part of normal editor operation.
• Sharing: We do not sell Google user data and do not share Google document content except with subprocessors required to operate the service, or where legally required.

Google API data is not used for advertising, resale, data brokerage, generalized profiling, or AI/model training.

DocDocDoc’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including Limited Use requirements.

6. Databases and Processors

Neon (Database)

We use Neon as our database provider to store account metadata, settings, terms-acceptance records, starred documents, document fingerprint hashes/signatures, support requests, and error reports.

Vercel (Hosting + optional Web Analytics)

We host DocDocDoc on Vercel. If analytics consent is granted, Vercel Web Analytics is enabled for aggregated traffic insights.

Google (OAuth and APIs)

Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland, and affiliated Google entities may process data required to provide OAuth and Google Workspace API services.

7. Cookies and Local Storage

Strictly necessary cookies

• docdocdoc.oauth.session.v1 (encrypted OAuth session cookie; HTTP-only)
• Short-lived OAuth security cookies for state/PKCE/return flow

These are required for secure sign-in and API access.

Consent cookie

• docdocdoc.cookieConsent.v1 (stores your analytics consent choice)

Optional analytics

Vercel Web Analytics is loaded only if you click "Accept" in the cookie banner.

According to Vercel Web Analytics documentation, analytics are designed as cookieless and privacy-focused (no third-party analytics cookies, request-hash based visitor counting, and no cross-site session reconstruction). We still disclose this processing transparently and only enable it after consent in this application.

If custom events are used in the future, we will avoid sending personal data (for example names, emails, invoice/order IDs, tokens) and redact sensitive URL/query segments where applicable.

Local and session storage on your device

We store editor/theme/preferences and selected UI state locally in your browser to provide the requested app behavior.

8. Recipients

Data may be shared with service providers/processors only as required to provide the service, including Vercel, Neon, and Google. We do not sell personal data.

9. International Transfers

Some providers may process data outside the EU/EEA. Where applicable, transfers are based on appropriate safeguards (e.g., adequacy decisions such as the EU-U.S. Data Privacy Framework and/or Standard Contractual Clauses).

10. Storage Periods

• OAuth state/PKCE cookies: short-lived (minutes).
• OAuth session cookie: up to 30 days unless deleted earlier (logout/revocation).
• Account metadata/settings/fingerprints/starred records: stored while your account is active or until deletion is requested, unless legal obligations require longer retention.
• Support requests: retained until the request is resolved and for a reasonable follow-up period thereafter, unless longer retention is legally required.
• Error reports: retained for a reasonable debugging/security period and deleted when no longer necessary, unless longer retention is required for abuse investigation or legal obligations.
• Local browser storage: remains on your device until you clear browser/site data or change settings in-app.

11. Data Subject Rights

Under the GDPR, you have rights to:

• access (Art. 15 GDPR),
• rectification (Art. 16 GDPR),
• erasure (Art. 17 GDPR),
• restriction of processing (Art. 18 GDPR),
• data portability (Art. 20 GDPR),
• object to processing based on Art. 6(1)(e)/(f) GDPR (Art. 21 GDPR),
• withdraw consent at any time for future processing (Art. 7(3) GDPR).

You also have the right to lodge a complaint with a supervisory authority.

12. Obligation to Provide Data

Providing Google account/API data is necessary if you want to use connected Google Docs editing. Without this data, connected editing features are unavailable.

13. Automated Decision-Making

We do not use automated decision-making (including profiling) within the meaning of Art. 22 GDPR.

14. Security

We use TLS/HTTPS for transmission security and apply technical/organizational measures appropriate to risk.

15. Data Protection Officer

No data protection officer has been appointed because there is currently no legal obligation to appoint one.

16. Changes to This Policy

We may update this policy to reflect legal, technical, or operational changes. The latest version is published on this page.

Vercel Web Analytics documentation: Privacy and Compliance and Web Analytics.

17. US State Privacy Addendum

This section applies to residents of US states with comprehensive privacy laws (including, where applicable, California). It supplements the rest of this policy.

Categories of personal information processed

In the preceding 12 months, we have processed categories described in this policy, including identifiers (such as email/account IDs), internet or electronic network activity information (such as interactions with our app), and customer-support/error-report information.

Business and commercial purposes

We process personal information to provide and maintain the service, authenticate users, synchronize Google Docs content requested by users, operate security and integrity controls, respond to support requests, and improve service quality.

Sensitive personal information

We do not use or disclose sensitive personal information to infer characteristics about users.

Sale, sharing, and targeted advertising

We do not sell personal information and do not share personal information for cross-context behavioral advertising.

Your privacy rights (where applicable)

• Right to know/access: request information about categories/sources/purposes/recipients and specific personal information, subject to legal limits.
• Right to deletion: request deletion of personal information, subject to legal exceptions.
• Right to correction: request correction of inaccurate personal information.
• Right to non-discrimination: you will not be discriminated against for exercising privacy rights.
• Right to data portability: request portable access to certain personal information.

How to submit a request

Submit requests using the contact details shown in the Controller section above. We may need to verify your identity before fulfilling a request. You may also designate an authorized agent where permitted by law.

Appeals

If we deny a request, you may contact us to appeal the decision where state law provides an appeal right.