Android’s Private Space can look like a hidden folder for apps, but that mental model is too simple. Private Space is a separate profile with its own app instances, accounts, storage behavior, lock state, and important limitations around notifications, backups, VPNs, sharing, and background activity.
If you treat it like a cosmetic hiding feature, the behavior can feel broken. A messaging app may stop notifying while the space is locked. An app installed in both places can show different accounts and data. A device backup may restore the main app but not its Private Space copy. A phone-wide VPN may not protect the Private Space app at all.
Private Space is more than hiding an icon
Android designed Private Space to isolate sensitive apps and content from the main profile.
When locked, the space can be hidden from the launcher and other system surfaces. Apps inside it are not simply invisible—they are stopped.
Google’s Android Help documentation says locked Private Space apps cannot perform foreground or background activities, including showing notifications.
Installing the same app creates a second instance
If an app already exists in your main profile and you choose “Install app in Private Space,” Android installs a new instance inside the private profile.
Google explicitly notes that the previous instance is not copied or modified.
That means the new instance can have:
- a different signed-in account;
- different local files;
- different permissions;
- different notification settings;
- different app data;
- a separate update state in some situations.
Your main-profile login does not automatically follow
Private Space does not automatically read the accounts from your main profile.
If you install a banking, chat, browser, or cloud app inside Private Space, you may need to sign in again.
This is expected separation, not failed migration.
Why notifications disappear when you lock Private Space
When Private Space locks, Android completely stops its apps.
That means a chat app inside the space cannot keep running in the background to receive and show messages. A health app cannot continue sensor tracking. A reminder app cannot behave like an always-available main-profile app.
This is a critical design trade-off: stronger hiding and isolation versus continuous background behavior.
Do not put a critical alert app there unless you understand the trade-off
Private Space is a poor fit for apps that must remain active while the space is locked.
Examples include:
- medical monitoring;
- alarm or emergency apps;
- real-time business messaging;
- authentication tools you need constantly;
- automation apps that must react in the background.
Google’s own documentation warns against using Private Space for apps that need background functionality while the space is locked.
Private Space app data is not part of ordinary device backup
This is one of the most important limitations.
Google says Private Space app data cannot be backed up and restored as part of device backup. If you delete Private Space, local app data inside it is deleted without a device-backup copy.
Cloud-synced data may return after you sign in again, but local-only data can be gone.
APKApps.cloud’s Android backup guide explains why “the app was backed up” does not guarantee every local database or file will return.
Private Space itself does not restore from a normal phone backup
If you migrate to a new Android phone, do not assume Private Space reappears with all of its apps and state.
The main device backup and the private profile are intentionally separate.
Before changing phones, identify any Private Space app that stores important local-only content and export it through that app’s own supported method if one exists.
Private Space apps bypass the device VPN
This is an unusual and easy-to-miss behavior.
Google’s Android Help page explicitly states that Private Space apps bypass the virtual private network configured on the device.
So if you rely on a device-wide VPN for routing or privacy, do not assume the Private Space instance uses the same tunnel.
Why the VPN difference matters
Suppose your main profile uses a VPN for work, DNS filtering, travel, or network privacy.
You install a browser inside Private Space and assume it inherits the same network path. According to Google’s current documentation, it does not.
That can change:
- public IP address;
- DNS path;
- geo-location behavior;
- access to internal work services;
- filtering provided by the main-profile VPN.
This is different from a Work Profile VPN
Work Profiles have their own enterprise networking model. A VPN can be configured specifically for work apps while personal apps remain outside it.
Private Space is not a work profile and does not behave like one.
This distinction becomes important on phones using both personal management features and enterprise management.
Private Space can use a different Google Account
Google recommends using a dedicated account in Private Space when stronger separation is the goal.
If you sign in with the same Google Account used in the main profile, some synchronized information can appear outside the space through normal account sync: photos, contacts, email, browsing history, saved passwords, app history, and recommendations.
The profile boundary cannot prevent cloud sync from connecting the same account to itself.
A hidden app can still leave cloud traces
Private Space hides local app presence from many everyday device surfaces while locked.
It does not make your online accounts forget what you did.
If the same account syncs browsing history, files, photos, or messages to the cloud, those records can appear on another device or in the main profile through the same service.
Private Space is not invisible to advanced device inspection
Google warns that Private Space can be uncovered through computer access, including ADB commands, device logs, or apps.
That means it is a privacy and separation feature, not a forensic invisibility system.
Do not use it under the assumption that no one with technical access to the device can determine that it exists.
Why sharing behaves differently
When Private Space is unlocked, Android can expose a “Private” tab in sharing surfaces such as the system share sheet, document picker, and photo picker.
When it is locked, that private profile disappears from those normal sharing surfaces.
This is consistent with the security model: locked means stopped and hidden, not merely password-protected while still participating everywhere.
Quick Share and Bluetooth have limits
Google documents several sharing limitations, including no direct Quick Share receive path into Private Space.
Bluetooth behavior is also asymmetric: content can be sent from Private Space apps in supported scenarios, but receiving directly into the private profile is limited.
If a file “cannot find” the Private Space app as a destination, that may be by design.
Why widgets and home-screen shortcuts are unavailable
Private Space does not support adding its apps’ widgets and shortcuts to the normal home screen.
A persistent widget would weaken the hiding boundary by exposing the app outside its profile.
If you depend on a calendar widget, task widget, smart-home widget, or note shortcut, keep the app in the main profile as well or choose a different privacy arrangement.
Private Space cannot host a Work Profile
Android does not let you create a Work Profile inside Private Space.
These are separate profile concepts with different management models.
If your employer requires Work Profile enrollment, set that up through the normal Android Enterprise flow, not inside Private Space.
Why Find Hub and smart-home features may not work there
Google lists several unsupported functions inside Private Space, including Find Hub and smart-home pairing/management.
These limitations follow the same pattern: services that need broad device-level integration do not always fit inside an isolated profile.
Worked example: WhatsApp in both profiles
You keep WhatsApp in the main profile and install another instance in Private Space.
The Private Space copy is a separate app instance. It can use a different account where the service supports that setup.
When you lock Private Space, that copy stops and its notifications disappear until you unlock it again.
Worked example: password manager disappears from autofill
You install a password manager only in Private Space and then lock the space.
The app is stopped and hidden from system surfaces. Expecting it to behave as an always-available autofill service conflicts with the locked-state model.
If you need the password manager throughout the phone, the main profile may be the more practical location.
Worked example: VPN-protected browser assumption
Your main profile uses a VPN. You install a browser inside Private Space and use it for sensitive browsing because you assume “the phone VPN covers everything.”
Google’s documentation says Private Space apps bypass the device VPN.
The privacy plan is therefore different from what you intended. Verify routing behavior instead of assuming the VPN icon applies across profiles.
Worked example: new phone migration
You back up your Android phone, buy a new device, and restore your main profile.
Main apps and supported app data return. Private Space does not restore as part of that normal backup.
If an app inside Private Space stored an offline database that was never synced or exported, that data may not be recoverable from the device backup.
How to decide whether an app belongs in Private Space
Private Space is a good fit when you want local separation and can tolerate the app stopping while locked.
Ask:
- Does this app need background notifications?
- Does it hold local-only data that needs backup?
- Does it need the device VPN?
- Does it rely on widgets, shortcuts, or smart-home integration?
- Do I want a separate account and app instance?
- Can I restore its data independently if the space is deleted?
Private Space is not the same as archiving an app
Archiving reduces storage use while preserving a path to reinstall the app. Private Space creates an isolated profile and another app instance.
Likewise, Private Space is not the same as hiding an icon with a launcher. The operating system changes app lifecycle and data boundaries.
The safest way to use it
- Use Private Space for apps that benefit from separation.
- Do not rely on it for critical background alerts.
- Use a separate Google Account if cloud separation matters.
- Back up important data inside each app using its own supported export or cloud sync.
- Do not assume the device VPN covers the space.
- Remember that deleting Private Space deletes its local app data.