Privacy Policy
1. Introduction
InterpreterX ("InterpreterX," "we," "us," or "our") provides a real-time AI assistance tool for professional interpreters through a website, Chrome extension, and related API services (collectively, the "Service").
The Service is operated by the entity operating InterpreterX ("Operator"). Registered operator name and address are available upon request at support@interpreterx.online. This Privacy Policy explains what information we collect, how we use it, and the choices available to you.
2. Scope
This policy applies to:
- The InterpreterX website at interpreterx.online;
- The InterpreterX Chrome extension;
- API endpoints used to authenticate accounts, authorize devices, meter usage, and deliver session credentials;
- Account, billing, and transactional email communications related to the Service.
This policy does not cover third-party websites, video platforms, or call services you use alongside InterpreterX. Those services have their own policies.
3. Information we collect
3.1 Information we do not intend to collect on our servers
We design the Service so that our servers do not store the audio of your calls or the live transcript text produced during a session. Usage metering on our servers is limited to session identifiers, device identifiers, and elapsed seconds—not the content of conversations.
3.2 Categories of information
| Category | Examples | Where processed |
|---|---|---|
| Account information | Name, email address | Authentication provider; our account database |
| Credentials | Password (hashed by auth provider) | Authentication provider only |
| Device authorization | Device ID, device label, session tokens | Extension storage; our API |
| Usage data | Session duration in seconds, plan entitlements | Our API and database |
| Billing data | Subscription status, purchase references | Payment processor; our database (metadata) |
| Technical metadata | IP address, browser type, request timestamps | Infrastructure providers |
| Local session content | Transcript lines, glossary, settings | Your browser / extension storage |
| Live audio | Tab or display audio during a session | Real-time processing provider (see below) |
4. Audio capture and processing
4.1 How audio is captured
When you start a session, you choose an audio source. For most interpreting workflows, InterpreterX captures audio from a browser tab or shared display surface (for example, a remote call or VRI platform). This is distinct from your computer microphone, which may be used separately for optional features such as pre-recorded opening phrases played into a call.
4.2 Real-time processing provider
To produce live transcription and translation, audio is streamed in real time to our contracted real-time audio processing provider. InterpreterX maintains a signed Business Associate Agreement covering applicable audio processing performed by that provider for the Service.
We do not retain call audio on our servers as a permanent recording. Retention by the processing provider is governed by that provider's policies and our agreement with them.
4.3 Transcription and translation
Transcription and real-time translation output appears in the extension during your session. That text may exist in your browser memory and, depending on your settings and actions, in local extension storage on your device. We do not upload completed transcripts to our account database.
4.4 Edited lines and retrainslation
If you edit transcript lines, those edits remain in your local session unless you save them locally. Certain auxiliary features that send isolated text to our API for re-translation or dictionary lookup may be unavailable in HIPAA-safe mode. Where active, such features could transmit text you submit; use them only with terms you are permitted to process.
4.5 Glossary and definitions
Terms you add to a personal glossary may be sent to the real-time processing provider as context to improve consistency during a session. Saved definitions and glossary entries may be stored locally and, for some settings, synchronized through browser sync storage tied to your browser profile.
5. Local and browser storage
- Chrome extension storage: Session tokens, device identifiers, preferences, optional saved transcripts, glossary, and openings.
- Website local storage: Authentication session state and short-lived signup or verification helpers.
- Cookies: We do not use advertising cookies. Infrastructure and auth providers may set strictly necessary cookies or similar technologies for security and session management.
6. Account, device, usage, and billing
Account registration uses our authentication provider (Supabase). Profile information is mirrored to our commercial API to manage trials, entitlements, and device linking.
Device authorization allows the extension to obtain API access after you approve a device through your account. Device tokens are stored locally in the extension.
Usage minutes are measured server-side while a session is active to enforce plan limits and prevent abuse. We store seconds consumed, not conversation content.
Payments and subscriptions are processed by Lemon Squeezy as merchant of record when checkout is enabled. We receive billing status and identifiers needed to activate your plan, not full payment card numbers.
Transactional emails (verification, password reset, security notices) are sent through our authentication email infrastructure, which may use Resend as an email delivery provider configured in Supabase.
Our API and website are hosted on Cloudflare (Workers, Pages, and D1 database). Cloudflare processes network metadata necessary to deliver and protect the Service.
7. Analytics
We do not operate third-party marketing analytics on the Service as of the last updated date above. Internal administrative metrics aggregate usage seconds and account events without conversation content.
8. How we use information
- Provide, maintain, and improve the Service;
- Authenticate users and authorize extension devices;
- Meter usage, manage trials, and process subscriptions;
- Send transactional communications;
- Detect abuse, fraud, and security incidents;
- Comply with law and enforce our Terms;
- Respond to support and compliance requests.
9. Legal bases (EEA/UK)
Where the GDPR or UK GDPR applies, we rely on: (a) performance of a contract; (b) legitimate interests (security, product improvement, fraud prevention) balanced against your rights; (c) consent where required (for example, optional communications); and (d) legal obligation.
10. Sharing and subprocessors
We share information with service providers that help us operate the Service, under contracts requiring appropriate safeguards. See our Subprocessor List for categories of providers, purposes, and links to their policies.
We do not sell personal information. We do not share personal information for cross-context behavioral advertising.
11. International transfers
We and our subprocessors may process information in the United States and other countries. Where required, we use appropriate transfer mechanisms such as standard contractual clauses. Contact us for more information about safeguards for your region.
12. Retention
| Category | Typical retention |
|---|---|
| Account profile | While your account is active, plus a reasonable period after deletion |
| Usage records | As needed for billing, tax, and dispute resolution |
| Auth audit metadata (hashed) | Security and compliance period defined internally |
| Local transcript content | Until you clear it or remove the extension; may clear on extension update |
| Live audio at processor | Per real-time provider policies; not stored by us as recordings |
13. Security
We use administrative, technical, and organizational measures designed to protect information, including encryption in transit (TLS), access controls, and separation of account systems from call content on our servers. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
13.1 Internal access
Access to production systems is limited to personnel who need it for their role and is subject to authentication and logging.
13.2 Incident response
We maintain procedures to investigate suspected incidents and will notify affected parties or regulators where required by law.
14. Your rights and choices
Depending on your location, you may have rights to access, correct, delete, or export personal information; object to or restrict certain processing; and withdraw consent. To exercise rights, contact support@interpreterx.online. We may verify your request.
Account deletion: You may request deletion of your account and associated server-side profile data by contacting support. Local extension data may remain until you remove the extension or clear storage.
15. HIPAA and regulated workflows
InterpreterX is designed to support HIPAA-regulated interpreting workflows. Applicable real-time audio processing is performed under a signed Business Associate Agreement with our audio processing provider. That BAA covers processing performed by that provider—not every feature, subprocessors, or your own organization’s obligations.
HIPAA compliance in any deployment is a shared responsibility. You and your organization must obtain necessary authorizations, configure the Service appropriately, train workforce members, secure devices, and execute any Business Associate Agreement required between you and InterpreterX or its Operator.
HIPAA-ready does not mean that every possible use of the Service is automatically HIPAA-compliant. For enterprise compliance and BAA inquiries, contact support@interpreterx.online.
16. Children
The Service is intended for professional interpreters at least 18 years of age. We do not knowingly collect personal information from children below that age.
17. California privacy (CCPA/CPRA)
California residents may have rights to know, delete, correct, and opt out of certain sharing. We do not sell or share personal information for cross-context behavioral advertising. To submit a request, email support@interpreterx.online.
18. Legal requests
We may disclose information if required by law, court order, or governmental request, or to protect rights, safety, and security. We review requests carefully and may notify you where permitted.
19. Changes to this policy
We may update this Privacy Policy from time to time. Material changes will be posted on this page with an updated "Last updated" date. Continued use after changes become effective constitutes acknowledgment where permitted by law.
20. Contact
Questions about this policy or our privacy practices: