Privacy Policy

Who we are

Lockout is provided by FitDawg Ltd. Write to us at Linden Tree Cottage, Alton, GU34 3AS, United Kingdom, or email support@lockout.adai.systems — that address reaches us for anything in this policy, including a request to see or delete your data.

This policy explains what Lockout collects, what it deliberately does not collect, and what happens to each. It covers the Lockout iPhone app.

The short version

Lockout is built so that the sensitive parts never leave your iPhone.

Your camera is used to count reps and the video is discarded frame by frame. Your location is used to measure distance and no coordinate is ever uploaded. The apps you lock are identified by sealed references from Apple that we cannot read.

What we do store is your settings, the outcomes of your challenges, and a small number of product events so we can tell where people get stuck — all of it against an anonymous identifier rather than your name, because we do not have your name.

One thing does go to an advertiser. Lockout tells Meta that the app was opened, so that an install can be credited to the ad that led to it. That message says the app was launched and nothing else — not who you are, not which apps you lock, not what you did in the app.

Nothing is used to track you across other apps or websites, and Lockout never asks for permission to track you, because it never reads the identifier that would make that possible.

Camera

When you start a camera-verified challenge, Lockout opens the front camera and runs Apple's on-device body-pose detection over the live frames.

Each frame is measured — the positions of up to thirteen joints — and then released. Lockout does not record video, does not save still images, does not write frames to disk, and does not send any image data to us or to any third party. No cloud AI service is involved in verifying an exercise.

The only thing that survives a challenge is the count: how many reps you did, the type of exercise, how long it took, and whether you finished.

This is not face recognition and not a biometric identity check. The joint positions describe where your limbs are for a fraction of a second; they are not compared against anything, not used to recognise you, and not kept. Lockout has no way to tell one person from another and does not try to.

It is also not a medical or fitness assessment. Counting reps from a camera is a product feature and it is not perfect — a rep can be missed or miscounted, and nothing it produces should be treated as a measurement of your health or ability.

The camera runs only while a challenge is on screen and is shut down when you leave it.

Location and motion

Location is used only for walking challenges, and only while one is running.

Lockout reads your position to calculate how far you have travelled, and reads your step count from Apple's motion sensors to check the distance was walked rather than driven or simulated. Both are processed on your iPhone.

Lockout does not store your route, does not keep a location history, and does not upload any coordinate. What is recorded is the total distance, the duration, and whether you completed the challenge.

The apps you lock

Lockout uses Apple's Screen Time framework (Family Controls, Managed Settings and Device Activity) to place a shield in front of the apps you choose.

Apple's design means Lockout never learns which apps those are. When you pick apps, iOS gives Lockout an opaque, device-specific reference — not a name, not a bundle identifier, and not any record of your usage. Those references are stored only in Lockout's App Group container on your iPhone, and are never uploaded.

Lockout cannot see how long you spend in any app, what you do in it, or when you opened it.

What we do collect

Account: when Lockout first runs it creates an anonymous account so your settings and history have somewhere to live. It is an identifier and nothing else — no email address, no name, no password. If you later choose Sign in with Apple, what we receive is the identifier Apple issues for you. Lockout does not ask Apple for your name or your email address and does not receive either of them, so there is nothing of that kind for us to store.

Settings: your default challenge type, target and unlock window, and for each rule the challenge, amount, unlock duration and whether it is switched on. Your daily allowance, the time you have earned and your protection streak are kept on the iPhone and are not uploaded.

Rules carry no reference to the app they protect — the sealed reference iOS gives us never leaves the device. There are two exceptions, and you control both.

The first is a nickname. If you give a rule one, that text is stored with it. Name a rule "Instagram" and we hold the word "Instagram". Leave it unnamed and we hold nothing that identifies the app.

The second is the question during setup that asks what steals the most of your time. The answers you tap are a fixed list of well-known app names, and the ones you choose are stored with your preferences and sent as analytics so we can see what people are trying to get away from. That is your answer to a question, not a record of what you use — Lockout still cannot see which apps you open or for how long.

Challenge history: the exercise, the target, what you achieved, how long it took, whether you completed it, and a reason if it ended early. For a walking challenge "what you achieved" is the distance you covered. These are the exercise results Apple's privacy label calls fitness data, and they are stored against your account.

Product analytics: named events such as reaching a step of onboarding, starting a challenge, or opening the paywall, with small pieces of context such as which challenge type was chosen, or how many days a streak had run when it ended. We use these to understand where people abandon setup.

Unlock sessions: when a window was opened against a rule, how long it was open for, and which challenge paid for it.

Subscriptions: buying is handled entirely by Apple, and we use RevenueCat to tell whether your subscription is active and what it entitles you to. What reaches us is the state of the subscription — active or not, which plan, whether a trial is running. Lockout does not process card payments itself and never sees your card number, bank details or billing address.

That is the whole list. Lockout writes to six tables — your profile, your preferences, your rules, your challenge attempts, your unlock sessions and your analytics events — and there is no seventh.

Standard network information — your IP address, and the fact that a request came from an iPhone running a particular version of iOS — reaches Supabase and RevenueCat because every request over the internet carries it. They process it to deliver, secure and protect their services, as any hosting provider does. Lockout does not read it, does not store it, and does not attach it to your account or to anything else.

The identifiers we use

