Updated 7 October 2026
WorkLingo Privacy Policy
WorkLingo is a language-learning application operated by BaneWorks. This policy explains the data processed by the app and its service providers. Privacy and data requests: support@baneworks.fi.
Account and service protection
Google Sign-In and Firebase Authentication process your account identifier and available account details, such as email address and display name, to sign you in and link your progress and purchases. Authentication credentials are handled by the SDKs and our protected backend.
Email/password registration and sign-in also use Firebase Authentication, which processes your email address and password credentials for account access.
Firebase App Check verifies requests using app/device attestation and App Check tokens to protect the service from abuse. Authentication and App Check tokens accompany protected requests. WorkLingo does not intentionally publish these credentials or include them in application logs.
Learning progress and activity
Firestore stores account/profile information, learning progress, XP, streaks, activity history, usage and rate-limit records, wallet balances and purchase entitlements. AI request/response records may be cached in your account subtree so retries do not repeat operations or rewards. Local app storage also holds settings, exercise state and cached learning information. Public profile/directory information may be visible to other users through social features.
Normal text vocabulary, sentence, quiz, reading and spaced-repetition exercises run locally. Feedback records include your user identifier, display name, submitted text, category, timestamp and processing status. Feedback, bug reports and social references may be stored outside your own account subtree.
AI conversations, evaluations and audio
When you use AI conversation or evaluation, relevant messages, conversation context, exercise instructions and answers are sent through WorkLingo's protected backend to Google Gemini as the primary text provider. Eligible fallback requests can be processed by OpenAI. Responses and evaluation results can be stored with your account's request records and learning activity.
Microphone access is used for optional spoken exercises. Recorded audio can be sent to OpenAI for speech-to-text transcription; text can be sent to OpenAI for text-to-speech playback. Transcripts and resulting scores may become part of your exercise or AI request records. Denying microphone access prevents recording but does not prevent ordinary text exercises.
Provider processing and retention depend on the service, endpoint and account configuration. WorkLingo does not promise zero retention or that provider-side data disappears when you delete the app or account. Avoid entering sensitive personal information in messages or recordings. See Gemini API terms, Gemini abuse monitoring and OpenAI API data controls.
Daily News
Daily News retrieves public news feeds through the backend, generates and grades questions deterministically, and uses a shared server cache of articles and exercises. This flow does not send news exercises to Gemini or OpenAI. Completion, score and reward records are associated with your account. Opening a publisher's article exposes your browser request to that publisher under its own privacy policy.
Advertising and privacy choices
When advertising is enabled, Google AdMob can process the Advertising ID, device or other identifiers, IP-derived approximate location, app interactions and diagnostics for advertising, measurement, fraud prevention and security. Android's advertising permission does not itself mean that personalized advertising is allowed.
Google User Messaging Platform (UMP) handles consent and privacy choices where required. Available advertising privacy options can be reopened from WorkLingo's settings. You can also manage the Advertising ID in Android settings. Advertising depends on applicable privacy choices and app configuration. See Google's privacy policy.
Purchases and subscriptions
Google Play Billing handles purchases and subscription payments. RevenueCat processes app user identifiers, product identifiers, purchase events and transaction information to verify purchases, restore access and manage entitlements. WorkLingo's backend stores purchase/reward processing records and account balances or entitlements to prevent duplicate grants. WorkLingo does not receive your full payment-card details from Google Play.
Deleting a WorkLingo account does not cancel a Google Play subscription. Manage or cancel subscriptions through Google Play. Google Play and RevenueCat retain their own records under their policies. See RevenueCat's privacy policy and Google's privacy policy.
Retention
- Account and learning records remain while the account exists unless removed through the app's supported deletion flow. There is no general promise that all activity or AI request caches expire after a fixed number of days.
- Local settings and caches remain until removed by the app, by clearing app storage or by uninstalling. Removing local storage does not delete server/provider records.
- Global RevenueCat event/transaction records, rewarded-ad nonces/transactions, feedback, bug reports and social references outside your account subtree are not removed by the current automated account-deletion endpoint. No uniform automatic expiry is promised for these records.
- Firebase, AI providers, Google Play, RevenueCat and AdMob may retain service, security, billing or legal records according to their own policies and configured services. Provider retention can continue after app/account deletion.
Account and data deletion
Use the account-deletion option in WorkLingo's settings and reauthenticate when requested. The protected backend removes your user subtree, including profile, wallet, entitlements, usage, rate limits, activity and account request records, and the current and legacy public directory entries. Firebase Authentication identity deletion proceeds only after backend cleanup succeeds.
Deletion has limits. It does not automatically erase global purchase/reward records, feedback or bug reports outside your user subtree, references in other users' records, public news caches, or records held independently by service providers. It does not cancel a subscription.
If you cannot access the app, or want to request access, correction, export or deletion of additional data, email support@baneworks.fi with the subject “WorkLingo data request” and enough account information to identify your account. Do not send passwords or authentication tokens. We may need to verify account ownership and assess provider-held or retained records separately; we do not promise complete immediate erasure of every record.
Service providers and security
WorkLingo uses Google/Firebase for authentication, attestation, database and backend processing; Google Gemini and OpenAI for the AI/audio functions described above; Google AdMob/UMP for configured advertising and choices; and Google Play/RevenueCat for billing and access. These services process relevant information to provide their functions. Data can be processed outside your country; a European backend location does not mean every provider stores or processes all data only in Europe.
Protected backend operations use authentication, App Check and access rules. Credits and entitlements are granted by trusted server processing. See Firebase privacy and security information for its service-specific processing.
Changes and contact
This policy may be updated to reflect changes in WorkLingo's behavior. The date above identifies this version. Contact BaneWorks at support@baneworks.fi for WorkLingo privacy questions.