BumuStudios·Türkçe sürüm·ImageToPdf policy·PdfPages policy

Who this policy is from

This policy covers the Android application Tomato Focus (listed on Google Play as "Tomato Focus: Focus Timer"), distributed through Google Play under the package name com.bumustudios.tomatofocus. It is written by the app's independent developer, BumuStudios. Questions can be sent to the address in Contact.

What the app does

Tomato Focus is a focus timer: focus sessions (25 minutes by default) alternate with short breaks, with a long break after a set number of sessions. You can choose a preset or your own lengths, keep a small task list and count sessions toward a task, see statistics for today, the week, your streak and all time, and play ambient sounds such as rain or white noise while you focus. There is no account and no subscription.

Your focus data stays on your device

This is the most important section, so it is stated plainly:

• Your tasks and session history are never uploaded. The app has no backend of its own. It does not transmit your task titles, your focus sessions, your statistics or your timer settings anywhere, and the usage statistics and crash reports described below never contain them: a crash report shows where in the code a crash happened, not your tasks.
• The timer, its alarms and its notifications run on the device. The time a session ends is scheduled with Android's own alarm service on your phone, and the countdown and "time's up" notifications are posted by the app on your phone. Nothing about them is sent to any server.
• Ambient sounds are generated on the device. Rain, brown, pink and white noise and ocean waves are computed live by the app while they play; they are not recordings and are not streamed from the internet. The app never uses the microphone. Ambient sound plays only while a focus session runs and the app is on screen.
• There is no export, sharing or sync feature. Your data is not copied anywhere by the app itself; the only copy that can leave the device is Android's own backup, described below.

What the app stores locally

The app keeps its data in its own private storage on the device. None of it is sent to the developer, to the ad networks or to the analytics services:

• your timer settings — session lengths, rounds before a long break, auto-start choices and your daily goal — and the state of the timer, including when the current phase ends;
• your tasks — the title you type, the estimated number of sessions, whether a task is done, and when it was created and completed;
• a log of your completed focus sessions — when each started and ended, how long it lasted and which task it counted toward — from which all statistics are calculated on the device;
• a reference reading of the phone's internal clock, used only to keep a running timer correct if the date or time is changed;
• your theme, text size and language choices, sound, vibration and keep-screen-on settings, your ambient sound and its volume, and whether the app has already asked for notification permission;
• whether the one-time "remove ads" purchase is active, when a "24 hours without ads" period ends, and a counter of how many interstitial ads have been shown, used to keep ad frequency low.

If the app ever finds its data file damaged, it keeps a copy of that file in the same private storage rather than overwriting it, so that your history is not silently lost.

Backup. Your timer settings, tasks, focus history and app settings are included in Android's backup and in device-to-device transfer, so that a new phone can restore your statistics. These backups are made by Android and stored in your Google account under your device's backup settings; the developer has no access to them, and you can turn backup off in Android's settings. The advertising and purchase state listed last above is excluded from backup and transfer, and so is everything the app or its components keep in Android's shared preferences and databases — which includes the ad, consent and update bookkeeping, which belong to the device they were made on.

Google's advertising and consent components also keep their own settings on the device, under Google's control, and the Google Firebase components described below keep three random identifiers in the app's private storage: a Firebase installation ID, the Analytics app-instance ID and a Crashlytics installation ID. Unlike your focus data, these identifiers travel with the usage statistics and crash reports. Uninstalling the app or clearing its data removes everything the app has stored on the device, these identifiers included; a copy in your Android backup is managed by Android's backup service.

Notifications and alarms

On Android 13 and later, the app asks for permission to show notifications the first time you start a timer, after a short screen explaining why; you can choose "Not now". The timer works the same without the permission — you simply will not be alerted while the app is closed. You can turn notifications on or off at any time in Android's settings, which the app's Settings → Notifications entry opens.

With the permission, the app shows a silent countdown notification while a timer runs and the app is not on screen, with Pause and Skip (or Resume and Stop) buttons, and a notification with a chime when a session or break ends. The countdown notification can show the title of the task you are working on; on a lock screen set to hide sensitive content, it shows the countdown without the task title.

The end-of-session alert uses Android's ordinary (inexact) alarms, so the app does not ask for the special "alarms and reminders" access. Because Android clears scheduled alarms when the phone restarts or the app is updated, the app declares RECEIVE_BOOT_COMPLETED: after a restart it catches the timer up, alerts you for any session that ended meanwhile and schedules the next alert again. It does the same after it is updated, and it notices a change of the date or time so that a running timer stays correct. All of this happens on the device.

Advertising — Google AdMob and its mediation partners

