Privacy Policy

Effective September 11, 2026

This policy describes how Baiz (“we”, “us”) handles information when you use the iOS app, this website, and related APIs.

Who we are

Baiz is a language learning and translation service for English, Mandarin, and Cantonese. Reach us at baiz_remove_@ryanly.ca.

Information we collect

We collect the following, depending on how you use the app:

• Account. Sign-in uses Google through Firebase Auth. We receive your Google user id, email address, and display name (and a profile photo URL if Google provides one). We do not receive your Google password. Guest and anonymous sign-in are not offered.
• Translation and learning data. We may store recent conversation transcripts (source text, translation, pinyin, and language labels), quiz progress, example sentences you generate, and preferences such as dialect, voice, and keyboard settings. This is saved on your device and, when you are signed in, in Firestore under your user id.
• Voice and typed input. When you use live translation, microphone audio is streamed to Google Gemini so it can transcribe and translate in real time. We may also send audio to Deepgram for on-screen transcripts. Typed text from the keyboard extension is sent to Google Gemini only when you ask to translate it. We do not keep raw audio files after a session ends.
• Usage and account status. The token server stores daily session counts, your plan tier, optional custom quota, and whether an account is blocked, so we can run the service fairly.
• Device storage. The app keeps a signed-in session and recent history on the device so the product can work offline and across launches. We do not use advertising or analytics cookies on this website.
• Technical logs. Hosts may record IP address, user agent, and request metadata in server logs for security and reliability.

We do not collect payment card details. There are no in-app purchases at this time. We do not run third-party advertising SDKs. This public website is static and does not read your Firestore data.

How we use it

• Create and sign you into your account
• Provide live translation, keyboard translation, and quizzes
• Sync your history and preferences across devices
• Issue short-lived translation tokens and enforce daily limits
• Keep the service secure, debug issues, and prevent abuse

We do not sell your personal information or share it for ads.

Who processes data for us

We use other companies to run the product. They process data on our instructions:

• Google: authentication (Firebase Auth), database (Cloud Firestore), and translation / speech models (Gemini Live, Gemini TTS, Vertex AI)
• Deepgram: optional streaming speech-to-text for on-screen transcripts
• Amazon Web Services: hosting the token and admin server for this site
• Google Cloud Storage: delivering iOS app updates

Firestore access is limited by security rules: a signed-in Google user can only read and write their own /users/{userId} document and subcollections. Anonymous accounts are denied. Admin tools use a server SDK and an allowlisted Google account; they are not available through the public pages.

Retention and deletion

We keep account and app data while your account exists. You can revoke Baiz’s access from your Google account. There is not currently a self-serve button to erase the login itself. Contact baiz_remove_@ryanly.ca if you want your account and remaining data deleted, and we will do that.

Your choices

Depending on where you live, you may have rights to access, correct, delete, or export personal information, or to object to certain processing. Contact baiz_remove_@ryanly.ca and we will handle the request for this app. If you are in the EEA or UK, we process this information to provide the service you asked for and, where needed, for security.

Children

Baiz is not directed at children under 13. Google sign-in is for the person who creates the account. We do not knowingly create login accounts for children under 13.

Security

Access to your app data is limited by signed-in Google accounts and Firestore rules. Translation sessions use short-lived tokens rather than embedding a long-lived cloud key in the client. No method of transmission or storage is perfectly secure.

Changes

If this policy changes in a material way, we will update the effective date on this page. Continued use after that date means you accept the updated policy.

Related: Terms of Use.