Privacy
Two lists.
Nothing in between.
The employer sees how teams are doing and never sees an individual's answers. That is not a setting anyone can flip — it is how the product is built: individual answers are not rendered on any employer screen.
Below: what the employer sees, what it never sees, and the one case in which the platform names a person. The full processing terms are in the privacy policy and in the contract with your company.
Aggregates to the employer.
Detail to the employee.
The employee sees their own report in full: seven abilities, the history, the trend. The employer sees the same seven abilities, but per team and without names.
What the employer sees
- Team median, spread and outliers
- Five HR scores and seven abilities, per team
- Movement over time and against a benchmark
- Participation rate per team — never a list of who
What it never sees
- One person's answers inside a game
- One person's traffic-light history
- Free text an employee wrote
- A personal progress history and its trend
A team with fewer than eight active players is not shown at all. Below that floor an aggregate stops protecting anyone: with four people it is too easy to work out who is meant.
One case, one recipient, a rule stated in advance.
A name appears exactly once.
There is one situation in which the platform names a person: when the signal is about a risk to that person. The rule is published in advance and is not changed unilaterally.
| Condition | Who receives it | What the alert contains |
|---|---|---|
| Burnout Risk at 70 or above | One named HR contact, set in the contract | Name, value, a suggestion to hold a 1:1 |
| Five red traffic lights in a row | The same person | Name and the length of the streak |
The recipient is one person, named in the contract. Not a department, not the employee's manager, not a mailing list. Every such alert is written to the access log.
Indicators are advisory. They are not grounds for a personnel decision — not for a review, not for dismissal, not for a change in pay.