Privacy Policy | Lock In Squad

This Privacy Policy explains what Lock In Squad ("we", "us", "our") collects when you use our mobile app and website (the "Services") and how we use it. For questions or requests, use the Contact Us page or Send feedback in the app's Settings.

Information we collect

Your account

Account: your email address and name, so you can sign in and we can reach you. You can sign up with email, Google or Apple.
Age and consent: that you confirmed you are 13 or older and when you accepted our terms and this policy.
Verification: one-time codes we email you, which expire after 10 minutes. When you verify an email address with a code, our server keeps a record of the address, the time and, if you're signed in, your account for about an hour, so it can trust that address while you finish signing up.
Guests: if you use the app without signing up, it makes an anonymous account with no email. The data below is saved to that account the same way, except anything that needs an email.
Messages: what you send through the Contact Us page or Send feedback, with the name and email you give.

Your profile and friends

Profile: your name, user ID, bio, profile photo, your lock (its body color, face, hat and top), your work days, and your total focus time and current streak. It also shows whether you have Premium, unless you hide the badge in Settings > Premium. Anyone signed in to the app can see your profile.
Friends: your friends, friend requests, friend streaks, group sessions, nudges and cheers, the milestones you share and who liked them, the people you block or report, and the referral code you signed up with.
What friends see: your hourly totals, your longest streak, how many times you have locked in, the milestones you share and your friends list. While Show when I'm locked in is on, under Settings > Privacy > Friends, they also see when you are locked in and your time zone. People in a group session with you see how long you have been locked in. Your sessions and blocked-app attempts are yours only.
Time locked in together: we count overlapping lock-in time when you and a friend participate in the same group. Only the two of you can view your shared weekly and total time. We keep recent timing intervals to avoid counting overlapping groups twice, and combine intervals older than 35 days into a total the next time you record shared time. Removing the friendship or deleting either account removes the shared statistic. This does not add bonus Minutes.
Group schedules: when you accept automatic blocking, we save the agreed dates, times, time zone, repetition, schedule version, your acceptance and any skipped occurrences. Invited people can review the plan, and group members can see participation. Your selected apps stay on your phone. Devices report observed blocking times, including after reconnecting, to count eligible Minutes and shared time without counting overlaps twice. Completed group timing receipts older than 35 days are discarded on the next attendance report. Leaving removes your receipts from that group. Changes to a plan require acceptance again and reach an offline phone when it reconnects.
Group invite links: a group lock-in's invite link holds a random join code. We keep the code with the lock-in, along with when it was made and the host's account ID, and delete it when the host turns the link off, the lock-in ends or the host deletes their account. While the link is on, anyone signed in to the app who has it sees the lock-in's name, the host's name and how many people are in it, and anyone with an account can use it to join.
Friend links: a link you share to add you as a friend carries the user ID on your profile, such as ZM7SUV4V, or rarely your account ID.
Checks: Google Cloud Vision checks each profile photo you upload for adult, racy or violent content. Photos that fail are removed. Names and bios are checked against a list of offensive words.

Blocking and settings

Android: the package names of the apps you pick to block or allow, and the websites you add to block.
iPhone and iPad: the apps, categories and websites you pick in Apple's Screen Time picker stay on your device. Your account keeps only how many of each you picked.
Settings: your block mode, timer or stopwatch, lock out delay, work days, ad and notification settings, and the items you own in the Shop.
Scheduled blocks: each schedule's name, days, and start and end times, saved to your account so your schedules follow you to your other phones. For each block, we also keep when it ran on each of your phones and whether you skipped it or ended it early. A schedule has no list of apps of its own. Each phone blocks the apps picked on its Block tab, so on iPhone and iPad they stay on the device.

Website blocking on Android

On Android you can pick websites for Lock In Squad to block while you're locked in. To do this, Lock In Squad uses Android's Accessibility service. You turn it on yourself in your phone's settings, after Lock In Squad shows you what it does and you tap Agree.

