SelfGuard

Privacy Policy

Last updated: 31 October 2026

SelfGuard (“SelfGuard”, “the app”, “we”, “us”) is an Android app that helps you block pornography, distracting apps, and content, and stay accountable during recovery. It is published on Google Play under the developer name RestartLab — an independent solo developer, not a registered company. This policy explains what information the app handles, why, and the specific cases where data leaves your device. It applies to the SelfGuard Android app (com.selfguardapp.android).

The short version. Your blocks, keywords, focus sessions, streaks, notes, and check-ins are stored only on your device and encrypted, and the app has no ads and no analytics or tracking SDKs. However, to create a content or app block — SelfGuard’s core feature — you must first sign in (with Google, or with a code we email you) and choose an accountability email, your own or someone you trust (this is required, not optional). Once you do, your email address, the accountability email, an ID for your phone, and the details of your active blocks (including the keywords and app names you block) are sent to our server to run sign-in, backup, and accountability alerts. Blocks follow your account, so a block also runs on your other phones signed in to it. If you buy Premium, Google Play takes the payment, and we keep only a record of the purchase (Section 6). Focus sessions don’t require signing in and stay on your device. You can delete your account in the app or on our website (Section 10). If you turn on the optional Network Protection, your device’s DNS is handled by a third-party filtering provider (see Section 4).

1. Information stored only on your device

The following is created and kept locally on your phone, in a database that is encrypted at rest. We cannot see it, and it is not sent to us (aside from the active-block details described in Section 3):

The app also keeps a short technical log in its private storage: the last few dozen times the app started or was updated, blocking switched on or off, the app checked in, a Google sign-in failed, or Android ended the app (for example after a crash). It holds no blocks, keywords, browsing or screen content, and it leaves your phone only if you choose to send it (see “Diagnostics you choose to send” in Section 3).

2. Device access and permissions

Permission / accessWhyLeaves your device?
Accessibility Service To enforce your blocks, SelfGuard reads on-screen content (the current app, the web address in supported browsers, and visible text) in real time to detect blocked apps, sites, and words. No. This is processed on-device, only to enforce your blocks. It is never recorded, stored, or transmitted.
Installed-app list To show you a list of your installed apps so you can choose which to block or silence. SelfGuard asks Android only for apps that have a launcher icon — it does not request the broad QUERY_ALL_PACKAGES permission. Their names are also read once, on the phone, so that while a block is running the app can tell its own settings page (where it could be removed) from an ordinary list of apps. No, the list is read on-device. Only the identifiers of apps you actually choose to block are backed up (see Section 3).
Internet Signing in, the accountability email and its verification, the lock backup, checking Premium purchases, and trusted-time sync. See Sections 3–6.
Your Google account — only if you tap “Continue with Google” Android shows Google’s own sign-in sheet. You pick an account there, and Google gives SelfGuard a sign-in token for that account only. SelfGuard never sees your password or your other accounts. Yes, the token goes to our server to sign you in (see Section 3).
Google Play billing To buy Premium. Google Play shows its own purchase sheet and takes the payment; SelfGuard never sees your card or other payment details. Yes: you buy from Google, and the purchase token goes to our server to give your account Premium (see Section 6).
Network state Added by Google’s billing library, which uses it to check whether the phone is online before it talks to Google Play. No. Nothing is collected, stored, or sent.
Device administrator Uninstall protection. While it is active, Android’s own package manager refuses to uninstall SelfGuard, so a block cannot be escaped by deleting the app. SelfGuard requests no administrator powers: it cannot lock your screen, change or expire your PIN, password or fingerprint, erase your device, or locate it. You switch it on yourself on Android’s own screen, and can switch it off at any time in Settings → Security → Device admin apps. No. Nothing is collected, stored, or sent.
Notifications For two messages, and only those: blocking has stopped and only you can start it again; and, once per install on Xiaomi and Transsion phones (Tecno, Infinix, itel), a reminder to switch on the phone’s own auto-start setting, without which those phones stop SelfGuard in the background. On Android 13 and later the app asks for it once a block exists, not before; older versions allow notifications without asking. Declining costs you the warning, nothing else. No. The notification is written and shown on your device.
Run at startup Android cancels an app’s alarms when the phone restarts. SelfGuard uses this only to put back the timer that checks its own enforcement is still running. No. Nothing is collected, stored, or sent.
Ignore battery optimisations Lets the app raise Android’s own one-tap dialog asking to keep running in the background — without it, phones put SelfGuard to sleep and blocks stop being enforced. The app only opens that dialog; the choice, and the switch, are yours, and it can be reversed in your battery settings at any time. No. Nothing is collected, stored, or sent.
Clipboard — only when you tap “Paste” On the screen where you enter the 6-digit code, a Paste button reads what you have copied and takes the six digits out of it, so the code need not be retyped. Nothing is read unless you tap it, and Android 12 and later show a notice each time. No. The clipboard text is used on your device, then discarded.

