Security & Compliance
Trust Center
This page is written for the person doing the security review. It sets out how Tutorify handles institutional and student data, who else touches it, and which documents we can provide for your vendor assessment. If something you need is not here, ask us at privacy@tutorify.ai and we will answer directly.
Our role under FERPA
Your institution is the controller and owner of its data. Tutorify acts as a school official with a legitimate educational interest under FERPA (34 CFR § 99.31(a)(1)), performing an institutional service under your direction and subject to a signed Data Privacy Agreement. We process data only on your documented instructions, we do not re-disclose education records except as you direct or FERPA permits, and we do not decide the purposes of processing ourselves.
FERPA obligations run to institutions rather than to vendors, so no vendor holds a FERPA certification. What we can offer is the contractual position above, backed by the controls on this page. Our Data Privacy Agreement and a School Official Designation Addendum are available for your counsel to review.
Where data lives
Tutorify runs on Amazon Web Services in the United States. Data is encrypted in transit and at rest with AES-256 using customer-managed keys with automatic rotation. Encryption, network isolation, and key policy are defined in infrastructure-as-code and applied by pipeline rather than configured by hand, which means the configuration is reviewable and reproducible rather than asserted.
Databases run in private subnets with no public route. Backups are encrypted, and restoration is tested rather than assumed.
Access and authentication
Students and instructors reach Tutorify through your LMS using LTI 1.3, which is built on OpenID Connect. Authentication happens at your institution’s identity provider, so any password policy or multi-factor requirement you enforce applies to Tutorify automatically, and there is no second credential for us to store or for an attacker to take.
Authorization has four tiers — system administrator, organization administrator, instructor, and student — and roles are derived from the LMS launch context. A student in Canvas is a student in Tutorify. Because entitlements are derived rather than separately maintained, they cannot drift out of step with enrollment when a student drops a course or an instructor changes assignment.
Internal staff access follows least privilege, is logged, and is reviewed. Access to institutional data is recorded in an audit trail.
AI processing
Model inference runs on infrastructure Tutorify operates. Course content and student work are not sent to any third-party inference provider, are not sent to consumer AI products, and are not used to train any model.
This is an architectural property rather than a contractual promise from a vendor: because we run the models ourselves, there is no third party in the inference path whose terms could change, whose retention policy you would have to audit, or whose own sub-processors you would need to trace.
Personal data is minimized before inference. Every AI output that affects a student — generated assessments, rubric-based grading, feedback — is reviewed by the instructor before it reaches the student or the gradebook. The full detail is on our AI Transparency page.
Sub-processors
These are the vendors that may process institutional data on our behalf. We impose data-protection obligations on each that are no less protective than our DPA, we remain responsible for their performance, and we notify institutional customers 30 days before adding one.
There is no AI inference provider on this list, because there is not one in the path. Model inference runs on infrastructure Tutorify operates.
| Sub-processor | Purpose | Location |
|---|---|---|
| Amazon Web Services | Hosting, storage, database, encryption key management | United States |
| Google Workspace | Business email and document collaboration for support correspondence | United States |
This list is dated at the top of the page and is reproduced in Annex B of the DPA.
Retention, return, and deletion
We hold institutional data for the term of your agreement. On expiry or termination we return and delete it at your choice within 30 days, excluding copies we are required by law to retain, and we confirm deletion in writing on request. Requests for deletion of a specific record are routed through your institution — write to privacy@tutorify.ai and we will coordinate with your designated contact.
Where a student or parent exercises a FERPA right of access or amendment, the request is directed to the institution that holds the record. We support you in meeting the 45-day statutory window and will produce the relevant data on your instruction.
Security incidents
We maintain a documented incident response plan with defined severity levels, named roles, and an escalation path, together with breach notification procedures written against state notification law. If a personal-data breach affects your data, we notify you without undue delay and no later than 72 hours after becoming aware of it, tell you what we know, and work with you through investigation and remediation.
Reporting a vulnerability
If you believe you have found a security issue, please write to privacy@tutorify.ai. Machine-readable contact details are published at /.well-known/security.txt in line with RFC 9116.
We will acknowledge your report, keep you updated while we investigate, and credit you if you would like to be credited. We ask that you give us a reasonable opportunity to fix an issue before disclosing it, that you do not access or modify data belonging to an institution or a student, and that you do not degrade the service for others. We will not pursue researchers who follow this.
Documentation for your review
Available on request, under NDA where appropriate:
- Data Privacy Agreement and School Official Designation Addendum
- Educational Purpose Limitation agreement
- Security overview covering infrastructure, application, and CI/CD controls
- Architecture and data-flow documentation
- Incident response and breach notification procedures
In preparation: a completed HECVAT 4 (Full), an accessibility conformance report against WCAG 2.1 Level AA, and an independent penetration test of the current application. We would rather tell you these are in progress than imply otherwise — if your timeline depends on one of them, tell us and we will give you a date.
Contact
Security review, vulnerability reports, privacy and data requests: privacy@tutorify.ai
Contracts, agreements, and legal: info@tutorify.ai
Product support: support@tutorify.ai