Parental controls - giving kids a GrapheneOS phone?

Id really prefer my kids to not have a stock Android phone. Id sooner do iOS, but I don’t wanna encourage them to get into an ecosystem straight away.

I’m thinking GrapheneOS.

Set up a separate user profile and turn off their ability to install their own apps. That way nothing gets installed without my knowing.

Obviously they can access anything through the browser really anyway. But it’s less convenient and I think would discourage them.

Ideally I would take their phones off them at night. If they want a podcast they can pre arrange downloading the file and playing it on an mp3 player.

Are there any other measures I can implement on GOS? I don’t want to shelter them too much but at the same time I don’t want them doomscrolling until 2am.

There really isn’t. Not really anything that would really work and not be removable.

I would not recommend GrapheneOS for parental control. There is no such setting in AOSP, you would be better served on stock android to limit your kids screen time and app installs.

This will not work, every time you power up the phone you need to unlock the owner profile.

Fair enough.. but at that point I feel like id be better off with iOS.

These days I don’t see the point of Android. GrapheneOS is just so much better

1 Like

Fair enough but I personally don’t see a meaningful difference with iOS besides the Apple walled garden.
Android 17 security is very good.

1 Like

Maybe Murena and FairPhone have some solutions ? I know they aren’t the best security wise but still.

If they know the password to the secondary profile, they can create a private space which has a browser. If you’re giving browser access, it’s a lost cause. You can remove the browser from that user profile using ADB, it’s quite simple commands than an AI can guide you through. You could give them just fingerprint and optionally 2nd factor pin as secondary unlock, and don’t tell them the password for the primary unlock and maybe create the private space initially with the primary unlock so they can’t use it.

It’s quite a complicated setup but it would prevent installing new apps without owner password and prevent web browsing.

I don’t see a huge reason why they should get web browsing as a dumb phone doesn’t have it and those work fine. With this setup they would get the benefits of a phone like advanced mapping, Signal, excellent camera, with only apps you allow them to install and no web access. If any apps don’t follow android best practice and allow visiting any website within them, that’s a way to continue web browsing.

Once MDM[1] is added to GrapheneOS, that should be a much simpler solution.

If they aren’t technical enough to figure out the private space method, then it is a lot simpler and that’s the only bypass I know of within the user profile. You’d still have to keep them out of the owner profile and unlock it before use after a restart or turn off.

iPhones are really great options for removing browser and app store because of apple configurator (mac needed). Here’s a post explaining it. That’s what i would recommend. Do not rely on screen time, though. It is not effective at preventing bypasses, but I heard it’s getting updated soon so time will tell.


  1. TLDR: It’s not been added yet and a experienced community member estimates it is 35% done. MDM would allow you to retain recommended security practices, like not using ADB, while effectively restricting private spaces, apps, and browsers. ↩︎