Security and privacy
Your file is read in your browser and sent to Claude, the AI service we use, only to check it. Final Eyes doesn’t save the file, its text or the suggestions.
What happens to your file
- Your browser reads the file. PDFs, Word documents and text are opened on your own device. Images are made smaller there before they’re sent.
- The text, or the image, is sent to be checked. A scanned PDF with no text in it is sent as pictures of its pages. It goes over an encrypted connection to our server, and from there to Anthropic, the company that makes the Claude AI models we use.
- The suggestions come back to your browser. You review them on your screen. Downloads, such as the amends list or a Word file with tracked changes, are made on your device. Checking a revised file against the amends happens on your device too, with nothing sent.
- Final Eyes keeps nothing. Our server doesn’t write your file, its text or the suggestions to a database, a log or a cache.
What we keep
- Counts, not content. For each check: when it ran, who ran it, the type of file, its size in characters and pages, how many suggestions it made, and how long it took. Also one-way fingerprints of the text each check read, which can’t be turned back into the text and stop one check being used for more than it paid for. We use these for plan limits and to keep the service running.
- Your account. Your name, email address and team, through Clerk, our sign-in provider.
- Your house style. If your team adds house style rules (for example, write “Wi-Fi”, not “wifi”), we keep that list so every check can follow it. It’s words your team chose, not file contents, and admins can change or clear it at any time.
- Brand guidelines. If you import a house style from a brand guide, its text is sent to Claude once to find the rules, the same way as a file you check. We don’t keep the guide or its text: only the rules you choose to save.
- Brand colours. The colour check runs on your device: pages and pictures are drawn in your browser and compared with the palette there. Nothing about it is sent anywhere. The palette is saved with the house style.
- Ideas. If you suggest a feature on the Ideas page, we keep what you wrote, who wrote it and who voted, so we can show the board and reply. Others see the idea once we’ve read it, but never who suggested it.
- Cancelling. If you cancel, the reason you chose from the list and what happened next. No free text.
- Billing. Paddle, our payment provider, holds your card details and invoices. We never see your card number.
- The free proof. To allow one free proof per visitor, we keep a random ID in a cookie and a scrambled (hashed) form of your internet address. The scrambled form can’t be turned back into the address, and only the last 30 days are used.
Who processes data for us
| Company | What for | What it handles |
|---|---|---|
| Anthropic | Checking the text | The text or images being checked. Anthropic doesn’t use it to train its models, and deletes it within 30 days (longer only if its safety systems flag it). |
| Vercel | Hosting the website and server | Requests passing through, including the text being checked, in memory only |
| Neon | Our database, in London | Counts, team names and plan details. No file contents. |
| Clerk | Sign-in and teams | Names, email addresses and team membership |
| Paddle | Payments, tax and invoices | Billing details |
| Sentry | Error reports | Where in our code something went wrong, the page, and ids. Messages are scrubbed. No file contents. |
| Upstash | Rate limits | Counts of requests per person and per team, kept for a minute or two. No file contents. |
Good to know
- Your words stay yours. Final Eyes never uses your files to train anything.
- Confidential work. Because Final Eyes stores nothing, it suits unreleased campaigns and client work. If your organisation has rules about AI services, check them first.
- Questions. For a data processing agreement or a security questionnaire, contact us through the Help page.