RelockIn
How it works
Features
Blog
FAQ
Get the app

RelockIn Privacy Policy

Effective date: November 20, 2026

Using the RelockIn web extension? See the web extension privacy policy instead. It covers only the extension, which collects less than the apps.

RelockIn helps you spend your time online the way you mean to. Your rules, schedules, and browsing stay on your device, and we built it that way on purpose. We do collect a limited amount of data to run accounts and subscriptions, fix bugs, and see which of our ads work. This page explains exactly what that is, in plain language, so you can decide what you’re comfortable with.

The short version

We don’t:

  • Sell your personal information for money.
  • Show you ads in RelockIn.
  • See your passwords or what you type into websites.
  • Collect your browsing history, the pages you visit, or your searches.
  • Collect the names of the apps you use or limit.
  • Upload your rules, schedules, or settings. We don’t offer sync today.
  • Send your data to AI models.

We do:

  • Store your account details if you choose to create an account.
  • Process subscriptions through RevenueCat and the App Store or Google Play.
  • Collect usage analytics and crash reports in the iOS and Android apps.
  • Measure our own advertising with Meta in the iOS and Android apps.
  • Store your AI channel votes under a pseudonymous voter ID, if you’re signed in when you vote.
  • Keep the messages you send us for support, and any AI label disputes you file.

You can turn off usage analytics, crash reports, and Meta ad measurement at any time (Section 10). In the EU, EEA, and UK, they stay off unless you say yes.

At a glance: apps and web extension

The iOS and Android apps do more than the web extension, and collect more as a result.

iOS and Android appsWeb extension
Rules, schedules, usage, settingsOn your deviceIn your browser, on your device
Optional accountYesYes
AI channel votesStored pseudonymously if signed inStored pseudonymously if signed in
Shared AI channel listDownloaded about dailyDownloaded about daily
Usage analyticsYes, unless turned offNo
Crash reportsYes, unless turned offNo
Subscriptions (RevenueCat)YesNo
Meta ad measurementYes, unless turned offNo
DuckDuckGo browser servicesYesNo

1. Who we are and what this covers

RelockIn is made by Storiator Labs Inc, based in Alberta, Canada (“we” or “us”). We are responsible for the personal information described here. This policy covers the RelockIn apps for iOS and Android, the RelockIn web extension, and relockin.com. The web extension also has its own web extension privacy policy, which covers only the extension in more detail.

2. What stays on your device

On every platform, the following is stored locally and isn’t sent to us:

  • Your rules, limits, schedules, sessions, and challenges.
  • Your detailed usage history, including time spent per rule and per day.
  • Your settings and site customizations.
  • Channels you hide with “Block channel”, which is separate from voting on whether a channel is AI (Section 5).

In the iOS and Android apps, this also stays on your device:

  • Your browsing history, bookmarks, and saved passwords in the RelockIn browser. Our scripts that customize websites don’t send anything from those pages to our servers.
  • iOS Screen Time data. Apple gives RelockIn only private tokens for the apps you choose. We can count them, but we don’t receive their names, and no Screen Time data leaves your device.
  • Android app activity. If you turn on app limits, RelockIn uses Android’s Usage Access and Accessibility permissions to tell which app is open, so it can apply your limits. It’s limited to the app’s package name and doesn’t read the content on your screen. This information is used on your device and isn’t sent to us.

Uninstalling RelockIn removes this local information. We can’t recover it for you, because we don’t have a copy.

3. What we collect in the iOS and Android apps

3.1 Account (optional)

You can use RelockIn without an account. If you create one, we store your email address, a user ID, and sign-in details, using Supabase. You can sign in with email and password or with Google on both platforms, and with Apple on iOS. If you use Google or Apple, they handle their own sign-in steps and share basic profile details with us. On iOS, we also keep a token from Apple so that we can revoke Sign in with Apple when you delete your account.

3.2 Subscriptions

Purchases are handled by Apple or Google. We never receive your card details. We use RevenueCat to manage subscriptions on both platforms. RevenueCat receives and stores:

  • A customer ID: a random ID, or your RelockIn user ID once you sign in, which links your subscription records to your account.
  • Your purchases, plan, price, renewals, cancellations, and country.
  • Which version of a test you were placed in (such as a pricing or onboarding test), your answer to “How did you hear about RelockIn?” if you give one, and, if usage analytics are on, whether you declined a trial at a particular step.

