We keep the action plan, not the original document.

Docgate is built for people who need a trustworthy document workflow, not a generic chat upload. The product does not keep the original uploaded file as reusable history, but it does keep the structured result needed for history and follow-up. If you sign in, Docgate also stores account data and may sync that structured result across devices.

Why Docgate exists

People should not need to drop sensitive official letters into a generic AI chat just to understand what they need to do next.

Original document

Uploaded files are used to produce the result and are not kept as part of your ongoing history.

What stays

Docgate keeps the structured result needed for follow-up: summary, action items, deadlines, glossary, and document metadata.

Account data

If you sign in, Docgate also stores your Google profile data and may sync structured results across devices.

Your controls

Settings now include export, synced-history deletion, local deletion, and account-deletion controls.

Why Docgate is allowed to process the data

Docgate processes document content and account data to provide the service you ask for: summaries, action plans, saved history, exports, and account sync.
Docgate processes some data for legitimate interests such as securing the service, preventing abuse, enforcing scan limits, and debugging product reliability issues.
Docgate processes subscription and invoicing data where necessary to perform the paid service and comply with legal obligations tied to billing and accounting.
Docgate does not use analytics or marketing cookies today, so consent for those activities is not currently part of the product flow.

What Docgate stores

In local mode, Docgate saves the structured result on this device: summary, explanation, action items, deadlines, glossary, sender, document type, selected country and language, and the date scanned.
Docgate also stores local preferences and a monthly scan-usage counter so the product can keep working without an account.
If you sign in, Docgate stores account data from Google sign-in, such as your name, email address, Google user ID, and profile picture.
If you sign in, Docgate may also sync the structured result needed for cross-device history, subscriptions, and usage tracking.

How long data is kept

Pending uploads stored for auth or upgrade handoff expire after about 15 minutes if they are not resumed.
Session cookies last for up to 90 days unless you sign out earlier.
Unauthenticated IP scan logs used for abuse prevention and free-limit enforcement are trimmed after 90 days.
Local structured results stay on this device until you delete them, clear browser storage, or your browser removes them.
Synced scan history stays with the account until you delete that history or delete the account.
Subscription and billing-related records may be retained longer where needed for fraud prevention, dispute handling, taxation, or accounting obligations.

What Docgate does not store

Docgate does not keep the original uploaded file as part of your reusable history after analysis.
Docgate does not use advertising cookies and does not sell personal data.
Docgate does not ask you to create a Docgate password. Sign-in is intended to stay social-login only.

Cookies and device storage

When you sign in, Docgate uses essential HTTP-only session cookies to keep your account secure.
Docgate also uses on-device browser storage so your scans, action plans, saved defaults, and dismissed notices remain available on this device.
Docgate does not use analytics or marketing cookies today. If that changes, consent should be requested before those cookies are set.

Your rights and controls

From Settings, signed-in users can download an account export, clear synced history, and request account deletion when there is no active paid subscription attached.
From the dashboard or Settings, users can delete local Docgate data from this browser and device at any time.
If your profile data comes from Google sign-in, the source of truth for your name, email address, and profile image remains your Google account.
You can also contact [email protected] to exercise rights that are not yet self-serve in the product.
You also have the right to complain to your local data protection authority if you believe your personal data has been handled unlawfully.

International transfers

Some service providers used by Docgate may process personal data outside the EEA or allow access from third countries.
Where that happens, appropriate transfer safeguards such as adequacy decisions or contractual safeguards should apply before production use.
The vendor register below is intended to show which services are involved and where final transfer details still need to be documented.

Deletion and control

You can permanently delete local Docgate data from the dashboard or Settings. That removes saved scan history, action plans, deadlines, preferences, pending uploads, and local usage data from this browser and device.
Deleting local data is meant to be a real delete, not a hidden archive.
Signed-in users can also clear synced history directly from Settings without deleting the account itself.
Deleting the account is intended to remove the Docgate-side account profile and synced history, but it does not automatically erase external billing records that payment providers may still need to retain.

Vendor register

Current services involved in account, AI, billing, and storage flows.

This register reflects the product paths visible in code today. Final production vendor details must be completed with live deployment information before launch.

Anthropic

Used for: Document understanding, follow-up Q&A, and reply drafting

Data involved: Uploaded text/images or extracted document content, plus structured document context needed for the answer.

Transfer note: Final production transfer mechanism should be documented against the deployed Anthropic setup before launch.

Google

Used for: Authentication and identity source

Data involved: Google account ID, name, email address, profile image, and authentication response data.

Transfer note: Final production transfer mechanism should be documented against the deployed Google authentication setup before launch.

Stripe

Used for: Checkout, subscriptions, and billing operations

Data involved: Customer, subscription, checkout, and billing metadata needed to run paid plans.

Transfer note: Final production transfer mechanism should be documented against the deployed Stripe setup before launch.

Hosting and database provider(s)

Used for: Application hosting, storage, and database infrastructure

Data involved: Account records, synced history, and server logs held by the deployed stack.

Transfer note: Publish the final vendor name(s), region(s), and transfer mechanism(s) for the live deployment before production launch.

Controller and contact

Controller: Docgate
Privacy email: [email protected]
Support email: [email protected]
Address: Berlin
Country: German