Privacy Policy
1. Who we are
timonbu is provided by developer mohammed aissaoui. It is an educational app offering lessons, levels, tests, AI-assisted learning and audio features. For privacy questions or data-rights requests, contact us at timonbu.support@gmail.com.
2. Account and sign-in data
When you create an account or sign in, we may process your Firebase user ID (UID), email address, display name, email-verification status and sign-in-provider information, such as Google Sign-In details if you choose that method and it is available. Firebase Authentication manages password credentials; do not send your password to us by email or chat. We use account data to create and manage your account, verify identity and link progress and features to your account.
3. Learning progress and app data
We may store learning-progress data in Cloud Firestore, such as completed levels, test results or scores, level-completion status, hearts, selected language and related timestamps. We use this information to display and synchronize your progress and operate app features.
4. AI text chat
The app provides an educational chat feature powered by AI. Messages and questions you type, along with previous messages needed to understand the conversation context, are sent from the app to our server through Cloudflare Workers. Our server then sends the necessary content to OpenAI to process the request and return a response. The supplied Worker does not create a separate ordinary chat-history table in D1, but it stores the message and response when you submit a report about a response. We use this data to provide explanations, corrections and educational assistance. Do not submit passwords, payment-card numbers or highly sensitive information in AI chat.
5. AI text quotas
Under the current in-app limits, a free user may use up to 200 AI usage tokens per day, while a Timonbu Premium user may use up to 6,000 AI usage tokens per day. The server counts the tokens reported by OpenAI and resets the text counter at the start of each UTC day. The free audio quota resets at the start of each UTC month, and the Premium audio quota resets at the start of each UTC day. Limits or the calculation method may change; the current limit is shown in the app. These quotas do not mean that chat content is never processed or that it cannot appear in service-provider security logs.
6. Audio and microphone
When you choose an audio feature, you may allow the app to use your microphone to record your speech and convert it to text. The app can also convert AI responses into speech. Audio recordings are sent securely to our server and then to OpenAI or the audio-processing provider used for speech-to-text. Text responses may be sent to a text-to-speech service to generate audio. We use the recording to fulfil the audio request. Under the current Worker code, the audio data is processed in memory and is not written as a raw audio file to Cloudflare D1 or R2. Service providers may process the recording or request data under their own policies, logs and retention periods; therefore, we cannot promise immediate deletion from every provider system.
7. Audio limits
The current free audio allowance is 120 seconds per month. Timonbu Premium currently allows up to 900 seconds per day (15 minutes). Each recording is limited to 30 seconds and a maximum file size of 1 MB. Limits may change, and the active allowance is displayed in the app. The app requests microphone permission when you use a recording feature that needs it. You can manage or revoke this permission in your device settings.
8. Hearts and rewarded ads
A free user starts with up to 20 hearts for tests. Hearts are deducted when answering according to the app's rules and are replenished during the displayed renewal period. A user may have up to 10 previously spent hearts restored after successfully completing and verifying a rewarded ad when available; the balance does not exceed the 20-heart maximum. Premium users receive unlimited hearts while their subscription is active, based on the subscription status recognized by the app.
9. Quota and usage data in Cloudflare D1
Our server stores a user identifier and data needed to manage AI, audio and hearts quotas in Cloudflare D1. This may include usage or balance, plan or Premium status, and usage-period, renewal or refill dates. We use this information to enforce plan limits, synchronize entitlements and prevent circumvention or abuse. These records are retained while reasonably needed for service operation, security or accounting, and are then deleted or disassociated from the account under the applicable deletion and retention processes.
10. Advertising and advertising ID
We use Google AdMob to display ads, including rewarded ads when available. Google and its partners may process the Android Advertising ID, device and app technical information or identifiers, ad-delivery and measurement data, and fraud-prevention signals. Ads may be personalized or non-personalized depending on your region, consent choices, device settings and app settings. We use the Google User Messaging Platform (UMP) to present consent and privacy choices in regions where required. You can use the privacy options available in the app to change ad preferences or withdraw consent where applicable. We do not use AI messages or voice recordings to create advertising profiles. Ads are not shown to Premium subscribers while their subscription is active according to the status recognized by the app.
11. Timonbu Premium and payments
The app offers a Timonbu Premium subscription through Google Play. Current benefits include unlimited hearts, ad removal, higher AI limits of up to 6,000 AI usage tokens per day and audio limits of up to 900 seconds per day. Google Play processes the purchase, payment method and card information. We do not ask you to send us bank-card details and do not store the full card number or security code. Depending on the billing and verification integration, the app or our server may receive information such as a product ID, purchase token/reference, subscription status, and purchase, renewal or expiration dates to verify eligibility, enable benefits and manage the subscription. The price, term and renewal conditions are shown in Google Play's purchase screen before you confirm.
12. Firebase Crashlytics and diagnostics
We use Firebase Crashlytics to collect crash reports, fix technical problems and improve app stability. Reports may include stack traces, relevant app state, technical device information such as device model and operating-system name/version, app version, Crashlytics Installation UUID, Firebase Installation ID, random technical identifiers and crash timestamps. Additional logs or preceding interaction breadcrumbs may be included if the relevant SDK features are enabled. We do not intentionally use Crashlytics to collect the content of your AI chats or voice recordings. According to Firebase documentation, Crashlytics keeps crash-report data and associated identifiers for 90 days before beginning removal from live and backup systems; details remain subject to provider changes and SDK configuration.
13. External service providers and sharing
Some features rely on external providers:
- Firebase Authentication: account creation, sign-in and identity verification.
- Cloud Firestore: account and learning-progress storage.
- Firebase Crashlytics: crash reporting and technical diagnostics.
- Google AdMob and Google UMP: advertising and privacy/consent choices.
- Google Play Billing: purchases, subscriptions and Premium entitlement verification.
- Cloudflare Workers and Cloudflare D1: app requests, server-side processing, quota management and associated data.
- OpenAI: processing AI messages and audio transcription or speech-generation requests, depending on the feature used.
14. Data retention
We keep account and learning-progress data while the account is active or until a deletion request is completed, subject to legitimate security or legal needs. D1 quota records are kept as needed to apply limits, renewals and abuse prevention. The server stores AI-response reports, including the report reason, user identifier, related message and reply, and report time. The supplied Worker code does not define a fixed automatic expiry for these reports; an appropriate retention and deletion schedule must be configured on the server. Crashlytics retains its data as described above. OpenAI states that API data is not used to train models by default. The Worker sends text-chat requests to /v1/chat/completions with store:false, which prevents application-state storage for that request under OpenAI documentation, but does not itself disable abuse-monitoring logs, which may generally be kept for up to 30 days. Retention varies by endpoint: OpenAI’s current table lists no abuse-monitoring retention for /v1/audio/transcriptions, while abuse-monitoring logs may be retained for up to 30 days for /v1/audio/speech and text chat. These details may vary with account settings and provider policy changes. Cloudflare may retain Workers Logs if enabled; its current documentation lists up to 3 days on the Free plan and 7 days on the Paid plan, subject to account settings and provider changes. We therefore do not promise that every copy or log held by every provider is deleted immediately when a request ends.
15. Account and data deletion
You can start an account-deletion request from the in-app account/profile settings, or from outside the app through the Delete Account page or by emailing us from the email address linked to your account at timonbu.support@gmail.com. After verifying ownership, deletion of data controlled by our services covers the Firebase Authentication account and linked identifiers; learning progress, hearts and language data in Firestore; account-linked AI, audio and hearts quota data and renewal dates in D1; and subscription-status records that we retain, to the extent supported by the systems and deletion process. Important: the supplied /chat/delete Worker route deletes D1 records only (reports, voice sessions, heart-spend records, ad-reward records and the account row); it does not itself delete the Firebase Authentication account or Cloud Firestore data, which must also be removed by the separate account-deletion workflow. Account deletion does not automatically erase records held by Google Play, OpenAI, Google/Firebase or Cloudflare under their separate policies or retention periods, nor records that must be retained by law or for security and fraud prevention. In ordinary circumstances, we aim to process a verified request within 30 days. We may notify you if a legitimate reason requires more time. See the Delete Account page for instructions.
16. Security
We use HTTPS/TLS to encrypt data in transit between the app and our services and take reasonable steps to protect our server and databases. Service API keys, including OpenAI keys, should be stored as server-side secrets and must not be embedded in the Android app or files that users can extract. Our server verifies the identity tokens required for protected operations. No method of transmission or storage can guarantee absolute security.
17. Children and age
The app is intended for users aged 13 and older and is not knowingly directed to children under 13. Children below the permitted age should not use the app or create an account. If we learn that an account belongs to a child below the intended age, we may take appropriate steps to delete the account and associated data as required by law. Different age requirements in Google Play settings or local law will take precedence.
18. Your rights and choices
Depending on applicable law, you may request access to, correction of or deletion of your data, and you may withdraw advertising consent or change ad preferences through in-app privacy options where available. You can revoke microphone permission in Android settings, although audio-recording features may then stop working. To make a request, contact timonbu.support@gmail.com.
19. Changes to this policy
We may update this policy when we add features, change service providers or change data practices. We will update the date at the top of this page and may display an in-app notice for material changes. We recommend reviewing this page periodically.
20. Contact
For privacy questions, data requests or rights requests, contact mohammed aissaoui at timonbu.support@gmail.com.