Privacy notice

01 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, because they can open your calls in the product.

02 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.

03 What a practice call produces

A practice call is transcribed, and any report on it is written from that transcript. The transcript and any report stay in that customer’s database.

While your account is active, you can open your own calls. So can your organisation’s administrators, while theirs is. Superhuman AI operates each customer’s database and can reach everything in it, transcripts and reports included. Nobody at Superhuman AI opens a transcript in the course of running the service.

This product keeps text and figures, never a recording of your voice.

04 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.

During a call, the trainee’s voice and the character’s replies go directly between the trainee’s browser and the model provider. They do not pass through our service.

After a call, its transcript is sent to the model provider to write its report, and to read it with that person’s other calls.

The scenario a call is run from (its character and their agenda, its situation and criteria, and the role and trade it is written for) is sent to the model provider to play the call, speak its brief and write its report. When an administrator drafts a scenario with the product’s help, the request, any document attached to it, and the role and languages it is for are sent to the model provider too.

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.

05 Who processes data for us

Three companies process a customer’s data for us. Each is described here by its part and what it receives.

The first is the model provider. During a call it receives the trainee’s voice and produces the character’s replies. After a call it receives the transcript, to write the report and to read it with that person’s other calls. It also receives the scenario a call is run from, its hidden agenda included, and an administrator’s drafting request with any document attached to it.

The second hosts each customer’s database, and so holds everything this product keeps about that customer and its people.

The third hosts the service. Every request to the product passes through its servers, a transcript included on its way to the database and to the model provider. It also counts page views, as route patterns.

06 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.

07 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.

08 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.

09 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.