Privacy policy

Relix is made by Daniel Bobunov, an independent developer based in New Jersey, USA, who publishes under the name Oversauced. The seller name on the App Store is the same person. In this policy "we", "us" and "our" mean that developer. We are responsible for the personal data described here.

Contact, including our person responsible for privacy:

• Relix is for people aged 14 and older. Relix will confirm that you are at least 14 before Screen Time setup, purchases, experiments or optional data sharing. If it cannot, setup pauses until your eligibility is resolved.
• Users aged 14 to 17 get the protections in section 8.
• Relix is for personal, voluntary use on your own iPhone. It is not a parental-control app, and it is not for schools, employers or other organisations. Do not use it to manage another person's device.

Relix uses Apple's Screen Time frameworks (FamilyControls, ManagedSettings and DeviceActivity) to block apps. This data stays on your device:

• the apps, categories and websites you pick to block. Apple gives Relix these as opaque tokens. To draw the block screen, Apple may give Relix's on-device shield extension an app's display name or a website's domain. Relix does not upload names, domains or tokens;
• how many apps, categories or websites you picked;
• whether you have given Relix Screen Time access, and changes to that;
• the timing records Apple's Screen Time system writes while a session runs (for example when a block started and ended);
• taps on the buttons of the block screen ("shield");
• anything Relix works out from these records, such as whether a session was "Unbroken", minutes counted from those records, why a session was interrupted, whether an earn-back unlock worked, and whether expected records were missing.

Relix uses these records only to run your focus sessions and settle their rewards. They are left out of analytics, exports and the Relix backup file (section 6), and Relix never uploads them. Like other app data, they can be part of an iCloud or computer backup of your iPhone that iOS makes; Apple or your computer handles that backup, not Relix. Per-session records become eligible for deletion 30 days after the session settles, and Relix removes them the next time it runs its cleanup. Your current block list stays until you change it or delete your data.

Other data that stays on your device: your collection (relics, engravings, essence, streak); your session history, intentions and any titles you write; your onboarding quiz answers (never sent; with analytics on, only the session length you chose is sent, section 4.2); your settings and your age band.

If you delete Relix without a backup file or export, this data is normally gone from the device (see section 10 for what deleting the app does and does not do).

4.1 Purchase service (when Relix starts)

When Relix starts, it contacts RevenueCat to check whether you have Relix Pro, even if you have never bought it. When you buy, restore or renew Pro, Apple processes the payment and RevenueCat receives the purchase details from Apple.

RevenueCat's purchase reporting is separate from the optional PostHog analytics in section 4.2. We never see your payment card; Apple handles payment under its own privacy policy.

4.2 Optional product analytics (only if you opt in)

Relix will ask during setup whether you want to share usage analytics. The answer is no unless you choose yes, and you can change it at any time in Settings. If you opt in, Relix sends events to PostHog on its US servers.

What we send:

