Privacy Policy
Last updated: March 16, 2026
This Privacy Policy applies to the Chrome extension LinguaBridge Global Language Coach and the related LinguaBridge backend services used for sign-in, billing, AI relay, and Azure speech token issuance.
1. Data We Process
Depending on the features you use, LinguaBridge may process:
- Text you select on web pages
- Text you type into translation, reply, study, or speech input fields
- Images you explicitly submit for OCR translation
- Speech-related usage metadata such as TTS character count and STT duration
- Account and billing data such as Google/Firebase sign-in identity, points balance, and usage history
- Configuration data such as language pair, model, voice, shortcuts, and UI preferences
- Technical metadata needed for operation and security, such as request identifiers, timestamps, and logs
2. How We Use Data
- To provide translation, reply drafting, study explanation, OCR, TTS, and STT features
- To authenticate users and maintain billing access
- To authorize, meter, and record usage for points-based billing
- To operate AI relay and Azure speech token endpoints
- To debug service failures, prevent abuse, and improve reliability
3. Where Data Is Sent
To deliver the product, data may be sent to:
- LinguaBridge backend services hosted by the developer for authentication, billing, AI proxying, and speech token issuance
- OpenAI, Anthropic, and DeepSeek APIs when you use supported AI features through the LinguaBridge backend
- Azure Speech services for text-to-speech and speech-to-text related features
- Google Firebase Authentication for sign-in and identity verification
- Stripe for checkout and payment processing
When you use AI features, your prompts (including selected text, typed input, and images) are forwarded directly to the chosen model provider's API through the LinguaBridge relay server. The relay server does not store, log, or retain your prompts in any form.
Your use of those third-party services is also subject to their own terms and privacy policies.
4. Storage and Retention
- The extension stores settings and session-related values in Chrome extension storage.
- The backend stores account records, billing balances, policy settings, and usage history in Google Firestore.
- Operational logs may include identifiers, timing, status, and limited request metadata for debugging and abuse prevention.
- We do not claim that user-submitted content is never retained; some content and metadata may be transiently processed or stored as required to operate the service.
5. User Control
- You can stop using the extension at any time.
- You can remove the extension to clear extension-managed browser data.
- You can stop using billing-backed features by signing out.
- You can request deletion or support through the contact channel listed in the Chrome Web Store listing.
6. Security
- Network communication uses HTTPS.
- Secrets are intended to be stored server-side or in protected local development files, not committed to source control.
- Users should not submit passwords, payment card numbers, or highly sensitive personal information into AI input fields.
7. Changes
We may update this policy as the product or data practices change. The latest version date appears at the top of this page.
8. Contact
For privacy or support questions, contact jiu.yun@foxmail.com.