What it reads: while you're locked in or a block you scheduled is on, the web address in the address bar of Chrome, Samsung Internet, Firefox, Edge, Brave, Opera, DuckDuckGo and Vivaldi. It reads nothing else on your screen and nothing in other apps. When you're not locked in and no scheduled block is on, it reads nothing at all.
What it does with it: it checks the address against your list on your phone. If the website is on your list, or for any website in allow mode, your browser goes back a page and Lock In Squad opens and tells you which website was blocked.
What we keep: the addresses it reads never leave your phone, and we don't log or record which websites you visit or try to open. The name of a blocked website stays on your phone only until Lock In Squad shows you the alert. The list of websites you choose to block is saved to your account, like the apps you block, so it follows you to a new phone. You can change or empty it on the Block tab. It is deleted when you delete your account.
Turning it off: go to Settings > Accessibility on your phone and turn off Lock In Squad website blocking.

Sessions and stats

Sessions: for each session, when it started and how long it lasted, whether it was a timer or a stopwatch, a timer's planned length, how it ended (on time, early, after the timer ran out, or after the app was closed during it), whether blocking was on, and whether it was part of a group session. On iPhone and iPad, the only thing a session records about blocking is whether it was on.
Stats: hourly totals, streaks, how many times you have locked in, the minutes you earn and spend, your time zone, and when you last opened the app.
Minutes: in version 2.1, our server keeps your minutes balance, the Shop items you own and a record of each change: each lock-in that earned minutes, with its start and end times, Shop purchases, rewarded ads, referral bonuses and other rewards. When the count the app sends differs from the server's, the server keeps its own and notes the change. All of this is kept while your account exists and deleted with it.
Blocked-app attempts (Android): each time you try to open a blocked app during a session, your phone saves the app's package name, the time and the session it happened in. The app then copies them to your account for the Stats screen, which keeps the newest 1,000. Your friends can't see them. We don't share them with anyone.

Notifications and email

Push tokens: if you allow notifications, a push token from Firebase Cloud Messaging for each phone you use, iPhone or Android, with its platform and app version.
Notification log: which notifications we sent you and whether you opened them, so we can send fewer when you don't. We also keep your notification permission and time zone, so reminders arrive at a sensible local time.
Failed notifications: when a phone stops receiving notifications, for example after the app is deleted, our server removes its push token and logs the time and the platform, never the token.
Delivery reports: when a push notification reaches your phone, the phone tells Firebase Cloud Messaging. The report includes the message's ID, when it arrived and the ID Firebase gives the app on your phone, never what the notification said. If we link Firebase's export to BigQuery, Firebase copies these reports into our own Google Cloud project in the US. They don't depend on Share usage data.
Email: we send verification codes and emails about your account. If your account has an email, we also send reminders and tips, such as streak reminders, milestones and a note when you have been away, plus the newsletter if you signed up for it. Our server sends email through Resend, which tells us whether each email was delivered, delayed, bounced or marked as spam.
No open or click tracking: we don't track whether you open an email from our server or click its links. These emails carry no tracking image. Their links go straight to where they point.
Our email provider: the service we use to send reminders and tips gets your email address, name, user ID, profile photo link, how you signed up, and when you joined and last signed in.

Purchases