We keep a copy of this information in our own database, so that we can understand our business and help with subscription problems. The test version and survey answer are sent whatever you choose in Privacy Options, because they’re part of running the subscription and pricing tests.

3.3 Usage analytics

Usage analytics tell us how features are used so we can decide what to improve. They’re stored under a random ID created on your device, not your account, email, or RevenueCat ID. They include:

  • The random ID, app version, major OS version, language, approximate install date, platform, subscription status, and whether you’re signed in.
  • Events such as finishing onboarding, adding a rule, starting a session, seeing the paywall, and answering a cancellation survey. Their times are shifted by a random amount of up to 7 days.
  • Counts and rounded amounts, such as how many rules you have, how many apps and sites they cover, and how long sessions last.

Analytics don’t include the pages you visit, your searches, or the names of your apps. There is one narrow exception: when you use a feature built for YouTube, Instagram, LinkedIn, or Reddit, an event can record which of those four sites it was.

3.4 Crash reports

When the app crashes, it can send a report to our database containing the technical error and stack trace, app and OS versions, the random analytics ID, and, on Android, the WebView version and whether the app was installed through Google Play. We use these reports only to fix bugs. We don’t use a third-party crash reporting service.

3.5 Usage summaries for subscribers

To understand what helps people stay subscribed, if you are or were a paying subscriber and usage analytics are on, we store a small set of broad labels with your RevenueCat ID. Unlike analytics, these labels are linked to your subscription record, and to your account if you’re signed in. They include:

  • Your platform, language, and major OS version.
  • Ranges such as how many rules, apps, and sites you use and how often you have sessions.
  • Which months after installing you were active.
  • Your test versions and “How did you hear about RelockIn?” answer.

They never include which apps or sites you use.

3.6 Meta ad measurement

We advertise on Meta’s platforms, including Facebook and Instagram. To see which ads work, the apps include Meta’s SDK. It starts only when ad measurement is allowed. When it runs:

  • Meta’s SDK sends Meta events such as installing and opening the app and viewing the paywall, on iOS also starting a trial or subscribing, along with an anonymous Meta ID and device details such as model, language, and time zone.
  • RevenueCat sends Meta subscription events, such as trials, purchases, and renewals, including their value. To match them to your device, it can include the anonymous Meta ID, device identifiers, IP address, user agent, and a hashed version of your customer ID.
  • iOS: we don’t ask for Apple’s tracking permission and don’t receive your device’s advertising ID (IDFA). Meta’s SDK marks events as not opted in to tracking. Apple’s SKAdNetwork and AdAttributionKit also report ad results without identifying you.
  • Android: Meta’s SDK can read your device’s advertising ID. You can delete or reset it in your Android settings.

Meta handles this data under its own terms and privacy policy, and may be able to connect it to a Meta account. We don’t send Meta your browsing history, your rules, the apps you limit, or your votes. We don’t use this to show you ads inside RelockIn.

3.7 Support and messages

If you contact us from the app, we receive your email address and message, and may also receive your user ID, RevenueCat ID, device model, app and OS versions, and subscription status. If you report a problem from the browser menu, we also receive the URL of the page you were on, which is shown as a site name in the form but sent in full. Written answers to the cancellation survey are stored the same way. We store these requests in Supabase and use Resend to email them to our team. To prevent spam, we limit how many requests can be sent, as described for our website forms in Section 6.

We can also send you a message inside the app, such as a reply to your request. The app checks for these using your RevenueCat ID.

3.8 Browser services from DuckDuckGo

The iOS and Android browsers are built on DuckDuckGo’s open-source browser, and two of its services are still active. These go directly to DuckDuckGo, not to us, and Privacy Options doesn’t turn them off:

  • Search and suggestions. DuckDuckGo is the default search engine, so it receives your searches, and what you type in the address bar if suggestions are on. We don’t receive them.
  • Protection lists. The app downloads tracker-blocking lists and browser configuration from DuckDuckGo.

We’ve turned off the usage statistics that DuckDuckGo’s browser normally sends to DuckDuckGo. On Android’s Google Play version, the browser still reads the install referrer from Google Play on your device, but we don’t send it to DuckDuckGo’s statistics or to our servers. See DuckDuckGo’s privacy policy for how it handles search and suggestions.

