Data Sharing by Activity Features

MATCHA's information sharing depends on which course, activity, cloud, collaboration, and support features are enabled. This page describes the information that is shared as a result of using each privacy-affecting feature available in MATCHA, assuming independent usage or course usage at privacy level 1 (Standard). Course and organization privacy levels either limit the availability of the features described here or (when possible) change their behavior to reduce information sharing, as discussed on the Data Protection and Privacy page .

Instructor-led activities and identity

Instructor-led activities use MATCHA cloud services to distribute activity settings, validate access, and connect a student's project to the course activity. When this feature is used, MATCHA may collect:

Student identification entered by the student or supplied by the activity, such as name, email, and student ID.
Course, activity, participant-key, access-code, and activity-setting metadata.
Connection and status information needed to run the activity, such as app version, device technical details, timestamps, and activity state.

This information is retained for the configured data retention period for the course or organization.

Proctoring

Proctoring allows instructors and designated proctors to monitor and control an activity, usually in person. To support proctoring, MATCHA collects information about students and their ongoing activity state.

Student identification, such as name, student ID, and email.
Check-in and check-out information, including room or seating information if proctors enter it.
Proctoring events from MATCHA, such as automation detections, focus-lost events, fullscreen or Single-App Mode violations, outage approvals, unlocks, and proctor actions.
Short-lived text typed in MATCHA for the student detail view, approximately the last minute of typing, while a proctor is actively viewing that student. This transient relay is not retained as long-term evidence.

MATCHA proctoring does not collect camera frames, microphone data, screenshots, or information about the contents of other applications. Proctoring records are retained for the configured data retention period.

Complete Work History

Complete Work History records the student's work process inside MATCHA, including work performed in MATCHA's built-in browser. When enabled, MATCHA may collect:

Document and notes editing history within MATCHA.
Built-in browser page visits, page snapshots, scrolling, clicks, mouse movement, input-field focus, and reading-time information.
Library references, saved project data, and other information stored in the .mcha project file.

MATCHA does not record passwords or other text typed into the built-in browser, except where a website later displays that text as page content. MATCHA does not record ordinary browsing outside MATCHA. Complete Work History remains local unless the student or activity submits, syncs, or shares the .mcha file.

Cloud submissions

Cloud submissions allow students to submit directly from MATCHA instead of manually uploading an exported file to an LMS. Depending on the activity configuration, MATCHA may submit a .docx export, a .mcha project file, or both.

Submission metadata, including student identity, activity ID, submission ID, timestamps, status, and configured storage target.
The submitted files. A submitted .mcha file may include document content, notes, edit history, browser history if collected, references, and project metadata.
Storage-link metadata for the selected destination.

Storage targets can include MATCHA Cloud or an instructor or institution's Google Drive, Dropbox, or OneDrive. When a third-party storage provider is used, that provider processes the submitted files. MATCHA requests access only to a dedicated MATCHA directory on connected third-party storage.

Cloud Sync and Live Collaboration

Cloud Sync and Live Collaboration store a document's primary copy in MATCHA Cloud so it can be synchronized across devices or shared with collaborators. When enabled, MATCHA may collect:

Document content, notes, references, project metadata, and edit history needed to synchronize the project.
User, collaborator, permission, presence, and activity metadata needed to show and control shared access.
Conflict, version, and synchronization metadata needed to keep the cloud copy consistent.

These features are optional and can be disabled for individual activities or controlled through enterprise settings.

Built-in AI assistant

MATCHA's built-in AI assistant provides instructor-configured writing help. When a student uses the assistant, MATCHA sends the information needed for the requested assistance to MATCHA services and then to a third-party LLM provider. This may include:

Assistant chat messages and requested instructions.
Selected text, nearby document context, or document segments needed to provide the requested writing assistance.
Browser context when research assistance is enabled, such as the active tab content and prior content available in the assistant chat until the chat history is cleared.

AI-made edits are tracked in MATCHA so permitted AI use remains auditable. Our current LLM provider does not retain the text sent as part of these requests, and MATCHA does not retain the request text after providing the feature.

Follow-up quizzes

Follow-up quizzes use AI to help instructors ask student-specific authorship questions and, where enabled, assist with preliminary review. This feature requires cloud submission. When enabled, MATCHA may collect and process:

The submitted student project, including document text, notes, and relevant work-history context.
AI-generated quiz questions, student responses, instructor review actions, and preliminary AI review outputs.
Submission, activity, and student identity metadata needed to connect the quiz to the correct student and activity.

Project content and quiz context may be processed by a third-party LLM provider to generate or review quiz material.

LTI integration

LTI integration lets students launch MATCHA activities from an LMS. When LTI is used, MATCHA may collect:

LMS-provided identity information, such as name, email, user ID, course role, and launch context.
Course, assignment, activity, and launch identifiers needed to connect the LMS activity to MATCHA.
Authentication and access metadata needed to confirm that the correct student is joining the correct activity.

This information is stored with the relevant activity data and may be exchanged with the LMS as needed to perform the integration configured by the institution.

Support and diagnostics

Support and diagnostic workflows are optional but sometimes necessary to solve technical problems. Depending on what a user sends, MATCHA may collect:

Support messages, ticket metadata, contact information, route or page context, app version, error logs, and diagnostic details.
Files, project attachments, or screenshots that the user deliberately attaches to a support request.
Aggregated or anonymized diagnostic information used to maintain platform reliability.

Support information is used to troubleshoot, secure, and improve MATCHA services. Users should avoid sending sensitive content that is not needed for support.

Back to Data Protection and Privacy Technical Documentation