Where your data goes

You are being asked to type in a cap table, a term sheet and a forecast — which, before a round closes, are about the most sensitive documents in the company. So the answer needs to be specific rather than reassuring.

The short version: the five tools that handle the worst of it run entirely in your browser and have no route to send your figures anywhere. Some tools look things up in public registers, which means an identifier — a company number, a domain — leaves. And two tools read a document you give them using an AI model, which genuinely does leave your machine. That last one is named at the top of the exceptions below rather than buried, because your lawyer would find it in thirty seconds and everything else here would die with it.

The line we draw

Leaves your browser

A public identifier you chose — the company number you picked off a list, or a domain. That is the whole input to a register lookup.
A term sheet or budget, if you use those two tools. Opt-in, per document, and named below.
Your answers, once, if you ask for a PDF. Also named below rather than glossed.

Never leaves it

Your cap table. Every shareholder, every percentage, every SAFE. The audit's arithmetic runs on your machine and has no route out.
Your readiness answers — the honest list of what is not tidy yet, which is the single most uncomfortable thing on this site to type into a stranger's form.
Who you are. No account, no email, no password, no name field. There is no key to hang a profile on, so there is no profile.

Five tools that never send anything at all

These are the ones handling the material you would least like to hand over. All of them — the questions, the maths, the flags, the report — are code running inside your tab. Producing the result on screen involves no request to us whatsoever.

LOCALCap-table auditYour shareholders, their percentages, the option pool, every SAFE you have signed.LOCALFundraising-readiness auditWhat you have not tidied up yet, written down in one place.LOCALSEIS / EIS eligibilityYour trade, your age, your gross assets, who holds what.LOCALFinancial model quality checkHow your forecast is actually built.LOCALData-room checklistThe list of documents you do and do not have.

Each of them has exactly one network call, and it is the same one: pressing Download PDF. A PDF has to be typeset somewhere and ours is typeset on the server, so that press sends your answers once. They are rendered and handed straight back in the same request — nothing is written to a database, nothing is logged, nothing is kept. If you would rather that never happened, the report on screen is complete without it; print the page instead.

The exception, named by us

Two tools read a document instead of asking you questions, and reading an arbitrary document is the one job we cannot do with rules alone. Both use Anthropic's Claude API.

What is sent, and by which tool

SAFE / term-sheet scanner — the document you upload or paste. That is a real term sheet, and we are not going to describe it as anything less.
DCF budget import — the budget table you paste, or the spreadsheet or PDF you hand it.

It goes to the API, not to a chatbot. Under Anthropic's commercial terms, what is sent through the API is not used to train their models. They hold it briefly for abuse monitoring and then it goes. We are pointing you at somebody else's policy here, which is the honest thing to do — read it yourself at anthropic.com/legal rather than take our summary of it.
We keep no copy. The document passes through the request and is gone when it returns. There is no upload folder and no database row holding your term sheet.
The model only reads — it does not judge. Its single job is to report what each clause says, with a supporting quote. Whether that clause is market-standard or unusual is decided afterwards by our own code, against our own benchmarks. So the opinion you are paying for is not an opinion the model formed about your deal.
It is opt-in, per document, and avoidable. Nothing reaches a model unless you hand a document to one of those two tools. Every other tool on the site works without it. And if you want the clause analysis but not the names, redact them first — the scanner is reading the terms, and does not care who signed.

Who else sees anything

The rest of the outbound list, in full. None of it is triggered by the five local tools.

Companies House

The company number you picked from the list

The Companies House health check, and the register cross-checks inside the readiness audit. The lookup is the check.

Foreign company registers · GLEIF

The company name and country you typed

The international company search only — it is a search of those registers, so the query has to reach them.

Stripe

Your card details, which go to Stripe and never to us

If you buy a paid report. No customer account is created to be retained.

Market-data sources

Nothing of yours

Treasury yields and public-market comparables are fetched on a schedule, for everybody, with nothing about you attached.

The valuation wizard saves a draft. Here is exactly what that means

It is long, and founders fill it in over days, so leaving would otherwise cost you the lot. The draft is held in your own browser's storage. If cross-device resume is switched on, a copy is also kept server-side — and it is worth knowing how, because the shape is the same one we use everywhere:

