1. Who we are

MathVoice operates the Studio web application at mathvoice.app and the REST API at api.mathvoice.app. References to "MathVoice", "we", "us", or "our" refer to the MathVoice service and its operators. Contact: [email protected].

2. What data we collect and why

2.1 Formula data (API calls)

When you use the Studio or an application built on the MathVoice API, the following data may be sent to our servers:

• IntentResult JSON — a structured object like {"type":"REPLACE_VALUE","target":{"role":"denominator"},"value":{"raw":"n"}}. This contains mathematical intent, not personal information.
• Formula LaTeX strings — the mathematical formulas you are editing (e.g., \frac{-b}{2a}). These are sent to the /v1/intent and /v1/mutate endpoints as formulaContext.latex.

We use this data to process your request and return a result. We do not store formula data beyond the duration of a single API request unless you have enabled session logging for debugging (opt-in only, available to Institutional accounts).

2.2 Voice audio

Default (Web Speech API): Voice audio is processed by your browser's built-in speech recognition. In Google Chrome and other Chromium-based browsers, audio is transmitted to Google's servers for recognition — it does not remain on your device. MathVoice itself never receives your audio; only the recognised text transcript is sent to the MathVoice intent API. If your institution requires that no audio leave the device, use Firefox with a local speech engine or enable the on-device Whisper mode. We recommend disclosing this to students and obtaining appropriate consent under FERPA/GDPR.

Whisper ASR backend (optional, off by default): If you or your institution enables the Whisper provider, audio recordings are transmitted to OpenAI's servers for transcription. You are responsible for obtaining appropriate consent under applicable law (FERPA, COPPA, GDPR) before enabling this mode for students. See your institution's DPA with OpenAI.

2.3 API usage logs

Our API server logs standard access data: endpoint path, HTTP method, status code, response time, and API key prefix (e.g., mv_live_abc…). We do not log request bodies. Logs are retained for 30 days for security and billing purposes.

2.4 Account data

If you create a Pro or Institutional account, we collect your email address and billing information. Payment is processed by Stripe; MathVoice does not store card details.

3. FERPA compliance

MathVoice is designed for FERPA-compliant use in US educational institutions. The FERPA compliance claim rests on two facts:

1. Voice audio in Chrome is sent to Google's servers via the Web Speech API — not to MathVoice, and not stored by MathVoice, but institutions should be aware of this third-party data flow. Firefox with a local speech engine, or the on-device Whisper mode, avoids this.
2. The only data transmitted — IntentResult JSON and LaTeX formula strings — does not contain student names, IDs, or any directly identifying information. A formula like \frac{-b}{2a} is not a student education record.

For institutional deployments where student-authored formulas might be considered education records, a signed Data Processing Agreement (DPA) is available (see Section 7). Under FERPA, MathVoice acts as a "school official" processing records for legitimate educational purposes.

4. COPPA (Children under 13)

MathVoice does not offer direct-to-student accounts for children under 13. The Studio may be used by students under 13 in an institutional context under a signed DPA with the school or district, which acts as the COPPA-compliant intermediary. We do not knowingly collect personal information from children under 13 outside of a signed institutional agreement.

5. GDPR (EU residents)

For users in the European Economic Area: MathVoice processes personal data (email, billing, API logs) on the legal basis of contract performance (Art. 6(1)(b) GDPR) for account holders, and legitimate interests (Art. 6(1)(f)) for security logging. Formula data and IntentResult objects are not personal data. You have the right to access, correct, or erase your personal data by emailing [email protected].

6. Data retention

• API access logs: 30 days, then permanently deleted
• Account data: retained while account is active; deleted within 30 days of account closure on request
• Formula/IntentResult data: not retained beyond request processing
• Backups: encrypted, retained for 7 days, then deleted

7. Data Processing Agreement (DPA)

A signed Data Processing Agreement is available for institutional customers. The DPA covers:

• Description of processing activities
• Data subject rights obligations
• Security measures and breach notification (72-hour notification commitment)
• Sub-processor list (Anthropic for LLM intent parsing; OpenAI optional for Whisper)
• Data deletion commitments
• Standard Contractual Clauses (EU SCCs) for cross-border transfers

Request a DPA: [email protected]

8. Security

• All API traffic over TLS 1.3
• API keys stored as bcrypt hashes, never in plain text
• Infrastructure on Vercel/AWS with SOC 2 Type II certification
• No production data in development or staging environments

9. Changes to this policy

We will notify institutional customers of material changes by email at least 30 days before the change takes effect. The current version is always at mathvoice.app/legal/privacy.