Compliance Centre
Universities, colleges, and schools answer to different privacy laws depending on where they operate, but those laws share one core rule: collect only the personal information the educational purpose requires. MATCHA is built so institutions can follow that rule.
Data minimization by design
Every privacy law in the Compliance Centre asks institutions to limit collection to what a legitimate educational purpose requires. MATCHA makes that a decision for each course and activity, rather than a product-wide default.
Instructors choose what each activity collects
Proctoring, check-ins, entry tickets, assigned seating, browser access, Complete Work History (browsing recording), the level of AI assistance, follow-up quizzes, and cloud submission are set activity by activity, so instructors can enable only what the assessment requires. Complete Work History, live collaboration, and cloud saving start switched off.
Privacy Levels cap what MATCHA can read
Each course has a Privacy Level, and organizations can set a minimum level for every course. At Level 2a, student names, IDs, and email addresses are encrypted end to end between the student and course staff. Level 2b does the same for submissions in LMS-linked courses. At Levels 3 and 4, identity, student work, and work histories are all encrypted, and AI processing of student work is disabled.
Students see it before they start
Before an instructor-led activity begins, the Activity Summary lists each kind of information the activity collects and who receives it: kept on the student's computer, shared with teaching staff, or shared with MATCHA and its subprocessors. Organizations can add custom data collection notices.
Local-first, with no elevated permissions
Outside a course, MATCHA Writer shares nothing with us apart from diagnostic logs. Work histories live in the project file on the student's own computer. The app needs no administrator rights, camera, microphone, screen recording, or accessibility permissions.
Retention you set
Organizations choose how long course data is kept after a course ends: anywhere from 1 to 36 months, with 12 months by default. The period covers courses, activities, submissions, and proctoring records.
Data residency by region
Each organization is hosted on one of three separate platforms, MATCHA USA, MATCHA Europe, or MATCHA Global, according to its institution's internet domain. Cloud submissions, and their backups, can be kept in Australia, Canada, the EU, Singapore, the UK, or the US. Each jurisdiction's page lists its options.
In the Compliance Centre
- JurisdictionsHow MATCHA complies with legislation around the world.
- AccessibilityWCAG 2.1 Level AA, documented in a published VPAT, with keyboard shortcuts and accessibility guidance.
- Data security and privacyPrivacy Levels, end-to-end encryption, security standards, data residency, and retention.
- Information sharing by activity featuresWhat each activity feature collects and who receives it.
- For privacy reviewersKey facts for PIAs and DPIAs, our subprocessors, and the HECVAT and other assessment frameworks.
- DocumentsOur policies and terms, the Children's Privacy Notice, the VPAT, and the Québec parental consent form.
