Technical overview of Argraide's Zero-PII data handling for educational institutions.
| Student Names | NOT COLLECTED |
| Email / Phone | NOT COLLECTED |
| IP Addresses | NOT LINKED TO RECORDS |
| Student Login | Random Username + Emoji Password |
| Optional Nicknames | Client-Side Encrypted* |
*Teachers can add nicknames. Each is encrypted in the teacher'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 student identifiers |
| Analytics (PostHog) | Teacher pages only |
Analytics: IP disabled, UUIDs only, all text masked, nothing on student pages. Optional in-activity AI helper can be switched off per activity or for a whole school or board.
Student
Emoji Login
No PII Required
Argraide
Processing
No contact details
AWS Canada
Montreal
Data Sovereign
If Exposed
Student Records
What's Found
Random usernames, hashed codes, scores
Privacy Risk
MINIMAL
No student 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.