Email us

Security and privacy

What happens to your documents.

Written for the person who approves the tool, and for the pharmaceutical client they forward it to.

Last reviewed 22 November 2026.

Where your text goes Word sends to your SourceAnchor server in London over HTTPS. The server sends the sentence and passages to a checking model on AWS Bedrock in the UK or the EEA; your papers' text to an indexing model on AWS Bedrock in London; and only DOIs and PubMed IDs to Crossref and PubMed. Word your draft Your server AWS, London HTTPS Checking model AWS Bedrock, UK or EEA the sentence and passages Indexing model AWS Bedrock, London your papers' text Crossref, PubMed citation details, retractions DOIs and PubMed IDs only

Where it runs

Each client has its own server on Amazon Web Services in London: its own virtual machine, encrypted disk, backups and secrets. Clients share AWS's network, but not a machine.

What leaves your server

  • Checking. To check a sentence, your server sends that sentence, the claims it is split into, and passages from your papers to Anthropic's Claude Haiku 4.5 on AWS Bedrock. Requests are sent from London, and AWS may serve them in any Region of its European profile, so checking happens in the UK or the EEA. The whole document is never sent.
  • Indexing. To make your papers searchable, their text is sent in pieces to Amazon's Titan embedding model on AWS Bedrock in London.
  • Citation details and retractions. To fill in citation details, and to check every day for retractions and corrections, your server sends a paper's DOI or PubMed ID to Crossref and to PubMed at the US National Library of Medicine. Never text from your documents. These lookups can be switched off for your server; that also stops the retraction checks.

A hosted server refuses to start with any model provider other than AWS Bedrock, or with a Bedrock Region outside Europe. It reaches Bedrock through its own AWS role, with no AWS keys stored on it. The ABPI wording rules run on your server, and the paragraph they read is not sent to any model. The product sends no email and uses no analytics or error-reporting service.

What is stored

Your papers and their text, the sentences checked, the verdicts and the passages they rest on, your decisions, and the audit log, on your server's encrypted disk. Application logs carry identifiers only: no claim text, passages, file names or email addresses.

Keeping and deleting

  • Each night the database is backed up to your server's storage in London and kept for 35 days; the last 14 nightly snapshots of the disk are kept.
  • You can ask us to remove a paper, or a Word document's records, together with the verdicts and quoted passages in your project that rest on it. Backups are never rewritten, so a copy can remain in them for up to about 44 days, and we tell you the date by which it will be gone.
  • At the end of a service we export your data for you, then delete your server, its backups, its snapshots and its secrets, and record a signed deletion record. What remains holds no document content: sealed hashes of the audit log, and AWS's record of actions in our account, kept 13 months.

Who can see it

  • Accounts are created by us on request; there is no open sign-up. A new account sets its own password before anything else. A sign-in ends after an hour without activity and never lasts more than twelve hours.
  • A user sees only the projects they hold a seat in. Through the product, we can read a project's verdicts only under a support pass issued by the project's owner, for 4, 24, 72 or 168 hours. Every read under it is logged and listed for you, and anyone on the project can end it at once.
  • Operational access to the server can read stored data. It is restricted to named people, every session is recorded in full, and every action in our AWS account is logged. Session recordings are hidden after 90 days and deleted about 90 days later.

How it is protected

HTTPS only, with HSTS; no other ports open, and no SSH. Passwords are hashed with bcrypt. Each audit entry is chained to the last with a keyed hash, and a check is refused if its audit entry cannot be written. Uploaded files are treated as untrusted and read in a separate process with limits on pages, size and time. Every code change is scanned for secrets and known-vulnerable dependencies, and a fixable critical or high finding fails the build.

Not yet

Two-factor sign-in, single sign-on, encryption with a key you control, and an external penetration test. We will say here when each exists.

Not for identifiable patient data or patient-specific recommendations. SourceAnchor is a document-checking tool for professionals who keep publication responsibility.