The rules we built in — Rapora Ethics

Consent, always

Rapora is used with the knowledge and consent of meeting participants. Our onboarding materials include consent language; our practitioners commit to it.

Team dynamics, not individual assessment

Rapora analyses patterns in how a meeting unfolds. It is not an employee-evaluation tool, will not produce individual scorecards, and our terms prohibit using it as one.

The tool surfaces; the professional interprets

Every candidate finding is shown with its quote and context for human review. Nothing is silently filtered out, and nothing is pronounced "guilty" by software. A finding is a question, not a verdict.

Patterns, not people

Findings attach to utterances — specific things said at specific moments — never to a person's character. The same person can trigger a pattern in one meeting and rescue the discussion in the next. The report reflects both.

Local by architecture, not by policy

Privacy promises backed by terms of service can change. Rapora's promise is structural: the software has no cloud to send your data to. Audio, transcripts, and reports exist only on the practitioner's machine. Retaining meeting audio is off by default and requires an explicit, informed choice.

Transparent to the people in the room

Teams being analysed deserve to know what the instrument does and doesn't do. We provide plain-language participant materials — in English and Bulgarian — and encourage practitioners to share them before the first session.

Full ethics documentation is available to practitioners in the programme, in English and Bulgarian. If any of it gives you pause, ask us the hard question: hello@rapora.io.

The rules we built in — published, because you should be able to check