Shared Keychain access groups and app groups
Apps from one developer team can share secrets and files; other developers cannot join.
In one line
Can share saved secrets and files between apps from the same developer on iPhone
Apps from one developer team can share secrets and files; other developers cannot join.
Lets one company recognize the same person across its own apps. It cannot see another company's keychain items.
What it can and can't do
What the user does: Nothing. The developer sets this up before the app ships
It can
- Share a login or token between apps from one Apple developer team
- Share files and settings through an app group folder
- Keep sign in working across a family of apps from the same maker
- Share on Android only between apps signed with the same key
It cannot
- Let apps from other developers join the group
- Share across teams; the group name starts with the team prefix
- Use sharedUserId on new Android apps; it was deprecated in Android 10
- Share on Android with no setup; it needs matching signing keys and a provider
How it differs between platforms: iPhone has built in groups. Android has no direct match and uses same signature sharing.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Partial | Supported |
| First version | Not available | Not available |
| Permission or entitlement | Not listed | keychain-access-groups, com.apple.security.application-groups |
| Protection level | signature | entitlement |
| How access is granted | none | entitlement |
| What the user sees | Not listed | Not listed |
| How long it lasts | Not listed | Not listed |
| How to take it back | Not listed | Not listed |
| Store policy | None listed | None listed |
| API | android:sharedUserId (deprecated API 29), signature permissions, shared content providers | Keychain access groups, App Groups containers, UserDefaults(suiteName:) |
| Notes | No direct match. Same signing key apps can share through providers. | Group IDs start with team prefix (keychain) or group. (app groups). Same Apple Developer team only. |
Data you get
What comes back: Shared container or keychain item
Shape: object
How often: persistent
No individual data fields. The signal is the access itself.
Technical limits
- Same team only
- Requires entitlement
The story
What it is
Lets apps from one company on the same phone share passwords, tokens and files.
For you
You sign in once and your other apps from the same company already know you. The upside is smooth use. The downside is that one company can link all of its apps to you without asking.
For makers
Makers use it for single sign on, shared settings and shared downloads between their own apps. Other companies cannot join the group, so it is a safe lane between a developer's own apps.
Where you see it
| Type | Example | Apps |
|---|---|---|
| productivity | You sign in to a mail app and its calendar app from the same company opens already signed in. | None named |
| games | A studio shares your save file between its main game and a companion app. | None named |
| banking | A bank shares a secure login token between its main app and a small widget app. | None named |
| media | A music app shares downloaded songs with its car and watch helper apps. | None named |
| enterprise | A company shares one login across its work apps so staff sign in once. | None named |
| analytics | A developer uses a shared ID to see that one person uses three of its apps. | None named |
Risks
- Links your apps without asking
- Cannot be reviewed easily
Android and iPhone in short
- Android: Android uses shared user IDs and signing keys for a similar feature, now rarely allowed.
- iPhone: Needs an Apple entitlement and the same developer team, with no prompt to you.
What the platform says
- Apple: App Groups. Developer guide: let apps from the same team share containers and data on one device.
Good uses and abuse
Legitimate uses
- Single sign-in across a suite
- Widgets and extensions sharing data
Known abuse
- Cross-app ID inside a brand's family of apps
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 1 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2019-09, Android Android 10 (API 29): sharedUserId deprecated
Related capabilities
Related
- Keychain and Block Store persistence across reinstall. Can recognize you after a reinstall using an ID that stays behind on your phone
- IDFV and App Set ID (developer-scoped IDs). Can recognise your phone across one company's apps, but not other companies' apps
Sources
How well checked: Based on official documentation.