RushLess was built so that quitting a habit does not mean handing over your data. There is no account, no profile on our side, and no server holding your history. Here is exactly what stays on device, the little that leaves it, and what we never collect.
Everything you enter in RushLess is written to a local database on your device and stays there. That includes the drinks you log with their brand, size, caffeine content and price, the trigger you tag when a craving hits, your weekly quota and taper schedule, your streak history, your coach sessions, your own custom drinks, and your savings goal with its name and price.
You do not need an account to use RushLess. There is no sign-up, no email address, and no profile stored on our side — we could not look up your log even if we wanted to. If you delete the app, that data is gone with it.
The energy-drink catalog and its barcodes ship inside the app as a bundled dataset. Looking a drink up or scanning its barcode is a local database query — no request is sent anywhere.
RushLess 1.0 has no cloud sync and no cross-device account, so your log exists on exactly one phone. We are not copying it to a server, and there is nothing for us to lose in a breach.
The RushLess coach is not a chatbot on a server. Its scenarios, questions and suggested alternatives ship inside the app, and the whole conversation is resolved on your device. Nothing you tap or type in the coach is transmitted, and your coach history is stored locally alongside the rest of your data.
The same is true of the 90-second craving reset and every number on the Stats tab: they are computed from your local database, on the phone, whether or not you have a connection.
To see whether the app actually helps, RushLess sends a small set of anonymous, aggregated product events through PostHog — things like the app being opened, an onboarding step finished, a craving reset completed, or the paywall shown. Each event is a counter with at most a coarse label attached (which onboarding step, which coach scenario, which of five trigger categories).
We never call PostHog’s identify function, and person profiles are disabled, so no profile is ever built about you. There is no autocapture of taps or screens, no session replay, no crash-log scraping of your content, and no advertising SDK anywhere in the app. Your drink log, your name, your goal and your coach conversations are never sent as event data.
The sections above describe the app. This site — getrushless.app — is a set of static pages, and it is built to need no cookie banner because it stores nothing on your device: no cookies, no localStorage, no fingerprinting, no ad or social embeds, and no web fonts loaded from anyone else’s server.
To see which pages and articles people actually read, the site loads Cloudflare Web Analytics. It counts page views and referrers without setting a cookie and without writing anything to your browser, so there is no identifier that follows you between visits or across sites. We also use Google Search Console, which places no code on the page at all and only shows us aggregate search statistics.
RushLess+ is billed through the App Store. Apple handles the payment; we never see your card details, billing address or Apple ID. We use RevenueCat to read the App Store receipt and tell the app whether your subscription is active, and it stores an anonymous app-user id together with that subscription status.
So that we can tell whether the subscription is worth what it costs people, RevenueCat is given the same anonymous analytics id the app already uses. It is not linked to a name, an email address or an Apple ID — it exists only to join two anonymous data sets.
RushLess asks for as little as possible, only at the moment a feature needs it, and every one of them can be declined without breaking the app:
The complete list of companies that ever touch anything from RushLess — the app and this site together. There is no fifth, and no data broker or advertising network among them:
Because your log lives on your device, you already hold it. Profile → Data exports the drinks you have added as a CSV file you can open in any spreadsheet, and re-importing an edited file updates them. Profile also has a reset that erases your entire local history in one step — profile, logs, plan, favourites, coach sessions and craving history.
There is no account to request an export of or delete, because we never created one. For the two things that do exist outside your phone — the anonymous product events and your subscription status — you can ask us what is held and ask for deletion under GDPR or CCPA, and a person answers within 30 days. Since those records carry no name or email address, we may need the anonymous id shown in the app to find them.
RushLess is rated 12+ and is not directed at children under 13. We do not knowingly collect data from them — and since the app has no account, no messaging and no server-side profile, there is very little that could be collected in the first place.
If we change how data is handled, we update this page and raise the version number at the top. Material changes are announced in the app before they take effect, not buried in a release note.
Questions, requests, or something that reads wrong on this page — write to us and a person answers.
support@getrushless.app