Whenomatic Privacy Policy
Whenomatic is an app for building automations on your phone: a rule is a trigger followed by steps. The short version of this policy: your rules run on your phone, and what the phone reads stays on the phone. Data leaves the device only when you use a feature that needs a server (the assistant, the weather, the map) or when a rule you wrote sends something to an address you chose. This page lists every such case.
1. Who we are and how to reach us
Whenomatic is developed and published by FlorencoTech (Ihor Vasylenko, an individual developer), who is the controller of the data described here.
Contact for privacy questions, access and deletion requests: whenomatic@gmail.com.
2. What stays on your phone
Rules are evaluated by the app itself, on the device. To do that, the app may read things you allow it to read: your location, calendar events, contacts, sensors and physical activity, Wi-Fi and Bluetooth state, the clipboard, files in the one folder you pick, battery and screen state. Each permission is asked for only when a rule you build needs it, and you can revoke it in Android settings at any time.
This information is processed locally and is not sent to us. It leaves the phone only if a rule you wrote puts it into a message, request or e-mail (see section 3.6).
Installed apps. The app looks up the list of apps on your phone to let you pick an app in a rule (“open app”, “app is installed”). The list is used only on the device and is never sent anywhere, except where a step you added yourself sends it.
3. What leaves the phone, and to whom
3.1. The assistant, free requests through our server
The assistant turns a sentence you type into a draft rule. Without your own key, the request goes through our server, which forwards it to Google’s Gemini API on a paid plan.
- What is sent: the text you typed, the conversation so far, the current draft rule, and — only when your request is about Bluetooth devices — the names of your paired Bluetooth devices (their addresses are filled in on the phone afterwards).
- Google. On the paid plan Google does not use these requests to improve its products and keeps them for 55 days to detect abuse (Gemini API Additional Terms of Service, Google Privacy Policy). Google acts as our service provider here.
- What our server keeps:
- a random installation ID created by the app (not derived from your device) and the balance of free requests tied to it;
- for each session: the country (two letters, derived from your IP address), time, model, token count, cost and outcome — for 90 days, after that only as daily totals without the installation ID;
- your IP address itself is not stored in our database: it is used in memory to find the country and, as a hash with a salt that changes daily, to limit requests per address.
- Hosting. The server runs on Railway. Railway’s own HTTP logs record the IP address of every request and are kept for 30 days; our application logs contain the method, path, status and time, but not the text of your requests. Database backups are kept for up to 89 days.
- The text of your requests and the assistant’s answers is not stored on our server, except when you report an answer (3.3).
- Approximate location. The country derived from your IP address is approximate location. It is used to offer the free assistant only where it is available and to prevent abuse.
3.2. The assistant with your own key
If you enter your own Gemini API key, requests go directly from your phone to Google, not through our server, under the terms of your own Google project. If that project is on the free tier, Google may use your requests to improve its products and human reviewers may read them (Gemini API Additional Terms of Service). In the European Economic Area, the United Kingdom and Switzerland only use a key from a project with billing enabled. Your key is stored encrypted on the phone (section 6) and is never sent to us.
3.3. “Why didn’t it work?” and reporting an answer
From the journal you can ask the assistant why a rule did not run. The app sends the journal entry and the rule, after removing phone numbers, e-mail addresses, coordinates, device addresses, Wi-Fi network names, NFC tag IDs and credentials written into the rule. Secrets ({secret:name}) are sent only as their name, never their value. The request travels the same way as in 3.1 or 3.2.
If you report an assistant answer, our server stores the answer, your request, the draft, the reason and your comment for 12 months, so that we can fix the problem.
3.4. Google Play Integrity
To make sure free requests are used by the genuine app on a real device, the app asks Google Play Integrity for a verdict. Google Play processes information about the device and the app to produce it, under Google’s terms. Our server receives the verdict and keeps only whether it passed; the raw verdict is not stored, and the token itself is kept for at most 14 days. Google Play can also remember a few bits per device for us, so that reinstalling the app does not reset the free requests.
3.5. Weather and map
- Open-Meteo. Weather steps and weather alerts send coordinates rounded to a grid of 0.05° (about 5 km) to Open-Meteo. Open-Meteo keeps request logs for up to 90 days. Weather data: Open-Meteo, CC BY 4.0.
- OpenStreetMap. When you pick a place on the map, the app downloads map tiles from the OpenStreetMap Foundation. The tile requests reveal the area of the map you are looking at — which, after “my location”, is where you are — and your IP address. Map data © OpenStreetMap contributors.
- Google Play services provide location, geofences and activity recognition on the device under Google’s privacy policy.
3.6. Addresses you put into your rules
A rule can send data to an address you entered: a web request (webhook), a message through Telegram, ntfy.sh or another messenger, an e-mail through your mail server, an MQTT broker. What is sent and where is decided by you when you write the rule; the app is only the transport. We have no access to this data, and the recipient’s own privacy policy applies. Before a rule that sends data outside the phone is saved, the app shows which of these paths it uses.
4. What the app stores on the phone
Your rules, their history, saved places, variables, the journal of the last 200 runs, the event monitor and the assistant chat are kept in the app’s private storage. You can clear the journal and the event monitor in the app, or remove everything by clearing the app’s data or uninstalling it.
5. Android backup
If Android backup is on, your rules and settings are included in your Google account backup so they can be restored on a new phone. The journal, the event monitor, the assistant chat, variables, secrets and your API key are excluded from both cloud backup and device-to-device transfer. We have no access to your backup.
6. Security
Secrets you use in rules and your own API key are stored encrypted with a key held in the Android Keystore. They never appear in the journal, in exports or in backups. All connections described in section 3 that the app makes on its own use HTTPS; the app refuses plain http:// addresses outside your local network.
7. Export and sharing
When you export rules to a file or share a rule, the file contains the rule itself: its steps, texts and addresses. Secrets are included only as references ({secret:name}), never their values. Check what a rule contains before you share it.
8. Age
Whenomatic is intended for people aged 18 and over; the assistant relies on the Gemini API, which requires this. We do not knowingly collect data from children.
9. Your rights and deleting your data
You can ask for a copy of the data our server holds about your installation, have it corrected or deleted, or object to its processing. Write to whenomatic@gmail.com and include the support ID shown in the app’s assistant settings — without it we cannot tell which records are yours. We answer within 30 days.
On request we delete the installation’s balance, sessions and reports. Copies in Railway backups disappear when those backups expire (up to 89 days), Railway’s HTTP logs after 30 days, and copies of requests at Google after 55 days under Google’s terms; we cannot shorten those periods. If you live in the EU, the UK or another country with data-protection law, you may also complain to your data-protection authority.
If you write to us, we keep your e-mail and the correspondence as long as needed to answer and handle the request.
10. Analytics and crash reports
The app contains no analytics, advertising or crash-reporting SDKs. Google Play may collect crash and performance statistics (Android vitals) if you allowed it in your device settings; we see them only in aggregated form.
11. Changes to this policy
If the app starts handling data in a new way, we update this page before that version is released and change the date at the top. Significant changes are also mentioned in the release notes on Google Play.