Privacy Policy

Applies to the reLapse mobile app and to getrelapse.com.
Version 1.0 · Last updated 23 August 2026

1. Who is responsible for your data

Controller under the GDPR: Canburak Tümer, Berlin, Germany — support@getrelapse.com. The full postal address is in the Impressum.

reLapse is developed and run by one person; there is no company behind it. No data protection officer has been appointed, because the criteria in Art. 37 GDPR and § 38 BDSG are not met.

2. Data that never leaves your device

The core of the app works entirely offline. The following are written only to local storage on your phone and never leave it — not to me, not to anyone else:

• The habits you create — name, icon, colour, sort order.
• Every logged entry — the timestamp, the time zone offset at the moment you logged, and whether it came from the app or a widget.
• Any note you attach to an entry.
• Your in-app settings, including which calendar habit you last viewed.

It is held in a SQLCipher database (AES-256), with the key generated on your device and kept in the iOS Keychain or Android Keystore. Because it cannot be read from outside the device, it also cannot be recovered for you: delete the app without a backup and the data is gone.

2.1 The widget exception

Widgets run as separate OS extensions and cannot open the encrypted database, so the app publishes a small copy into the shared app container for them: habit name, icon, colour and a 90-day count. That copy is unencrypted but stays inside the app sandbox on your device and is never transmitted. Notes and entry history are never part of it.

2.2 Pattern reminders

Pro can turn on an opt-in reminder shortly before a time you often log. It is scheduled by the operating system, on the device, from the same on-device analysis Insights uses — nothing about when you log is sent anywhere to produce it. The notification never names the habit (a lock screen is not a private place), reads only “Around this time — You log more often now than at other hours,” and asks for the OS notification permission the first time you turn it on, not before. Turning it off leaves nothing scheduled.

3. Data I or my processors do receive

These are the only situations in which personal data leaves your device.

3.1 Buying or restoring Pro

reLapse has no accounts, no sign-in and no password — there is nothing to register and nothing to log into. Buying happens entirely inside Apple's or Google's own purchase sheet: no name, no email and no identifier of mine passes through me at that point, because I am not there for it. Apple and Google are merchant of record and separate controllers for the payment itself; I never see your card, billing address or payment details.

What I do receive, as the purchase completes, is purchase state: a receipt, product identifiers, purchase and expiry dates, and renewal or cancellation events, and the name of the screen a purchase was started from (for example the welcome flow or the second-habit prompt), tied to a random identifier RevenueCat assigns your install — not your name, your email or your Apple/Google account. It is used to verify the purchase is genuine and keep your tier correct as a subscription renews or lapses (Art. 6(1)(b) GDPR). RevenueCat is my processor for this and the only party involved; there is no reLapse server in between, and no habit name, entry, timestamp or note ever reaches anyone at this step.

Restoring on a new device works the same way, automatically, for whichever store account is signed in on that device — there is no login step of its own to restore.

3.2 Advertising in the free tier

The free tier shows banners on the Home and Calendar screens and one in the Recent list, served by Start.io — never while you are logging or during the Undo window. Pro removes them. Start.io receives technical data to serve them, such as your device's advertising identifier where the system provides one, IP address, device type, OS version and coarse location derived from the IP; its own privacy policy lists the details. Habit names, entries and notes are never passed to the ad network; there is no code path that could.

Every banner is non-personalised, for everyone: the app tells Start.io that you have not consented to personalised advertising. On iPhone, before the first banner is requested, iOS asks whether reLapse may track you across other companies' apps and websites (Apple's App Tracking Transparency prompt), because Start.io's software declares that it may use your device's advertising identifier and location for advertising when you allow it. You can say no, and reLapse works exactly the same; you can change your answer at any time in Settings > Privacy & Security > Tracking. Pro users are never asked, and reLapse itself does not track you. The basis for serving these banners is my legitimate interest in funding a free tier (Art. 6(1)(f) GDPR). To stop them altogether, upgrade to Pro. Start.io also honours opt-outs made directly with it — see its privacy policy.

3.3 Purchase statistics

