Privacy Policy
Last updated: July 20, 2026 · Applies to the Whenbee app for iOS and Android, and to whenbee.app
The short version: your tasks, time guesses, and everything Whenbee learns about you stay on your phone. There is no account. We don't sell data, show ads, or track you across other apps. A small amount of anonymous usage and crash data reaches us so we can fix bugs and improve the app, and anything you type into the feedback form is sent to us because that's the point of the form. The rest of this page spells that out.
What stays on your phone
The core of Whenbee runs entirely on your device. Your tasks, time guesses, timer results, categories, routines, and the calibration the app learns from them are stored in a local database on your phone. They are never uploaded. There is no account and no cloud copy. If you delete the app, that data is gone with it.
The same is true for these features:
- Voice entry. If you speak a task, your speech is transcribed on your device using the system's on-device speech recognition. Neither the audio nor the transcript is sent anywhere. The microphone is only active while you're recording.
- Calendar (Honest-Day). If you grant calendar access, Whenbee reads your calendar to show you a realistic view of your day and writes events back only when you confirm them. Your calendar data is read and written on your device and never transmitted to us.
- On-device AI. On devices that support it, Whenbee can use the platform's on-device model to tidy a spoken task into a short title. This runs on your phone and has no network path. Devices without it use simple local rules instead.
- Notifications. Timer and routine reminders are scheduled locally on your device. We don't use push servers and never see a push token.
What leaves your phone, and why
1. Anonymous usage analytics
To see which features get used and where people get stuck, the app sends anonymous usage events to PostHog, an analytics service, hosted in the European Union (Frankfurt). An event looks like "task logged" or "trial started", along with numbers such as a time guess, an actual duration, and the name of the category it belongs to. Events are tied to a random identifier generated on your device — not to your name, email, or any advertising ID, none of which we have.
We never send the text of your tasks. The only text you create that appears in analytics is the short names you give your categories (for example "Deep work"). Everything else is numbers and fixed labels.
2. Crash and error reports
When something breaks, the app sends a technical report to PostHog — the same service that handles analytics, hosted in the European Union (Frankfurt): what failed, a stack trace, and basic device and OS information. These reports don't include your tasks or timing data, and the app deliberately does not send its console or debug logs, which is the one route by which task text could otherwise slip out.
3. Purchases
Payment for Whenbee Pro is handled by Apple's App Store or Google Play. We never see your card details. RevenueCat, a subscription-management service, processes your purchase receipt under a random anonymous ID and tells the app whether Pro is active. That means a record of what you bought and when exists with RevenueCat; who you are does not.
4. Feedback you send us
If you use "Send feedback" in Settings, we receive what you wrote, along with a random install identifier, the app version, your OS, and your device language. This goes to a database we run on Supabase and is stored so we can read it and act on it. Sending feedback is entirely optional, and the text box is the only way anything you type reaches us — so please don't include personal details you wouldn't want stored. If you'd like a submission deleted, email us and we'll remove it.
What we don't do
- No advertising and no ad networks. The app contains no ads and no advertising SDKs.
- No tracking across other companies' apps or websites, and no advertising identifiers.
- No selling or renting your data, and no sharing with data brokers. We share data only with the service providers named above, who process it on our behalf.
- No account, so nothing is tied to an email, a phone number, or a profile.
Identifiers
Three random identifiers exist so the services above can function: an analytics ID (PostHog), a purchase ID (RevenueCat), and a feedback install ID. Each is a random string generated for your install. None of them contains or links to your name, email, device serial, or advertising ID. They exist so that, for example, analytics can tell ten taps by one person apart from one tap by ten people. If you delete the app, they're abandoned.
Where this data is processed
Usage analytics and crash reports are both processed by PostHog in the European Union. Purchase records (RevenueCat) are processed in the United States under standard contractual clauses and the EU-U.S. Data Privacy Framework, the mechanisms EU law provides for such transfers. Feedback is stored with Supabase. All data leaving the app travels over encrypted connections (HTTPS).
How long we keep it
- Usage analytics and crash reports: kept while we actively use them to improve the app; deleted on request.
- Feedback: kept until we've acted on it; deleted on request.
- Purchase records: kept while needed to honor your purchase (a lifetime purchase, for example, has to stay on record so it keeps working).
Your choices and rights
Most of your data never reaches us, so you control it directly: "Erase everything" in Settings clears the app's local data, and deleting the app removes it all.
For the small amount that does reach us, you can email us to ask what we hold, have it corrected, or have it deleted, and we'll do so within 30 days. If you're in the EU or UK, these are your rights under the GDPR (access, rectification, erasure, restriction, portability, and objection), and you can also complain to your local data protection authority. If you're in California, the CCPA gives you similar rights to know and delete — and since we don't sell or share personal information for advertising, there's nothing to opt out of.
Children
Whenbee is not directed at children under 13, and we don't knowingly collect data from them. If you believe a child has sent us personal information (for example through the feedback form), email us and we'll delete it.
This website
whenbee.app uses PostHog analytics to understand how visitors use the site. The app policy above covers the app; the website collects standard web analytics only.
Changes
If this policy changes, we'll update the date at the top and post the new version here. If a change meaningfully expands what we collect, we'll say so in the app before it takes effect.
Who we are
Whenbee is built by Ali Suliman, an independent developer, who is the data controller for the data described above.
Questions or requests: support@whenbee.app