Privacy Policy

1. Introduction and Scope

This Privacy Policy explains how 1001662213 Ontario Inc., operating as Terza(“Terza,” “we,” “us,” or “our”), collects, uses, discloses, and protects personal information in connection with the Terza mobile application and related services (the “Service”).

This Policy applies to individuals who create accounts to use the Service (“Teachers”) and to students whose lessons are recorded through the Service (“Students”), as well as the parents and legal guardians of Minor Students (“Parents”) and other individuals whose information is processed through the Service. It should be read together with Terza’s Terms of Use. Students under the age of 18 whose lessons are recorded through the Service are “Minor Students.”

You are under no obligation to provide personal information, with the caveat that your refusal to do so may prevent you from using certain portions of the Service. For Minor Students, a Parent’s refusal to provide consent means lessons cannot be recorded for that student.

By creating an account and providing personal information to Terza, Teachers consent to the collection, use, and disclosure of their personal information as described in this Policy. Parental consent for Minor Students is obtained separately through the verifiable parental consent process described in Section 4 and is not implied by use of the Service.

2. Information We Collect

2.1 From Teachers

• Account information: name, email, password (or Sign in with Apple credential)
• Subscription and billing information (processed by Apple; Terza does not directly receive full payment card details)
• Studio and student roster data entered by the Teacher
• Usage data related to how the Teacher interacts with the Service

2.2 From or About Students

• Lesson audio recordings, initiated by the Teacher for lessons involving the Student, after verifiable parental consent is completed in the case of Minor Students
• Transcripts generated on-device from that audio
• AI-generated observations, summaries, and draft practice notes derived from the transcript
• A longitudinal progress record built up across lessons

2.3 From Parents and Guardians

• Contact information necessary to deliver and complete the verifiable parental consent process
• The consent record itself (what was disclosed, when, and the Parent’s response)
• Any communications a parent sends to Terza regarding their child’s data (e.g., withdrawal, access, or deletion requests)

2.4 Automatically Collected Information

• Error and crash monitoring. The Terza app, backend, and website use Sentry for operational error and crash monitoring, configured not to collect personal information (no IP addresses, names, transcripts, or other identifying data are sent). Standard technical context (device model, operating system version, app version) is captured automatically as part of any error report, to help diagnose the issue.
• Push notification device tokens.The iOS app registers an opaque device token with Apple’s Push Notification service so Teachers can receive alerts (for example, a parent granting consent, or a lesson summary ready for review). This token identifies the app installation on a Teacher’s device; it is not linked to Student or Parent identity.
• Verifiable parental consent records.When a Parent completes the consent process, Terza’s backend automatically captures the IP address and browser user-agent string from that request, as part of the proof-of-consent record kept to demonstrate compliance with applicable law. This is retained as part of the consent record described in Section 6.
• Website analytics.terza.app marketing pages use Plausible Analytics, a cookieless analytics service that does not collect IP addresses or set persistent identifiers. Analytics is not loaded on the consent or consent-withdrawal pages, since those pages’ URLs contain a Parent’s or Teacher’s unique access token.
• Hosting-provider request logs.As with any web service, Terza’s hosting provider (Netlify) and backend provider (Supabase) automatically log standard request metadata, such as IP address and user-agent, at the infrastructure level to operate and secure the Service. Terza’s own application code does not read, store, or otherwise process these infrastructure-level logs.

3. How Lesson Data Is Processed

• The Teacher records a lesson on their device.
• The audio is transcribed on-device, using Apple’s system speech-recognition framework. Audio is not sent to any third party for the purpose of transcription.
• The resulting text transcriptis sent to Terza’s backend and then to Anthropic’s API for AI analysis — cleanup, speaker-turn inference, issue extraction, and generation of a teacher-facing summary and draft practice notes.
• The Teacher reviews all AI-generated output. Nothing is shared with a Parent until the Teacher approves it.
• Lesson audio, transcripts, and derived content are stored in Terza’s backend (Supabase), subject to the retention schedule in Section 6.

4. Verifiable Parental Consent for Minor Students

4.1 Consent Is Completed by the Parent, Not the Teacher

Before any lesson involving a Minor Student is recorded, the Minor Student’s Parent must directly completea Terza-issued consent process. This is enforced at the database level: a Minor Student cannot be enabled for recording until a completed consent record exists. A Teacher cannot complete this step on a Parent’s behalf.

4.2 What Is Disclosed

The consent notice discloses the categories of data collected, that the transcript is sent to Anthropic for AI analysis, that Supabase stores the underlying data, that Resend delivers the consent request and confirmation emails (which include the Minor Student’s first name), the retention periods in Section 6, and the Parent’s rights under Section 7.

4.3 AI Processing Disclosure

Disclosure of AI processing is included within the single consent flow, rather than as a separate opt-in, because AI analysis is integral to delivering the Service (it is how the Teacher’s summary and draft practice notes are generated). Separate, additional opt-in consent is obtained for the optional program described in Section 5.3.

5. How We Use Information

5.1 Core Service Delivery

We use the data described in Section 2 to operate the Service: generating summaries and draft practice notes, maintaining the longitudinal progress record, enabling Teacher review and release workflows, communicating with Teachers, and improving the reliability and effectiveness of the Service. We may also use such data to comply with applicable laws and regulations, to respond to lawful requests from public authorities, to enforce our Terms of Use, and to protect our rights, property, or safety and the rights, property, and safety of our users and others, as well as for any lawful purpose including research and product development.

5.2 In-Studio Lesson Reference

After a Teacher reviews and approves a lesson summary, Terza generates a retrieval-ready embedding of the reviewed content. This powers the Ask and Reflect features within a Teacher’s own studio — for example, surfacing relevant history from a student’s past lessons. This capability is part of core Service delivery and is not optional.