To see where people leave the purchase screen, the app reports a handful of steps of that screen to my own analytics server (a self-hosted Umami instance, run by me): that a purchase screen was shown, from which screen of the app, which plan was tapped, whether a purchase or a restore was started, whether it went through or why not (a category such as “cancelled” or “network”, never the store's own message), and that the screen was closed. Each report also carries the platform, the app version and the app's language. Nothing about your habits, entries or notes is ever part of it; the reports are built from a fixed list of values that has no room for them.

There is no account and no persistent identifier: a random number is made each time the app starts, kept only in memory, and used to tell one visit to the purchase screen apart from another. The server sees your IP address to work out a country and does not store it. Reports are not deleted on a fixed schedule: they are anonymous (no account, no persistent identifier, and the IP address is not stored), and I keep them to compare releases over time. If that changes I will say so here and state a period. The server is a machine I rent from Hetzner in Frankfurt, Germany, and the data does not leave the EU. The basis is my legitimate interest in understanding and improving how the free tier turns into Pro (Art. 6(1)(f) GDPR). This is on by default and you can switch it off at any time in Settings > “Share anonymous purchase statistics”; nothing is sent after that. It is not tracking across other companies' apps or websites.

3.4 Backups you create

Backup is a manual action. The app encrypts a snapshot with a passphrase you choose (AES-256-GCM) and hands the file to the system share sheet; you decide where it goes. The passphrase is never stored or transmitted, so nobody — including me and whoever hosts the file — can read it, and a forgotten passphrase cannot be recovered. Once the file is in a third party's storage, that provider's privacy policy governs it.

3.5 Contacting support

If you email support@getrelapse.com I receive your email address, your message and anything you choose to attach. I use it only to answer you. Legal basis: Art. 6(1)(b) GDPR where your message concerns a contract, otherwise Art. 6(1)(f) — my legitimate interest in responding to enquiries. Support correspondence is deleted once the matter is resolved and no legal retention period applies, normally within 12 months.

3.6 This website

getrelapse.com is a static site. It sets no cookies, runs no analytics, loads no third-party fonts, trackers or embeds, and has nothing for you to consent to. Your browser's request is served and forgotten. The site is hosted by DreamHost, Inc. in the United States, which may keep short-lived server logs containing IP addresses for security and troubleshooting; the legal basis is Art. 6(1)(f) GDPR and the transfer is covered by section 5 below.

4. What I do not do

Personal data is never sold or rented. There is no profiling and no automated decision-making under Art. 22 GDPR, no behavioural analytics on habit data (no SDK in the app reads your habits, and the purchase statistics in 3.3 cannot carry them), and no marketing email.

5. Processors and international transfers

Some of these are established in, or transfer data to, the United States. Those transfers rely on the European Commission's Standard Contractual Clauses and, where the recipient is certified, on the EU–US Data Privacy Framework. You may request a copy of the relevant safeguards from me.

6. How long I keep things

• On-device data: until you delete it. It is under your control, not mine.
• Purchase and entitlement records: there is no account for these to belong to, so there is nothing of mine to delete on request. RevenueCat retains the receipt data behind your subscription, tied to a random identifier rather than your name, under its own retention policy — it is what proves the purchase is genuine, the same role a receipt plays with Apple or Google directly.
• My own accounting records: aggregate revenue and payout figures from Apple and Google, kept because German commercial and tax law requires it (§ 147 AO, § 257 HGB — up to 10 years). These are my own bookkeeping, not a record of what any individual user bought.
• Support email: normally deleted within 12 months of the matter being resolved.
• Purchase statistics (3.3): anonymous, so with no fixed deletion date; reviewed if that changes.
• Server logs: a short period set by the hosting provider, typically no more than 30 days.

7. Your rights

Under the GDPR you have the right to:

• access the personal data I hold about you (Art. 15);
• have inaccurate data corrected (Art. 16);
• have your data erased (Art. 17);
• restrict processing (Art. 18);
• receive your data in a portable format (Art. 20);
• object to processing based on legitimate interests (Art. 21);
• withdraw consent at any time, without affecting processing already carried out (Art. 7(3)).

Write to support@getrelapse.com and I will respond within one month — though for your habit data, the fastest route to erasure and portability is inside the app itself: Settings → Backup & restore exports everything, and Settings → Delete all data erases it, immediately, without needing to ask me at all. There is no account to look you up by, so most of these rights are already satisfied by the app's design rather than by a request to me. See deleting your data.

You also have the right to lodge a complaint with a supervisory authority. The competent supervisory authority is the Berliner Beauftragte für Datenschutz und Informationsfreiheit, Alt-Moabit 59–61, 10555 Berlin.

8. Children

reLapse is not directed at children. It is rated for users aged 12 and over and I do not knowingly collect personal data from children under 16. If you believe a child has provided me with personal data, contact me and I will delete it.

9. Security

Encryption at rest, keys in platform secure storage, TLS in transit, backups encrypted before they leave the app. No system is perfectly secure, but there is no reLapse backend to breach in the first place — nothing server-side holds a copy of your habits for anyone to reach.

10. Changes to this policy

If I change how data is handled I will update this page and move the version number. Material changes will also be surfaced in the app. The current version always lives at getrelapse.com/privacy.html.