The app is free and is supported by ads served by Google AdMob (Google Ireland Limited / Google LLC, depending on your region). AdMob is embedded in the app as a software development kit, and it does collect data, independently of the developer. When ads are served, AdMob and Google's advertising partners may collect and process:

The app does not request GPS or precise location permission, and it does not send your tasks, task titles or focus history to AdMob or to any ad network. The developer receives no personal data from AdMob — only aggregated, anonymous reporting such as impression and revenue totals.

Because ads require an advertising identifier, the app declares the com.google.android.gms.permission.AD_ID permission. The ad formats and where they appear:

• Banner — at the bottom of the Tasks and Statistics tabs. There is never a banner on the Timer or Settings tab.
• Interstitial (full-screen) — only after a completed focus session, when you leave its summary with a button; never during a focus session, never when that button starts the next focus session, and never when you close the summary with Back or by tapping outside it. The first two of the app's lifetime are skipped, and two are never shown less than two minutes apart.
• Rewarded video — only if you choose it, from Settings → 24 hours without ads; watching it to the end turns off the other ads for 24 hours. The entry is shown only when such an ad is available.
• App-open ad — when you return to the app from the background, at most once every four hours, and never while a focus session is running or paused.

Mediation partners

AdMob uses mediation: for any ad request, it may pass the request to one of the following ad networks, whose software development kits are built into the app for that purpose, and let that network serve the ad. A network that receives a request then receives the same categories of data listed in the table above — advertising ID, approximate location derived from your IP address, device information and ad interaction events — and processes them under its own privacy policy. Your consent choices (below) are passed to these networks through the industry-standard consent signal written by Google's consent tool.

• AppLovin — AppLovin Privacy Policy
• Unity Ads — Unity Game Player and App User Privacy Policy
• Liftoff Monetize (formerly Vungle) — Liftoff Privacy Policy
• Meta Audience Network — Meta Privacy Policy
• Mintegral — Mintegral Privacy Policy
• Pangle — Pangle Privacy Policy

How Google handles this data is governed by Google's own policies, not by this one:

• Google Privacy Policy
• How Google uses information from sites or apps that use our services
• AdMob and third-party advertising

Usage statistics and crash reports — Google Firebase

To see how the app is used and to find and fix crashes, the developer has built two Google Firebase services into it: Google Analytics for Firebase and Firebase Crashlytics. Google provides them as the developer's data processor, and they are active only in the version of the app distributed through Google Play. The app adds nothing of its own to what they collect — no custom events, no user ID or user properties, no custom keys or log messages — so only their automatic collection applies:

The "sessions" counted here are times the app is opened, not your focus sessions. Analytics records that a screen was shown and for how long, not what you do on it, and a crash report shows where in the code the crash happened, not your tasks or history. Neither service receives your name, your email address or any account details.

In the EEA, the UK and Switzerland, the consent form described below under "Your advertising choices" also covers Analytics: your choices there decide whether Analytics may store its identifiers on your device and whether the data may be used for advertising. Use of the data for advertising ("ad user data") and for ad personalisation stays off there until you consent. You can change your choice at any time from Settings → Privacy options; the entry appears where it is required. The app has no separate switch for the usage statistics or the crash reports; uninstalling it stops both.

Analytics keeps data linked to an installation's identifiers for no longer than 14 months; aggregated reports that contain no identifiers may be kept longer. Crashlytics keeps crash reports for 90 days.

Google processes this data on the developer's behalf, as its data processor, under the Firebase and Google Analytics data processing terms. It may be processed on Google's servers outside your country, including in the United States, and it is encrypted in transit (TLS).

Google describes these services here:

• Privacy and security in Firebase
• Google Privacy Policy

Purchases — Google Play Billing

The app offers one optional, one-time, non-consumable purchase that permanently removes ads. There is no subscription and nothing recurring.

The transaction is handled entirely by Google Play Billing. The developer never sees or receives your card number, bank details, billing address or full name. Google Play reports only aggregated sales figures, and Google Analytics for Firebase records that a purchase was made — product, name and price, with no payment details (see above). Inside the app, the purchase is recorded as a single true/false flag on your device, restored from your Google Play account when you reinstall or move to a new device. Your handling of payment data by Google is covered by the Google Privacy Policy and Google Play's terms.

The app also uses Google Play's in-app update service, which lets Google Play tell you inside the app that a newer version is available and download it if you agree. That exchange takes place between your device and Google Play.

Your advertising choices

If you are in the EEA, the UK or Switzerland