Two, and it is worth being exact about both because they are the part of this policy people most often assume the worst about.

Your Lockout identifier. The anonymous account described above is a random identifier with no meaning outside Lockout. It is what ties your rules, your challenge history and your preferences to you rather than to somebody else, and it is written alongside every row we store. The same identifier is given to RevenueCat, so that the subscription Apple has sold you is matched to the right Lockout account and not to a stranger's.

Your device's identifier. RevenueCat's software, which runs inside Lockout, includes Apple's identifier for vendor with every request it makes to RevenueCat's servers. It is used to support subscriptions and accounts — recognising the same device across a reinstall, and helping RevenueCat tell genuine purchases from fraudulent ones.

What it is not is the advertising identifier. Apple's identifier for vendor is scoped to us alone: no other developer's apps can see the same value, so it cannot be used to follow you between apps or across the web. Lockout does not request the advertising identifier and does not ask for permission to track you: Meta's software is configured not to read it, which is why no tracking prompt ever appears. Neither identifier is used to build a profile of you, or for anything Apple would call tracking.

Who processes this data

Supabase — database and authentication hosting, for the account, settings, history and analytics described above.

RevenueCat — subscription and entitlement status. It receives your Lockout identifier, Apple's purchase information for your subscription, your device's identifier for vendor, and the country of your App Store storefront. It does not receive your rules, your challenge history, your analytics or anything else you do in the app.

Apple — the App Store handles all payments, and Sign in with Apple handles authentication if you use it.

Meta — advertising measurement. Lockout includes Meta's software for one purpose: to tell Meta that the app was opened, so that an install can be credited to the ad that led to it. That happens on every launch, not only for people who arrived from an ad. What Meta receives is that the app was launched, together with basic device and app information such as the device model, the iOS version and the version of Lockout. What it does not receive is your Lockout identifier, your rules, your challenge history, your product events, your subscription status, your location, or anything your camera saw. Lockout never reads your advertising identifier, so Meta is never given one.

Lockout contains no crash-reporting service. We do not sell data, do not share it with data brokers, and do not use any of it to track you across other companies' apps or websites.

Data is stored on servers located in the United States (Oregon, us-west-2). If you are in the UK or EEA, we rely on the UK International Data Transfer Addendum and the EU Standard Contractual Clauses for that transfer.

How long we keep it

Your account and everything attached to it — your preferences, your rules, any nickname you have typed, your challenge history and your unlock sessions — are kept while your account exists, and go when you delete it.

Analytics events are kept no longer than 24 months. That is a limit we hold ourselves to rather than something the app enforces on your device.

Deleting your account in Settings deletes the account itself, and your preferences, rules, history and analytics go with it. Everything Lockout has written to this iPhone — including your allowance, your streak and the diagnostic trail — is erased at the same time.

Two things deletion cannot reach, because they are not ours to delete. Your subscription is billed by Apple and continues until you cancel it in your Apple Account settings. RevenueCat keeps the purchase record and the identifiers attached to it, as it must for billing, tax and fraud-prevention purposes; it holds your Lockout identifier, your device's identifier, and Apple's purchase information, and nothing you did in the app. Both Apple and RevenueCat are subject to their own retention policies, and how long their infrastructure holds a record is theirs to state, not ours.

Your rights

Depending on where you live, you may have the right to access, correct, export or delete your data, to object to or restrict processing, and to complain to a regulator.

You can delete everything from inside the app, and you do not have to ask us: Settings › Account › Delete account and data. It removes your account and everything attached to it, and wipes what Lockout has stored on this iPhone. For anything else — a copy of your data, a correction, an objection — email support@lockout.adai.systems and we will respond within one month.

The UK regulator is the Information Commissioner's Office (ico.org.uk).

Diagnostics

Lockout keeps a short technical trail on your iPhone — the last few steps of a launch, and how long each took — so that a problem can be diagnosed from Settings › Diagnostics. It contains timings and stage names. It never leaves your iPhone unless you copy it and send it to us yourself.

Lockout does not use a crash-reporting service. The product events described above are written by Lockout's own code to our own database; there is no third-party analytics SDK gathering them alongside it. Meta's software is present for the advertising measurement described above and sends only the app-launch event — the product events are not shared with it. RevenueCat's software has a diagnostics feature of its own and Lockout leaves it switched off.

Permissions, and taking them back

Every permission Lockout asks for can be withdrawn at any time, and none of them is required for the app to keep running.

Camera: iOS Settings › Lockout › Camera. Camera challenges stop working; walking challenges do not use it.

Location and Motion: iOS Settings › Lockout. Walking challenges stop working.

Notifications: iOS Settings › Lockout › Notifications. On iPhones running iOS 26.5 or later the shield opens Lockout directly and notifications are only a fallback; on earlier versions, turning them off means you have to open Lockout yourself after tapping the shield.

Screen Time: iOS Settings › Screen Time. Revoking it removes every shield, and Lockout stops claiming to protect anything.

Analytics and sync: deleting your account in Settings › Account stops all of it and removes what has already been collected.

Children

Lockout is not directed at children and is not intended for anyone under 13. We do not knowingly collect data from children. If you believe a child has provided us with data, email support@lockout.adai.systems and we will delete it.

Changes

If we change how Lockout handles data, we will update this policy and the date at the top. Material changes will be highlighted in the app before they take effect.