Your data

This page names every party on the path between the form and the mailbox. It names them, one by one, because a category is not a disclosure. If a page tells you a provider is involved without telling you which, it has told you nothing you can check.

The inbound path

PartyWhat it does
Cloudflare PagesHosts the site and runs the intake function
Cloudflare TurnstileBot check. Receives a challenge token and browser signals, never the text you send
MailgunCarries the message to the mailbox
Google WorkspaceDestination. Holds the delivered message, read by the one person who answers it

Which Mailgun region carries the message is not asserted here. The binding that names the endpoint is set in the deployment environment rather than in the source, so this page cannot check it, and a claim about where data goes is the last thing it should publish unchecked. The current answer is available on request, in writing.

What is stored

What reaches the mailbox is what you type: what you want to build, the address to reply to, and the optional line naming who pointed you here. All three travel in the same message, and the last of them exists so an introduction can be credited to whoever made it rather than to a tracker.

Nothing. There is no database, no object store and no log line behind the form. What you send exists in the mail API call that carries it, and in the mailbox that receives it, and nowhere else.

That is worth stating precisely, because it changes what the deletion question even means. Nothing is deleted from a store on the web path, because nothing was ever written to one. It is a property of how the intake function is built rather than a policy somebody has to remember to enforce, and the source is functions/api/intake.ts, the file holding the whole of the intake path. The repository is private, so that is a file to ask for rather than one to open: ask and you get it.

What happens to it after that

The path above is the web path, and it stops at the mailbox. What happens to your material once there is a conversation, and once there is an engagement, is answered by Term 6 — What You Send Us. The wording is repeated here rather than linked to, so this page is complete on its own.

Before there is a contract. What you send us before an engagement — what you write here, and what you say on the read-back call — is read by me, and by nobody else.

The cases the system is built against. A build runs on your own cases, because a decision that has never met a real one has not been shown to work. You pick them. They are used to build and to prove the system that decides them, and for nothing else: not to train a model that is sold on, and not in any other engagement.

During an engagement. The work is carried by a fleet of AI agents this company builds and operates. Your code, your data and the systems they run against are processed by that fleet. That is how the work gets done at this price, it is said here rather than discovered later, and it is written into the DPA rather than left to a page.

What is never delegated. What gets built, what gets refused, and who answers for it. A tool that writes code does not change who answers for it.

What we cannot promise yet. The retention periods are not set. They sit with an accountant and a contract reviewer, and until they come back this says so rather than publishing a period nobody has decided. The current position is available on request, in writing.

If your side needs signed paper before you send anything, say so in one line and we will sign your NDA or send you ours. You do not need one for the paragraph above to bind us.

Please do not paste anyone else's personal data here — customer lists, CVs, records. We do not want it and have no basis to hold it. Describe it instead. If it arrives anyway it is deleted and you are told.

Deletion

The automatic half is answered above: on the web path there is no stored copy, so there is nothing to schedule a deletion of.

The other half is the mailbox and whatever follows it, and it is not settled. The retention periods are not set. They sit with an accountant and a contract reviewer. Until they come back, this page says so rather than publishing a period nobody has decided — a stated hole is a disclosure, and an invented number is not. The current position is available on request, in writing, and the periods appear here when they exist.

Open since 24 August 2026.

Ask

Write to [email protected] and ask what is held about you, or ask for it to go. You get an answer in writing, and it names the same parties this page does.