TRUST CENTRE
Schools deserve specifics, not reassurance. This page summarizes our published policies and organizational commitments; the applicable legal documents and accepted agreements govern. We distinguish what we do today, what is underway, and what we do not yet claim.
Our products support professional judgment; they do not replace it. AI drafts can be inaccurate, incomplete, or unsuitable. Educators must review and approve output before using it in a classroom, sharing it with a family, or adding it to 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.
Drafts are starting points, not final decisions. Teachers are responsible for reviewing, editing, and approving output before use; AI does not replace that professional responsibility.
Teachers choose the curriculum outcomes and context that drive each draft, so the professional framing of the work stays with the professional.
We use necessary storage to remember your choices and keep this website working. Analytics is off until you accept. You can reject it and still browse, or change your choice later in Analytics settings.
Our current services are offered to customers based in Canada and are for adult users, not student accounts or student-facing services. Product inputs and uploads must be non-personal and non-confidential. Do not submit information that identifies a student directly or indirectly, private records, credentials, sensitive personal information, or confidential third-party material. Removing a name alone is not enough if a learner remains identifiable.
Necessary adult account, billing, and support information is handled through designated channels, not AI inputs. Our Privacy Policy explains how we protect it. We do not sell personal information, use it for third-party advertising, or use or authorize customer content to train or fine-tune general-purpose generative AI models. Disclosed provider safety and policy-enforcement processing may apply; it is not permission for general-purpose model training.
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. Under our current organizational Data Privacy Agreement, if a security breach affects personal information in Customer Data, we notify the customer without undue delay and no later than 72 hours after becoming aware. The applicable accepted agreement governs each customer; publishing an updated policy does not amend an earlier contract.
For school and organizational services, core application storage — including databases, file storage, backups, and operational logs containing personal information — stays in Canada under the applicable agreement. This is not tied to one cloud vendor. Permitted AI processing and expressly authorized usage analytics may occur outside Canada within the specific exceptions in that agreement. Our public website is hosted outside Canada; individual-account data locations are described in the Privacy Policy.
Our Subprocessor List describes services, processing locations, and provider-specific retention. Requested AI features use permitted inputs and necessary request metadata through commercial APIs or cloud-hosted models. Paid API access does not itself mean Canadian-only processing or zero retention. We assess the applicable route and terms before use; a provider-list update cannot reduce an accepted safeguard or authorize new processing.
Under our current organizational DPA, adding or replacing a subprocessor that touches personal information normally requires at least 30 days’ written notice. An urgent replacement needed to protect security or availability may happen immediately, with notice without undue delay afterward and the same objection rights.
Access to Customer Data is limited to authorized personnel who need it for their work, with confidentiality obligations and safeguards appropriate to the data. The public website provides company information and consultation requests; it is not a channel for student records or sensitive school information.
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.
We aim to support keyboard navigation, screen readers, touch input, and reduced-motion preferences, but parts of our websites and products may still present barriers. We have not completed a formal accessibility audit. If you encounter a barrier or need content in an alternative format, contact us — we respond to accessibility requests within five business days and make reasonable efforts to accommodate requests.
Our published Support & Service Levels document explains how to get help and serves as the Service Level Schedule for organizational Orders. Where that schedule applies, it sets a 99.5% monthly uptime target, subject to its exclusions and service-credit process. Response targets are goals, not guaranteed response times; the applicable Order and agreement govern.
Individual accounts have no uptime guarantee, and individual Beta use has no service-level commitment. Organization-provided access follows the organization’s accepted agreement instead of the individual-account exclusions. Hosting, maintenance, and ongoing support for custom work depend on the agreed scope; they are not automatically included in every custom-work price.
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