Privacy

01 What we collect

• Account. Your email address, your display name, your date of birth, and a password hash or the fact that you signed in with Google. We never see your Google password. The date of birth is the age check and nothing else — it is not used to personalise anything and it is never shown to a character.
• Setup answers. What you said you are here for, your self-described experience level, and your microphone and audio-device preferences.
• Sessions. The audio of your reps, the transcript of both sides, the moment-to-moment interest readings the character reacted to, your score and the evidence behind it, and one short line of what a character carries into the next encounter.
• Field log. Which exercise you were given, whether you did it, how nervous you expected to be and how nervous you were, and anything you chose to write down.
• Usage. How many reps you have run, when, against which character, and a per-session record of which provider and model served it and what it cost. This is how we meter the plan and how we check our own bills.
• Safety. When automated moderation acts on a session, or when you report a problem with one, we record what happened: which category was triggered, which side of the conversation it came from, what we did, and — for a report — what you wrote. The turn itself is not copied into that record.
• Technical. Ordinary server and delivery logs kept by our hosting providers — IP address, browser, timestamps — used for security and debugging.

02 What we do not collect

No advertising or cross-site trackers. No card numbers — those go directly to our merchant of record and never reach us. No contact list, no location, no microphone access outside a session you started. We do not sell personal data, and we do not share it with advertisers. If we add product analytics, this page will list the processor before it is switched on.

03 Why we are allowed to hold it

Most of it because we cannot provide the service without it — you asked for an account and a scorecard, and both require storing what happened. The usage ledger we keep because we have a legitimate interest in metering plans accurately and reconciling what we are charged. Session audio we keep on the basis of your consent, given when you start a rep and withdrawable by deleting the recording or the account.

04 Who else touches it

• Supabase — database, authentication and file storage. Your rows are readable only by your own account, enforced by row-level security in the database itself rather than by application code.
• Vercel — application hosting and delivery.
• OpenAI — the live voice model that speaks with you, the model that grades the transcript afterwards, and the classifier that checks both sides of a conversation against the content bounds in the safety policy. The classifier sees one turn at a time and returns a verdict; it is not used to train anything.
• ElevenLabs — an alternative voice provider, used only for sessions served by it.
• Our merchant of record — payment, invoicing and tax, for paid accounts only. They receive what a payment needs and nothing about your sessions.
• Our email provider — sign-in links, confirmations and the weekly review letter.

Each of these is a processor acting on our instructions for the purpose named. Some of them operate outside your country, so your data may be transferred and stored abroad under the safeguards their terms provide.

05 How long we keep it

• Session audio — thirty days. A scheduled job deletes the file and clears the pointer to it. The expiry is stamped when the recording is stored, so changing the window later can never quietly extend audio you were told would be gone.
• Transcripts, scores and your field log stay while your account is open, because they are what your progress is made of.
• The usage ledger is append-only and kept for as long as accounting requires, in a form tied to your account rather than to what you said.
• Safety records stay while your account is open. They are the evidence that the content rules ran, which is the thing we have to be able to show — and they are also the record an account closure would rest on.
• Everything goes when the account closes.

06 What you can ask for

A copy of everything we hold about you, a correction, a deletion of any individual rep, or the deletion of the whole account and everything in it. Write to support@nerve.training and it is done within a working day. Self-service export and per-rep deletion are being built into the settings screen; until they land, the request is handled by a person, not ignored.

Depending on where you live you may also have the right to object to processing, to restrict it, or to complain to your local data protection authority. We would rather you told us first.

07 Cookies

Only the ones that sign you in and keep you signed in, plus what our hosting needs to serve the page. No advertising cookies and no cross-site tracking, so there is no consent banner to dismiss.

08 Children

The service is for adults. We do not knowingly collect anything from anybody under 18, and if we find that we have, we delete it and close the account.

09 Security, changes and contact

Recordings live in a private bucket reached only through short-lived signed links. Database access is restricted per user at the database layer. No system is perfect; if something happens that affects you, we will tell you rather than wait to be asked.

If this policy changes materially we will email you before it takes effect. Questions, requests and complaints go to support@nerve.training.