LVL Privacy Policy

Effective 1 November 2026

LVL is a habit tracker built so that your data stays yours. There is no account, no sign-up, and no LVL server: everything you record lives on your device. The only things that leave it are anonymous usage counts, ad requests, purchase receipts, and a check for app updates, each described below.

What LVL stores, and where

Habits, journal entries, workouts, streaks, badges, to-dos, bucket-list goals, and your profile details (name, and optionally birth date, gender, weight, and height) are stored only in the app's local storage on your device. Photos you choose — a profile photo, or photos attached to journal entries — are saved as files in the app's own storage on your device; deleting a journal entry deletes its photo. None of this is transmitted to us — we have no server to send it to, and we never see it.

Anonymous usage analytics

To understand which parts of LVL are used, the app sends anonymous event counts to Aptabase, hosted in the EU. An event says that something happened — for example that a habit was ticked, a workout finished, a journal entry added, the paywall opened, or a purchase started — and sometimes carries a small fixed detail such as which plan or app icon was chosen. Events never contain anything you typed: no habit names, notes, journal text, profile details, or photos.

Alongside each event Aptabase receives basic technical information: app version, operating system and version, language setting, and a random session identifier that changes every session. There is no user ID or advertising identifier, nothing that links events to you or across sessions, and the data is not used for advertising or tracking.

Backups

When you export a backup, LVL creates a file on your device and hands it to your system share sheet. It goes only where you choose to send it — your cloud drive, your email, your files. We never receive a copy. Backups contain your entries and settings but not photo files, so photos stay on the device they were taken on.

Ads (free version)

LVL shows only optional rewarded ads, served by Google AdMob — an ad plays only when you tap an offer that says what you get in return. LVL requests non-personalized ads only. To serve any ad, Google may process device information such as your IP address, device identifiers, and coarse ad-serving data for purposes like fraud prevention and frequency capping. In the EEA and UK, a consent dialog is shown before any ad request, and you can revisit that choice at any time from Ad privacy in Settings. See Google's Privacy Policy and how Google uses ad data.

Purchases

Premium and one-off purchases such as a streak repair are processed by Apple's App Store or Google Play; LVL never sees your payment details. To recognise your purchases across reinstalls and devices, receipt information (product, price, transaction date) is validated by RevenueCat using an anonymous identifier. This identifier is not linked to your name, and your habit data plays no part in it.

Badge rewards

Some badges show a code that can be redeemed for a shirt. The code is built into the app and simply displayed when you earn the badge; earning or viewing it sends nothing to us.

Update check

Up to twice a day, LVL asks which version is newest so it can tell you when an update is out. On iPhone it asks Apple's public App Store lookup; on Android it reads a small file on our website. The request carries no identifier and nothing you have recorded — like any web request, the server sees your IP address, which we do not log or use.

Notifications

Reminders are scheduled locally on your device and only if you turn them on. No notification data leaves the device.

Children

LVL is not for children under 13. The app asks for a birth date during setup; if it indicates an age under 13, LVL deletes all locally stored data and does not allow use.

Deleting your data

Because everything you record is stored locally, deleting the app deletes your data. There is no account to close and nothing retained on our side. Backup files you exported remain wherever you saved them, under your control. Anonymous analytics events cannot be tied back to you, so there is nothing personal to delete; purchase records held by RevenueCat can be deleted on request through the contact below.

Changes

If this policy changes, the updated version will be posted at this address with a new effective date.

Contact

Questions about privacy: ondra.luka3@gmail.com