Push token registration (FCM token, APNs device token)
Gets an address that lets a server reach this app install, even when the app is closed.
In one line
Can get an address so its server can reach your app, even when closed
Gets an address that lets a server reach this app install, even when the app is closed.
The token ties one install to a server-side profile and lets the company wake or message the person at any time. It rotates on reinstall, restore or data clear, so servers use it to detect churn.
What it can and can't do
What the user does: Nothing. It happens when the app opens and registers for push
It can
- Get a unique token for this install of the app
- Send that token to its server
- Receive silent pushes on iPhone even if you said no to alerts
It cannot
- Show alerts on Android 13 or newer without your permission
- Show alerts on iPhone if you refused the alert prompt
- Learn who you are from the token alone
How it differs between platforms: iPhone gives a token even if you deny alerts. Android 13 and newer asks before visible notifications.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Supported |
| First version | Android 1.0 (API 1) | iOS 3.0 |
| Permission or entitlement | INTERNET (normal); POST_NOTIFICATIONS (API 33) only for visible alerts | aps-environment entitlement (Push Notifications capability) |
| Protection level | normal | entitlement |
| How access is granted | install | entitlement |
| What the user sees | None for the token; Android 13+ prompt for visible notifications | None for the token; alert permission is a separate prompt |
| How long it lasts | FCM token rotates on app restore to a new device, uninstall and reinstall, data clear, or token refresh; stale after 1 month idle, expired after 270 days | Token changes on reinstall, restore to a new device, or OS reinstall; Apple says do not assume a fixed length (32 bytes in practice) |
| How to take it back | Settings > Apps > Notifications; Force stop; uninstall | Settings > Notifications; uninstall |
| Store policy | Google Play: FCM is the supported route for non-China devices | App Review 4.5.4: push must not be required for the app to function; no spam |
| API | FirebaseMessaging.getToken(), FirebaseMessagingService.onNewToken() | UIApplication.registerForRemoteNotifications(), didRegisterForRemoteNotificationsWithDeviceToken |
| Notes | GCM was replaced by FCM in 2016; Play services delivers messages over one shared connection | Token is issued even when the person denies alerts, so silent pushes can still arrive |
Data you get
What comes back: Opaque device or install token
Shape: string
How often: On rotation events
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
fcm_token | string | chars | about 160 to 200 | random |
apns_token | binary | binary | 32 typical | random |
Technical limits
- Token is per install, not per person or device
- Delivery still needs a visible-notification grant to show anything on Android 13+ and iOS
The story
What it is
A secret address that lets a company's server send messages to one app install.
For you
You never see it. When you first open an app, it quietly gets this address, even if you say no to alerts. That address lets the company reach your phone and recognize this install.
For makers
Makers store the token with your account so they can message you at any time. A new token after a reinstall also tells them someone left and came back, which feeds churn and ad measurement.
Where you see it
| Type | Example | Apps |
|---|---|---|
| messaging | A chat app uses your token to send a message alert to the right phone. | |
| games | A game ties the token to your player profile so it can ring you when a friend plays. | Clash Royale |
| shopping | A retailer links your token to your cart so it can send an abandoned cart reminder. | Amazon |
| ads | An ad company links tokens across apps in the same family to see the same device. | None named |
| analytics | A product team counts new tokens to measure reinstalls and lapsed users. | None named |
| security | A bank uses a token to push a login approval to the registered phone. | None named |
| live | A sports app sends goal alerts to every device that follows the team. | ESPN |
Risks
- Links one install to a profile
- Can be shared or traded
Android and iPhone in short
- Android: Android 13 and up asks for permission only for visible alerts. The token itself is silent.
- iPhone: iOS gives a token even if you deny alerts, so silent pushes can still arrive.
What the platform says
- Google: Manage FCM tokens. Google tells developers to keep device tokens fresh so messages reach each install.
- Apple: Registering with APNs. Apple describes how an app asks for a device token to receive remote notifications.
Good uses and abuse
Legitimate uses
- Re-engagement
- Alerts
Known abuse
- Cross-linking installs through a shared token store
- Spam
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 5 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
- 2016-05, Android Firebase Cloud Messaging: FCM announced as the successor to GCM
- 2019-04, Android Play services: GCM server APIs shut down; FCM only
- 2019-09, iPhone iOS 13: Device token description format changed; apps must read the raw Data bytes
- 2024-07, Android FCM: Legacy FCM HTTP and XMPP APIs begin shutting down; HTTP v1 required
Related capabilities
Related
- FCM message delivery: payload, TTL, collapse. Can send alerts to an Android phone through Google, up to 4 KB per message
- APNs delivery: payload, priority, expiration, collapse. Can send alerts to an iPhone through Apple, up to 4 KB of data per message
- Uninstall detection through push failures. Can find out the app was removed, but only after hours or days
Same idea on the web
- Push API (Web Push). Can send you notifications after you leave, once you allow them
Sources
How well checked: Based on official documentation.