Privacy Policy

What the waitlist form collected

While it was open, the waitlist form asked you for four things, and stored exactly those four. These are the details we still hold for everyone who joined:

• Your email address — so we can tell you when Corpus opens.
• Your name (the parent or guardian filling in the form) — so we can address you properly rather than sending anonymous mail.
• How many players you would sign up — a number, nothing more. It told us how many places to hold. It is not linked to any child, and it does not identify anyone.
• The sport (soccer by default) — so we tell you about the right library.

We also record when you ticked the consent box and which version of this policy you agreed to, so that we can always show what you were told at the time.

That is the complete list. The waitlist form never collected a date of birth, a phone number, an address, a school, a photograph, a video, or any payment details.

We collect no information about children

The waitlist holds nothing about any child. Not a name, not an age, not a date of birth, not an initial, not a school, not a photo. We used to ask for a child’s first name and age; we decided we did not need them, so we removed those questions from the form and deleted the columns from the database entirely. There is nowhere for that information to be stored even by accident.

The only children-related thing we know is a number — how many places to hold for you. A number describes no one and cannot be traced back to a child.

This is why the waitlist asks you to agree to a short, simple policy rather than putting you through a consent process about your child’s data: there is no child’s data here to consent to.

What changes when Corpus launches

We want to be straight with you about this rather than let you find out later.

• Right now, Corpus collects no information about anyone at all — the waitlist is closed and there is no form on this site. What we still hold from the list is only your name, your email, how many children you would have signed up, and the sport.
• When Corpus actually launches, using it will involve information relating to a child— for example your child’s name and the movement and video content they study. That is simply what the product does; a coaching tool that knows nothing about the player cannot coach them.
• Before any of that happens, you will be asked again.There will be a separate, updated privacy policy covering children’s data, and an explicit parental consent step that you actively complete. You will be shown what we want to collect, why, and for how long, and you can say no.
• Nobody’s waitlist entry gets quietly rolled into broader terms. Being on this list will never be treated as agreement to that future collection, and we will not start collecting anything about your child on the strength of a box you ticked today.

Put plainly: joining the waitlist today does not opt you or your child into anything beyond this page. The tick box on the waitlist form agrees to this policy, in this version, and nothing else.

Why we collect it, and what we do with it

One purpose: to run the pre-launch waitlist. We use it to email you about the launch of Corpus — including, now, to tell you that the founding free trial has been cancelled. That is all it is used for, and the closure of the list does not give it a second use.

We do not use it for advertising, and we do not build behavioural data from it. We could not profile your child from it if we wanted to — we hold nothing about them.

We do not sell or share it

Your details are never sold, rented, traded, or shared for anyone else’s marketing. The only third party who ever touches this data is our hosting infrastructure — Supabase (the managed Postgres database where the list is stored) and Vercel (which serves the website). They process it on our instructions to keep the service running; they are not allowed to use it for anything of their own. The waitlist database is hosted in the United States.

Who can see it

The waitlist table is locked so that no browser, no logged-in Corpus user, and no anonymous visitor can read it — not even one row, not even a count. It is reachable only by a server-side administrator key. In practice that means the site owner is the only person who can view the list.

How long we keep it

Waitlist entries are temporary. We delete a signup within 30 days of whichever of these happens first:

• Corpus launches and you have taken up (or declined) a place;
• you tell us you are no longer interested;
• you ask us to delete it.

If none of those has happened, we still delete waitlist entries within 30 days of launch. A pre-launch mailing list has no reason to outlive the launch, and closing the list does not extend that window by a day. Nothing is kept “just in case”, and a waitlist row is never quietly converted into the start of an account record.

How to see, correct, or delete your data

Email seiji@corpustec.com from the address you signed up with and say what you want:

• Delete it — we permanently remove the row. It is a hard delete, not a flag; nothing is archived.
• Show me what you hold — we send you back everything stored against your email.
• Correct it — tell us what is wrong and we fix it.
• Withdraw consent — this is the same as asking for deletion, and withdrawing is as easy as giving it was.

We answer within 30 days, and normally much sooner. You do not have to give a reason, and asking costs you nothing. If you are in the UK or EU and you are not happy with how we handle your request, you can complain to your national data protection authority.

Children

The waitlist was filled in by an adult, about themselves. Children did not sign up, and we never asked you anything about them beyond how many places to hold. Nothing on this list is personal data about a child, so there is no children’s data here for anyone to lose, leak, share or misuse.

Nothing was ever saved without the box agreeing to this policy being ticked first — every row on file carries a recorded consent, and no row exists without one.

This is a description of the list as it stands today, not a promise about the product forever — see “What changes when Corpus launches” above for exactly what will be different, and for our commitment to ask you again first.

Protecting the form from abuse

This no longer runs — there is no form left to protect. While the waitlist was open, our server briefly counted how many submissions came from one internet connection or one email address, to stop automated scripts flooding it. Your IP address was never stored: it was converted into an unreadable one-way code the moment it arrived, that code was used only for counting, and it was deleted automatically within 24 hours. It was never linked to your signup, never logged, and could not be turned back into an IP address. Nothing from that counting survives.

Cookies

This site sets no advertising or analytics cookies. If you later create a Corpus account, we set a cookie that keeps you signed in — that is a strictly necessary one, and it is the only kind we use.

Changes to this policy

If we change this policy in a way that matters, we publish a new version here and record the new version against future signups, so what you agreed to at the time is never rewritten behind you. Your stored entry keeps the version number of the text you actually saw.

A new version is never applied retroactively to your consent. If a change would mean collecting something new — and the launch of Corpus will — we ask you again rather than treating an old tick as agreement to new terms.

Contact

Privacy questions, data requests, deletions — one address: seiji@corpustec.com.