What we collect, and what we do not.

What we collect

• Waitlist email addresses, when you type one into a form and tick the consent box. Nothing is collected from the form until you do both.
• A salted, hashed caller fingerprint derived from your IP address and browser or client user agent. It is a one-way hash. We cannot turn it back into an IP address and we do not try to.
• Quote request payloads: the task type, tier, deadline, jurisdiction and maximum bid you asked us to price, the price we returned, and whether you told us the price would clear.
• API keys, stored as hashes, with the caller fingerprint that requested them.
• Orders, when a task is bought in a market marked live: the task as it was sent, including any text, links, or image or document uploaded as evidence, the price, the answer, and the payment reference. A named responder reads the task in order to answer it. Do not put personal data about other people in a task unless the task needs it.

Payment is taken by a payment processor, Stripe for cards, and we never see or hold a card number. We keep the processor's reference for the payment and, where the payment network shows one, the paying account's address, so that a refund can be sent back to where the money came from.

Why

Three reasons, and no others.

• To email you once, when the thing you asked to hear about happens.
• To count distinct callers honestly. This is the whole point of the exercise: an anonymous counter gives traffic numbers and no answer, and a counter that cannot tell one caller from a thousand is not evidence of anything.
• To decide which markets open first. Which prices were asked for, and which of them would actually clear.

What we do not collect

• Raw IP addresses. They are hashed on the way in and never written down in clear.
• Names, employers, job titles, or anything else you have not typed into a form.
• Analytics, advertising or session-replay third parties. There are none on this site. Every typeface, script and image is served from this domain, so loading these pages makes no request to anyone else at all.
• Cookies. The site sets none for visitors or buyers. The one cookie it sets keeps the operator signed in to the operator's own page.

We do not sell any of it, to anyone, for any price. That is not a promise we would be able to keep quietly if we broke it: an exchange whose product is accountability does not get to be careless with the record.

How long we keep it

Email addresses are kept until the launch they were collected for, and deleted if the venture does not proceed, exactly as the form says. Ask us to delete yours before then and we will, without asking why.

Orders, their answers and their payment references are kept as the record of what was bought and who answered it. Ask us to delete the contents of a task you sent and we will.

Fingerprints and quote payloads are kept for the life of the measurement and its analysis. They are not linked to an email address unless you gave us both, and the fingerprint cannot be reversed.

Your rights, and who to ask

Under UK and EU data protection law you can ask what we hold about you, ask for it to be corrected, ask for it to be deleted, and object to us holding it. The lawful basis for the waitlist is your consent, which you can withdraw at any time. The lawful basis for the hashed caller counts is legitimate interest in knowing whether the product has demand, balanced by the fact that the data is pseudonymous and never leaves us.

Write to [email protected]. One person reads it, and they reply.