Privacy Policy

Who we are

ZoomerDocs is operated by an individual, not a company.

This policy covers the ZoomerDocs website and its API. It explains what we collect, why, who else ever sees it, and how long we keep it. If anything here is unclear, write to us — the address is at the bottom of this page.

What we collect

Your account. Your email address, a bcrypt hash of your password (never the password itself), and whether you have verified your email. If you sign in with Google, we receive your Google account's email address and its account identifier — nothing else, and no access to your Drive, your contacts, or anything beyond the fact that Google vouched for that address.

Your documents. The files you upload, the text extracted from them, the numeric embeddings built from that text so search and chat can find the right passage, and whatever an operation produces — a translation, a summary, extracted fields. Your chat messages and the model's replies are stored so a conversation can be reopened.

Your usage. A record of every operation you run and every AI call it makes: which operation, which model, how many tokens, what it cost us, and the credits it spent. This is how the balance shown in your account is computed, and it is the only way we can tell what the service costs to run.

Technical data. Your IP address, used to rate-limit sign-in and registration attempts, and ordinary server logs. We run no third-party analytics, advertising or tracking scripts of any kind — the usage figures we have are the ones this application records about itself.

Why we process it

We process your documents for exactly one reason: to perform the operation you asked for. Nothing is sent to a model unless you start an operation or send a chat message.

We process your account and usage data to run the service — to sign you in, to meter credits, to protect the service from abuse and from automated account farming, and to meet legal obligations where we have them. Where the GDPR applies to you, our legal bases are performance of our contract with you and our legitimate interest in keeping the service secure and solvent.

How long we keep it

How long an upload, a finished operation and its result file are kept is set by this deployment, and the window that applies is stated in the app. When it passes, a scheduled job does the deleting, and it removes the file's bytes, its extracted text and its search index entries together. Where a deployment is configured to keep them indefinitely, they stay until you delete them yourself.

Your account, your chats and your credit ledger are kept until you ask us to delete the account. Expired sign-in tokens are purged on a rolling basis. Ledger entries may be kept after deletion in a form no longer linked to you, because they are our accounting records.

Who else sees it

AI models. To do the AI work — reading a scanned page, summarizing, translating, extracting fields, answering questions in chat — the relevant part of your document is sent to Google's Gemini API, which processes it to return the result. Some of the models this service uses run on our own servers instead, and content sent to those never leaves our infrastructure.

Email. Verification and password-reset messages go out through an email relay. It sees your address and the message itself, and nothing about your documents.

Hosting and error monitoring. Our servers and databases run at a hosting provider that stores the data on our behalf. Where error monitoring is enabled, crash reports go to a monitoring provider — configured to strip request bodies and cookies before anything is sent, so your document contents are not in them. We do not sell your data, and we share it with no one else.

What we never do

We do not train models on your documents, and we do not permit anyone else to. Your files are not a dataset.

Our support and admin tools show metadata only — filenames, sizes, whether a job succeeded, what it cost. They are built with no way to open a file's contents or read a chat. That is enforced in the code, not by a rule we ask staff to follow.

Cookies and local storage

We set one cookie: an httpOnly session cookie that keeps you signed in. It is strictly necessary — without it, every page reload would sign you out — and it is not used to track you anywhere. We use no advertising or analytics cookies.

Your browser also stores two preferences locally: your colour theme and whether the sidebar is collapsed. Neither ever leaves your device.

How it is protected

Traffic is served over HTTPS. Passwords are stored as bcrypt hashes. Sessions use a short-lived access token plus a rotating, single-use refresh token — if an old one is ever replayed, the whole session chain is revoked as a sign of compromise.

Every document, chat and job is scoped to the account that created it, and a request for someone else's is answered exactly as a request for something that does not exist. No system is perfectly secure, but these are how the service is built rather than things we intend to do.

Your choices and rights

You can delete any document from the Documents page and any run from History whenever you like. Deleting removes the stored bytes, the extracted text and the search index entries — not only the row you can see.

You can also ask us for a copy of the personal data we hold about you, ask us to correct it, ask us to delete your account entirely, or object to a particular kind of processing. Write to the address below. We act on deletion and data requests within 30 days, and we will ask you to confirm from the account's own email address first.

Where the GDPR or a similar law applies to you, you also have the right to complain to your local data protection authority.

Children

ZoomerDocs is not intended for children under 16, and we do not knowingly create accounts for them. If you believe a child has an account here, tell us and we will delete it.

Changes to this policy

If we change this policy in a way that matters — a new processor, a different retention window, a new category of data — the date at the top of this page changes, and where the change is significant we tell account holders by email. Continuing to use the service after a change means you accept the updated policy.

Contact us

This deployment has not published a contact address. Please use the contact details given on the site you reached this page from.