Privacy notice
What happens to what you type into the early-access form
Version 2026-08-08 · in effect from 8 August 2026
This notice covers one thing: the early-access request form on the landing page. It is the only place on this site that collects anything. The version above is recorded with every request, so it is always possible to say which wording someone actually agreed to.
Nothing is being collected today
The early-access list has not opened. The form is not rendered on the landing page, the server refuses submissions, and no request can be recorded — including by anyone who tries to reach the endpoint directly. What follows describes what will happen when it does open.
What the form collects
Everything in this list comes from the form itself — there is no hidden field beyond the three described at the end of it, and nothing is gathered from anywhere else.
- Email addressrequired
- the only way to reply to the request, and the identifier that keeps a repeat submission from becoming a second record
- First namerequired
- so a reply can address you rather than your inbox
- Companyoptional
- context for the request
- Roleoptional
- who is in the room when an export decision is made — chosen from 6 options
- Product categoryrequired
- whether the pilot can say anything useful about your product — chosen from 18 options
- The export decision you are trying to makerequired
- free text, up to 600 characters, used to understand what the product is being asked for
- When you agreed to this notice, and which version of itrequired
- so it is possible to say what you actually agreed to
- Whether you separately opted in to product updatesoptional
- recorded only if you tick it; it is a separate box and never a condition of joining
- The page you submitted from, the referring website's hostname, and campaign tags if the link carried themoptional
- to tell where interest is coming from
What is deliberately not collected
These are design decisions, not omissions, and each one is enforced in the code rather than promised in prose.
- No IP address — not stored whole, not stored truncated, not stored hashed. The waitlist table has no column for one.
- No cookie is set by this site, and no analytics, advertising or bot-detection script runs on it.
- No device or browser fingerprint.
- No telephone number, revenue figure, headcount, or any special-category data.
- The referring page's path is discarded; only its hostname is kept.
To stop one script filling the database, the server counts recent submissions in memory for 10 minutes, keyed by a value derived from the network address and a random secret that changes every time the server restarts. It cannot be turned back into an address, cannot be matched against one, and is never written to the database or a log — nothing about it is stored.
Why it is handled, and on what basis
Purpose. To decide who is invited into a limited pilot, in what order, and to reply to the request. It is not used to profile anyone, is not combined with data from anywhere else, is not sold, and is not shared with anyone beyond the two providers named below.
Basis: your consent. You are asked for it in a ticked box that is not pre-ticked, it is recorded with the moment you gave it and the version of this notice you were shown, and you can withdraw it at any time.
Agreeing to have your request handled is separate from agreeing to product updates. The second box is optional, unticked, and joining the list never depends on it.
How long it is kept
24 months from the date of the request — long enough to run a pilot and invite people from the queue in order, short enough that a request nobody acted on does not sit in a database indefinitely. That is a decision, not a legal requirement, and it is stated as one. Erasure happens sooner if you ask for it — there is no waiting period.
A request moves through a small number of states, and never more than one at a time: waiting, invited, activated, declined, withdrawn. Every request starts at waiting.
Who else is involved
- Supabase — hosts the database the request is stored in.
- Vercel — hosts and serves this website, and handles the request in transit.
Nobody else receives it. Where the database physically sits, and therefore whether the data leaves the European Economic Area, is listed below as still to be established — because the answer depends on a choice that has not been made yet, and guessing at it here would be worse than saying so.
What you can ask for
- See it
- ask for a copy of what is held about you
- Correct it
- ask for anything inaccurate to be changed
- Delete it
- ask for the record to be removed; it will be
- Withdraw consent
- at any time, without giving a reason
- Object or restrict
- ask that it stop being used while a question about it is resolved
- Take it with you
- ask for it in a machine-readable form
There is no address to write to yet. A privacy notice that cannot tell you where to send an erasure request is not finished — so rather than print a mailbox that does not exist, this notice prints none, and the form stays closed until one does. Nothing has been collected in the meantime.
What this notice cannot yet tell you
These are stated openly rather than filled in with plausible text. Each one names the single thing that would settle it, and while any of them is open the form collects nothing.
- Who the data controller is
- the legal name and registered address of the entity that will hold these requests. Not stated here because inventing it would misinform a reader who has no way to check.
- The contact address for access and erasure requests
- a mailbox that exists and is read, set as WAITLIST_PRIVACY_CONTACT. Until it is set, this notice publishes no address and the form collects nothing.
- Where the database physically sits
- the Supabase project's region, which is chosen when the project is created. Stated here once it is known, because it determines whether data leaves the EEA.