Skip to content

EMBLEE

Privacy and your data

Learn how Emblee uses your data and which privacy controls are available to you.

Who operates Emblee?

Thomas Anderl

Himmelstraße 5, 1190 Vienna, Austria

thomasanderl@outlook.com

Privacy contact: thomasanderl@outlook.com

Learning and accounts

Guest progress, settings and practice history are stored in your browser. An account uses your email and authentication credentials through Supabase. Where Google sign-in is available, Google provides your email and account identifier to Supabase to authenticate you. Supabase can also retain your name and profile-picture URL as account metadata. Emblee does not download or display that picture, and this does not give us access to your photo library. We do not request access to your Google Drive, contacts or other Google services, and we do not retain Google API access tokens in Emblee. Google also processes the sign-in under its own privacy policy. Where native Sign in with Apple is available, Apple provides an account identifier and the email address you choose to share, including a private relay address when you choose Hide My Email. We request your email only. Our server encrypts the Apple refresh credential used to revoke app authorization when you delete your account. Account deletion removes that stored credential. If Apple revocation is unavailable, we explain how to remove Emblee from your Apple Account settings. Signed-in learning progress is stored on our backend and synchronized between devices. It includes lesson progress, practice attempts, review scheduling and interface preferences.

When you buy or restore through the mobile store as a guest, Supabase creates a device session with a random identifier. RevenueCat uses that identifier to verify your store purchases and course access. Emblee does not ask for a name, email address or password for this checkout. Guest learning progress stays on the device.

Account sessions are stored in this browser, or in the native Keychain on iOS, to keep you signed in. Trial and purchase records determine course access. They are separate from optional statistics.

AI answer checks

When you ask us to reconsider an answer, the server sends your submitted answer and relevant lesson/question context to Google Gemini or OpenAI, depending on your app version and the service configuration. We do not include your account ID or email in the model request. Avoid entering personal or sensitive information in answers. These checks are limited to the exercise; they are not an open chat service. Approved alternative answers can become shared accepted answers for that question.

Stored feedback responses and AI judgments expire after 24 hours. Hourly cleanup deletes expired records, normally within 25 hours of creation; service outages can delay deletion. Temporary request reservations are deleted after expiry, and usage counters are normally removed within 49 hours. These rules cover our active database, not provider logs or backups.

Shared accepted answers are retained as course content without automatic expiry. They may be corrected or removed when necessary. They are not linked to the submitting account, so account deletion cannot automatically identify and remove them. To request removal, contact us with the course, question and answer concerned; do not send passwords or sign-in codes. We can remove matching shared answers and their associated accepted-response records from our active database. A course identifier and a hash of the normalized wording are retained to prevent the same wording from being accepted again. Provider records and backups follow separate handling.

Optional statistics

These are off until you opt in. You can change your choice under Privacy & optional measurement in the website footer or learner Settings. We respect supported Do Not Track and Global Privacy Control signals. The expanded learning statistics require a new choice, even if you allowed earlier page-only statistics.

We count public page visits, practice clicks, lesson openings and completions, placement starts and completions, completed review sessions, study days and later-day returns on the same device. We also count a limited number of audio starts and failures, with loading time grouped into under one second, one to three seconds or over three seconds. Events contain a random event identifier, an authored page, lesson or course identifier, event type, interface and teaching languages, web/Android/iOS platform and server receipt time. They do not include your account identity, email, answers, referrer, URL parameters, recording text or recording address. No visitor or session identifier is sent. These are aggregate activity reports, not cross-device tracking or exact conversion rates.

While sharing is allowed, local counters avoid repeating study-day events and limit audio statistics to twenty outcomes per course per day. These counters contain dates and counts, not a device identifier. They expire after 29 days and are removed on your next measurement action, or immediately when you change your choice. Offline activity is not queued for later upload. Daily database cleanup removes event records older than 29 days; outages can delay cleanup and backups have separate retention.

On public website pages, the same opt-in also enables Vercel Web Analytics. Vercel receives the public page path with its query and fragment removed, the referring page when supplied by your browser, browser/device information and approximate location (such as country or city) derived from the connection. Vercel processes the request IP address and browser information to derive a visitor hash; its documentation says the visitor session is discarded after 24 hours. We do not enable analytics cookies, user identification, session recordings or custom Vercel events. Aggregate reports have the retention provided by our hosting plan. Payment utilities, account/learning routes and feedback forms are excluded. Vercel analytics is not installed in the native apps. This provider processing is separate from our anonymous event table described above.

