Document Controlversioned · indexed · searchable

Privacy and security

Where your documents go, and who can see them

Plain answers about storage, encryption, AI processing, backups and deletion. Where we do not do something yet, we say so.

Operator: Advanced Research Systems · Effective 27 October 2026 · Applies to the private beta

  • Every connection to Document Control uses HTTPS (TLS). Passwords and documents never travel unencrypted.
  • Your files live on our own server in a Hostinger data centre in Germany, not on a shared consumer cloud drive.
  • Each organisation's documents are walled off from every other organisation, enforced inside the database.
  • To write summaries and answers, the relevant text goes to Anthropic's Claude API. Anthropic does not train its models on it and deletes it within 30 days.
  • Scanning, OCR and PDF conversion run on our own server. No other AI or document service sees your files.
  • No advertising, no analytics trackers, no selling or sharing of your data. One login cookie, nothing else.
  • Every upload is virus-scanned on our own server (ClamAV) before it is stored. Infected files are refused.
  • Files are not yet encrypted separately at rest inside the database. Details below.

Where your documents are stored

Document Control runs on a virtual private server we rent from Hostinger, in their data centre in Germany. Your original files, every older version, the extracted text and the AI summaries are stored in a PostgreSQL database on that server. The server is used only for our own services; it is not shared hosting.

OCR for scans and photos, and conversion of Word and PowerPoint files to PDF, run in a separate container on the same server (Stirling PDF). Your files are not sent to any outside OCR or conversion service.

Encryption

In transit

All pages, uploads, downloads and answers travel over HTTPS (TLS). The login cookie is marked Secure, so browsers never send it over an unencrypted connection. Calls from our server to Anthropic and Google are also made over HTTPS.

At rest

Passwords are never stored: we keep only a bcrypt hash, which cannot be turned back into the password. Login sessions are stored only as SHA-256 hashes of the session token.

Your documents are stored in the database as they were uploaded. They are not yet encrypted separately inside the database, so the server's own access controls are what protect them at rest. This is one of the reasons we ask beta testers not to upload confidential, financial or personal documents. Per-organisation encryption at rest is on our roadmap before paid plans launch.

Who can see your documents

What is sent to AI services

Document Control uses Anthropic's Claude API, and only that AI service.

Under Anthropic's commercial terms, they do not use these inputs or outputs to train their models, and they delete them within 30 days. They may keep content longer only if their automated safety systems flag it as a Usage Policy violation, or if the law requires it. See Anthropic: is my data used for training? and Anthropic: how long is data stored?

The Research assistant (Premium)

Research is a Premium feature and is not part of the free beta. When it runs, it sends search queries, never your documents, to the Brave Search API, then writes a text report with links to its sources. It does not download files from the web into your library: what it files is the report it wrote, as a text document. You can withdraw or delete that report like any other document.

Malware and file safety

Every upload is virus-scanned before it is stored.

Each upload is checked by ClamAV, an open-source antivirus engine running in its own container on our server, before anything is saved. Its virus definitions update automatically several times a day. An infected file is refused and nothing is stored. If the scanner is unavailable, uploads are refused until it is back, rather than accepted unscanned. Files never leave our server to be scanned.

No scanner catches everything, so the other protections stay in place. Files are only ever downloaded by people in the organisation that uploaded them. Each upload is fingerprinted (SHA-256). Documents are shown in a built-in PDF viewer that does not run scripts embedded in files. OCR and conversion run in an isolated container. Treat downloads as you would any file from a colleague.

Backups

Backups exist so a server failure does not lose your library. They are not used for anything else.

Accounts, logins and cookies

Other services we use

ServiceWhat it doesWhat it receives
Hostinger (Germany)Hosts the serverEverything stored on the server
Anthropic Claude APISummaries and answersDocument text and questions, as described above
Google DriveNightly off-site backupEncrypted backup copies of files and the register, which Google cannot read
GmailWelcome emails to approved testersYour name, email, organisation name and temporary password
TelegramNotifies us of new beta applicationsWhat you wrote on the application form
Brave Search APIWeb search for Research (Premium only)Search queries only

We do not sell, rent or share your data with anyone else, and we do not use it for advertising. When paid plans launch, payments will be handled by a payment processor; we will never see or store your card number.

Deleting your data

Your rights

You can ask us at any time for a copy of your data, to correct it, or to delete it. You can also download any of your files yourself, at any time. Because our server is in the European Union, we aim to meet the GDPR's standards for everyone, wherever you live. We will answer requests within 30 days.

Document Control is not intended for children under 16.

Changes and contact

If we change how your data is handled, we will update this page and its effective date, and email active users about significant changes before they take effect.

Questions, requests or security reports: greentrust@gmail.com (Advanced Research Systems).