If I add a second Google account or a second space, does the blocking still hold?

Accounts have nothing to do with the protection in the first place. Tabaa does not touch Google accounts and places no limit on adding, removing or switching them, so the number of accounts on the phone changes nothing. Second space and the work profile are a different matter: both are locked by default, and cloned apps and private space are locked as well on Android 15 and newer.

Does Device Owner let Tabaa read my messages?

The privilege is administrative: managing apps, the network and device policy. Tabaa runs no accessibility service that reads the screen and no notification-listener service, and it asks for no camera, microphone, SMS, contacts, photos or files. The reports show how long each app was used, where the device is, and which sites were blocked. Nothing else.

Does installing it need root or a modified system?

No. Device Owner is an official device-management mechanism built into Android itself. There is no root, no unlocked bootloader, no unofficial modification, and no effect on the warranty. Tabaa also installs no VPN on the phone and routes none of your traffic through a server of its own.

Why does it need a new phone or a factory reset?

That is Android's rule, not a choice Tabaa made: the privilege can only be granted while a device is clean, so that no app can ever seize it later on a phone in use without the owner knowing. Back your data up first and you will have everything important back after setup.

And if I want the whole thing gone one day?

Removal is possible, but only through a factory reset whose key sits with the supervisor you chose. The decision does not vanish; it moves to the person you yourself decided to trust with it, and once it is done the phone is completely ordinary again. Factory reset from recovery mode is deliberately left available, so no device can ever turn into a brick.

What is Device Owner, and why does it stop the blocker being deleted?

Published 27 August 2026 - last updated 27 August 2026

Device Owner is the highest administrative privilege in Android, granted to a single app once, during device setup. It is the same mechanism companies use to manage staff phones. It matters because it moves blocking from the account or the app down to the device itself: the operating system suspends disallowed apps, so no new account, second user or second space escapes the policy, and the person holding the phone cannot delete the app.

What Device Owner actually is

Android ships with an official device-management mechanism that lets one app be appointed the device administrator, or Device Owner, while the phone is being set up for the first time. It is the same mechanism large companies use to run their staff phones: the managing app can control apps, the network and device policy in ways no ordinary app can reach. Tabaa uses that same official mechanism. The purpose is not corporate administration but protection from explicit content and digital addiction, and it involves no hack, no root and no modification of the system.

The technical difference underneath is that nothing sits watching your screen trying to close whatever it recognises. The system itself suspends the app that is not allowed. So the block holds on any launcher your child installs, for any user on the phone, on Wi-Fi and on mobile data alike, with any SIM, and whether a Google account is signed in or not.

Blocking can sit at four different levels

Every protection tool is trying to do roughly the same thing, and the real difference between them is not the length of the blocklist. It is the level the block is enforced at, because that is what decides which gap opens first:

Account level. The protection hangs off an account, not a phone. Google Family Link is the example, and Google states plainly on its own support page that if you add other user profiles to the device, your child's Family Link settings will not apply to those profiles, and it advises the parent to put a screen lock on the other profile themselves to stop the switch.
App level. An app installed inside a single user profile, working through the accessibility service that reads what is on screen. Qustodio writes in its own help center that if the accessibility service is turned off, all monitoring stops and the device is left with unrestricted internet access. It also writes that multi-user and guest mode on Android may be used to bypass its protection, and advises the parent to disable multi-user in Android's settings by hand.
Network level. DNS filtering on a router or a network setting. It can refuse a domain name and nothing more: it cannot stop an app from opening and cannot cap a minute of screen time, and it ends the moment the phone switches to mobile data. The full argument is in why DNS blocking is not enough.
Device level. The policy is enforced by the operating system across the whole phone. There is no account to leave, no user profile to hide inside, and no accessibility switch to flip off. This is where Tabaa sits.

What changes in practice when the policy sits on the device

Situation	Protection tied to an account or an app	Tabaa with Device Owner
Adding a second user, a second space or a cloned app	Out of scope: the settings are bound to one account or one user profile	Locked by default: adding and switching users blocked, work profile blocked, cloning and private space blocked on Android 15 and newer
Adding a new Google account, or signing out	Ends supervision that hangs off the account	Changes nothing: Tabaa does not touch accounts, and you can add as many as you like
Deleting the blocker itself	Possible: turn off the device administrator privilege in settings, then uninstall. At most the partner gets a notification after the fact	Not available to the phone holder: the system itself removes the uninstall, force stop and clear data buttons
Permissions the app asks for	The accessibility service that reads the screen, and in many tools a local VPN on top	Neither one: enforcement comes from system policy
Cutting the phone off the internet	Depends on the tool	Blocking continues: the policy and any running focus lock are stored on the device, so neither needs a connection
Content inside a browser embedded in an app or a game	Usually tied to the browser	Covered: private DNS is pinned in the system settings and locked, so every query on the device passes through it

None of that is theoretical. Because enforcement comes from the system, the phone leaves setup already carrying working lists: 47 VPN, proxy, Tor and DNS-changer packages refused in every mode, suspended even when they came preinstalled on the device. The default blocklist holds 32 apps, 11 of them unofficial Telegram forks, because blocking the official app alone is worthless while a modified copy of it keeps running.

