Privacy Policy

Last updated October 25, 2026

This policy explains what data the blokr app and this website handle, why, and what your choices are. The short version: the Screen Time data that makes blokr work never leaves your device, we use analytics to improve the app, and we do not sell personal data.

Who is responsible

blokr is responsible for the processing described here. You can reach us at our support address for any privacy question or request.

Screen Time data stays on your device

blokr blocks and limits apps through Apple's Screen Time framework (Family Controls and Device Activity). Apple processes which apps you use and for how long on the device itself. blokr receives permission to apply limits, but it cannot read your app usage, and this data is never sent to us or to anyone else. The usage reports inside blokr are drawn by Apple's framework on your device. The apps and websites you pick to block are stored as Apple tokens on your device; we cannot see which apps they are.

Data we collect in the app

• Usage analytics. Which screens you open and which features you use (for example creating, starting or ending a block), plus device model, iOS version, app version, language, country derived from your IP address, and a random identifier created when you install the app. This is processed by Amplitude, Mixpanel and Google Firebase Analytics. Purpose: understanding how the app is used so we can improve it.
• Session replay. For roughly one in four app sessions, Amplitude Session Replay records how blokr's own screens are used: which screens appear, taps and scrolls. Text you type into fields is masked. It covers blokr only, never other apps. Purpose: finding confusing screens and bugs.
• Crash reports. When the app crashes, Firebase Crashlytics receives a technical report (stack trace, device model, iOS version, app version). Purpose: fixing crashes.
• Advertising measurement. blokr asks for permission through Apple's App Tracking Transparency prompt. If you allow it, Google Firebase may use your device's advertising identifier to tell us whether an install came from one of our ads (Google Ads). If you decline, the advertising identifier is not available to us or to Google, and no tracking across other companies' apps or websites takes place. You can change this any time under Settings › Privacy & Security › Tracking on your iPhone.
• Purchases. Payments are handled by Apple; we never see your payment details. RevenueCat checks your subscription status with an anonymous app user identifier, so Pro works after a reinstall and across your devices.
• Support messages. If you contact us through the in-app chat (Crisp) or by email, we receive what you send us and the contact details you use, and keep them to answer you.

This website

This website sets no cookies. It is served through Cloudflare, which processes your IP address to deliver the pages and protect the site from abuse. We use Cloudflare Web Analytics to count visits: which pages are viewed, from which referring site, country and device type, and how fast pages load. It stores nothing on your device, does not fingerprint you and does not follow you across other websites. Links to the App Store may carry a campaign name so Apple can tell us how many installs a page led to; that name contains no personal data.

Legal bases

• Providing the app, purchases and support: performance of our agreement with you (Art. 6(1)(b) GDPR).
• Usage analytics, session replay and crash reports: our legitimate interest in understanding, fixing and improving the app (Art. 6(1)(f) GDPR). You can object at any time; see Your rights.
• Advertising measurement: your consent, given through the App Tracking Transparency prompt (Art. 6(1)(a) GDPR).
• Website visit statistics: our legitimate interest in knowing which pages people find useful (Art. 6(1)(f) GDPR).
• Records required by law, such as tax records for purchases: legal obligation (Art. 6(1)(c) GDPR).

Who receives data

We share data only with the service providers named above: Amplitude, Mixpanel, Google (Firebase Analytics, Crashlytics and Google Ads), RevenueCat, Crisp, Apple and Cloudflare. They process it on our behalf under contracts that limit what they may do with it. We do not sell personal data.

Several of these providers are based in, or process data in, the United States. Those transfers rely on the EU-U.S. Data Privacy Framework where the provider is certified under it, and otherwise on the European Commission's Standard Contractual Clauses.

How long we keep data

We keep analytics data, session replays and crash reports only as long as we need them to understand and improve the app, after which they are deleted or anonymised. Support conversations are kept while we help you and for a reasonable time afterwards in case you follow up. Purchase records are kept as long as tax and accounting law requires. Deleting the app removes everything stored on your device.

Your rights

Under the GDPR you can ask for access to your data, correction, deletion, restriction or portability, and you can object to processing based on legitimate interest. Where processing relies on consent, you can withdraw it at any time without affecting earlier processing. Email us via the support page. Because analytics use a random identifier rather than your name, tell us your blokr user ID if you have it, or describe roughly when you used the app, so we can find your data. You also have the right to complain to a data protection authority, in particular in the EU country where you live.

Children

blokr is not directed at children under 13. If you are under the age of digital consent in your country, please use blokr only with a parent's or guardian's permission. If you believe a child has given us personal data, contact us and we will delete it.

Changes

We will update this page when our practices change and show the date at the top.