Privacy Policy

This policy applies to berlingo.app and the Berlingo apps for iOS and Android. Features may differ by platform.

• Public website pages do not require an account. Account-based learning, synchronization and Pro access require sign-in.
• Contact the Berlingo operator about privacy at linhdndev@gmail.com.

We process the data needed to operate Berlingo and the information you choose to provide.

• Account: Firebase user identifier and the name and email shared by Apple or Google, including an Apple private relay address. We do not receive your Apple or Google password.
• Learning: level, goals, timezone, preferences, answers, scores, activity, review schedules, bookmarks and progress. Where available, optional leaderboard participation can show your chosen display name, rank and XP to other participants; name visibility is configurable.
• Purchases: products, transactions and subscription status needed to verify and restore Pro. We do not receive your complete payment card or bank details.
• Support: your messages and contact details. Network requests also expose connection and request information to our hosting and media providers. Optional mobile crash reports are described below.

Berlingo uses Google Sign-In through Firebase Authentication to identify your account. It requests only basic identity permissions (openid, email and profile).

• Access: Google may provide your account identifier, name, email address and profile photo. Berlingo does not request access to Gmail messages, Google Drive files, Calendar or contacts, and never receives your Google password.
• Use: we authenticate you, display your profile and associate your account with learning progress. Your verified email may receive learning reminders, enabled by default for eligible accounts. Disable reminders in Profile or use the unsubscribe link in an email.
• Storage and sharing: Firebase stores your authentication identity. Cloudflare hosts the API and database for your account identifier, learning data and reminder email/preferences, and delivers reminder emails. Your name and photo can appear in the app. We use providers to operate these features; we do not sell Google sign-in data or share it with advertisers or use it for targeted advertising.
• Retention and control: Google-related account data is retained as described in the retention and deletion sections below. You can remove Berlingo access in your Google Account connections. Revoking access does not delete existing Berlingo data; use Profile deletion and contact linhdndev@gmail.com to request removal of remaining authentication data.
• Berlingo’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

• Google API Services User Data Policy
• Google Account
• Google Privacy Policy

We use data to provide and protect the learning service.

• Authenticate users, save and synchronize progress, calculate reviews and statistics, and personalize learning recommendations.
• Verify and restore Pro, respond to support and privacy requests, and maintain security and reliability.
• We do not sell or rent personal data, or use learning history for targeted advertising. Embedded media providers have their own practices, described below.

Providers may process data outside your country under their published policies and terms.

• Apple, Google and Firebase provide authentication. Cloudflare hosts the API, database and content delivery. When configured, Google Analytics on the website uses cookies and processes usage, device and network information to measure site activity.
• Apple and Google process store payments. RevenueCat receives your Firebase identifier, purchase and subscription information, and SDK service or device identifiers to verify and restore access.
• YouTube supplies videos and thumbnails and may receive network, device and playback information and use cookies or identifiers. The player does not receive your Firebase token or learning history. Apple Speech, device/browser speech services and Firebase Crashlytics process the data described below.
• The website loads Google AdSense, which may process IP addresses, device/browser information and cookies or similar identifiers to serve and measure ads under Google’s policies and your available choices. Berlingo does not send your Google sign-in profile, authentication tokens or learning history to AdSense. Browser privacy controls can limit cookies.

Recording starts when you choose to speak. You can refuse or revoke microphone and speech permissions and use features that do not require recording.

• iOS creates a temporary M4A recording for Apple Speech. Recognition may run on the device or through Apple. The app removes the file when recognition finishes or is cancelled; an interrupted file may remain until temporary data is cleared.
• Android uses the device speech service, possibly Google. The website uses the browser speech service. These services may send audio to their providers and require a network connection.
• Berlingo calculates the score from the transcript in memory. Its API receives the exercise identifier and score, not your recording or raw transcript.

The website uses browser storage, a session cookie and a language cookie. Native apps store settings, cached content and account-specific learning data for offline use.

• Signing out or uninstalling does not delete server data. Caches may remain after sign-out. Remove local data through browser or device controls; copies on other devices are not remotely erased by account deletion.
• Firebase Crashlytics on iOS and Android is optional and off by default. If enabled, reports may contain crash traces, app/OS/device information, SDK diagnostic identifiers and sanitized error codes, without your Firebase identifier, email, answers or audio. Turn sharing off in Sign-in or Profile to stop new reporting and request deletion of unsent reports. Reports already submitted cannot be recalled. The website does not use Crashlytics.

We keep your learning profile and synchronized progress while you use the account, until you delete that data. Signing out or uninstalling alone does not start deletion.

• Authentication records in Firebase remain after the current in-app deletion flow, as explained below. This allows the sign-in identity to be used again.
• Apple, Google and RevenueCat retain purchase and transaction records under their policies for billing, restoration, refunds and applicable obligations. Deleting learning data does not erase those records.
• Support correspondence is kept as needed to handle your request and related obligations. Providers apply their own retention policies to service and diagnostic records. Contact us about retained personal data; we will explain any applicable reason for keeping it.

On the website, iOS or Android, sign in to the correct account, open Profile, choose Delete account and confirm. A network connection is required.

• After the server confirms deletion, your learning profile and associated synchronized activity, progress, reviews, bookmarks and statistics are deleted. This cannot be undone.
• The app or browser clears the account-specific local learning data covered by its deletion flow. Cached content, settings or copies on other devices may need to be removed separately using device or browser controls.
• Deletion does not cancel an App Store or Google Play subscription. Manage or cancel it in the store where you purchased. If deletion fails or you cannot sign in, email linhdndev@gmail.com for help.

Depending on your location, you may have rights to access, correct, export or delete data, restrict or object to processing, and withdraw consent.

• Email linhdndev@gmail.com to make a request. We may verify account ownership. Do not send passwords or payment credentials. You can change device permissions and optional crash-report sharing at any time.
• EEA and UK users may complain to their data protection authority. California residents may request information, correction and deletion without discriminatory treatment. We do not sell or share personal data for cross-context behavioral advertising.

Berlingo is a general-audience service and is not directed to children under 13. We do not knowingly collect their personal data; contact us if you believe a child has provided data.

• Account and learning data are sent to the Berlingo API over HTTPS. No storage or transmission method is completely secure.
• We update this policy when the service or requirements change and publish the current version and date here.