Twilock ("we," "us," or "the app") helps you stop doomscrolling during your chosen night and morning windows. We built Twilock to protect your attention, and we take the same care with your privacy. This policy explains what data the app handles, why, and the choices you have.
Our core principle: your Screen Time and app usage data never leaves your device. We do not sell your data, use your Screen Time data for advertising, or share it with data brokers.
Data that stays only on your device
- Screen Time & app usage data. Twilock uses Apple's Family Controls / Screen Time framework to shield the apps you select during your no scroll windows. This usage data is processed entirely on your device and is never uploaded to us or anyone else. We cannot see which apps you use or how long you use them.
- Your no scroll windows & app selection. The times you set and the apps you choose to shield are stored locally on your device.
- Self reported check ins. Any sleep, energy, or mood ratings you enter are stored on your device only and are not uploaded.
Data stored to power accounts & the social features
These features are optional. Onboarding offers sign in, but includes a "Skip" option, creating an account is only actually required if you want to use the Friends tab. If you do sign in, we store the minimum needed, via our backend provider, Supabase:
- Account. You can sign in with Apple or Google. Depending on the method and your choices, we receive an email address (including an Apple private relay address), a unique account identifier, and a name that you can edit for your profile. Supabase stores this information to keep your account and social features working. We do not receive your Apple or Google password.
- Profile & progress. To show you on your friends' leaderboard, we store your display name, invite code, current streak, and longest streak. We also sync a day by day record of your no scroll windows, the date, which window (night or morning), the outcome (clean, frozen, or violated), and your device's time zone, so your streak and history stay consistent across devices. We do not store which apps you shield, your raw app usage data, your check ins, or your earned badges on our servers, those stay on your device only.
- Friends. Friend connections and pending friend requests you create (via invite codes) are stored so the social and leaderboard features work.
Product analytics and reliability
We use PostHog to understand product use and investigate problems, including app opens, onboarding progress, screen visits, purchases, routine outcomes, and technical crash reports. These records use a persistent installation identifier rather than a name or email address as their analytics identity. The identifier is stored in the device's Keychain and is also used with RevenueCat and in signed in history records. These records are pseudonymous, rather than anonymous, and can be associated with an optional account. Crash reports may be sent on a later launch.
Your selected app identities, raw Screen Time usage, and local check in answers are not included in these analytics records.
Onboarding recordings
During onboarding, we may use PostHog session replay to understand where setup fails or becomes confusing. The app masks text inputs, images, and system hosted views, including Apple's app picker, and disables network telemetry in these recordings. Recording stops outside onboarding, including on the purchase screen. Other visible interface text and interactions can appear in a recording.
Advertising measurement and your tracking choice
Twilock does not display third party ads. We use Meta and RevenueCat to measure whether our own advertising leads to installs, trials, or purchases. Apple may ask for permission to track your activity across other companies' apps and websites. Declining does not prevent purchasing or remove Twilock features. You can change your tracking permission in iPhone Settings → Privacy & Security → Tracking.
When you allow tracking, the app can send advertising identifiers, including IDFA when available, IDFV, IP address, and a Meta matching identifier, to RevenueCat for advertising measurement. RevenueCat can pass transaction events and permitted matching information to Meta through our configured integration. The Meta SDK also sends app activation and registration events with advertiser tracking disabled when permission is absent. Your selected apps, raw Screen Time usage, routine settings, and check in answers are not sent for advertising measurement.
Separately, Apple Ads attribution uses Apple's AdServices service to report campaign information. RevenueCat and PostHog use that information to understand campaign performance. AdServices collection does not depend on allowing the tracking prompt.
Purchases
Apple processes purchases and subscriptions. We use RevenueCat to verify transaction history, manage access, restore eligible purchases, and understand subscription performance. RevenueCat also receives the persistent installation identifier and the permitted attribution information described above. Existing lifetime purchases remain supported. We do not receive payment card details.
What we do not do
- We do not sell or rent your personal data.
- We do not use your selected app identities or raw Screen Time usage for advertising or share them with data brokers.
- We do not display third party ads.
- We do not require tracking permission to purchase or use Twilock.
Third party services
- Apple: Sign in with Apple, Screen Time / Family Controls, purchases, and Apple Ads attribution.
- Google: authenticates you if you choose Sign in with Google.
- Supabase: stores optional account, profile, synced routine outcomes, and friend connections.
- RevenueCat: processes purchase history and identifiers for access, analytics, and permitted advertising measurement.
- PostHog: processes product events, crash reports, campaign analytics, and masked onboarding recordings associated with the installation identifier.
- Meta: receives app activation and registration events and configured advertising attribution and transaction events, with tracking consent communicated by the app and purchase service.
Data retention and deletion
You can delete your account from Settings → Delete Account inside Twilock. This removes the associated account, profile, synced progress, and friend connections from our account backend. Deleting an account does not cancel an Apple subscription; manage subscriptions through your App Store account.
Deleting the app removes its ordinary local storage, but Keychain backed identifiers and Apple purchase records can remain after deletion or reinstallation. Account deletion does not automatically erase records held separately by purchase, analytics, or advertising services. Contact [email protected] for help with a data request. Some purchase records may need to be retained for transaction, fraud prevention, or legal purposes.
Age rating and children
For Twilock's current age rating in your region, see the App Store listing.
Twilock is not directed to children under 13. We do not knowingly collect personal information from children under 13.
Changes to this policy
We may update this policy from time to time. Material changes will be reflected here with an updated date.
Contact
Questions about this policy or your data? Contact us at [email protected].
Twilock is operated by Hussain Taheri. This policy describes the app’s data practices as of the date above.