Skip to content

    Security at Ontario Curriculum AI

    We protect educator data with enterprise-grade encryption, Canadian-only hosting, and a zero student data policy — built for Ontario school board procurement from day one.

    Student PII Collected

    Zero

    No student names, grades, or identifiers stored

    Encryption in Transit

    TLS 1.2+

    All connections encrypted end-to-end

    Encryption at Rest

    AES-256

    Industry-standard data-at-rest encryption

    Data Residency

    Canada

    All data hosted in Canadian data centres

    Security Principles

    Our security posture is grounded in four principles designed for the Canadian education sector.

    Privacy by Design

    We never collect, store, or process student personally identifiable information (PII). Educator inputs are processed in real time and not retained for model training.

    AI Data Isolation

    Prompts and outputs are never used to train AI models. Each generation is an isolated, stateless transaction — no data is shared across users or sessions.

    Canadian Data Sovereignty

    All platform data resides in Canadian data centres, with no cross-border transfer. Canadian residency supports Ontario education-sector privacy and data-governance requirements, but hosting location alone does not establish compliance — schools and boards remain responsible for assessing the legal, policy, contractual and privacy requirements that apply to them.

    Regulatory Alignment

    We design our practices with PIPEDA (federal), FIPPA/MFIPPA (Ontario) and the Ontario Education Act in mind, and we provide the documentation boards need for procurement review and privacy impact assessments. The compliance determination itself rests with the board.

    Technical Controls

    Enterprise-grade safeguards applied across every layer of the platform.

    Encryption

    • TLS 1.2+ for all data in transit — no unencrypted connections permitted
    • AES-256 encryption for all data at rest
    • API keys and secrets stored in encrypted vaults, never in source code
    • Secure session management with short-lived, rotating tokens

    Infrastructure

    • Hosted on SOC 2 Type II certified infrastructure providers — our own SOC 2 Type II audit is in progress, not yet complete
    • Canadian-region deployment with no cross-border data transfer
    • Automated daily backups with point-in-time recovery
    • Network isolation and firewall rules enforced at the edge

    Access Control

    • Row-Level Security (RLS) enforced on all database tables
    • Role-based access control with principle of least privilege
    • Service-role functions isolated from public API surface
    • Admin operations require multi-factor authentication

    Incident Response

    • Documented incident response plan with defined escalation paths
    • 72-hour breach notification commitment, modelled on PIPEDA breach-reporting expectations
    • Continuous monitoring and automated anomaly detection
    • Post-incident review and remediation process

    Security Roadmap

    Completed

    • TLS 1.2+ everywhere
    • AES-256 at rest
    • RLS on all tables
    • PIPEDA-aligned privacy practices

    In Progress

    • SOC 2 Type II audit
    • Penetration testing

    Planned

    • Bug bounty program
    • ISO 27001 certification

    Need a Security Review Package?

    We provide complete security documentation packages for board procurement teams, including DPA, PIA support, and technical security summaries.

    Security questions? Contact us at hello@ontariocurriculumai.com

    Ontario Curriculum AI is an independent platform and is not affiliated with or endorsed by any school board or the Ontario Ministry of Education. This page describes our security and privacy practices; it is not a legal opinion and it does not certify compliance on behalf of any school, board or educator. Whether a tool may be used with particular information is determined by the board under its own policies and its obligations under MFIPPA and the Education Act. Security practices described here reflect our current implementation as of February 2026 and are subject to continuous improvement. Last updated: February 2026.