Privacy policy
Last updated 17 November 2026.
VerbatimCV does not store the CVs it parses. A CV sent to the API is processed in memory, the result is returned in the response, and neither is kept or logged by us. We keep only what an account needs: your email address, your API key in hashed form, your plan and how many parses you made each day.
Who we are
VerbatimCV is run by Thomas Waye, a sole trader based in Scotland ("we"), who is the controller of the account data described below. Contact us about privacy at privacy@verbatimcv.com.
Two roles
- CVs you send to the API. You decide which CVs to parse and why, so you are the controller of the personal data in them and we are your processor. Our data processing agreement covers this. If you are a job candidate whose CV was parsed by one of our customers, contact that organisation: we hold no copy of your CV.
- Your account. For the data needed to run your account (below), we are the controller and this policy explains what we do with it.
CVs and parse results
- Files and links sent to
POST /v1/parseare read in memory on our API server (Fly.io, Paris) and are not written to disk, stored in a database or logged. - The CV's text is sent to Anthropic's API to extract the fields. When a page's text can't be read reliably, an image of that page is sent too; it may show the candidate's photo, which is never extracted or returned. OCR of scanned pages runs on our own server. Anthropic does not use API data to train its models and deletes API inputs and outputs within 30 days, except where its systems flag content for a usage-policy review or the law requires longer retention.
- We never extract date of birth, age, gender, photos, marital status or nationality. The result only records whether such details were present.
- Our logs record request IDs, API key and account IDs, timings, token counts and error codes: never CV content, links, results or email addresses.
Account data we keep
| Data | Why | Kept for |
|---|---|---|
| Email address | To identify your account and send sign-in links | Until you delete your account |
| API keys, stored only as a SHA-256 hash plus the first 12 characters | To authenticate requests and show you which key is active | Until you delete your account |
| Plan and daily parse counts | To apply your quota and show your usage | Until you delete your account |
| Sign-in link records (email, a hash of the link, times) | To make each link work once and limit how many are sent | Removed automatically, normally within a day of expiry |
| Sign-in emails, at our email provider | To deliver the link | 30 days (Resend's retention) |
| IP addresses of signup requests, in memory only | To limit how many sign-in links one address can request | About one minute; never written to storage |
| Server logs (no CV content, no email addresses) | To run, secure and debug the service | 7 days (Fly.io's retention) |
Our legal bases under UK GDPR are performing our contract with you (Article 6(1)(b)) for account data, and our legitimate interest in keeping the service secure and free of abuse (Article 6(1)(f)) for logs and sign-in limits.
Cookies
The account page at api.verbatimcv.com/account sets one strictly necessary cookie,
vcv_session, to keep you signed in for up to 7 days. The documentation site sets no
cookies and uses no analytics or advertising trackers.
Who processes data for us
Our sub-processor list names each provider, what it does and where. Anthropic and Resend are in the United States. Transfers to them are covered by safeguards recognised under UK law, such as the UK International Data Transfer Addendum to the EU Standard Contractual Clauses in their data processing terms, or the UK Extension to the EU–US Data Privacy Framework where the provider is certified. We do not sell personal data or share it for advertising.
Your rights
You can ask us for a copy of your data, to correct it, to delete it (which deletes your account and keys), to restrict or object to its use, or to receive it in a portable format. Email privacy@verbatimcv.com from the address on the account; we reply within one month. You can also complain to the Information Commissioner's Office at ico.org.uk.
Security
All traffic uses HTTPS. API keys and sign-in links are stored only as hashes. The account database is reachable only by our API server, and CVs are never written to storage.
Changes
We will post changes here and update the date above. If a change affects how we handle CVs or account data in a material way, we will email account holders before it takes effect.