Rein Privacy Policy
Effective November 1, 2026
The short version: Rein blocks apps using Apple's Screen Time technology. What you do on your phone — which apps you use and for how long — stays on your phone. Rein doesn't send it anywhere, doesn't sell it and doesn't use it for ads. If you create an account, we keep a copy of your settings so you don't lose them when you switch phones. And, to know which of our ads work, the app tells Meta that it was installed and a few basic steps (on iPhone, using the advertising identifier only with your permission).
This policy explains what data the Rein app (iOS and, later, Android), published by Nova Inc. ("we"), handles. Any questions? Email us at supportnovateam@gmail.com.
1. Screen Time: what never leaves your phone
To block apps, Rein uses Apple's Screen Time tools (Family Controls, Device Activity and Managed Settings), with the permission you grant and can revoke at any time in Settings.
- The apps you pick reach Rein as encrypted identifiers created by Apple. Rein doesn't know their names: the icons and names you see in the app are drawn by the system itself.
- Your screen time (minutes, pickups, the charts in Progress) is calculated by iOS and only shown inside an Apple extension that, by design, can't send data off your phone. Rein can't read it or upload it.
- What Rein counts (minutes blocked, attempts to open a blocked app, your streak) is stored on your phone.
- We don't share this data with anyone, use it for advertising or profiling, or sell it.
2. Your account (optional)
You can use Rein without an account. If you choose "Continue with Apple" or "Continue with Google", we use Firebase Authentication (by Google) to create it. We receive a user ID and, depending on what you allow, your name and email. With Apple's "Hide My Email", we receive a relay address instead of yours. If you don't sign in, Firebase creates an anonymous user with no personal data.
3. Cloud backup (only with an account)
With an account, Rein keeps a copy in Cloud Firestore (by Google) of:
- your blocks: name, type, days, schedules, limits, number of opens and the message you wrote;
- your streak (the days you kept it) and the total number of blocked attempts;
- your Tight Rein settings (the method and its options — never your PIN or key, which stay in your phone's keychain);
- your preferences: block screen, notifications, daily goal and your answers during setup (what you want Rein for and how much time you thought you spent on your phone).
The copy does not include which apps you block (on a new phone you pick them again), any usage data or any app names. Only you can read it: the database rules only allow access to your own user.
4. Purchases
Rein Premium payments are handled by Apple (or Google Play on Android); we never see your payment details. We use RevenueCat to know whether your subscription is active: it receives the store receipt, the products purchased and a customer ID (anonymous or, with an account, your user ID plus the platform). RevenueCat keeps purchase history for as long as accounting and the law require.
5. Measuring our ads (Meta)
We advertise Rein on Facebook and Instagram. To know which ads bring people to the app, Rein includes Meta's SDK (App Events), which sends Meta the install, when the app is opened and a few steps: finishing the welcome, creating your first block, opening the Premium screen and starting your first focus session. Purchases (trial, subscription, renewals and amount) are reported to Meta by RevenueCat so they can be attributed to the ad.
- On iPhone, the advertising identifier (IDFA) is only used if you accept Apple's "Allow Rein to track your activity" prompt. You can change it at any time in Settings → Privacy & Security → Tracking. Without that permission, Meta only receives events without the identifier, plus Apple's aggregated, anonymous attribution (SKAdNetwork).
- On Android, Meta may use Google's advertising ID, which you can delete or reset in your phone's settings.
- These events never include your screen time, which apps you block, the names of your blocks or anything you type.
- Meta handles this data under its own policy: facebook.com/privacy/policy.
6. What we don't do
- No ads inside Rein.
- We don't use your screen time or the apps you choose for advertising, and we don't give them to Meta or anyone else.
- We don't sell your data. No other analytics tools, and no app names sent to any service.
- Reminders (session end, check-ins, the notice before a trial is charged) are local notifications scheduled by your phone; they don't go through our servers.
7. App configuration
When it opens, Rein reads a public document from our server with update or maintenance notices and the support email. That request carries no personal data.
8. How long we keep data and how to delete it
- What's on your phone is deleted when you uninstall Rein.
- The cloud backup and your account exist until you delete them: Profile → Delete my account removes both immediately.
- You can also email us to get a copy of your data, correct it or delete it. We reply within 30 days at most.
9. Your rights
Depending on where you live (for example, the EU under the GDPR or California under the CCPA), you have the right to access, correct, delete and port your data, and to object to its processing. We process your data to provide the service you ask for (the account, the backup and the subscription) and, to measure ads, on your consent (Apple's tracking permission) or our legitimate interest in knowing which advertising works. If you live in California, sending these events to Meta may count as "sharing" under the CCPA: you can opt out by turning off tracking or by emailing us. Email us to exercise any of these rights.
10. Where data is stored
Firebase (Google), RevenueCat and Meta store data on servers in the United States and other countries, with the safeguards the law requires for these transfers.
11. Children
Rein is meant for people managing their own phone. It isn't directed at children under 13, and we don't knowingly collect data from children under that age. If you believe a child has given us data, email us and we'll delete it.
12. Security
Connections are encrypted (HTTPS/TLS) and access to the cloud backup is restricted to your user. No system is perfect, but we keep as little as possible to reduce the risk.
13. Changes
If we change this policy, we'll post the new version here with its date and, for important changes, let you know in the app.