Why can’t the guest profile have a Private Space?

gos-users

Hey everyone,

On GOS, regular user profiles are allowed to have a Private Space (unlike on Stock OS for Pixel, if I’m not mistaken).

But why can’t the guest profile have one too?
Technically, isn’t the guest profile just another user profile under the hood?

Personally, I only use the guest profile.
My owner profile stays clean — no apps configured, nothing stored.
All my apps and configurations live inside the guest profile.

That way, when the phone reboots, everything in the guest profile is wiped,
and I simply create a new guest profile, restore my data, and I’m good to go :)

By doing this, I also stay compliant with the law — I can safely share my password if needed.
I just have to wait for the auto-reboot (set to 18 hours by default) before doing so.

I use Molly as a slave device (with the master running on Signal-CLI).

The only thing that really bothers me is not being able to use Private Space within the guest profile —
it would be great to have it, so I could run certain apps twice inside the same environment.

I also feel like the guest profile is kind of the “forgotten feature” —
but in reality, it might actually be one of the strongest security setups if used properly :)

GrouchyGrape

gos-users may I ask how you're restoring data to the guest profile? What apps you're using in there? Just curious as I find this setup interesting.

mmobder

gos-users Is it the same fort work profile (Shelter etc) within guest?

gos-users

I’m using an encrypted cloud setup with Cryptomator to restore data to the guest profile.
For messaging, I use Molly as a slave device connected to a master device running Signal-CLI on a Linux distribution that operates entirely in RAM-only mode.

Here’s roughly how I manage the Signal devices:

List linked devices

signal-cli -u +XXX listDevices

Remove an old device

signal-cli -u +XXX removeDevice -d X

Add a new one (QR scanned via zbarcam)

signal-cli -u +XXX addDevice --uri ""

Because everything runs entirely in RAM, all guest profile data are erased on reboot. My main Signal instance also operates in RAM, allowing me to leverage the guest profile reset for additional security
This means I can always provide my password if legally required, yet no persistent data remains once the system powers off — same setup on my PC.

In some countries, refusing to decrypt your device can actually result in criminal penalties (for example the UK under the RIPA Act, France under the Code de procédure pénale, and Australia under the Assistance and Access Act).

So, for me, having everything RAM-only with a passphrase-encrypted ephemeral guest profile is the best of both worlds — belt and suspenders security :)

Kibi

Would love this. Guest mode deserves more love, feels like it doesn't get nearly the attention it needs and deserves. Thread Bump since question still standing.

jdoe

@GrapheneOS can you confirm there are no forensic traces left by Guest profiles? Leveraging Guest profiles to spawn amnesic sessions sounds really good. If this could be automated by GrapheneOS to create Guest profiles from simple xml files containing various settings and apps to install would be HUGE!

graphenemuffin

@jdoe Mmm I just opened a thread about this here https://discuss.grapheneos.org/d/28370-does-rebooting-andor-removing-a-guest-profile-erase-all-traces-of-it, I'd love to know too