Last updated: 4 October 2026
Bide (“we”, “our”, or “the App”) is a self-guided tool for getting through urges and building habits. This policy explains what the App stores, what leaves your device, and what control you have.
The short version. Bide works without an account. Your habits, check-ins, written notes and progress are stored only on your device in encrypted storage. If you agree to share usage analytics, Bide sends how the App is used (such as which habit you chose, which screens and tools you open, and check-ins) to PostHog under a random analytics ID, and never anything you write. Crash reports, without personal details, go to Sentry unless you turn them off. If you use paid features, RevenueCat receives a random app-specific identifier and store purchase information so the App can provide and restore your access.
The following is stored locally in an encrypted database on your phone:
This data is encrypted at rest using a key held in your device’s secure storage. It is not sent to Newkbyte, RevenueCat, Apple or Google. Uninstalling the App removes the local data from that device.
Bide does not ask for an email address, phone number, name or sign-in. We do not operate a Bide user-account database and cannot read your habits, notes or check-ins.
Bide asks once, at the end of setup, whether you want to share usage analytics. It is off unless you say yes, and you can change your answer at any time in Settings → "Share how I use Bide". Nothing is sent before you answer, and nothing is sent at all if you say no.
If you say yes, Bide creates a random analytics ID on your phone. It is not your name, Apple ID, Google account, device ID or advertising ID. Usage events are sent under that ID to PostHog, Inc., using its EU cloud (data stored in the EU). They contain only:
They never contain anything you write (notes, reasons, plans, captions), exact amounts you enter (money goals are sent only as a range, such as "£250–£500"), your contacts, or your location. Bide asks PostHog to discard your IP address, and no location is kept.
While analytics is on, the same random ID is also given to RevenueCat, so that purchase events confirmed by the App Store or Google Play (such as a trial converting or a renewal) can be counted against it.
We use this to understand which parts of Bide help people and where the App falls short. It is not used for advertising, and it is not shared with advertisers or data brokers. Our legal basis is your consent. We keep analytics to compare use of Bide's features across releases and identify improvements. An automatic service checks hourly and requests cleanup after each 300-day analytics history cycle. Cleanup removes profile fields and all event history already received for that ID, including newer events in the same cycle. The random ID and technical cleanup timestamps remain so future analytics can continue. PostHog processes deletion in the background; our service checks completion and flags overdue requests. This is not a guarantee of erasure on an exact day. You can request earlier deletion as described below. The cleanup service runs on Cloudflare and processes analytics profile records in memory solely to manage deletion; it does not keep a separate copy of those records.
Turning analytics off stops sending immediately and deletes the analytics ID from your phone. If you turn it on again later, a new ID is created. To delete data already sent, email support@newkbyte.com with the ID shown in Settings under "Your analytics ID", and we will arrange deletion from PostHog. Event deletion is processed in the background; we check that it has completed.
To find and fix crashes, Bide sends crash reports to Functional Software, Inc. (Sentry), using its EU region (data stored in the EU). Crash reports are on by default, and you can turn them off in Settings → "Send crash reports".
A crash report contains the type of error, the lines of Bide's code involved, the App version, and your phone's model, operating system and language. Bide removes the error message before sending, because a message could quote something you typed. A report never contains your habit, notes, reasons, check-ins, anything you write, screenshots, your name or an advertising ID.
If you have agreed to usage analytics, Sentry also receives an anonymous count of app sessions, so we can tell how often Bide crashes. Our legal basis for crash reports is our legitimate interest in keeping the App working. Sentry keeps crash reports for up to 90 days.
Version 1.0 of Bide sent identifier-free event counts and limited diagnostics to a Newkbyte endpoint hosted by Cloudflare. Version 1.1 and later no longer send anything there.
Subscriptions and the one-time Lifetime purchase are processed by the Apple App Store or Google Play and managed for us by RevenueCat, Inc. Newkbyte and RevenueCat do not receive your full payment-card details.
To provide, restore and manage paid access, RevenueCat receives:
RevenueCat does not receive your habit names, notes, reasons, check-ins or journal content. See RevenueCat’s privacy policy for information about its processing.
“Clear local data and start over” deletes Bide’s local database, including the local copy of its random RevenueCat identifier. It does not delete transaction records held by Apple, Google or RevenueCat, some of which may need to be kept to operate purchases, prevent fraud or meet legal obligations.
"Delete all data" in Settings also turns off usage analytics, deletes the analytics ID from your phone and resets crash reports to their default.
For a request concerning RevenueCat purchase data, email support@newkbyte.com. If possible, contact us before clearing or reinstalling the App and tell us whether you use iOS or Android and the approximate purchase date. Because Bide has no account and the identifier is anonymous, we may need store receipt information to locate the correct record. We will arrange deletion with RevenueCat where it is legally and technically permitted. Requests about Apple or Google store records must be made to the relevant store provider.
Reminders are scheduled and delivered entirely on your device. Bide does not use push notifications and no Bide server is involved. Notifications never name the habit you are working on.
If you enable the optional lock, verification is performed by your device’s operating system. Bide receives only the success or failure result. No biometric data is accessible to, or stored by, Bide or Newkbyte.
Information about habits and urges may be considered health-related and sensitive in some jurisdictions. Your written notes, reasons and detailed habit records remain on your device, and Bide does not require an account. If you choose to share usage analytics, limited information such as your chosen habit and check-in outcomes is sent as described in section 3.
Bide is not directed at children. We do not knowingly collect personal data from children through the App.
If this policy changes materially, the updated version will be published here with a revised date.
Questions or privacy requests: support@newkbyte.com