Privacy Policy

DSNOOPDOC has two ways of handling documents, and what happens to your file depends on which one you use.

Anonymous tool use (merge, convert, sign, and the other free utilities without an account): your file is uploaded for the single job you asked for, processed, and removed once the job completes or the session ends. Office-format conversion and OCR run through ephemeral server-side workers for that one job — we do not keep a copy afterward.

Workspace accounts (when you create an account): documents you explicitly save, folders, published forms, and tracked-link activity are stored so the feature works — that is the point of a workspace. This data is isolated per tenant (organization) in our database and is not visible to other tenants.

Where a Google Drive option appears next to "choose from your computer," clicking it opens Google's own file picker and sign-in — we never see or store your Google password. We request read-only access limited to the single file you explicitly select in that picker (the drive.file OAuth scope), not your whole Drive. Once you pick a file, we download that one file and treat it exactly like a device upload from that point on, subject to the same handling described above; we do not browse, list, or access any other file in your Drive, and we do not retain the Google access token beyond that one import.

Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Document chat, summaries, and related AI features run on models we operate ourselves, not a third-party cloud AI provider. Document content used for these features is not sent to an external AI vendor and is not used to train any model, ours or anyone else's.

If you create an account, we store what is needed to run it: your name, email/username, tenant/organization association, and the workspace content described above. We do not sell this information.

Email + password accounts store a bcrypt hash of your password — never the password itself — and must verify the email address before first sign-in. We send one email with a time-limited verification link; the account can't sign in until you click it, and you can request a new link if it expires.

"Continue with Google" is a separate sign-in method from the Drive import above — it's used to create or sign in to your account, not to access files. When you use it, Google sends us your email address, name, and profile picture (only what its "Sign In" consent screen shares — not your password, and not Drive access). If that email already matches an existing password-based account, we link the two automatically since Google has already verified you own that address; you can then sign in either way.

Your signed-in session is kept in your browser's local storage, not a cookie. We use Google Analytics (which does set cookies) to understand aggregate traffic and usage patterns — not individual document contents — and it can be blocked without breaking any tool. Google's own sign-in flow (Google Sign-In and the Drive picker) sets cookies on Google's domain that we don't control. Full details: Cookie Policy.

We use standard infrastructure providers to host the application and database. We do not sell document content or account data to advertisers or data brokers.

You can delete saved documents and folders from your workspace at any time. To request deletion of your account and associated data, or to ask any question about this policy, email privacy@dsnoopdoc.com.

DSNOOPDOC is not directed at children under 13, and we do not knowingly collect data from them.

If this policy changes in a way that materially affects how we handle your data, we will update the date at the top of this page. Continued use of the service after a change means you accept the updated policy.