3.9 Permissions

Some permissions are for the app’s own features, like app limits. Others are used only by the browser, such as location, camera, and microphone, which websites can use only if you allow them to. RelockIn doesn’t collect your location, photos, or recordings.

4. What the web extension does

The extension is much simpler. It has no usage analytics, crash reporting, Meta SDK, RevenueCat, or payments. All of its rules, schedules, usage, and settings are stored in your browser’s local extension storage, and they don’t sync through your browser account.

  • Website access. The extension runs on the sites you visit so it can match them to your rules and count your time. It checks the current page’s URL locally and doesn’t send it to us. It doesn’t use the browser’s history, tabs, or cookies permissions.
  • Optional account. You can sign in with email and password, Google, or Apple, using Supabase (Section 3.1).
  • AI votes. If you’re signed in, your votes are stored as described in Section 5. On Firefox, this needs your permission first.
  • Shared AI channel list. About once a day, on every browser and whether or not you’re signed in, the extension downloads the published list from our server. Like any web request, this exposes your IP address and browser details to Supabase, our server provider, and it doesn’t include any information about you or your activity.

We may add basic usage analytics to the extension in the future. If we do, we’ll update this policy first.

5. AI channel votes

RelockIn can label or hide YouTube videos from channels that people have flagged as AI-generated. This relies on votes from RelockIn users, and works the same way in the apps and the extension.

What we store

If you vote while signed in, we store your vote (AI or not AI), the channel’s ID, the channel’s handle and name as you saw them, the app or extension version, and the date. We don’t store your user ID with your votes. Instead, they’re stored under a voter ID: a one-way code made from your user ID with a secret key that we keep separately from the votes. Without that key, our vote records alone don’t show which account cast which vote.

We use the key to link votes to an account only on purpose, one account at a time: to delete your votes when you delete your account, or to exclude an account’s votes for spam or abuse. You can change or withdraw a vote, and we use a daily limit on vote changes to prevent abuse. For that limit, we keep a count of today’s vote changes under the same voter ID.

If you vote while signed out, your votes stay on your device and work only for you. They upload when you sign in. Privacy Options doesn’t control votes, because you’re choosing to submit them.

What we do with votes

  • We combine votes into a published list that RelockIn downloads for everyone. Channels are placed in tiers based on how many votes they have and what share say AI. It can also include our own review of a channel.
  • The published list contains channel IDs, tiers, and vote totals. For channels we’ve reviewed as AI, it can include the channel’s handle and name. It’s publicly downloadable.
  • We can exclude a voter’s votes from the list, for example to deal with spam or abuse.

What we don’t do with votes

  • We don’t publish who voted, or how any person voted.
  • We don’t sell votes, or send them to Meta or to AI models.
  • We don’t use your votes to advertise to you.
  • We don’t upload the channels you hide with “Block channel”, or anything about what you watch.

Disputing a label

If you think a channel’s label is wrong, you can ask us to review it using the form at relockin.com/ai-dispute, which the apps and extension link to next to the vote. What it stores is described in Section 6. If we agree, we record our own review of the channel, which can then appear in the published list as described above. We don’t publish disputes or who filed them.

Other sites

We plan to extend voting to other sites soon, including Facebook and Instagram. It will work the same way, storing the account or page you voted on under your voter ID. We’ll update this policy if it differs from what’s described here.