Premium: if you buy Premium, the purchase record from the App Store or Google Play (the product, the platform, the time and the store's transaction details). Our server checks it with Apple or Google and records the price and currency when the store includes them, the store's country, and whether it was a test purchase.
One account per purchase: each purchase's transaction ID (App Store) or order ID (Google Play) is linked to the Lock In Squad account that bought it, so Premium belongs to that one account. In version 2.1, the app also gives Apple or Google a code made from your account ID with each purchase, so the store's record names the account too.
Refunds: Apple and Google tell us when a Premium purchase is refunded or charged back, with the store's reason. Apple also tells us when it declines a refund or reverses one. A refund removes Premium from your account. If the refund is reversed, Premium comes back. When you ask Apple for a refund, we send Apple no information about how you use the app.

Usage data (the Share usage data switch)

Settings > Privacy > Share usage data covers the data we collect only to learn how the app is used. While it is on, we collect the following.

Usage events: the screens you view and how long each one stays in front, the settings you change, your steps through sign-up and the welcome screens, locking in and locking out (including a hold on Lock Out that you start and let go), what you do with friends and group sessions and the screen each action started on, Shop and Premium actions, notifications received, dismissed and opened, whether you locked in within 10 minutes of opening a notification, ads shown, tapped and rewarded (with AdMob's estimate of what each ad earned), how fast the app starts, draws its screens and reaches our server, and the alerts and errors the app shows you.
Taps, swipes and scrolling: the buttons you tap, long press or swipe on (with the button's wording), each swipe's direction and length, how far down each screen you scroll and how many times you scroll it, and which home screen widget you tap, with its size and the face it showed.
With each lock-in and lock-out: the kind of network (such as Wi-Fi, cellular or none, and on cellular whether it is 4G, 5G and so on), whether the connection is metered, the battery level, whether it is charging and, on Android, how it is plugged in, and whether Low Power Mode or Battery Saver is on. During a lock-in we also record each change of network and each time you leave the app, with how long you were away.
Your phone: memory warnings, the screen turning between portrait and landscape (with the window's size), and a change of time zone, by its name, such as Europe/London.
With each event: your user ID, the phone model, OS version, app version and build, your language and region settings, the random install ID described below, the screen you were on, and the country our server sees for the request's IP address.
Once a day: how many widgets you have placed, your notification permission, whether a screen reader, larger text, reduce motion or dark mode is on, the kind of network, the battery level and whether it is charging, whether Low Power Mode or Battery Saver is on, your time zone, the screen's orientation and how much storage the app uses. On Android, also whether the app is exempt from battery optimization and your phone's free and total storage.
Install source: on Android, Google Play's install referrer, which says where the install came from. When a link opens the app, its campaign fields and the first part of its path, without any code or ID in it.
Invite links: when you share a friend or group invite link, when one opens the app, what a group link led to (such as open, full or ended), and when you join through one, send a friend request from one or turn one off. These events never include the link's ID, its join code or anyone's name.
Notifications on iPhone: when a push arrived and its IDs, never its text.
Blocked apps (Android): the package name of a blocked app when its alert shows. It stays in our own analytics database.
App opens: when the app opened and what opened it (the icon, a notification and which one, or a link), with the app version. Your account keeps about the newest 200.
Progress stamps: the first time you see and finish each welcome screen, each permission prompt and your answer, each tutorial step, your first lock-in and first session, steps toward making an account or buying Premium, and sessions the app put back after it was closed.
Device record: one for each install, with the OS version, the app version (and the build number on Android), the phone model on Android, language and region, your notification permission, when the install was first and last seen, and a random install ID that the app makes and keeps on the phone. It holds no advertising ID and no other ID from your phone. On iPhone and iPad, it notes only whether the device is a phone or a tablet. The usage events above carry the model.
More session details: the platform and app version, and on Android the block mode and how many apps you picked, saved with each session.
Email summaries: for accounts with an email, our server works out your sessions and active days over the last 7 and 30 days, your total sessions and minutes, and when you first locked in, last had a session and last opened the app. It gives these to our email provider with your platform, app version and notification permission.

We store usage events in Google BigQuery, in our own Google Cloud project in the US, and Google processes them for us. We don't sell them, share them with other companies or use them for ads.

Usage events never include anything you type, such as passwords, emails, names or search text. The exception is a note you write in a lock-in rating, described below, which is recorded only when you tap Done. A button's wording keeps only the app's own words, so a friend's name on a button is left out. On iPhone, they include nothing from Screen Time. On Android, they never include the name of a website, whether it is one you add to your list or remove from it, an address website blocking reads or a website you tried to open.

Usage events also never include the name or address of your network, your carrier, your contacts, your phone's location (only the country and time zone described above) or how long you use other apps. On iPhone, they don't include how much free storage your phone has.

Where the switch starts depends on where you are. In the US and most other countries it starts on. In the UK it also starts on, under the exception for statistics that improve a service in the UK's PECR rules (Schedule A1), and turning it off is how you object. In the EEA and Switzerland it starts off, and the app asks you once, "Help improve Lock In Squad?" It stays off unless you tap Yes. You can change the switch at any time. Until the app knows which applies to you, it sends no usage data, and it deletes what it held if the switch turns out to be off. Our server reads the switch from your account. Until a version of the app with the switch has saved your choice there, the server treats it as on.

Turning the switch off stops new usage data, and the app deletes the events it has not sent yet. Our server then deletes the email summaries it keeps for our email provider. Usage data saved earlier stays in your account until you delete the account, and usage events already sent are kept as described under Data retention. The switch does not cover crash reports or the data the app needs to work, which the rest of this section describes.

Version 2.0.7 of the Android app, the version on Google Play until November 1, 2026, had no Share usage data switch and sent usage data to Google Analytics for Firebase, including your advertising ID where your phone allowed it. Version 2.1 and later do not use Google Analytics, and the iPhone app never did.

Lock-in ratings and reasons for leaving

Lock-in ratings: while Share usage data is on, the app sometimes asks how a lock-in went after you lock out. We keep your answer from 1 to 5, any reasons you tick, a note if you write one and tap Done, and the lock-in's length, whether it was a timer or a stopwatch and how it ended. We also record when the question comes up and when you close it. Your account in our app database keeps the answer, the reasons, the note and the lock-in's length. Usage events carry all of it. Both are deleted when you delete your account. Usage events are kept for two years at most.
Reasons for leaving: when you delete your account in the app, it asks why you're leaving. Answering is optional. If you tap Skip, nothing is sent. If you answer, we keep the reason you pick, your note with any email address in it masked, your platform and app version, how many days old the account was, how many times you locked in and how many hours you spent locked in (each as a range, such as 6 to 20), whether you had Premium, whether it was a guest account, and the day.
How we keep reasons for leaving: the answer is stored in BigQuery, in our own Google Cloud project in the US. It carries no account ID, email or name, so it stays after your account is deleted, for up to two years. We record it whatever the Share usage data switch says, because you choose to give it. Please don't put personal details in the note.

Our server's records

Our server keeps its own records of what it does, in the same BigQuery database as usage events. Records about your account carry your user ID, never your email address, your name, a push token or anything you type. A reason you give for leaving, with its note, is kept apart from these records without your user ID, as described above.

Notifications: each push notification our server sends to each of your devices, which notification it was, whether Firebase Cloud Messaging accepted it, and the device's platform and app version. Also the notifications it held back or didn't send, with the reason. When a device's push token stops working, which usually means the app was removed, we record that with how old the token was.
Email: each email our server sends you, named by which email it is, and the delivery reports Resend sends back for it.
Purchases and refunds: the purchases, refunds and Premium changes described under Purchases.
Accounts: when an account is made and how (email, Google, Apple or as a guest), when a guest account is saved and when you verify an email address. A deleted account is counted with no ID, only its sign-in method, whether it was a guest account and how old it was.
Friends and groups: friend requests sent and accepted, and group sessions started and ended, with the session's ID, how many people were in it and how long it lasted. When someone joins a group lock-in through its invite link, we record that with the lock-in's ID and how many people are in it. These records never include names, join codes or the other person's ID.

These records follow Share usage data, except purchase, refund and account records, which we keep whatever the switch says.

Reports and reviews from the app stores

We copy the reports Apple and Google make about the app into our own Google Cloud project in the US. Most are counts of store page visits, downloads and installs, deletions, crashes and ratings by day, country, device and source. We also copy the reviews people post about the app on the App Store and Google Play. For each review we keep the stars, the title and text, the dates, our reply and the details the store gives with it, such as the country, language, device and app version. From Google Play we also keep the review's link. We don't copy the name a reviewer posts under. We don't match reviews or these reports to accounts.

Crash reports

The app sends crash reports to Firebase Crashlytics whether or not Share usage data is on. A report includes your user ID, the device model, OS version and app version, the screen you were on, whether a lock-in was running, whether you use the app as a guest, and a short trail of recent actions such as screens opened, lock in and lock out, ads shown and purchase steps. The app also reports some errors it recovers from.

We may copy these crash reports, and Firebase Cloud Messaging's records of the pushes we send to your devices, into BigQuery in our own Google Cloud project in the US. Neither depends on Share usage data.

Protecting the Services

App checks: in version 2.1, the app asks Google Play Integrity on Android, or Apple's App Attest on iPhone and iPad (DeviceCheck where App Attest isn't available), to confirm that requests to our server come from the real Lock In Squad app on a real device. Google and Apple run these checks under their own privacy policies. Our server's logs keep whether each request passed and, when it didn't, why. They never keep the check's token or an ID from your device. While Share usage data is on, usage events also record how the check went when the app starts.
Limits on requests: to limit how often codes, emails and forms, including the forms on our website, can be sent, our server keeps counters keyed by a scrambled (hashed) form of an IP address, email address or email domain, or by an account ID. Each counter is deleted about a day after it starts.

Ads and consent

Ads: Google AdMob serves the ads. It receives your IP address, a rough location based on it, details about your device, your advertising ID (on iPhone, only if you allow tracking) and which ads you see and tap.
Rewarded ads: in version 2.1, when you watch a rewarded ad to earn 10 minutes, Google AdMob tells our server directly. It sends your account ID, a one-time code the app attached to that ad and AdMob's own ID for the reward, so the server can add the minutes. The reward is saved in your minutes history with that code.
Consent: Google's ads consent form, on iPhone and Android, and Apple's tracking prompt, on iPhone, keep your answers on your phone. With Share usage data on, your answers are also saved as progress stamps.

On our website

Forms: what you type into the contact form, the newsletter sign-up or the account deletion form.
Newsletter sign-ups: we keep your email address, that it came from our website and the time, and email you a link to confirm. You're added to the newsletter and the biweekly digest only once you confirm. The link works for 7 days, and a sign-up you don't confirm is deleted after that.
Account deletion requests: if the email address belongs to an account, we keep the address, the reason and note you give, your IP address and browser details, and the request's status and times, and email you a link that works for 24 hours. Once you confirm, we remove the email address, note, IP address and browser details, and keep the status, the times, the reason you picked, where the request came from and your account ID. A request you never confirm is deleted a week after its link expires.
Page views and store clicks: our server records each page you view (its path), the website that sent you here (its domain only), any campaign tags in the page address, such as utm_source, and which App Store or Google Play button you tap and where it sits on the page. With each record it keeps your country, which our host Vercel works out from your IP address, and the kind of device, such as an iPhone, an iPad, an Android phone or tablet, or a computer. We don't record your IP address. These records use no cookies, store nothing on your device and carry no ID for you or your browser, so nothing in them ties them to you or to each other.
Store links: our links to the App Store and Google Play carry the name of the page they're on, so the stores can tell us which page led to an install. On the page for a group lock-in or profile link, the Google Play link also carries the ID in that link, and a group lock-in's join code when the link has one, so the app can open the lock-in or profile after you install it. The app uses the join code once and leaves it out of its usage data. Page views, store clicks and Vercel Web Analytics record these pages without the ID or the join code.
Visits: Vercel Web Analytics counts visits to our pages.

We keep page views and store clicks in BigQuery, in our own Google Cloud project in the US, for two years. In the UK we collect them under the exception for statistics in the PECR rules (Schedule A1, paragraph 5). To object, block requests to lockinsquad.com/api/site-events in your browser, for example with a content blocker, or turn off JavaScript for our site. Because the records carry no ID, we can't pick out the ones that came from your visits.

How we use information

To run the Services: blocking, sync, sessions, streaks, stats, friends, group sessions and notifications.
To run your account, including sign-in, verification emails, support and account deletion.
To send the emails described above.
To see whether our notifications and emails arrive.
To keep Premium in step with purchases and refunds.
To find and fix crashes and errors.
To learn how the app is used and improve it, from usage data while Share usage data is on.
To learn how people find our website and the app, from website statistics and store reports.
To learn how lock-ins go and why people leave, from the answers you choose to give and from store reviews.
To show ads, personalized or not according to your consent.
To keep the Services safe, including checking profile photos and names, checking that requests come from our app, limiting how often requests can be made, preventing fraud and meeting legal duties.
To recover from a failure, from our nightly backups.

Legal bases in the EEA and the UK

Consent (personalized ads, and in the EEA, usage data and the server records that follow Share usage data).
Contract (to provide the Services, including Premium and refunds).
Legitimate interests (crash reports, security and moderation, the account, purchase and refund records our server keeps, website statistics, and in the UK, usage data, which you can object to by turning off Share usage data).
Legal obligations.

Your choices and controls

Usage data: Settings > Privacy > Share usage data.
Ads: Settings > Privacy > Ad preferences and Reset ad consent. On iPhone you can also change tracking in the Settings app. We show personalized or non-personalized ads according to your consent and your device settings.
Friends: Settings > Privacy > Friends, where you can turn off Show when I'm locked in and manage the people you have blocked.
Notifications and email: turn notifications off in your phone's settings. Settings > Notifications has switches for Reminders and tips and for the Email newsletter. Each of those emails also has a link to turn them off.
Website statistics: block requests to lockinsquad.com/api/site-events, as described under On our website.
Delete your account: in the app, tap the gear on the You tab to open Settings, then tap Delete account, or use our Delete account page.

Sharing and processors

We don't sell personal information. These companies process data for us:

Google Firebase, for sign-in, our database, file storage, push notifications, crash reports (Crashlytics), App Check and, in version 2.0.7 of the Android app, Google Analytics.
Google Cloud Storage, which keeps our nightly backups in the US.
Google AdMob, for ads, ad consent, ad measurement and confirming rewarded ads.
Google Cloud Vision, to check profile photos.
Google Cloud BigQuery, which stores our usage events, our server's records, reasons for leaving, daily totals, store reports and reviews, and website statistics in the US.
Email services, for verification, account, support and reminder emails.
Resend, which sends our server's emails and reports whether each one was delivered.
Apple and Google, for Sign in with Apple and Google, to check Premium purchases, to tell us about refunds, to confirm that requests come from our app (Google Play Integrity, Apple App Attest and DeviceCheck) and for their reports and reviews about the app.
Vercel, which hosts our website, counts visits and works out the country for website statistics.

Other people who use the app see what "Your profile and friends" above describes.

We may disclose information if required by law, to protect rights or safety, or in connection with a business transaction.

Data retention

Account, profile, settings, session history and minutes history: kept while your account exists.
Group invite links: the join code is kept until the host turns the link off, the lock-in ends or the host deletes their account.
App opens: about the newest 200 entries.
Usage events and our server's records: two years in BigQuery, then deleted.
Lock-in ratings: kept with your account until you delete it. The usage events that carry them are deleted with your account or after two years.
Reasons for leaving: two years in BigQuery, then deleted. They carry no account ID, so deleting your account doesn't remove them.
Daily totals: counts and sums for each day, such as how many people used the app or locked in. They carry no account ID. We keep them with no time limit.
The day you first used the app: to count how many people keep using the app, we keep this day with your account ID until you delete your account.
Website page views and store clicks: two years in BigQuery, then deleted.
Reports and reviews from the app stores: no set end date.
Copies of crash reports, push records and delivery reports in BigQuery, if we make them: no set end date. Deleting your account doesn't remove them.
Blocked-app attempts (Android): the newest 1,000 in your account. Your phone holds up to 500 that the app has not copied yet.
Verification codes: stored in our Firebase Realtime Database. They expire after 10 minutes and are deleted within about an hour. The record that you verified an address is deleted within two hours.
Device records, progress stamps and notification logs: kept while your account exists.
Limits on requests: each counter is deleted about a day after it starts.
Newsletter sign-ups you don't confirm: deleted after the link expires, 7 days after you sign up.
Account deletion requests from our website: a confirmed request keeps what On our website describes, with no set end date. One you never confirm is deleted a week after its link expires.
Premium purchases: the purchase record and its link to your account ID are kept, even after you delete your account.
Backups: each night we copy our whole app database (the Firebase Realtime Database, which holds your account) to a private Google Cloud Storage bucket in the US. Each copy is deleted after 30 days. We use the copies only to recover from a failure.
When you delete your account: we delete your account data, including your profile photo, usage data, minutes history, lock-in ratings, push tokens and the copy our email provider reads. Copies of it in our nightly backups are deleted within 30 days. Your usage events, our server's records about your account and the day you first used the app are deleted from BigQuery within about four hours. The deletion itself is counted with no ID. A refund that arrives later is recorded without your user ID. We keep a note of the deleted account's ID for 400 days, used only to stop new records about it. We keep the record of a Premium purchase and its link to your account ID, and you can restore the purchase on a new account. A reason you give for leaving stays, without your account ID. Crash reports, and Google Analytics data from version 2.0.7 of the Android app, stay with Google until Google's retention period for them ends.

Security

We use reasonable safeguards to protect information, including the checks described under Protecting the Services and the nightly backups described under Data retention. No method is 100% secure.

International transfers

Your information may be processed in other countries. Where required, we rely on appropriate safeguards.

Your rights

Depending on where you live, you may ask to access, correct, delete or move your data, or withdraw consent. Use the Contact Us page or Send feedback in the app. We may verify your identity.

US state privacy (where applicable):

We do not sell personal information.
You can opt out of personalized ads by turning off ad personalization in the app's consent controls and your device settings.
Access and deletion requests: the Contact Us page or Send feedback in the app.

Children's privacy

We design Lock In Squad for a general audience, and it may be useful to younger users. We do not knowingly collect personal information from children under the age required by law in their region (for example, under 13 in the US) without verifiable parental consent. If you believe a child has provided personal information, please use the Contact Us page or Send feedback in the app so we can review and delete the information where required.

If you are under the age where consent is required in your region, use the app only with a parent or guardian's permission. Your ads consent choices and your device settings decide whether ads are personalized. Without consent, we show non-personalized ads where that applies.

Permissions we request and why

Android: Usage access and Display over other apps, to see which app is open and block the ones you picked. The app also reads which apps are installed and how long you used each one in the last 7 days, to list and sort the apps you can block. Only the apps you pick are saved to your account. Accessibility, only if you turn on website blocking, to read your browser's address bar while you're locked in or a scheduled block is on. Alarms & reminders, only if you schedule a block, so it starts on time with the app closed. Notification access, only if you turn on Hide notifications from blocked apps, to read the notifications from the apps you blocked while you're locked in or a scheduled block is on, hold them and show them again after; nothing it reads leaves your phone. Notifications, if you allow them.
iPhone and iPad: Screen Time, to block the apps you pick. Notifications, if you allow them. Tracking (App Tracking Transparency), only for personalized ads. Photos and the camera, only when you choose a profile photo or save an image of your streak.

If you decline a permission, the features that need it won't work.

Third-party links

Our Services link to other sites and apps, such as the App Store and Google Play. Their own privacy policies apply there.

Changes

We may update this policy and will change the effective date above when we do. We may tell you about significant changes in the app.