LIVE INTERPRETER · PRIVACY
Privacy Notice
This notice explains how information may be processed when you use Run Up Studio Live Interpreter. It applies only to this real-time voice interpretation product.
1. Information the product may process
- Microphone audio: live speech captured after you grant permission and start a session.
- Speech and translation content: interim recognition, confirmed transcripts, translated text, generated speech requests, custom vocabulary, and scene settings.
- Account information: email address, account identifier, authentication status, preferences, and subscription status where account features are enabled.
- History and settings: conversations or configuration you choose to save locally or synchronize through a future account feature.
- Technical information: browser, device, language, approximate network and region signals, error events, security events, latency, provider-selection and fallback information.
- Billing information: plan, transaction identifiers, payment status, tax and receipt information. Full payment-card data should be handled by the hosted payment provider rather than stored by Run Up Studio.
- Support information: messages, screenshots, logs, and other details you send when asking for help.
2. When microphone processing begins
The service should not begin listening until you grant browser or operating-system permission and activate the listening control. You can stop the session through the product control and can revoke microphone permission through your device or browser settings.
You are responsible for notifying other participants that their speech is being processed and obtaining any consent required by applicable law.
3. How voice and language data are used
Voice and language data may be used to recognize speech, determine language direction, translate content, generate subtitles, produce spoken output, maintain conversational context, troubleshoot a requested issue, prevent abuse, and improve service reliability.
Live audio is intended to be transient by default. Run Up Studio should not intentionally retain raw session audio after processing unless a clearly labeled recording, history, quality-review, support, or account-sync feature is enabled and the user is informed before retention begins.
4. Third-party processing
Depending on the mode selected and actual fallback path, microphone audio, transcripts, translated text, or speech-synthesis requests may be sent to one or more speech-recognition, machine-translation, language-model, text-to-speech, hosting, authentication, analytics, or payment providers.
The product should identify the active or actual processing path where technically practical. Providers may process information in different regions and under their own service terms, privacy notices, retention settings, and contractual controls.
Before production launch, Run Up Studio must maintain and publish an accurate provider list or an equivalent in-product disclosure that matches the real configuration.
5. Local storage and conversation history
The current browser experience may use device-local browser storage for settings, temporary credentials entered for local testing, and conversation history. Information stored locally remains on that browser profile until you clear it, use an available delete control, or the browser removes it.
Future account synchronization must be opt-in or clearly disclosed, must identify what is uploaded, and must provide deletion controls. Do not use a shared device for sensitive conversations unless you clear visible and stored content afterward.
6. Purposes of processing
- Provide real-time recognition, translation, subtitles, and voice output.
- Maintain accounts, plan limits, preferences, and billing status.
- Measure latency, uptime, errors, and feature reliability.
- Detect abuse, protect users, and secure the service.
- Respond to support, privacy, and legal requests.
- Comply with legal obligations and resolve disputes.
We do not sell the content of private conversations. Any future advertising or cross-context behavioral advertising use would require a separate, prominent update and any choices required by law.
7. Retention
Raw live audio should be retained only for the shortest time needed to complete the active processing request unless the user knowingly enables another purpose. Transcript, translation, account, billing, security, and support records may have different retention periods.
Exact production retention periods are not yet final. They must be published before paid general availability and must match provider configuration, backups, fraud requirements, legal obligations, and user deletion controls.
8. Security
We use reasonable technical and organizational measures appropriate to the service, such as encrypted network transport, access controls, secret management, hosted authentication, logging controls, and separation of client and server credentials where implemented.
No system can guarantee absolute security. Do not use the service for secrets or high-risk information that should not be processed by an automated online service.
9. Your choices and requests
- Do not grant microphone permission or stop listening at any time.
- Disable spoken output when subtitles alone are sufficient.
- Clear visible content and locally saved history.
- Revoke browser microphone permission.
- Cancel account sync or subscription features where available.
- Request access, correction, deletion, or a copy of account-linked information.
- Object to or restrict certain processing where applicable law provides that right.
Requests may require identity verification. Some billing, security, fraud, or legal records may need to be retained.
10. Children
Live Interpreter is not directed to children under 13, and we do not knowingly collect personal information from a child under 13 without legally required authorization. If you believe a child has submitted information, contact us so the situation can be reviewed.
11. International use
The service and its providers may process information in countries other than your own. Where required, appropriate contractual or legal transfer mechanisms should be used. Availability may be limited by region, provider support, sanctions, export restrictions, or local law.
12. Changes and contact
We may update this notice when providers, storage, accounts, payments, or product behavior changes. Material changes should be communicated through the product or account channel where reasonably practical.
Privacy questions and requests may be sent to [email protected]. The final legal entity name and mailing address will be published before paid general availability.
This draft intentionally avoids claiming that audio is never stored. Final language must be verified against every active provider, fallback route, log, browser-storage behavior, account feature, and backup before launch.