• a random ID PostHog creates for your copy of Relix. We do not ask for your name or email for analytics and do not join this ID to your RevenueCat ID. The ID still distinguishes your app's events, so we treat it as personal data where the law does;
• onboarding: which step you reached, whether you started your first focus session at the end of setup or skipped it, and the session length you chose. Your quiz answers are not sent;
• focus sessions: that a session started, and whether you ended it early or not, with its planned length and mode. The session's result (such as cracked or Unbroken), Honour status, your streak and Screen Time-derived details (verification, interruption reasons, minutes counted from Screen Time records, whether blocking was armed) are not sent;
• earn-backs: that you opened the mini-game (with the session's mode), how many answers you got right and whether you won. Whether the native unlock worked is not sent;
• sharing a relic: only that you used the share button, not which relic or its rarity;
• keepsakes and engravings: which catalogue keepsake you bought, and, when you pin an engraving, whether it has a title (never the title itself);
• the Pro screen: seen (how many plans loaded and whether the App Store was reachable); purchase attempted (plan type, whether it had a trial, and the result: success, cancelled, pending, failed, not allowed, already owned, not eligible, unverified or network error); restore attempted and its result (found, nothing found or error);
• technical fields: a per-event ID and timestamp used to avoid duplicates, device model, iOS version, app version, language, time zone and screen size.

What we never send: your name, email, contacts, photos, location, advertising ID, the names of apps you use or block, or any Screen Time data. Relix tells PostHog not to look up your location from your IP address. PostHog still receives the IP address when your phone connects; we set PostHog to discard it rather than store it. Relix sends no automatic app events (such as installing, opening or closing the app), does not record your screen and does not capture taps automatically.

Why: to learn which parts of Relix work, where people get stuck, and whether Relix helps people focus.

4.3 Crash reports

Relix does not include a third-party crash-reporting tool. If you turned on "Share with App Developers" in iPhone Settings, Apple may send us crash logs and basic usage statistics under Apple's privacy policy. If we ever add a crash-reporting tool, it will be off unless you opt in, and we will update this policy first.

4.4 Messages you send us

If you email us, we receive your email address and what you write, through our email providers: Cloudflare, which receives and forwards email sent to our support address, and Google, which hosts the mailbox. We use it only to answer you. Relix has no in-app diagnostics upload: to report a problem, describe it in your email.

4.5 Notifications

Relix schedules notifications on your iPhone, for example "your relic is forged", "break over" and, if you start a trial, an optional reminder. They are created on the device. Relix does not send us a push token.

4.6 Share cards

When you share a relic, Relix makes the image on your iPhone and hands it to the iOS share sheet. We do not receive it. Share cards never show Screen Time-derived marks such as "Unbroken".

4.7 What Relix does not do

• No accounts or sign-in.
• No advertising and no ad networks.
• No tracking as Apple defines it, and no tracking permission request.
• No selling of personal data, and no sharing for targeted advertising.
• No location, contacts, photos, camera or microphone access.
• No automated decisions with legal or similarly serious effects on you.

If we add a recipient, we will update this policy before it receives any data.

This website has no cookies, no analytics and no ads. Like every website, its host (Cloudflare) sees your IP address and browser details, in security logs kept by Cloudflare under its own policy.

Relix has no account and no cloud copy of your data. Relix does not back up your collection automatically and does not sync it to iCloud. You can make a backup file yourself:

• Back up my collection (Settings → Your data) creates one file and opens the iPhone share sheet. You choose where it goes, for example Files, iCloud Drive, AirDrop or email. Relix never receives the file. It is not encrypted, so keep it somewhere you trust. The service you save it to handles it under its own terms.
• What the file contains:
  • your collection: relics (with their gold seams, your attuned relic and your showcase), engravings with their pins and titles, keepsakes owned and equipped, and essence;
  • the reward state Relix needs so that a restore never grants a reward twice: forge days, reward slots used, tickets, a pending mend, your streak, and the IDs of sessions already rewarded;
  • your session history as Relix decided it: planned times and length, mode, Honour or not, whether you ended it early, outcome, the relic awarded, your intention and project;
  • your workbook (projects, templates, reflections) and your schedule definitions.
• What it never contains: the Screen Time records in section 3 or what Relix measured from them, such as Unbroken marks, verification results and interruption reasons. The rewards those sessions earned are part of your collection, so they are in the file. It also never contains the apps or websites you block, purchase or subscription details, your age range, your analytics ID, or your consent choices.
• Restore from a backup (Settings → Your data):
  • Relix checks the file first: its version, its checksum and every value in it. Then it shows a summary of what the file contains.
  • It replaces your collection only when you confirm. Your current schedules and this iPhone's last 30 days of session records stay; the summary says so.
  • A restore never grants rewards again and never turns blocking on. Restored schedules come back switched off.
  • You can't restore while a focus session or Hard Mode is running.
• Copies on your iPhone: Relix keeps a temporary copy of the file it hands to the share sheet. That copy is removed at your next backup or export (once it is a day old), by Delete all my data, or when iOS clears temporary files. When you pick a file to restore, iOS gives Relix a copy; Relix deletes it once it has read it, and again the next time it opens or when you delete your data. While a restore is being saved, Relix keeps a copy of the backup on your iPhone and deletes it once the restore is complete.

Relix will use Apple's age-range tools to establish that you are at least 14 and whether you are 18 or older. Relix stores only the result (for example "14–17") on your iPhone, never your birthdate. Users established as 14 or older but not established as 18 or older get the teen protections:

• Analytics are off unless you opt in.
• No experiments.
• No discounts, save or win-back offers, countdowns or promotional pop-ups.
• No notifications designed to bring you back. Necessary notices, such as a session ending or a purchase update, still arrive.
• You can still see Pro's standard prices in Settings → Plans. Purchases go through Apple and may need a parent's approval (Ask to Buy) or consent required by your state.
• In Hard Mode, teens can always leave after a 60-second wait, as often as needed, and continuous Hard Mode blocking lasts at most 4 hours.

Parents and guardians: contact us by email (address in section 15). We will check that a request comes from someone entitled to make it.

Relix does not admit users under 14. We do not knowingly collect personal data from children under 14. The purchase-service check in section 4.1 runs when the app starts, before the age check; it carries no name, email or Apple ID. If you believe a child under 14 has given us data, email us and we will delete what we can locate.

• Delete all my data (Settings → Your data). Relix first switches off your schedules and releases every block it controls, including a running session and earn-back breaks. If Hard Mode is running, you first wait as long as an Emergency exit takes; no exit is used. Then it deletes your data on the iPhone: your collection, history, settings, Screen Time records, scheduled notifications, its analytics ID and unsent analytics, and temporary copies of backup and export files. It does not delete analytics already sent to PostHog: when it is done, it shows your former analytics ID (if you ever shared analytics) so you can ask us to delete those events (see Request my data / deletion below). Deletion never needs a subscription or an Emergency exit.
• Share usage analytics (Settings). Turn it off at any time; Relix stops sending analytics straight away.
• Request my data / deletion (Settings › Your data, shown once analytics has ever been on). Relix opens an email to us containing your analytics ID and nothing else. You must send the email; opening it does not send it. You can also copy the ID and write to us yourself. We delete the data in PostHog within 30 days of receiving your request.
• Back up and export. "Back up my collection" (Settings) gives you the backup file described in section 6. The workbook's CSV export gives you your session history as Relix decided it, as a spreadsheet. Neither is sent to us.
• Deleting the app normally removes its data from your iPhone. It does not cancel a subscription, does not ask RevenueCat or PostHog to delete anything, and does not remove existing iCloud or computer backups. Offloading the app keeps its data. Use Delete all my data first if you want Relix to carry out its deletion process.
• Purchase records that Apple or RevenueCat must keep by law stay with them; we will tell you which ones on request. To manage or cancel a subscription, use your Apple account settings.
• We cannot delete files you exported or backup files you saved yourself.

Data on your iPhone is protected by iOS. Relix sends data to RevenueCat and PostHog over encrypted connections. No secret keys ship inside the app. No system is perfectly secure. If a breach affects you, we will tell you and the authorities where the law requires.

Relix launches in the United States, Canada, the United Kingdom, Australia and New Zealand. It is not offered in the EU or EEA at launch.

Under this policy, wherever you live, you can ask us what data we hold about you, and ask us to correct it, delete it or give you a copy. Email us (address in section 15). We answer within 30 days, or sooner where the law requires (for example one calendar month in the UK, or 20 working days in New Zealand). We may need information to locate your records and to check the request, such as your analytics ID (shown in Settings). Data that exists only on your iPhone can be managed with the app's own controls. We will explain any lawful exception or data we cannot reach. We will not treat you worse for using your rights.

Additional legal rights apply where a law covers our processing.

United States. We do not sell personal data, share it for cross-context behavioural advertising, or use it for targeted advertising or profiling with legal effects.

• California: where the CCPA applies, California residents have its rights of access, deletion and correction, and the right to limit certain uses of sensitive personal information where relevant. We never sell or share information of users we know are under 18, and offers and experiments are switched off for them.
• Texas: where the Texas Data Privacy and Security Act applies, you can appeal our decision on a request by emailing us, and then contact the Texas Attorney General. Purchases by minors with Texas Apple accounts may need a parent's consent through Apple.
• Other states: where a state privacy law applies (for example Virginia, Colorado, Connecticut or Oregon), you have its rights, including appeal. Use the same email.

Canada. We follow PIPEDA and applicable provincial laws, including Quebec's Law 25. You can withdraw consent, access and correct your data, and complain to the Office of the Privacy Commissioner of Canada or your provincial commissioner. Our person responsible for privacy is the developer, Daniel Bobunov, reachable at our support email address (section 15).

United Kingdom. We follow the UK GDPR, the Data Protection Act 2018 and the Age Appropriate Design Code. Optional analytics rely on your consent, which you can withdraw at any time in Settings; you can ask us for the legal basis of any other processing. You can also object, restrict processing and withdraw consent, and complain to the Information Commissioner's Office (ico.org.uk).

Australia. Where the Privacy Act 1988 applies to us, we handle personal information under the Australian Privacy Principles. You can complain to us first and then to the Office of the Australian Information Commissioner (oaic.gov.au).

New Zealand. We follow the Privacy Act 2020. You can complain to the Office of the Privacy Commissioner (privacy.org.nz).

Transfers. RevenueCat and PostHog process data in the United States. You can ask us for details of how transfers of your data are protected.

Apple's developer licence (section 3.3.3(P)) limits how apps may use data from its Screen Time frameworks. Relix uses that data only to give you, the individual, control over your own device for focus. Relix does not share it with anyone: not us, not analytics or advertising companies, not friends, schools or employers. It stays with you and your iPhone.

We publish changes on this page with a new date. If a change needs your consent, for example sending new kinds of data, Relix will ask you in the app before it applies.