6. Our website

  • Forms. If you use our support, account deletion, AI label dispute, source code access, or waitlist forms, we store what you submit, including your email address, in Supabase. Support, deletion, dispute, and source code access requests are also emailed to our team through Resend.
  • AI label disputes. A dispute includes the channel’s link and name, whether you say it is or isn’t AI, whether and how you’re connected to the channel, your explanation, any proof or links you add, and your email address. If you open the form from the app or extension, it’s filled in with the channel and its current label, and records which of them you came from.
  • Source code access. If you apply to review our code at relockin.com/source-access, we store your name, email address, and GitHub username, any profile link and organization you add, what the review is for, which code you asked for, what you want to check, and which version of the conditions you agreed to. If we approve it, we invite your GitHub account to our repositories, and GitHub handles that under its own privacy policy.
  • Spam limits. To stop the support, deletion, dispute, and source code access forms (including support requests from the apps) being flooded, we count how many requests come from each sender and email address. For this we store one-way hashes of your IP address, or your user ID if you’re signed in, and of the email address you entered, and delete them after 2 days.
  • Campaign links. If you arrive at our download page through a campaign link, we record the campaign code, the referring page, and your browser’s user agent, so we can see which campaigns bring people to RelockIn. We don’t store your IP address with this record.
  • Hosting. Our website is hosted on Cloudflare, which receives your IP address and browser details to deliver the site and protect it from abuse.
  • Third-party content. Our pages load fonts from Google and some images from a content delivery network, and those providers receive your IP address as a result.
  • We don’t run analytics or advertising trackers on our website.

7. No sync today

Right now, RelockIn has essentially no synced data. An account doesn’t copy your rules, schedules, settings, or usage history to our servers or to your other devices. The only things an account connects across devices are your subscription and your AI channel votes.

Cloud sync is something we may build one day, but it isn’t imminent. If we do, we’ll update this policy and explain what it stores before it’s available to you.

8. Why we use your information

We use the information above to:

  • Provide RelockIn, including your account, subscription, and shared AI channel list.
  • Provide support and respond to you, including about AI label disputes and source code access.
  • Find and fix bugs, and decide what to improve.
  • Understand subscriptions, cancellations, and pricing and onboarding tests.
  • Measure whether our advertising works.
  • Prevent spam and abuse, and meet our legal, tax, and accounting obligations.

If you’re in the EU, EEA, or UK, our legal bases are: contract, for your account, subscription, and support; consent, for usage analytics, crash reports, subscriber usage summaries, and Meta ad measurement; legitimate interests, for AI votes and label disputes, source code access, preventing abuse, pricing and onboarding tests, and understanding how people found us; and legal obligation, for tax and accounting records. You can object to processing based on legitimate interests by contacting us.

9. Who we share information with

We don’t sell your personal information for money. We share it only with the companies below, and if required by law or as part of a merger or sale of our business. Some privacy laws define “selling” or “sharing” broadly enough to include advertising measurement like the Meta data described in Section 3.6. You can turn that off at any time (Section 10).

CompanyWhat forApplies to
SupabaseDatabase, sign-in, and hosting for our server functionsApps, extension, website
RevenueCatSubscription managementApps
Apple and GoogleApp stores, purchases, optional sign-inApps, extension (sign-in only)
MetaMeasuring our ads, unless turned offApps
DuckDuckGoSearch and protection listsApps
ResendEmailing support requests, AI label disputes, and source code access requests to our teamApps, website
Cloudflare, Google Fonts, and our website’s image providerDelivering our websiteWebsite

10. Your choices

  • Privacy Options (iOS and Android). Everywhere, you can open the browser’s Settings and go to RelockIn Privacy Options to turn off “Usage analytics and crash reports” and “Ad measurement with Meta”.
  • EU, EEA, and UK. We ask first, using your device region or app store country. Both choices stay off until you answer. If you decline, analytics waiting on your device are deleted. Meta’s SDK can’t be fully stopped once started, so if you turn ad measurement off, it stops sending events immediately and doesn’t start again the next time you open the app.
  • Use RelockIn without an account. Nothing is stored against an account, and AI votes stay on your device.
  • Device controls. You can remove RelockIn’s Screen Time, Usage Access, and Accessibility permissions in your device settings, though app limits won’t work without them.

Turning these off stops new data from being sent. To remove data we already have, see Section 12.

11. How long we keep information

  • Data on your device: until you delete it or uninstall RelockIn.
  • Account and AI votes: until you delete your account. Votes you withdraw are deleted.
  • Crash reports: up to 12 months.
  • Usage analytics and campaign link visits: up to 24 months.
  • Support requests, AI label disputes, and in-app messages: up to 2 years.
  • Source code access requests: up to 2 years after we decline the request, or after your access ends.
  • Spam-limit counters: 2 days.
  • Subscriber usage summaries: up to 24 months after your subscription ends, or until you delete your account.
  • Our copy of your subscription records: up to 7 years after your subscription ends, for tax, accounting, and legal purposes, or until you delete your account.
  • Published AI channel list: the list contains only totals, so past totals aren’t tied to you. Deleting your account removes your votes from future lists.