SelfGuard declares six Android permissions — INTERNET, notifications, run at startup, the battery-optimisation exemption, Google Play billing and network state above (the last two come with Google’s billing library) — plus one that Android’s own support library adds so that no other app can send SelfGuard its internal messages. The Accessibility Service and the device administrator are not permissions the app can request: you grant each of them yourself, on Android’s own screens, and can withdraw either at any time. SelfGuard does not request location, contacts, storage, camera, or microphone.

3. Information sent when you sign in and create blocks (accountability)

Creating any block requires signing in and a verified accountability email. This is a required step for SelfGuard’s core blocking — you cannot create an app, keyword, adult-content, short-video, browser, profile, or network block without it. When you set this up and while you have active blocks, we process:

Focus sessions don’t need an account and are never sent to our server. Deep focus, part of Premium, needs the account Premium is on, but its sessions stay on your phone too. If you skip signing in and only use Focus, none of the above is collected.

Versions of SelfGuard from before accounts were added don’t sign in. They verify the accountability email the same way, and key the lock backup and heartbeats to that address instead. After updating, they are asked to sign in at their next block.

Diagnostics you choose to send. If blocking stops working, Settings → Send diagnostics opens an email to us in your own email app. It contains your phone’s make, model and Android version; the app version; whether blocking was switched on, whether Android was actually running it, and when it last saw your screen change; whether uninstall protection, battery exemption and notifications are on; how many blocks are active, by type, and when the last one ends; whether you are signed in and have an accountability email set; your Premium plan and until when, as our server last said; and the technical log from Section 1. It never includes which apps or keywords you block, your email addresses, or anything you browsed. You can read it before sending, and nothing is sent unless you send it.

4. Network Protection (Private DNS) — optional

SelfGuard’s optional Network Protection guides you to set your device’s system Private DNS to a family-filtering DNS provider — CleanBrowsing (family-filter-dns.cleanbrowsing.org) — so that adult sites are blocked and Safe Search is enforced for apps that use your device’s DNS. If you enable it:

5. Trusted time

So that a block can’t be ended early by changing the phone’s clock, SelfGuard takes the time from a trusted source rather than from the device:

6. Purchases and Premium

SelfGuard Premium is sold through Google Play, as a monthly or yearly subscription or a one-time Lifetime purchase. Google Play takes the payment. We never see your card, bank or other payment details.

When you buy, the app gives Google a one-way hash of your account’s email address, never the address itself. That ties the purchase to your SelfGuard account, so no other account can claim it. Our server then asks Google about the purchase and keeps:

We use this only to give Premium to every phone signed in to your account, to end it when a subscription runs out or is refunded, and, if you move to Lifetime, to end your subscription with Google and refund the time it had left.

When Premium ends, any block set to run longer than the free limit of 3 days ends 3 days later. We email you when Premium ends. If your accountability email belongs to someone else, they get one short email when those blocks end; it names your account and the dates. We keep a note that each of these emails was sent, so none is sent twice.

7. Who processes data on our behalf

We use a small number of service providers strictly to run the features above:

We do not sell or rent your personal information. The app contains no advertising and no third-party analytics or tracking SDKs of any kind. (This website is a separate thing — see Section 12.)

8. Data retention

9. Security

On-device data is stored in an encrypted database (SQLCipher). Data sent to our server is transmitted over HTTPS. Our server keeps only a hash of each phone’s sign-in key, never the key itself. Our server’s own keys, for sending email and for checking purchases with Google Play, are held only in our hosting provider’s secret store and are never included in the app.

10. Your choices and rights

11. Children’s privacy

SelfGuard is intended for adults aged 18 and over and is not directed to children. It is not designed for, marketed to, or intended for use by anyone under 18, and we do not knowingly collect personal information from children. If you believe a child has provided us data, contact us and we will delete it.

12. This website

This page and the rest of selfguardapp.com are hosted on Cloudflare, which serves the site and processes standard request data such as your IP address. The site also uses Cloudflare Web Analytics to count page views. It uses no cookies, does not fingerprint your browser, and does not track you across other websites — it records aggregate information such as page, referrer, country and device type.

This applies to the website only. The Android app itself contains no analytics or tracking of any kind (Section 7).

13. Changes to this policy

We may update this policy as the app evolves. Material changes will be reflected here with a new “Last updated” date. Continued use after an update means you accept the revised policy.

14. Contact

Questions or requests about privacy: privacy@selfguardapp.com.