Your data. In plain language.

1. Who and what this policy covers

This policy covers the TahaKa Language mobile app and its developer website. It describes the current pre-release implementation. You can contact the developer using the support and privacy address below.

The app is operated by Taha Kouera.

2. Learning data on your device

The app stores learning content and your activity locally. This can include vocabulary and favorites, review progress, study statistics, reading and listening progress, custom decks, game state, coins, flames, boosts, and your preferences.

An account is optional. Content updates still connect to our Supabase service, even when you are not signed in. Like other internet requests, these connections expose network information such as your IP address to the receiving service. Local reminders use your device timezone and study activity; their settings are stored on your phone.

3. Optional account and cloud backup

If you choose to create an account, Supabase processes your email address, account identifier and authentication information to send and verify a sign-in code. The app does not ask you to create a password.

The optional backup contains word review identifiers, review dates and scheduling information, coin balance and totals, rewarded-ad counters, study-session expiry, flames and boosts. It is associated with your account identifier and the backup update time. A backup may be created when you sign in and when you choose Back up now. This is not continuous synchronization of everything on your device; custom decks and other local items are not all included.

4. Advertising and your choices

TahaKa uses Google AdMob for banner ads and optional rewarded ads. Google’s Mobile Ads SDK can process IP addresses (including an inferred general location), device or other identifiers, app and ad interactions, and diagnostic information for advertising, measurement and fraud prevention. These SDK activities occur separately from your optional TahaKa account.

Google’s User Messaging Platform requests consent information and shows a consent form where required. The app checks whether ad requests are permitted before starting ads. Where available, Settings → Ad privacy choices lets you revisit those choices. Your device may provide additional advertising settings. Completing an eligible rewarded ad updates the app’s reward counters; opening the ad alone does not earn a reward.

5. Microphone and speech playback

Pronunciation practice uses your device’s speech-recognition service with microphone permission. That service may send audio to its provider for recognition. The app does not force on-device-only recognition, so we cannot promise that speech stays on your phone. Recognized text is used for the current practice activity; no direct raw-audio file storage or upload was found in the app’s own implementation.

For pronunciation playback, the app first uses device text-to-speech voices. Some voices require internet. When a Google Cloud Text-to-Speech fallback is configured and device playback cannot be used, the selected text and voice/audio settings are sent to Google to synthesize speech. The temporary audio file is removed after playback completes or is cancelled.

6. Handwriting and other features

Guided Chinese and Japanese stroke practice is handled locally. The fallback digital-ink recognition uses Google ML Kit and may download language models. Google describes recognition of handwriting input as on-device processing, while its SDK can still collect device/app information, identifiers, feature and language information, and performance diagnostics.

Real-money purchases are not enabled in the reviewed pre-release configuration. If purchases become available, the store terms and updated privacy information must be shown before launch. The app’s dependencies alone should not be interpreted as a promise that payments are currently offered.

7. This website and support

This website is hosted with OpenAI Sites and delivered through Cloudflare. It does not add advertising pixels or audience analytics. Its hosting provider necessarily processes web requests and may retain access/security logs. Fonts and illustrations are served with the site rather than loaded from a third-party font service.

The account-deletion page connects to Supabase only when you use the verification flow. It uses your account email and one-time code to authenticate you, and keeps the deletion session in memory rather than saving it to browser storage. Closing or reloading the page means verifying again. Emailing support shares your message, attachments and sender information with the developer and the email providers. Cloudflare Email Routing forwards support messages to a Google Gmail inbox. Never send your verification code to support.

8. Retention and deletion

Local learning data remains on your device until you remove it using your device’s app-data controls or another applicable local reset. Clearing local data does not automatically delete a cloud account or backup.

The active account and its cloud backup remain until you request account deletion. The app and this website call an authenticated deletion service. The deployed database links cloud backups to the account for removal with it. Deletion is permanent, but does not erase copies already stored locally on your devices.

Operational logs, infrastructure backups and records controlled by third-party providers may have separate retention rules. Exact release-specific retention details have not yet been confirmed; this draft does not promise immediate erasure from every provider’s historical systems.

9. Your controls and requests

You can use the app without creating an account, choose whether to back up, manage microphone and notification permissions in device settings, revisit ad privacy choices when available, and delete your account and cloud backup.

In the app, use Settings → Account → Delete my account and backup. On this site, the Delete your account page lets you verify your email and initiate deletion without reinstalling the app. Requests to access or correct personal data, or questions about applicable privacy rights, can be sent to the support and privacy email below.

10. Providers, security and location

Data sent to configured Supabase and Google endpoints uses HTTPS. No system is completely secure. We do not claim that all local data is encrypted simply because security-related dependencies are present.

The relevant providers include Supabase (accounts, backups and content delivery), Google advertising and ML Kit services, the device speech/voice provider, and—when configured—Google Cloud Text-to-Speech. Their processing can involve countries outside your location. The production service region and applicable transfer arrangements still require confirmation before this policy is finalized.

11. Age range and changes

The intended release age range and any child-directed configuration have not yet been confirmed. This draft does not claim compliance with child-directed advertising rules. The developer must finalize the audience and matching SDK/store settings before release.

We will update this policy when app features, providers or data practices change, and show the updated date on this page. Material changes should be reflected in the app’s disclosures and store declarations.

12. Contact

For support and privacy requests, contact support@tahakalanguage.com.