Superhuman AI

Privacy notice

What this product holds, where it holds it, and what leaves. Written to be checked, not to be agreed to.

Last updated 9 September 2026

  1. Who this is for

    Superhuman AI sells to organisations. An account belongs to a company, that company's own administrator runs it, and the people who use it were given accounts by their employer.

    If you use this product at work and want to know what is held about you, your administrator can answer faster than we can — they can see it, and we can only see that it exists.

  2. Where a customer's data lives

    Each customer's data lives in a database of its own, not in a shared one with a customer column.

    That database is created in the country the customer names, and the deployment that serves them is registered against it.

    This is not a configuration setting. A deployment reads one database, and which one is fixed in the code that is deployed — so there is no request that could reach another customer's data by being wrong about who is asking.

  3. What a practice call produces

    A practice call is transcribed and scored. The transcript and its report stay in that customer's database.

    A trainee sees their own calls. A manager sees their team's. An administrator sees their organisation's. Nobody at Superhuman AI opens a transcript in the course of running the service.

    Audio is not kept. What remains is the text of what was said and the score it was given.

  4. What the product sends anywhere else

    Conversations are generated by a large-language-model provider acting as a sub-processor. Nothing is used to train it.

    Pages behind sign-in load no third-party images, fonts or scripts, so opening one sends no request anywhere else.

    Page views are counted as route patterns — /coach/scenarios/[slug], never the scenario's name — so no customer's words leave in a URL.

  5. Sign-in and passwords

    A password is stored as a scrypt hash and never in a readable form. Nobody here can read one, and a reset produces a single-use link rather than a password somebody chose for you.

    Changing a password ends every other signed-in session for that account.

  6. What is recorded about administrators

    Acts one person performs on another — a password reset, an appointment, a change of job role — are written to an audit trail inside that customer's own database, with who did it and when.

    The customer's administrator can read it. It exists so that a question about what happened has an answer that does not depend on anybody remembering.

  7. How long things are kept

    For as long as the customer's account is open. When an account is closed, its database is exported for the customer and then destroyed — there is no shared store it leaves rows behind in.

    A customer can ask for a person's calls and reports to be deleted before then, and their administrator can do it without us.

  8. Asking about your data

    Write to support@superhumanai.tech. If you use the product through an employer, say which organisation — we will route the request to their administrator, because their data is theirs and we do not act inside it on somebody else's word.

Questions about any of this go to support@superhumanai.tech.