Privacy Policy
Last updated: 9 October 2026
This Privacy Policy explains how the hone mobile application ("hone", "the app", "we") handles your information. The short version: your habits and your history are stored on your device. A small set of anonymous identifiers reaches our services so that purchases, the Studio Bundle, invites and support work, and this page lists each of them. A few Pro features send a photo or a text you choose to an AI service to be read, and section 4 says exactly what is sent.
1. What stays on your device
What you create in hone is stored locally on your device: your habits, completions, streaks, categories, achievements, notes, printed sheets and settings. hone asks for no email, no name and no password, and we keep no copy of this data on a server. If you uninstall the app, the data is removed with it. You can make your own copy with the app's export feature.
Content from the app leaves the device in two cases only: when you use one of the Pro features in section 4, and when you write to us through the support screen (section 3).
If the backup of your Android device is switched on, Android can include hone's data in the device backup in your Google account. That backup is made by Android, and we have no access to it.
2. What the app sends on its own
From the first launch, hone sends the following without asking. None of it contains your habits or your history.
- Purchase identifier. hone uses RevenueCat to check whether Hone Pro is active. RevenueCat issues an anonymous app user ID on first launch and holds the purchase status behind it. Together with this ID the app sends RevenueCat the install source reported by Google Play (for example a link from another Clearpoint Studios app) and the result of an integrity check of the app: whether it was installed from an app store, carries our signature, and runs outside a debugger or an emulator.
- Install identifier and product events. A random ID generated on the device, sent to our own statistics service on Cloudflare with anonymous events: that the app was opened, which onboarding steps were shown, that the Pro screen was opened or closed, whether a purchase was started, completed, cancelled or failed, that the Studio Bundle screen was opened or a bundle code was redeemed, that a streak freeze was applied automatically, and that day 7, 30 or 66 of a protocol was reached. Each batch of events carries the app version, your language, the platform, the anonymous RevenueCat ID, whether Pro is active and the install source. The service notes the country the request comes from and does not store your IP address. It answers with the variants of running product tests assigned to your installation.
- Device identifier (hashed). A SHA-256 hash of the Android ID of your phone, sent together with the anonymous RevenueCat ID to our service for the Studio Bundle and invites (a Cloudflare Worker). This happens once after installation on first launch, to check whether a Studio Bundle belongs to this device. It happens again when you restore purchases and no purchase is found, when you redeem a bundle code, when you open the invite screen, and when you use an invite link or an invite code. The hash lets the service give Pro back after a reinstall on the same phone, limits how many devices one bundle code can unlock, and stops an invite from being redeemed more than once from the same device. The Android ID itself never leaves the device. The hash carries no name and no contact detail, is not used for advertising and is not sold.
- Studio Bundle status. On each launch the app asks the same service, with the anonymous RevenueCat ID alone, whether a Studio Bundle is active for this installation. If you installed hone through an invite link or a bundle link, Google Play passes the app the referrer string of that link, which contains the code.
- Anonymous support account. On launch the app signs in to our support backend at Supabase with an anonymous account, so that a reply to a message you send can reach you. The account is a random ID. It has no email, no name and no password.
- Push token. hone includes Firebase Cloud Messaging from Google, which delivers our reply to a support message as a notification. Firebase creates an installation ID and a push token for the app. If notifications are allowed for hone, the app stores this token with the anonymous support account on our support backend, together with the platform and your language.
- Play Store check. At most once a day the app can ask Google Play whether the store pages of other Clearpoint Studios apps exist, so that the More Apps list links only to apps that are available. These requests carry no identifier.
All of this travels over HTTPS.
3. What is sent when you write to us
Nothing in this section is sent until you press send on the support screen. We then receive the message you wrote, a subject taken from its first line, your language, the app version, your Android version, the manufacturer and model of your device, and whether Pro is active. If you bought Pro, the ticket also carries your anonymous RevenueCat ID, so that a refund under the guarantee can be matched to your purchase. The backend notes the country the request comes from.
Tickets and messages are stored by Supabase on servers in the European Union (Frankfurt, Germany). Messages are passed to Google's Gemini API for translation, so that we can read a message written in another language and you can read our reply in yours. A copy of a message you send from the support form, with the app version, the operating system version and your language, is relayed through a Cloudflare Worker to our Telegram chat, so that we notice it quickly. This relay keeps your IP address for ten minutes to limit spam.
4. Pro features that read a photo or a text
Four features of Hone Pro use an AI model. Nothing is sent until you start one of them, and none of them runs on its own.
- Reading a printed sheet. The photo you take of the sheet, the code printed on it, the habit names printed on it, the day numbers above the columns and the layout of its boxes.
- Proof photo. The photo you take or choose, and the names of the habits it could prove, each with the note you added to that habit if there is one.
- The weekly reading of your week. The names of your habits, and for each one how often it was due, done and missed in that week and its current streak, plus the totals per day and for the week.
- Habit suggestions from a sentence. The sentence you write and the names of the habits you already have.
Each request goes over HTTPS to our reading service on Cloudflare, which passes it to Google's Gemini API and returns the answer to your phone. The request carries your anonymous RevenueCat ID, because the service checks with RevenueCat that Pro is active, and the offset of your time zone, so that the daily allowance resets at your local midnight. Where the answer is a text, it also carries your language. When a Pro user opens the sheet screen, the app asks the service how many readings are left today. That request carries the same ID and offset and no content.
Our service keeps a counter of how many requests each identifier used today. It saves no copy of the photo, of the text or of the answer. If a request fails, a short excerpt of the model's answer can be written to the service's error log.
5. Purchases and the Studio Bundle
Hone Pro and the Studio Bundle are sold through Google Play, which processes the payment. hone does not receive or store your payment details. RevenueCat holds the purchase status behind the anonymous ID described in section 2. These transactions are also subject to the privacy policy of Google Play.
The Studio Bundle is one purchase that unlocks Pro in several Clearpoint Studios apps. For it, our service stores a bundle code, the apps in which the code was redeemed, the anonymous RevenueCat ID of each of those installations and the hashed device identifier from section 2. It also logs each attempt to redeem a code with the hashed device identifier, which limits guessing. If a bundle purchase is refunded, RevenueCat tells the service, and Pro from that bundle ends in every app.
6. The former accountability partner feature
Earlier versions of hone had an optional accountability partner feature that stored a small profile on our backend. The feature has been removed, and the current version of the app neither creates nor reads such a profile. If you created a partner profile in an earlier version and want it deleted, email us your friend code. The steps are at hone.clearpointstudios.at/delete.
7. Data retention
How long each thing is kept, and by whom:
- On your device. Kept as long as hone is installed. It goes when you uninstall the app. We never receive a copy, so there is nothing on our side to keep.
- Install identifier and product events. Deleted automatically 400 days after they arrive. A scheduled job on the statistics service runs every day and removes everything past that date, including the install record itself once nothing newer has come from it.
- Purchase identifier. Held by RevenueCat so that a purchase can be restored. It is deleted when you ask us.
- Hashed device identifier, bundle codes and invite codes. Held by our Studio Bundle and invite service until you ask us to delete them, because recognising the phone after a reinstall is what the hash is for.
- Support account, tickets, messages and push token. Held on our support backend and deleted when you ask us. Closed tickets and their messages are also removed by a scheduled job that runs every day. The copy relayed to our Telegram chat stays there until we delete it. The IP address the relay uses to limit spam is deleted after ten minutes.
- Photos and texts sent to the Pro features in section 4. Not kept by our service. The counter behind your purchase identifier is deleted automatically 30 days after your last request.
When you ask for deletion, we remove the data from our services. Requests are handled within 30 days.
8. No advertising, no cross-app tracking
hone contains no advertising, no ad SDK and no analytics SDK of another company. The only statistics are the anonymous product events described in section 2, which go to a service we run ourselves. Nothing described on this page is sold, shared with advertisers or used to follow you across apps of other companies.
9. Children's privacy
hone is a general-audience app and is not directed at children. We do not knowingly collect personal information from children.
10. Data security
Data on your device is governed by your device's own protections, such as your screen lock and device encryption. Everything described in sections 2 to 5 is transmitted over HTTPS/TLS. On the support backend, access rules restrict your tickets and messages to the anonymous account that wrote them and to us. We recommend keeping your device secured and up to date.
11. Your rights
Under the GDPR you can ask what is stored about you, ask for it to be corrected or deleted, and object to its processing. Write to the address below. Because every identifier on this page is anonymous, include your invite code or your Studio Bundle code if you have one, so that we can find the matching records.
12. Service providers
Google Play handles payments, distribution and the install referrer. RevenueCat holds the purchase status. Cloudflare hosts this website and the services we run ourselves: the product statistics, the Studio Bundle and invite service, the reading service for the Pro features and the feedback relay. Supabase stores the support account, tickets, messages and push token. Google's Firebase Cloud Messaging delivers the notification for a support reply. Google's Gemini API reads the photos and texts you send with the Pro features in section 4 and translates support messages. Telegram carries the relayed copy of a message from the support form.
13. Changes to this policy
We may update this Privacy Policy from time to time. Any changes will be posted on this page with an updated "Last updated" date. Material changes affecting how data is handled will be reflected here before they take effect.
14. Contact
If you have any questions about this Privacy Policy, contact us at [email protected].
Back to hone.clearpointstudios.at