TRUST CENTRE
Schools deserve specifics, not reassurance. Everything on this page is backed by our published legal documents, and we say plainly what we do today, what is underway, and what we do not yet claim.
Our products are built to support professional judgment, not replace it. AI drafts; educators decide. We design every workflow so a qualified person reviews AI output before it reaches a student, a family, or an official record.
We are specific about what our tools do. We avoid broad claims about AI transforming education, and we do not ship features whose behaviour we cannot explain to the teachers and administrators who rely on them.
Nothing our tools produce is final until a teacher makes it final. Drafts are starting points: teachers review, edit, and approve every output, and the workflow makes the review step explicit rather than optional.
Teachers choose the curriculum outcomes and context that drive each draft, so the professional framing of the work stays with the professional.
This website collects no personal information from visitors — no cookies, no accounts, only anonymous activity such as pages viewed and files downloaded. Contact and consultation submissions are collected for the purpose of responding to your inquiry and are handled by authorized staff only.
Within our products, we work with school authorities to define what data enters a workflow, what it is used for, and how long it is kept. Our published Privacy Policy puts the commitments in writing: we do not sell personal information, we do not use it for third-party advertising, and we do not train AI models on customer content without explicit opt-in.
We design for school-division privacy expectations from the start of each project rather than retrofitting them at the end. Data minimization is the default: workflows are scoped to use the least data needed to do the job.
Privacy questions from school authorities get direct answers from our team, including during procurement, before any agreement is signed. We commit in writing to every organizational customer that if a breach of security affects personal information in customer data, we notify the customer without undue delay and no later than 72 hours after becoming aware.
Product hosting, database, file storage, backups, and authentication run in AWS’s Canadian region (ca-central-1, Montréal) — school and organizational customer data at rest stays in Canada. AI inference runs on in-region models, with no training on customer content.
We publish a tiered subprocessor list: core providers that may process customer data are held to the full bar of our customer data-protection agreements, and limited-scope providers only ever receive content submitted to specific, signposted media features. Customers get at least 30 days’ written notice before we add or replace a subprocessor that touches personal information.
Access to systems and submissions is restricted to authorized staff. We keep the public website separate from our product and operations applications, so a visitor-facing page never shares a boundary with school data.
We describe our security practices to customers directly and specifically. We do not use the word "secure" as an absolute, and we would rather explain a real control than publish a reassuring generality.
We do not currently claim any formal compliance certification or third-party audit. Formal reviews are on our roadmap, and we will list a certification here only after it has been achieved and verified, and never before that point.
If your procurement process requires specific attestations, contact us and we will tell you plainly where we stand on each one.
We answer privacy, security, and vendor questionnaires as part of working with school authorities, and we make our team available to technology and privacy leads during evaluation.
If your review needs documentation we have not published, ask. A direct answer from us is faster than waiting for a page to exist.
We are early in our accessibility journey and do not yet claim conformance with a specific standard — our published Accessibility Statement says so plainly. We are working toward WCAG 2.1 Level AA as our websites and products mature.
In practice on this website, core content and navigation work with a keyboard, a screen reader, touch input, and reduced-motion preferences, and pages remain readable without JavaScript. If you encounter a barrier or need content in an alternative format, contact us — we respond to accessibility requests within five business days.
Our Support & Service Levels document is published on this site — it doubles as the Service Level Schedule referenced in organizational customers’ Orders. It covers how to get help, support hours, severity-based response targets, and a 99.5% monthly uptime target for subscription services, with scheduled maintenance kept outside school hours where practical.
Route them through our contact page and mention that your question is for a privacy, security, or procurement review, so it reaches the people who can give you a direct answer.
Contact us