12. Deleting your account and data

You can delete your account in the app under your account settings, which takes effect right away. You can also submit a request at relockin.com/delete-account from any platform, including the web extension. Our team handles those requests by hand, may need to confirm that the request is yours, and aims to finish within 30 days.

  • We delete: your account and sign-in details, your AI votes, your subscriber usage summaries, your RevenueCat customer record and our copy of your subscription records, in-app messages to you, and support requests, AI label disputes, and source code access requests linked to your account or email address. If you used Sign in with Apple, deleting in the app also revokes it. For a website request, we’ll tell you how to remove it in your Apple settings.
  • We keep: a one-way hash of your user ID and the date, as a record that the deletion happened.
  • Usage analytics and crash reports: these are stored under a random ID, not your account, so we can’t find them from your email or account. They can only be deleted if we can identify the random ID, and otherwise they remain under that ID until the end of the period in Section 11.
  • Others: deleting your account doesn’t cancel your subscription, which you manage through the App Store or Google Play. Apple and Google keep their own purchase records. Deleting also doesn’t remove what Meta or DuckDuckGo hold under their own policies.

13. Security

Data sent to our servers is encrypted in transit. Access to our database is restricted, and the individual votes table isn’t publicly readable. Votes are stored under pseudonymous voter IDs, not user IDs (Section 5). Data on your device is protected by your device’s and browser’s standard security. No system is completely secure, so if a breach affects you, we’ll notify you and the relevant authorities where the law requires it.

RelockIn changes how some websites look and behave, which means it has to run alongside them:

  • iOS: our scripts run in a separate space that websites can’t read. Each site gets only its own settings.
  • Android: each site also gets only its own settings, but Android’s browser engine has no such separate space. A site could technically read its own settings and the limit details for your rules that cover it, such as your hidden channels on YouTube. Other sites can’t see them.
  • Site data: to make some features work, RelockIn can change site data on your device. For example, the iOS app removes certain Reddit cookies. This doesn’t send anything to us.

14. Where data is stored

We’re based in Canada, and our service providers process data in the United States and other countries, whose laws may differ from yours and which may give authorities there access to it. Where the law requires it, including for data from the EU, EEA, and UK, we rely on appropriate safeguards for these transfers, such as standard contractual clauses. You can contact us for more information.

15. Your rights

Depending on where you live, you may have the right to access, correct, delete, or receive a copy of your personal information, to object to or limit how it’s used, and to withdraw consent at any time. Contact us using Section 18 to use these rights. We won’t treat you differently for doing so. We may need to confirm your identity first, and we can only act on data we’re able to connect to you.

  • Canada: our handling of personal information is subject to PIPEDA and Alberta’s Personal Information Protection Act. You can complain to the Office of the Privacy Commissioner of Canada or the Office of the Information and Privacy Commissioner of Alberta.
  • EU, EEA, and UK: you can complain to your local data protection authority.
  • United States: some states give you the right to opt out of the “sale” or “sharing” of personal information, which you can do for Meta ad measurement in Privacy Options, and to appeal a decision we make about your request by replying to it.

16. Children

You must be at least 13 to use RelockIn, and RelockIn isn’t directed at children under 13. In some countries, a higher age applies before a person can give their own consent, and a parent or guardian must consent for them. If you believe a child under 13 has given us personal information, contact us and we’ll delete it.

17. Other websites and changes to this policy

Websites you visit in RelockIn have their own privacy practices, including their own trackers, though the browser blocks many of them. We’re not responsible for what those sites do.

We’ll update this policy as RelockIn changes and revise the date at the top. If a change materially affects how we use your information, we’ll let you know in the app or by another reasonable means, and ask for your consent where required.

18. Contact us

Questions or requests about your privacy are welcome.

Storiator Labs Inc
[email protected]
Alberta, Canada

Follow us
Instagram TikTok LinkedIn Discord
Get on the App Store or Google Play
Or, get the browser extension:
RelockIn
  • Terms & Conditions
  • Privacy Policy
  • Source Code
  • Blog
  • FAQ
  • Support
Storiator Labs Inc. ©2026