How the privilege is granted

Once, and specifically during setup: Android will only appoint a Device Owner while the device is clean, meaning a new phone opening for the first time or a phone that has just been factory reset. With Tabaa that happens by scanning a QR code from the installation page at the welcome screen. Because a factory reset wipes the phone, that page carries a backup checklist first, and there is a full step-by-step guide: how to back up before installing Tabaa. The condition comes from Android, not from us, and it is in fact the source of the protection's strength: the reason no app can quietly take this privilege on a phone in use is the same reason you cannot strip it off with a tap.

And why does that stop the blocker being deleted?

Because Android treats the managing app as part of the administration of the device itself: uninstall, disable, force stop and clear data are not offered to the person holding the phone. Blocking also survives a reboot, and comes back if the system kills the service, because an exact alarm and a background task restart it. It keeps working with the phone fully offline, because the policy and any running focus lock live on the device. The honest wording matters here: removing the system is possible, but only through a factory reset whose key is held by the supervisor. The decision still exists, it simply sits with the person you chose and trusted, and that is the whole accountability model we set out in asking a friend to supervise your phone.

And because enforcement comes from the system rather than from an app chasing the screen, the speed is different in kind. A blocked app closes within about a third of a second of being opened. Any change the supervisor makes from the supervisor app reaches the phone in roughly 3 seconds, and instantly when the silent push arrives. The same privilege lets Tabaa update itself on the phone with no store and no step from the user, so an improvement to the blocking reaches every device the same day.

The honest limits of the privilege

DNS filtering needs Android 9 or newer, because the private DNS setting simply does not exist in the system before that. The app installs from Android 8, but on 8.x there is no device-level content filtering, and the supervisor is told so.
The locks on cloned apps and private space are restrictions that exist in Android 15 and newer. On older versions, second space is covered by blocking the adding and switching of users.
Filtering works at the DNS level, so an app carrying its own encrypted DNS resolver inside its code can route around it. That is exactly why VPN, proxy and DNS-changer apps are blocked as a list, and why the VPN setting itself is locked. We say this plainly rather than using the word impossible.
Factory reset from recovery mode is deliberately left available, so no device can turn into a brick. What is prevented is deletion in the normal use of the phone, not deletion absolutely and without exception.

Is this the core difference between Tabaa and the rest?

Largely, yes, because it is the difference every other difference is built on. Foreign accountability apps such as Ever Accountable are strong at reporting to a partner, but they depend on Android's accessibility service, and that is documented on their own site. The accessibility service is a permission switched on and off in Android's settings, which means its key sits on the very phone it is meant to protect. BlockerX publishes the removal path itself, step by step, in its FAQ: settings, then security, then device administrators. Its Play Store description says that deleting the app sends a notification to the accountability partner, which is a report after the event rather than prevention of it.

Google Family Link is free and genuinely good for young children's accounts, and Google backs it with human support on a published phone number. But its supervision hangs off a Google account rather than the device, and in Google's own words the Family Link settings for a child's account do not apply to any other user profile added to the same phone. One more piece of fairness to a competitor: Bark sells a phone of its own with its controls installed at the factory, and that is real device-level enforcement. It just requires buying their handset, and it is sold in the American market, whereas Tabaa gives the same level of enforcement on the phone the family already owns.

The head-to-head comparisons are in Tabaa versus Ever Accountable, Tabaa versus Google Family Link and Tabaa versus BlockerX, and the full picture is in the best Arabic porn blocker for adults. All the prices are on the pricing page.

Common questions

If I add a second Google account or a second space, does the blocking still hold?: Accounts have nothing to do with the protection in the first place. Tabaa does not touch Google accounts and places no limit on adding, removing or switching them, so the number of accounts on the phone changes nothing. Second space and the work profile are a different matter: both are locked by default, and cloned apps and private space are locked as well on Android 15 and newer.
Does Device Owner let Tabaa read my messages?: The privilege is administrative: managing apps, the network and device policy. Tabaa runs no accessibility service that reads the screen and no notification-listener service, and it asks for no camera, microphone, SMS, contacts, photos or files. The reports show how long each app was used, where the device is, and which sites were blocked. Nothing else.
Does installing it need root or a modified system?: No. Device Owner is an official device-management mechanism built into Android itself. There is no root, no unlocked bootloader, no unofficial modification, and no effect on the warranty. Tabaa also installs no VPN on the phone and routes none of your traffic through a server of its own.
Why does it need a new phone or a factory reset?: That is Android's rule, not a choice Tabaa made: the privilege can only be granted while a device is clean, so that no app can ever seize it later on a phone in use without the owner knowing. Back your data up first and you will have everything important back after setup.
And if I want the whole thing gone one day?: Removal is possible, but only through a factory reset whose key sits with the supervisor you chose. The decision does not vanish; it moves to the person you yourself decided to trust with it, and once it is done the phone is completely ordinary again. Factory reset from recovery mode is deliberately left available, so no device can ever turn into a brick.