1) Who Operates SIMO
SIMO is operated by Canoe Interpretation. If you have questions or want to make a privacy request, email privacy@canoeinterpretation.com.
2) What SIMO Processes
SIMO is built for live interpretation-style experiences. Depending on how you use the app, SIMO may process:
- Meeting audio: audio shared from a Zoom meeting for speech-to-text processing.
- Captions and translations: transcript text and translated text produced from that audio.
- Session metadata: room identifiers/codes, language selections, timestamps, and meeting identifiers used to route streams.
- Operational telemetry: logs and metrics used to keep the service reliable and secure (for example: request timing, error rates, and basic diagnostics).
3) Why We Process It
- To provide real-time captions, translation, and optional text-to-speech playback.
- To operate the Zoom integration (including webhook events and meeting session lifecycle).
- To secure and maintain the service (abuse prevention, incident response, and troubleshooting).
4) Service Providers
SIMO uses cloud service providers to deliver real-time speech features. In the current Zoom runtime and supported deployment configurations:
- Deepgram: server-side speech-to-text for Zoom RTMS audio ingest.
- OpenAI: server-side machine translation and default text-to-speech synthesis for Marketplace production.
Providers receive only the data needed for the function being performed (for example, audio for transcription or text for translation). If provider configuration changes in production, this section is updated accordingly.
5) What We Do Not Do
- We do not sell meeting content (audio, transcripts, translations).
- We do not run advertising based on meeting content.
- We do not require end users to create a SIMO account to see captions or listen to TTS (unless an organizer chooses to restrict access).
6) Data Retention
SIMO is designed for real-time use. In current production operation:
- Audio and transcript content are processed in-stream for real-time delivery and are session-bound/transient only; Marketplace production does not store them as a durable transcript or raw-audio archive.
- Room/session configuration metadata and meeting-to-room routing information may be retained for up to 365 days to run access, routing, support, and security workflows.
- Short-lived listener playback state may be held in transient memory for Zoom audio coordination and expires automatically.
- Operational logs are retained for up to 30 days for reliability, troubleshooting, abuse prevention, and incident response.
- Metrics aggregates are retained for up to 90 days for reliability and capacity planning.
- Managed database backups may be retained for up to 30 days under the managed platform backup lifecycle.
7) Uninstall and Deauthorization
If SIMO is removed from Zoom, Zoom sends a deauthorization event to SIMO. Current production behavior stops active Zoom session state for that meeting and completes the required Zoom data-compliance callback.
Because SIMO does not currently create a durable transcript archive, there is no stored full-meeting transcript to delete as part of uninstall. Retained configuration or operational records continue to follow the practices described in this policy.
8) Your Privacy Rights
Depending on where you live, you may have rights to access, delete, correct, or receive a portable copy of personal information associated with your use of SIMO.
To exercise these rights, email privacy@canoeinterpretation.com with enough information for us to locate the relevant room/session metadata, such as the event date, room code or room name, meeting UUID if available, and the email address used to contact support. We may need to verify the request before acting on it.
Because Marketplace production does not create a durable transcript or raw-audio archive, access/deletion requests for meeting content generally apply to transient session state while active and to retained room/session metadata, logs, or support records after the session ends.
9) Security
- We use HTTPS/TLS to protect data in transit for production endpoints.
- Secrets (API keys, tokens) are managed via environment configuration and are not intended to be exposed client-side.
- We monitor service health and respond to security incidents using documented procedures.
10) Cookies and website analytics
The public SIMO pages (like /support and /privacy) are informational and do not require a user login.
Some administrative functionality may use authentication tokens/cookies for operators.
With your permission, we use Google Analytics cookies on public informational pages to understand website traffic. Analytics does not load until you select Accept. It receives public page paths and basic visit/device information; we exclude URL query strings, meeting rooms, account and admin pages, meeting content, and form contents. Advertising personalization and Google signals are disabled. Google processes analytics data under its Privacy Policy. You can decline or withdraw permission using Analytics settings at the bottom of public pages. Your choice is stored in your browser.
11) Your Responsibilities In Meetings
Only use SIMO when you have permission to enable meeting content sharing and to process meeting audio for captions/translation. Meeting hosts and organizations are responsible for providing any notices and obtaining any consents required by their policies or laws.
12) Changes To This Policy
We may update this policy from time to time. The effective date at the top reflects the current version.
Quick contact: privacy@canoeinterpretation.com