Privacy policy

— is the data controller for the information described here. Questions go to our contact address.

A document you upload is sent to our parsing model, and the original file and the parsed result are stored so you can retrieve the run later. They are deleted automatically once the retention period for your plan has passed:

We do not use your documents to train models, and we do not share them with anyone outside the processing described here.

For every request we store the endpoint called, whether it succeeded, the HTTP status, the number of pages, the file size in bytes, how long it took, a request id and an error code if there was one. This is what fills the usage charts in your console and what lets us answer a support question about a specific run.

We do not store the extracted text in this record, only the counts. The text lives in the result file covered by clause 2.

If you create an account we store your email address, a hash of your password (never the password itself), whether the address has been verified, and your subscription and payment history. If you sign in with Google we receive your email address and name from Google and store the same fields.

API keys are stored as hashes with a short display prefix. We cannot show you a key again after it is created.

The free allowance has to be countable, or it would be trivially abusable. Two things make that possible:

• a cookie named ds_aid, set for one year, containing a random identifier and nothing else. It is HTTP-only, so page scripts cannot read it;
• a salted hash of your IP address, used to count the allowance across a network. The hash cannot be reversed to recover the address.

Neither is used for advertising or shared with anyone. There are no third-party analytics or tracking scripts on this site.

Separately from the hash above, we record the IP address each request came from, in full, against that request. This applies to everyone: signed out, signed in, and API calls.

We keep it for one reason, which is to investigate abuse of the service: automated scraping of the free tier, attempts to break in, and traffic we are asked about by a provider or a court. It is available only to our administrators, it is never used to build a profile of you, never used for advertising, and never sold or shared with anyone except where we are legally required to produce it.

Each address is deleted automatically 30 days after the request that carried it. The record of the request itself remains, because it is also our billing record, but the address is erased from it. Under the GDPR our basis for this is legitimate interest, namely keeping the service available and secure for everyone using it.

• ds_aid: the anonymous allowance identifier above. One year.
• ds_session: your sign-in session. Deleted when you sign out.

Both are strictly necessary to operate the service. We set no advertising or analytics cookies.

Payments are handled by Razorpay, which receives the information it needs to take a payment and issues its own privacy terms. We never see or store your full card number. Email is delivered through our SMTP provider. Everything else runs on infrastructure we operate: parsing, storage and the database.

If we add a payment provider or change one, the checkout page names the provider handling your payment before you enter any detail.

Passwords are hashed, API keys are hashed with a server-side pepper, payment provider credentials are encrypted at rest, and the IP hash used for the free allowance is salted. The addresses covered by clause 6 are stored as given, reachable only by an administrator, and erased on the schedule stated there. Session cookies are HTTP-only and, in production, restricted to HTTPS.

You can see your usage and export it as CSV from the console at any time. You can delete your account from the settings page, which removes your personal data, erases the IP addresses recorded against your requests, and revokes your keys.

Tax invoices survive account deletion because Indian tax law requires us to retain them; they keep the billing email and the amounts, and are no longer linked to a user record. To ask for a copy of your data or to raise a concern, contact us.

If this policy changes materially we will email account holders before it takes effect. The date at the top of the page always reflects the current version.