• Each embedding is linked to its source lesson via an internal reference
• That reference is nulled 12 months after the student’s last recorded lesson, when the underlying identifiable lesson record is deleted or de-identified under the retention schedule in Section 6
• Voyage AI, which generates these embeddings, receives only observation-level content with student names removed — never the raw lesson audio or transcript

5.3 Cross-Studio Anonymized Reference (Opt-In)

With separate, explicit, opt-in consent, Terza may additionally include de-identified, aggregated lesson content in a cross-studio dataset used to improve pedagogical relevance of AI outputs — for example, enabling the “Ask Terza” community-reference feature to surface answers like “Other teachers using Terza have tried…” This program:

• Is entirely voluntary; the Service is fully functional without it
• Scrubs identifying information from pedagogical content at the point of insertion, before it is aggregated across studios
• Is anonymized from the outset and, unlike the in-studio reference described in Section 5.2, carries no internal reference back to a specific student
• Can be withdrawn at any time through account settings, which stops future contributions — previously contributed content cannot be identified or removed, because it is anonymized at the point of insertion and cannot be traced back to a Teacher or student

5.4 What We Do Not Do

We do not sell personal information. We do not use Minor Student data for advertising. We do not permit our AI provider to train models on Service content — Terza’s agreement with Anthropic includes an unconditional no-training commitment.

6. Data Retention

Retention periods are also published in Terza’s Data Retention Schedule, which governs the technical implementation of deletion and de-identification jobs.

7. Your Rights

7.1 Teachers

Teachers may access, correct, or request deletion of their own account information by contacting privacy@terza.app.

7.2 Parents and Guardians of Minor Students

A parent or guardian who has completed the consent process for a Minor Student may, at any time:

• Withdraw consent. This immediately stops future recording of that Minor Student and automatically deletes their stored audio recordings, transcripts, and progress-record content. The consent and withdrawal record documenting the request itself is retained for compliance purposes and is not affected by this deletion.
• Request access to the personal information Terza holds about their child.
• Request deletion of any other personal information Terza holds about their child that is not automatically deleted upon withdrawal.

Requests can be made by replying to any consent-related email, through the withdrawal link provided in those emails (which requires an explicit confirmation step before any deletion occurs), or by emailing privacy@terza.app.

8. Third-Party Service Providers

Teachers provide Terza with personal information about their Students and their Students’ Parents, including names, contact information, and lesson audio recordings (“Third-Party Data”). By providing Third-Party Data, the Teacher represents and warrants that they have authority to provide such information or that verifiable parental consent has been obtained in accordance with Section 4 (for Minor Students), and that the Teacher has informed the relevant individuals how their information will be collected and used by Terza to provide the Service.

Terza shares personal information only with service providers necessary to deliver the Service, under contractual terms restricting their use of the data:

Terza does not use Supabase’s built-in AI convenience features (such as AI-assisted SQL generation), because these route through an OpenAI sub-processor outside Terza’s approved processing chain.

If Terza adopts any additional third-party service that receives lesson audio, transcripts, or Minor Student personal information, this Policy and the applicable parental consent notices will be updated to name that provider before it is put into use.

9. Data Security and Disclosure

Terza applies row-level security to all tenant data in its database, encrypts data in transit, and encrypts lesson audio recordings at rest using per-teacher encryption keys held in the Teacher’s iCloud Keychain. These keys are not accessible to Terza or its infrastructure provider, meaning stored audio recordings cannot be decrypted without the originating Teacher’s device-held key. Terza limits internal access to other personal information (transcripts, observations, practice notes) to what is necessary to operate the Service. A formal written information security program, with a designated coordinator and annual risk assessments as required under the COPPA 2025 Final Rule, is available and can be reviewed on request by emailing security@terza.app.

In the event of a merger, acquisition, reorganization, bankruptcy, asset sale, or similar transaction involving Terza or substantially all of its assets, personal information held by Terza may be disclosed to the prospective counterparty as part of due diligence and may be transferred to the successor entity as part of the transaction.

Terza may disclose personal information to government authorities, law enforcement, regulators, courts, or other third parties where Terza believes in good faith that disclosure is: (a) required by applicable law, regulation, court order, subpoena, or other legal process; (b) necessary to protect the rights, property, or safety of Terza, its users, or the public; (c) necessary to detect, prevent, or address fraud, security, or technical issues; or (d) necessary to enforce Terza’s Terms of Use or this Policy. Terza will make reasonable efforts to notify affected Teachers before disclosing their personal information pursuant to legal process, unless prohibited by law or court order from doing so.

10. International Data Transfers

Terza’s backend infrastructure is hosted in Canada. Anthropic’s API processing occurs in the United States by default. Where personal information is transferred internationally, this occurs under contractual safeguards, including Standard Contractual Clauses where applicable. Personal information processed by Anthropic in the United States may be subject to U.S. law, including lawful access by U.S. government authorities under applicable national-security and law-enforcement legislation.

11. Children’s Privacy — Summary

Terza does not knowingly permit children to create or operate their own accounts. Personal information relating to Minor Students is collected only in connection with a Teacher-initiated lesson recording after a parent or guardian has directly completed Terza’s verifiable parental consent process, as described in Section 4.

This Policy, together with the consent notice presented to parents, is intended to satisfy COPPA’s requirement that parental consent notices identify third-party recipients of a child’s information by name and explain the purpose of each disclosure.

12. Changes to This Privacy Policy

Where changes are material, we will notify Teachers by email or in-application notification at least 30 days before the changes take effect and will update parental consent notices accordingly for any newly enrolled Minor Student. The updated Policy will be posted at terza.app/privacy with a revised effective date.

13. Contact Us

Terza — Privacy
privacy@terza.app
terza.app