It is keyed to a random token, not to you. The token sits in a cookie your own JavaScript cannot read, and we store only its SHA-256 hash — the way a password is stored. There is no email address, no name and no account on the row.
It expires after thirty days and is removed by a scheduled job, not by anybody remembering to tidy up.
Clear the cookie and it is unreachable — by you and by us. We cannot look up your draft, because we have nothing to look it up by.

The other cookies are counters. Each tool has one — rs_company, rs_safe, and so on — holding two numbers: how many times this browser has used that one tool, and when the day started. No identifier, nothing to join up, and clearing them resets the count. They exist because some of these tools cost us money per run.

How to check all of that without asking us

A claim of this kind is worth what it can be tested against. Four tests, in increasing order of thoroughness. The first two need nothing from us.

1
Run the cap-table audit with the internet switched off.
Open the cap-table audit, let it load, then turn on airplane mode and enter a real cap table. Every finding, every dilution figure and every flag still appears, because that arithmetic is running on your machine. Something that computes with the network off is not sending anything anywhere, and the test takes a minute.
2
Watch the network tab.
Your own lawyer or CTO can open the browser developer tools and see every outbound request the page makes, live. Fill in the audit in front of them: no request carrying your figures appears, because there is no route for one. The first and only one is the PDF, if you ask for it.
3
Read the response headers.
curl -I https://vc-scan.com prints an enforced Content-Security-Policy. Its connect-src names this site and our own database — nothing else. Your browser is not permitted to contact any register, model provider or analytics host directly, even if our code tried. Your browser enforces that, not us.The honest limit of that test: it proves where your browser may go, not what our server does on your behalf. For that, the table above is the complete answer.
4
Ask us to put it in writing.
We will give a written confirmation of non-retention as an annex to an NDA, and we will walk your advisers through any check on this page on a call. If your counsel would rather the AI step never happened at all, say so — every tool except those two works without it.

The principle underneath

For the tools that matter most, we do not store your figures — not because we have undertaken not to, but because there is nowhere to put them. No account, no email field, no identifier: nothing to attach a history to. The useful consequence is that we never become a processor of your data at all, so there is no data-processing agreement to negotiate and nothing about our internal procedures you have to take on trust.

“We are not allowed to” is a promise. “There is nowhere to” is a fact — and one you can confirm in two minutes.

The one thing we will not pretend

If you use the term-sheet scanner, your term sheet leaves your machine. There is no version of a tool that reads an arbitrary document where it does not, and we are not going to dress that up, because your counsel would spot it immediately and then doubt everything else on this page.

What is true is narrower and more useful. It is one tool, not the site. It happens only when you hand it a document. Nothing is kept on our side. The judgement about your deal is made afterwards, by our code, from the clauses — not by the model. And the whole rest of the platform, including everything touching your cap table, works without ever going near it.

It is worth adding that the realistic alternative is rarely more private. The usual way to get a SAFE read is to email it to somebody, where it lands in a mailbox, a backup and an archive, and stays there for years.

Full disclosure

The things we collect that are not part of any tool. We mention them unprompted because the alternative is your advisers finding them after we said we collect nothing, and that costs more than the facts themselves are worth.

Cookieless traffic analytics — page, country, referrer. No cookie, no identifier, nothing joining one visit to the next. Form contents are not collected and, for the five local tools, could not be: they never reach a server.
Aggregate counters — a date, an action name and a number, so we know whether anyone is using the thing we just built. No company, no document, no visitor in them, and they cannot be turned back into any of those.
Ordinary server logs — our host keeps request logs, as every host does. We do not mine them and they age out on the host's own schedule, not ours.
Where it all runs — the website on Vercel, a small amount of state in a managed Postgres database, the document reading at Anthropic. Payments go to Stripe and card details never touch our servers.

The formal version, written for the UK GDPR transparency requirement, is the privacy notice. This page and that one describe the same system; if you ever find them disagreeing, tell us — that is a bug, and the sort we would want to hear about.

Run the cap-table audit Company checkLast updated September 2026