Back to home
Privacy Policy

How Bingelang handles your data

This policy explains what information Bingelang collects, how it is used, and the choices you have regarding your account and learning data.

Last updated: September 1, 2026

Who we are

Bingelang is a language-learning platform focused on immersive learning through video, reading, and speaking practice.

If you have questions about this policy or want to request help with your data, you can contact us at contact@bingelang.com.

What we collect

Depending on how you use Bingelang, we may collect:

  • Account information such as your email address, login method, and username.
  • Profile information you choose to provide, including your public username.
  • Learning data such as watch time, reading progress, streaks, achievements, and leaderboard activity.
  • For signed-in accounts, theme announcement views, theme trials, confirmed choices, dismissals, and observations of your saved theme.
  • Anonymous landing-page acquisition events such as a landing view, primary call-to-action click, language selection, and signup step.
  • Technical data such as device, browser, IP-related logs, and security events.
  • Messages you send to us through the contact form or support channels.

How we use your data

  • To create and manage your account.
  • To let you sign in, including with Google Sign-In.
  • To save your progress and personalize your experience.
  • To power features such as streaks, achievements, and the leaderboard.
  • To respond to support requests and improve the product.
  • To understand which visual themes people choose and return to, using aggregate administration reports.
  • To understand whether the public landing page helps new visitors find a language and create an account.
  • To protect the platform against abuse, fraud, or unauthorized access.

First-party acquisition measurement

Bingelang measures a limited funnel from the public landing page to a newly created account. Signed-in visitors and browsers already recognized as having an account are excluded from this acquisition funnel.

A random first-party browser identifier connects landing views, main calls to action, language choices, and signup steps. These events do not contain an email address, IP address, user-agent string, or advertising profile. Administrators see aggregate counts rather than individual visitor or account identities.

Before a conversion is counted, Bingelang verifies that the authenticated account was created after the tracked signup visit. Logging into an existing account is not counted as a new-account conversion. A non-identifying browser flag remembers that an account has been seen so later signed-out visits on that browser stay outside the new-visitor funnel.

Third-party services

Bingelang uses trusted service providers to operate the product, including:

  • Supabase for authentication, database, and related backend services.
  • Google for Sign in with Google and certain AI or speech features when enabled.
  • Cloudflare for hosting, delivery, and performance.
  • Resend or comparable email infrastructure for transactional communications.

These providers only receive the information needed to perform their role for Bingelang.

Public information

Your public username may be shown in community-facing features such as the leaderboard. Your email address is not intended to be shown publicly.

Data retention

Theme measurement events are linked to your account and retained for up to 180 days. They contain theme choices and event times, without email addresses, browsing URLs, or device identifiers. Pending theme events are kept in your browser for up to 24 hours for delivery retries. Your theme preference itself stays in your browser until you change it or clear the stored preference.

We keep account and learning data for as long as your account remains active or as needed to provide the service, comply with legal obligations, resolve disputes, and enforce our agreements.

The anonymous acquisition context expires in the browser after 30 days. The non-identifying account-known browser flag expires within 13 months. Raw acquisition events are retained for no longer than 13 months so that short-term landing-page performance can be compared without keeping anonymous browser identifiers indefinitely.

Your choices

You can contact us to request access, correction, or deletion of your account data.

You can also update some account information directly inside the product, such as your public username.

Changes to this policy

We may update this Privacy Policy from time to time. If we make material changes, we will update the date at the top of this page.