Trust and privacy
Protected from the direct lead - not “anonymous”
The rules are enforced in the database and tested automatically. There is no setting that switches them off.
Protected, not anonymous
What we do not promise
Full anonymity. In a team of 15, a lead knows who covers which machine or outlet, so anonymity would be a false promise.
What we do promise
The entry is protected from the direct lead, and the worker knows exactly who can see their name and when. Only the level above can unlock a name, with a recorded reason that the worker can see.
Who sees what
Each cell is a rule enforced in the database.
Content of an entry
- Worker
- own
- Lead
- team, no names
- Level above
- unit, no names
- Director
- summary + source
- Admin
- no (logged)
Worker's name
- Worker
- -
- Lead
- never
- Level above
- with a reason the worker sees
- Director
- no
- Admin
- no
Verbatim quote one level up
- Worker
- -
- Lead
- -
- Level above
- when 5+ people raise the topic; signed and urgent at once
- Director
- same
- Admin
- -
Editing the original
- Worker
- only before confirming
- Lead
- no - adds a layer
- Level above
- no
- Director
- no
- Admin
- no
Who didn't report
- Worker
- own streak
- Lead
- no - only “11 of 15”
- Level above
- no
- Director
- no
- Admin
- no
Perception gap
- Worker
- -
- Lead
- no
- Level above
- own unit, 50+ people
- Director
- per unit, 50+ people
- Admin
- -
Voice recording
- Worker
- own
- Lead
- only if signed
- Level above
- only if signed
- Director
- only if signed
- Admin
- no
The 14 rules
No company can switch them off.
- 01The direct lead never sees the worker's name next to an unsigned entry.
- 02A name on an unsigned entry can be unlocked only by the level above the lead, with a reason the worker sees.
- 03Only the worker signs, by an explicit action. The system never does.
- 04There is no list of who didn't report. Leads see a number (“11 of 15”).
- 05No rankings, no score of an individual by name, no ratio of signed to unsigned entries.
- 06No tone or emotion analysis, no voiceprint, no location.
- 07The original never changes. Leads and everyone above only add their own labelled layer.
- 08The lead's weekly report is locked before they see the team's weekly summary.
- 09Urgent cannot be removed without a person above the lead and a reason; the confirmation chain cannot be switched off.
- 10The perception gap is calculated only for units with 50 or more different people, weekly, in aggregate.
- 11Retention stays within fixed limits. “Forever” doesn't exist.
- 12Reports about a person, ethics or legality are not handled in the app - they go to the company's designated officer.
- 13The worker always sees what went up from their entry, which roles saw it, and every name unlock.
- 14Participation is voluntary. There is no mandatory entry and no penalty for not speaking.
How long data is kept
- Audio
- 24–72 hours (default 72), then deleted
- Transcript
- 90–180 days (default 180)
- Structured items, no names
- 12–24 months (default 24)
- Names of third parties
- removed before saving; companies, sites and machines stay
- Identity
- by phone number - never by voiceprint
Legal basis and data processing
- Legal basis: legitimate interest with a documented assessment (LIA) and a DPIA - never employee consent, which cannot be freely given at work.
- Participation is voluntary, and this is written into the rules every worker sees before their first entry.
- No emotion recognition at work and no scoring of individuals - in line with the EU AI Act.
- Where works councils have a say (for example in Germany or Austria), the pilot starts with them.
- EU hosting. AI providers process data under API terms that exclude training on it. Sub-processors are listed in the data processing agreement.
- Dedicated instance for larger groups: own database, domain, keys and region, AI models inside your perimeter.
Legal documents for your lawyer to review.
Data processing agreement, DPIA template, legitimate-interest assessment, employee notice and the list of sub-processors.