Before any ad is requested, the app shows a consent form built with Google's User Messaging Platform, where you choose what you allow. Your choice is stored on your device by Google's component, is respected on later launches, and is passed on to the mediation partners listed above.

You can change your decision at any time: open the app, go to Settings → Privacy options, and the same form reappears. You may withdraw consent there. Withdrawing consent does not disable the app; the timer, tasks, statistics and ambient sounds keep working, and ads may still be shown in a non-personalised form. The same choices also apply to Google Analytics for Firebase, as described above.

In US states with privacy laws

Where a US state privacy law gives you the right to opt out of the sale or sharing of personal information or of targeted advertising, the same Google consent tool is used to present that choice where applicable, and the Settings → Privacy options entry then lets you review it.

Everywhere else

The privacy options entry appears only where a consent choice is legally required, so you may not see it. You can still control advertising at the operating-system level: open Android Settings → Privacy → Ads (the exact path varies by manufacturer and Android version) to reset your advertising ID, or to delete it entirely, which stops apps from receiving a stable advertising identifier.

Removing ads completely

Buying the one-time ad removal stops ad requests from the app altogether. Watching the optional rewarded video instead turns off the banner, interstitial and app-open ads for 24 hours.

Permissions the app requests

These are the permissions the app declares itself. The Google and ad-network components built into it add a few more that Android grants at installation without asking you, such as Google Play's billing and licence-check permissions, Android's advertising-services permissions, and permissions to read the Wi-Fi state, keep the processor awake briefly, vibrate, run background work and read the Play install referrer. The app does not use the special exact-alarm access, and it requests no storage, camera, microphone, contacts, location or account permissions on any Android version.

Children

This app is a general-purpose utility. It is not directed at children under 13 (or under 16 in the EEA, or the equivalent minimum age in your country), it is not listed in a children's category, and it is not designed for or marketed to children. The developer does not knowingly collect any personal information from children. If you believe a child has provided personal information through the ad, analytics or crash-reporting services in this app, contact the address below and contact Google, whose services would hold it.

Data retention

The developer runs no server and keeps no user data of its own. The usage statistics and crash reports are held by Google on the developer's behalf: Analytics data linked to an installation's identifiers for no longer than 14 months (aggregated reports without identifiers may be kept longer), and crash reports for 90 days. Tasks can be deleted in the app; everything else held on your device stays there until you clear the app's data or uninstall the app, and a copy in your Android backup follows your device's backup settings. Data collected by Google through AdMob and Google Play, and by the mediation partners, is retained according to their own retention schedules, described in their privacy policies linked above.

Security

Your focus data is kept in the app's private storage, which Android protects from other apps. The app itself sends none of your data over the network. Google's services used by the app — AdMob, Google Play and Firebase — transmit data over encrypted connections (TLS); the mediation partners describe their own security practices in their privacy policies. Because the app holds no account and the developer holds no copy of your data, there is no developer-side database of your tasks or history that could be exposed.

Legal bases and your rights

Where the GDPR (EU/UK) applies, the legal basis for personalised advertising is your consent, collected through the form described above and withdrawable at any time. Non-personalised advertising, fraud prevention and the security of the ad services rely on legitimate interests. Processing your purchase is necessary to perform the contract you enter when you buy ad removal. The usage statistics and crash reports rely on the developer's legitimate interest in keeping the app working and understanding, in aggregate, how it is used; storing Analytics identifiers on your device and any advertising use of the data follow your choices in the consent form.

Under the GDPR, and under Turkey's KVKK (Law No. 6698) on equivalent terms, you have the right to ask whether your personal data is processed, to access it, to have it corrected or erased, to restrict or object to its processing, to data portability, and to withdraw consent. You may also lodge a complaint with your national data protection authority — in Turkey, the Kişisel Verileri Koruma Kurumu (KVKK).

The usage statistics and crash reports are pseudonymous: they carry random identifiers, never your name or email address, so the developer cannot tell which records are yours. Where the consent form is shown, you can withdraw consent at any time in Settings → Privacy options, and you can object to this processing, or ask about it, by writing to the address below. Uninstalling the app or clearing its data ends the link to the old identifiers, and data already sent then expires on the schedule above. Requests concerning advertising data must be directed to Google, or to the mediation partner concerned, as the party that holds it, using the tools in their privacy policies linked above. For anything else, or for help finding the right route, write to the address below.

Changes to this policy

If the app's data practices change — for example if a new third-party service is added — this page will be updated and the "last updated" date at the top will change. Material changes will also be reflected in the app's Google Play listing. Continuing to use the app after an update means you accept the revised policy.

Contact

For any question about this policy or about privacy in this app, write to: