Self-Audit Checklist

Bill 194 Compliance Matrix

How Argraide meets Ontario's privacy requirements for educational technology

21

Requirements Checked

100%

Compliance Rate

0

Student PII Fields Collected

Data Residency

Data must be stored in Canada

All data hosted in AWS Montreal (ca-central-1)

Compliant

No transfer to foreign jurisdictions without consent

Data never leaves Canada. No cross-border transfers.

Compliant

Data Minimization

Collect only necessary personal information

We collect 0 (zero) fields of student PII. Only randomized emoji identifiers.

Compliant

Purpose limitation for collected data

Data used solely for educational progress tracking. No marketing or advertising.

Compliant

Retention limitation

Student data auto-purged at end of school year or upon teacher request.

Compliant

Student Privacy (MFIPPA/FIPPA)

No collection of student names

Students identified by random usernames only (e.g., "CosmicPanda42").

Compliant

No collection of student emails

No email required. Authentication via emoji-based passphrase.

Compliant

No collection of biometric data

Not collected. No facial recognition, voice, or fingerprint data.

Compliant

Parental consent for students under 13

Not required. Zero PII architecture means no personal information to consent to.

Compliant

Encryption & Security

Data encrypted in transit

TLS 1.3 for all connections. HTTPS enforced.

Compliant

Data encrypted at rest

AES-256 encryption on database storage (Supabase/PostgreSQL).

Compliant

Secure authentication

Teachers: Supabase Auth with bcrypt hashing. Students: Zero-knowledge emoji login.

Compliant

Access controls

Row-level security (RLS) policies. Teachers only see their own classes.

Compliant

Zero-Knowledge Architecture

Student nicknames protected

Client-side AES-256-GCM encryption. Server never receives plaintext or key.

Compliant

Key derivation

PBKDF2 with 600,000 iterations (OWASP 2023 recommendation).

Compliant

Decryption capability

Platform cannot decrypt nicknames. Only teacher with passphrase can.

Compliant

Transparency & Accountability

Clear privacy policy

Published at /privacy. Plain language. Updated December 2025.

Compliant

Data Processing Addendum available

Available at /dpa for institutional customers.

Compliant

Contact for privacy inquiries

support@argraide.com

Compliant

Third-Party Services

Vetted subprocessors only

Supabase (Canada), Stripe (PCI-DSS compliant), Vercel (USA - no student data).

Compliant

AI processing disclosure

AI generates activities only. No student data sent to AI providers.

Compliant

Technical Specifications

Infrastructure

  • Database: Supabase (PostgreSQL) - ca-central-1
  • Hosting: Vercel Edge Network
  • CDN: Vercel CDN (global, no PII cached)
  • Payments: Stripe (PCI-DSS Level 1)

Encryption Standards

  • In Transit: TLS 1.3
  • At Rest: AES-256
  • Nicknames: AES-256-GCM (client-side)
  • Key Derivation: PBKDF2-SHA256, 600K iterations

This self-audit was last updated: January 2026

For formal verification or to request a third-party audit, contact privacy@argraide.com