Your time is yours. So is your data.

The short version

Lerf has no accounts and no ads. It never sells your information and never uses it for cross-app tracking. The app cannot see which apps you block or how much you use them; Apple's Screen Time framework keeps that on your phone. The app does send a small amount of anonymous usage data and your purchase status to two service providers so we can tell whether Lerf works and keep subscriptions working. This website uses a Meta pixel and Stripe to sell the Lerf Tag. The details are below.

The Lerf app

What stays on your phone

The apps and categories you choose to block, your sessions, your schedule, and your settings are stored on your device. Apple's Screen Time APIs are built so that developers cannot read your app selections or your usage. The screen that shows where your week went is drawn by an Apple-sandboxed extension that has no network access, so those numbers never leave the phone. Lerf has no way to see them, and neither does anyone we work with.

Usage data we collect

To find out where the app fails or confuses people, Lerf records basic product events: which onboarding screens you reach, the choice you make on the first screen (studying, relaxing, working, being present), taps on features such as starting a session, setting a schedule, or opening the subscription screen, app opens, and whether a Screen Time or notification permission was granted. Each event carries your device model, iOS version, app version, and a build channel. If the app crashes, a crash report is collected. These events are processed by PostHog, an analytics provider, on our behalf.

This data is keyed to a random identifier that the app generates and stores in your device's keychain. It is not your name, email, phone number, Apple ID, or advertising identifier, and we have no way to connect it to you. Events never include your blocked apps, your screen time, or anything you typed.

Purchase data we collect

When you start a free trial, subscribe, renew, cancel, or receive a refund, Apple's purchase record for that transaction (product, dates, price, country, and status) is sent to RevenueCat, which manages subscription status on our behalf, keyed to the same random identifier. We use it to know what is active, to restore purchases, and to report revenue. Your payment details stay with Apple; we never see your card.

Apple

App Store purchases, subscription management, and Apple's own crash and diagnostic reporting are governed by your Apple account and device settings. Apple may share aggregated App Store metrics and, depending on your settings, crash and diagnostic information with us.

What the app does not collect

No advertising SDKs, no location, no contacts, no photos, no advertising identifier (IDFA), and no request to track you across other companies' apps or websites. The app's App Store privacy label lists purchase history, product interaction, other usage data, crash data, diagnostic data, and a user ID, none of it linked to your identity and none of it used for tracking. If the label and this policy ever disagree, tell us and we will fix whichever one is wrong.

Support

If you contact support, we receive whatever you choose to include: your email address, device details, screenshots, and a description of the issue. We use it to respond and to fix the problem.

This website

Meta pixel

lerfapp.com loads the Meta (Facebook) pixel, which sets the _fbp and _fbc cookies and reports page views, product views, and checkout starts to Meta so we can measure our ads. When you buy a Lerf Tag, our server also sends Meta a purchase event through its Conversions API containing your email, phone number, name, city, state, postal code, and country as one-way hashes, plus your IP address, browser user agent, and those cookie values. Meta uses this under its own privacy policy. You can limit it with an ad blocker, by blocking third-party cookies, or in your Meta ad settings.

Checkout attribution

When you click a buy button, we store your IP address, browser user agent, the page you arrived from, any utm_ parameters, and any Meta click ID for seven days under a random reference number so a completed order can be matched to the ad that led to it. Only that reference number is passed to Stripe.

Stripe

Lerf Tag orders are processed by Stripe. Stripe collects your payment details, and we receive your name, email address, phone number if you give one, and shipping address to fulfill and support the order. We do not see or store your card number.

Hosting

The site is served by Cloudflare, which keeps standard server logs (IP address, user agent, requested pages) for security and performance.

Retention

Data on your phone stays until you change it, reset the app, or delete Lerf. Usage and purchase records held by PostHog and RevenueCat are kept while we operate the app and for as long as we need them to report revenue, and are deleted on request where we can identify them. Checkout attribution expires after seven days. Order records are kept as long as needed for fulfillment, returns, and tax and accounting obligations. Support email is kept as long as reasonably necessary to respond and maintain a support history.

Children

Lerf is not directed to children under 13 and does not knowingly collect personal information from them.

Your choices and rights

You can revoke Screen Time access in iOS Settings, delete the app to remove its local data and stop all collection, and cancel a subscription in your Apple ID settings. The app does not yet have an in-app switch for usage analytics; deleting the app is the way to stop it today. For the website, see the Meta pixel section above.

You can ask us to access, correct, or delete information we hold about you by emailing [email protected]. For app analytics and purchase records we can only act on what we can identify, which usually means the email you used for a Tag order or a support message. If you are in the EU, UK, or a US state with a privacy law, you have the rights those laws provide, including the right to complain to your local authority; we do not sell personal information or share it for targeted advertising as those laws define it, except as described in the Meta pixel section.

See Privacy Choices for step-by-step options.

Changes

When Lerf's practices change, this page changes first, with a new effective date. Previous versions are available on request.

Contact

[email protected]