Effective date: 16 October 2026 · App: Revive (com.revivesupport.revive) · Contact: [email protected]
Revive is developed and operated by N7 CYBER CONSULTANCY LTD, a company registered in Scotland (company number SC875993) with its registered office at 5 South Charlotte Street, Edinburgh, EH2 4AN ("we", "us") — the data controller, registered with the UK Information Commissioner's Office under reference ZC252822. Contact for anything about your data: [email protected], or by post to the registered office. This policy explains what Revive does with information, in plain language. Where a section says on your device only, that information never leaves your phone.
Revive helps people who want to stop compulsive use of certain websites, keywords or apps. It blocks the things you list, protects those settings behind a PIN and two-factor authentication, and — optionally — lets a person you trust (an "accountability partner") know if you switch that protection off.
The following is stored in Android's encrypted app storage (backed by the device Keystore) and is never transmitted to us or anyone else:
| Data | Notes |
|---|---|
| Your PIN | Stored only as a salted hash; the PIN itself is never stored. |
| Authenticator (TOTP) secrets — yours and your partner's | Used to verify codes on the device. |
| Backup / one-time codes | Stored hashed. |
| Blocklists — domains, keywords, apps | Your configuration. |
| Habit, lapse and focus-timer records | Your personal progress data. |
| Your PIN-recovery email address | Stored encrypted on the device; see section 5 for the one moment it is transmitted. |
| Settings and preferences |
Accessibility service. To enforce your blocklist, Revive's accessibility service observes which app is in the foreground and reads the browser's address bar. This information is used instantly to decide whether to show a block screen or close a tab. It is not stored and not transmitted.
VPN service. Revive runs a local VPN on the device to filter DNS lookups against your blocklist. No browsing traffic is routed through any remote server, and nothing about your browsing is logged or sent anywhere.
Accountability mode is optional and off by default. When you enable it, you enter details of a partner and the app tells you clearly that this person will be asked to accept and will then be notified about your protection status.
While Accountability mode is active, the app sends the following to our server:
| Data | Why |
|---|---|
| A random device identifier generated by the app | To match events to your install. It is not linked to your Google account, phone number, IMEI, or advertising ID. |
| Your phone's model name | Shown in alerts so the partner knows which device. |
| Your partner's name, email address and mobile number | To ask for their consent and address the alerts. |
| Protection events: protection turned off, a block removed, Accountability switched off, the app force-stopped, the subscription ending (protection paused), the app going silent (possible uninstall; after a lapsed subscription, three messages over 30 days and then the record is removed), or a data-deletion request — with the time and the delivery channel used | The purpose of the feature. |
| A liveness signal roughly every 15 minutes: whether protection, the VPN and the accessibility service are running, and the app version | Solely so that sustained silence can be turned into a single "the app may have been uninstalled" alert. The signal itself is never sent to your partner. |
Where it is stored. On infrastructure provided by Supabase in Stockholm, Sweden (European Union). Access is restricted by row-level security: the app can only write its own events, and no app install can read another's data.
How alerts reach your partner. By SMS through Twilio and by email through Resend. These providers process your partner's phone number or email address only to deliver the message.
Your partner's consent. Your partner is a third party who has not used the app, so before any alert is sent they are asked, during setup, by one email with Accept / Decline buttons linking to this policy (partners are contacted by email only from 15 October 2026; earlier partners who gave a mobile number keep it only for the optional texted approval code). Setup does not complete until they have accepted. Alerts are sent on a channel only after they accept it. Where your partner's details came from: the user who nominated them typed them in; we hold no name for that user and cannot identify them to the partner beyond the phone model shown. The request email tells the partner who we are, why we have their details and their rights. If a partner declines or opts out, we keep a scrambled record of their address or number (a keyed one-way code held with a secret that is not stored alongside it) for as long as their objection stands. The user who nominated them may ask them to reconsider, by email only, after a cooling-off period of seven days, at most three times in a day and at most three times in all; after three unanswered invitations, or at any time by using the "Don't contact me again" link in any email from us, the address is closed for good and no Revive user can cause us to contact it again. The same applies if a partner asks us to erase their details: we delete everything except that scrambled record, which we keep specifically so that we never contact them again; on an explicit request we will remove it too, with the consequence that a later nomination could then reach them. Every alert email carries an unsubscribe link, which withdraws consent immediately. Declining or unsubscribing by email triggers one confirmation email containing a re-subscribe link and the permanent "Don't contact me again" link, and nothing else. We record each request and response (channel, outcome, time) as evidence of consent. If your partner declines or opts out, the app tells you, and you can choose a different partner or, after the cooling-off, invite them again within the limits above. You can change your partner only in that situation or while the app is in Solo mode (leaving Accountability mode itself needs your partner's code; if your partner has declined or opted out, the app switches to Solo mode by itself and no code is needed); a new partner is asked for consent in exactly the same way.
Partner approval codes (optional). Sensitive actions can be approved with a one-time code emailed to your partner, or, for partners added before 15 October 2026 who gave a mobile number, texted to them. To send it, the app passes your partner's mobile number to our server, which texts the code through Twilio and stores only a masked version of the number, a hashed code, a hashed device identifier and the action description, for 15 minutes plus a short purge window. The authenticator-app method works entirely offline and is always available as an alternative. SMS codes are not offered for US or Canadian (+1) numbers, and cannot be sent to a partner who has opted out of texts (replied STOP) until they text START.
Only alerts: the type of event (for example, "protection was turned off"), the time, and your device's model name. Your partner never receives your blocklists, browsing activity, PIN, or any content.
You provide a recovery email address during setup. It is stored encrypted on your device only. If you use "Forgot PIN → Email me a code", the app sends that address and a one-time six-digit code to our server, which emails the code to you via Resend. The server records only your device identifier and the time of the request (to limit abuse to five requests per hour) — the address itself is not stored on our server, and those request records are deleted within an hour. Codes expire after 15 minutes.
Revive uses Firebase Crashlytics (Google) to collect crash reports so we can fix bugs. A report contains the crash stack trace, device model, Android version and app version. It does not contain your PIN, blocklists, partner details, or browsing information. Crash reporting is on by default; turn it off at any time in Settings → About → Crash reporting. If you send a report from Settings → Report a problem, we receive the description you type, an optional reply address, and a diagnostic snapshot of the part of the app you chose (timings, settings state and error codes; never your PIN, blocklists, partner details or browsing). Reports are stored for 30 days and emailed to our support inbox. Revive also sends error and diagnostic events to our own server (Supabase, EU) when something goes wrong in the app, and when you send a report: an error code, a short description of the fault, timing and state information for the part of the app affected (for example whether the VPN was running, notification settings, and how many sites or apps are on your lists but not what they are), your device model, Android version, app version, and a random per-install identifier. These never contain your PIN, the contents of your blocklists, partner details or browsing. The same crash-reporting switch controls them. They are kept for 30 days.
Requests to our server carry a Firebase App Check token that lets the server recognise the genuine Revive app. The token contains no personal information. Requests without a valid token are still served; the check is used only to detect abuse.
Some providers (Twilio, Google, Cloudflare, Resend's US entity, and our mailbox provider, Microsoft) process data outside the UK/EU. For each transfer we rely on the UK Extension to the EU-US Data Privacy Framework where the provider's certification covers it, and otherwise on the contractual safeguards in that provider's agreement with us (the UK International Data Transfer Addendum or Agreement).
| Where | Retention |
|---|---|
| On your device | Until you delete it in the app or uninstall Revive. |
| Server — device record, events, liveness | While Accountability mode is active. Leaving Accountability mode clears your partner's details from our server straight away. Settings → Privacy & data → Delete my data removes everything we hold: immediately in Solo mode; in Accountability mode after a 7-day cooling-off period — your partner is told, alerts continue meanwhile, and you can cancel at any time before the deadline (this protects the accountability relationship from being ended impulsively). Your legal right to erasure is separate from that feature: if you exercise it (email [email protected] quoting the support reference shown on the Privacy & data screen), a partner cannot prevent it, Accountability processing and partner alerts stop when the request is accepted, and your server record is deleted immediately — or, if you prefer, held for up to seven days in a deletion-only state so you can reverse an accidental request. If the app is uninstalled or goes silent, your partner receives at most one final "the app may have been uninstalled" alert and the record is deleted automatically 30 days later. You can also request deletion by emailing [email protected] — we act within 30 days. |
| Server — alert history | Deleted automatically after 90 days. |
| Server — your partner's consent records | Kept while the accountability relationship exists (evidence of consent); deleted with the device record. |
| Server — PIN-recovery request log | Deleted automatically within about an hour. |
| Server — SMS approval codes | Deleted automatically after expiry (15 minutes) plus a short purge window. |
| Server — error and diagnostic events, and problem reports (including a reply address if you gave one) | Deleted automatically after 30 days. |
| Crash reports | Retained by Firebase Crashlytics for 90 days. |
Information is encrypted in transit (TLS) and at rest. On-device secrets are protected by the Android Keystore; where a device cannot provide secure storage, Revive refuses to set up features that would require storing a secret unsafely. Server data is protected by row-level security and access keys that are never included in the app. Our servers hold no information that would allow anyone to unlock the app remotely.
Revive is intended for adults (18+). We do not knowingly collect information from anyone under 18.
If you are in the UK or EU you have the right to access, correct, delete, restrict or object to our processing of your personal information, and to data portability. Our lawful bases are your consent (Accountability mode and partner details, which you can withdraw by switching to Solo mode or deleting your data) and our legitimate interests in keeping the app reliable and secure (crash reports, abuse prevention). To exercise any right, email [email protected]. If you are in the EU, our EU representative under Article 27 is: [to be appointed before the app is offered in the EU — name and contact will appear here]. You can also complain to the UK Information Commissioner's Office (ico.org.uk) or your local data-protection authority.
We will update this page and change the effective date when the policy changes. Material changes will be highlighted in the app's release notes.