Loading...
Technical overview of Kontaim's Zero-PII data handling for live session participants.
| Participant Names | NOT COLLECTED |
| Email / Phone | NOT COLLECTED |
| IP Addresses | NOT LINKED TO RECORDS |
| Participant Join | Display Name + Session Code |
| Optional Nicknames | Client-Side Encrypted* |
*Facilitators may add nicknames. Each is encrypted in the facilitator's browser with a key generated on their device; we store only ciphertext and cannot decrypt it.
| Data Residency | AWS Canada (Montreal) |
| Encryption (Rest) | AES-256 |
| Encryption (Transit) | TLS 1.3 |
| 3rd Party Data Sharing | Named subprocessors only |
| AI Providers (US) | No participant identifiers |
| Analytics (PostHog) | Teacher pages only |
Analytics: IP disabled, UUIDs only, all text masked, nothing on participant pages. Optional in-activity AI helper can be switched off per activity or for a whole school or board.
Participant
Join Code Only
No PII Required
Kontaim
Processing
No contact details
AWS Canada
Montreal
Data Sovereign
If Exposed
Participant Records
What's Found
Anonymous Display Names
Privacy Risk
MINIMAL
No participant account holds a name or email. Roster nicknames are stored encrypted with a key we never receive; a name typed into a live session is optional, visible only to the teacher, and becomes “Player 1, Player 2” 7 days after the session closes; typed responses and drawings are deleted after 30 days, and the anonymous per-Player results after a year.
See our complete Privacy Policy.