Privacy statement

1 Who is responsible

The operator of DocsOrigin decides what is collected here and why, and is the contact for anything in this document: support@docsorigin.com. This statement describes the real behaviour of this system. Where it says something is not collected, that means there is no code that collects it.

2 What is stored when you open an account

Your email address, your name as you typed it, a one-way hash of your password (⛔ never the password itself), your interface language, the country you selected for your business, and the moment the account was created. Sessions are kept as a token in a cookie so that you stay signed in.

3 What is stored when you use the product

The business records you create: your business profile and tax identifier, your clients and their billing details, your catalogue items, your documents and their lines, payments, recurring schedules and any logo you upload. This is your commercial data. It is stored so the product can show it back to you, and it is scoped to your business on every single query.

Every action on a tax document is written to an audit log with the user, the action and the time. That log exists because a document trail without one is not a trail, and it cannot be switched off.

4 What is stored when you just visit these public pages

No account is needed and none is created. Cookies are set only for things you did: your chosen interface language, your chosen display country, a short-lived message cookie after an action, and an anonymous token used to protect forms against cross-site posting. There is no advertising cookie, no analytics pixel, no fingerprinting and no third-party tag on these pages.

The web server keeps ordinary request logs, which include an IP address, for a short period, for security and abuse investigation. Fonts are requested from a font host, which means that host sees the request; nothing else on this page comes from anywhere but this domain.

5 What is stored when you send an enquiry

What you typed into the form: name, email, and whichever of phone, business name, country, budget and message you filled in, plus the service you asked about, your interface language and the campaign or referring page that brought you. This exists to answer you.

For rate limiting, a keyed hash of your IP address is stored instead of the address itself, so that repeated automated submissions can be blocked without keeping a list of who visited. The hash cannot be reversed into an address.

6 Why we are allowed to hold it

Account and product data is processed to give you the service you asked for — a contract you entered by opening the account. Enquiry data is processed to respond to a request you made. Security logs and rate-limit hashes are processed for the legitimate interest of keeping the service usable and not overrun. There is no processing for advertising, profiling or automated decision-making.

7 Who else sees it

Nobody buys it, because it is not for sale. The parties that necessarily touch it are the hosting provider that runs the server and stores the database, the mail provider used to send an email you asked for, and the font host described above. That is the complete list.

Access by us is limited to what is needed to operate the service or to answer a support request you raised. Your documents are not read for any other purpose, and they are never used to train anything.

8 How long it is kept

Account and business data is kept while the account exists, and deleted on request. Issued tax documents are the exception: they are immutable by design, and where the law of your country sets a record-keeping period they are retained for it — deleting a tax document on request would break both the law and the hash chain that makes the rest of your documents provable.

Enquiry data is kept while it is being answered and for a reasonable follow-up period afterwards, then deleted. Rate-limit hashes are deleted automatically after 24 hours. Server request logs are kept for a short period only.

9 Your rights

You can ask for a copy of what is held about you, ask for it to be corrected, ask for it to be deleted, ask us to restrict what we do with it, or object to processing. Much of this you can simply do yourself: export is built in and free, and most fields are editable in your settings.

Write to support@docsorigin.com. Depending on where you live you may also have a right to complain to a supervisory authority, and you are entitled to do that without going through us first.

10 How it is protected

Passwords are stored as a modern one-way hash. Every database query is parameterised, so a value can never become part of a statement. Every query touching business data is scoped to a single business, so there is no path from one account to another's records. Every state change requires a POST carrying a token derived from your session and a server secret. Exported CSV is escaped against spreadsheet formula injection.

What is not claimed: this service has no ISO 27001 certificate, no SOC 2 report and no third-party penetration test. Those are real things with real evidence, and claiming them without the evidence would be exactly the sort of statement this page exists to avoid.

11 Your documents are never indexed

The application and every shared-document link are excluded in robots.txt, carry noindex headers, and never appear in the sitemap. A client's tax document turning up in a search engine is a data leak, not traffic, so it is blocked in two independent ways rather than one.