Withdrawing stops future optional events and clears the local counters. Existing events have no account identity and cannot be reliably matched back to you. Account and purchase operations continue to work when you decline.

AI provider processing and retention

We use Google’s paid Gemini API service. Google states that paid-service prompts and responses are not used to improve its products. Our requests disable optional project logging. Google’s separate abuse-monitoring policy describes a 55-day retention period for prompts, context and responses. This is not a zero-retention service, and deleting our temporary records does not delete those provider copies.

Newer versions support OpenAI for these requested checks. OpenAI states that API inputs and outputs are not used for model training unless the account opts in; our account sharing is disabled. We request no stored Responses. This does not by itself remove OpenAI’s separate abuse-monitoring retention, which is normally up to 30 days. Zero Data Retention is a separate, approved control that excludes request content from routine abuse-monitoring logs. OpenAI answer checks in newer versions are optional and require confirmation that you are at least 18. We hold this confirmation only in session memory and clear it when the account/content session resets. We do not request a birthdate or identity document for this check. You can continue learning without using AI checks. Older app versions continue using Gemini.

Teen learners

Emblee is intended for learners aged 13 and above. If you are under 18, use Emblee with your parent or guardian’s permission. Do not put your contact details, school, address or passwords into practice answers. Contact our privacy email for help with a young learner’s data or permissions.

Feedback and language requests

You can send private feedback or request a course without an account. We store the type of message, requested learning and explanation languages, your note, interface language, time sent, and an email only if you provide one. We use these to respond to feedback and plan courses. Course-availability emails require your separate opt-in; this is not a newsletter subscription. No message is sent to an AI provider.

When we send a course-availability notice, Resend receives your email address and the notice. We retain a private record of the requested course, a hash of the recipient address, an unsubscribe-token hash, send status, time and provider email ID to avoid duplicate notices and handle failures. This record is removed with the original request. An accepted send does not prove inbox delivery. Use the email’s unsubscribe link to stop further notices for your existing requests.

When you report a question or recording, we also attach its course and material reference, teaching language, and relevant content revisions or recording file hashes. This helps us find the affected material after an update. Your answer, account identity and sign-in credentials are not attached automatically.

After a placement check, you can optionally tell us whether the suggested starting level feels right, too high or too low, or that you are unsure. We store your choice, optional comment, course and teaching language, test-bank and scoring-policy revisions, suggested level and correct/answered counts by level. We use this feedback to investigate placement quality. Submitted answers, account identity and placement-session identity are not attached. Feedback does not change your result or course access, and self-reported feedback is not an independently verified proficiency assessment. A local receipt can hide the survey after a successful send on that device.

Submissions are kept for up to 12 months and removed by daily cleanup; outages can delay removal. We use a daily-changing keyed hash of connection information for abuse limits, not a stored raw IP address. Abuse counters are removed after two days. These records are not linked to your Emblee account. Contact thomasanderl@outlook.com to withdraw course-update consent or request deletion, mentioning the email or message you supplied. Earlier encrypted database backups expire separately.

Hosting, email and payments

Emblee uses Vercel for hosting, Supabase for authentication/database/storage, Resend for authentication and opted-in course-availability emails, and Google Gemini or, when enabled, OpenAI for requested AI feedback. Google Gemini and Google Cloud Text-to-Speech may also generate authored speech through a separate operator process. Playing a stored recording does not send your voice for synthesis.

RevenueCat manages purchase history and course entitlements. Paddle handles available web checkouts, while Google Play or Apple handles purchases in the respective store app. Payment availability is shown in the app. Billing providers handle payment information; our course-access records are separate. Hosting and provider request logs may contain technical connection data outside the optional event table.

Database backups

Encrypted database snapshots are stored as private GitHub Actions artifacts with seven-day retention. The recovery key is kept separately. These snapshots include accounts, learning progress, trial and purchase-access records, shared accepted answers and removal markers; temporary AI feedback caches are excluded.

Deleting data from the active database does not immediately remove it from an earlier snapshot. Before using a restored database, we reconcile subsequent removal requests and clean up expired data. Audio-file backups are separate from database snapshots.

Your controls

Export your saved learning progress, change your password or delete your account in Account. Account deletion removes the account and its linked server learning progress; it does not cancel subscriptions or guarantee immediate removal from provider records and backups. Guest progress can remain on this browser and can be reset separately in Settings.

You may have rights to access, correct, delete, restrict or obtain a copy of personal data, object to certain processing, withdraw consent, and complain to a supervisory authority. For a privacy request, email the contact above. We may need to verify that the request concerns your data. See Help with Emblee for the controls available now.