---
title: "Security at Speakeroo"
description: "Security at Speakeroo: encryption, access, subprocessors, the read-only MCP server, incident response, and how to report a vulnerability."
url: "https://speakeroo.app/security"
---

# Security at Speakeroo

How we protect the data people send to Speakeroo, and to its MCP server.

Last updated: November 20, 2026

## Encryption

- Every connection to Speakeroo uses HTTPS, including the website, the mobile app, the public API and mcp.speakeroo.app.
- Data is encrypted at rest by the infrastructure that stores it.
- Production secrets live in Cloudflare Worker secrets and Convex environment variables, never in the web client or the repository.

## Access

- Access to production systems is limited to the people who need it to run and support the service, under a duty of confidentiality.
- Site sign-in is handled by WorkOS. The MCP server also accepts anonymous calls, with no account.

## Subprocessors

The MCP connector runs on Cloudflare, Convex, WorkOS, OpenAI, Google's Gemini API, Langfuse, PostHog and Sentry. Some providers transcribe or analyse content to produce a response; others deliver traffic, count usage or record errors.

The [Data Processing Addendum](https://speakeroo.app/dpa) describes subprocessor purposes and locations, and gives organization owners 30 days' notice before a new one starts.

## The MCP server

- The MCP server is read-only. Its seven tools return coaching and reference material, and they change no account, practice history, score or setting.
- Text and audio sent to it are used to produce the response and are not stored afterwards. Inline audio is deleted when the analysis settles.
- An anonymous caller's allowance is counted from a keyed hash of the IP address and the UTC day. The address itself is not stored, though Cloudflare sees it to deliver and rate-limit requests.
- Tool usage is counted without content: which tool, whether it worked, how long it took, the context chosen, the word count, and which client connected.

## Incident response

- If a breach affects an organization's information under our DPA, we tell them without undue delay and within 72 hours of becoming aware, with what we know and what we are doing about it.

## Certifications and audits

- We are a small team. We do not hold SOC 2 or ISO 27001 certification, and no third party audits our systems today.
- Our infrastructure and AI providers publish their own compliance reports. We answer written security questions about how we protect data.

## Reporting a vulnerability

- Write to [support@speakeroo.app](mailto:support@speakeroo.app) with what you found and how to reproduce it. We will read it and tell you what we plan to do.
- We do not run a paid bug bounty.

Read the [Privacy Policy](https://speakeroo.app/privacy), the [Data Processing Addendum](https://speakeroo.app/dpa) and the [Terms of Use](https://speakeroo.app/terms).

© 2026 Simple Pi Pty Ltd. All rights reserved.
