Skip to Content
Platform.Ontology

Uninstall detection through push failures

Servers learn an app was removed when the push provider reports the token as invalid.

Used to track youNotifications and backgroundAfter uninstallAndroid and iPhoneAfter you uninstall

In one line

Can find out the app was removed, but only after hours or days

Servers learn an app was removed when the push provider reports the token as invalid.

A company can tell, days later, which people deleted the app and then retarget them in ads or email. No on-device code runs after uninstall; the signal is the push service reply.

What it can and can't do

What the user does: Nothing. The app's server learns it when a push fails

It can

  • Learn the app was removed when the push service says the token is invalid
  • Stop sending messages to that device
  • Mark you as inactive in its records

It cannot

  • Know right away; Android can take hours to days
  • Get a direct feedback service from Apple, which was retired in 2021
  • Learn anything about the phone after you remove it

How it differs between platforms: On iPhone, Apple returns a 410 error after removal. On Android, the delay depends on Google Play services.

On Android and iPhone

AndroidiPhone
StatusSupportedSupported
First versionAndroid 1.0iOS 3.0
Permission or entitlementNot listedNot listed
Protection levelnonenone
How access is grantednonenone
What the user seesNoneNone
How long it lastsVisible to the server days after removal; FCM returns UNREGISTERED or NOT_FOUND once a send failsAPNs returns 410 Unregistered with a timestamp once the token is invalid
How to take it backCannot be blockedCannot be blocked
Store policyNo Play rule forbids detecting churn; privacy policy must discloseApp Review 5.1.2: must disclose tracking
APIFCM HTTP v1 error codesAPNs reason codes 410 Unregistered, 400 BadDeviceToken
NotesDetection is not instant: the Play services connection must report the removal; typical delay hours to daysApple says a 410 is returned after the app is removed; the old feedback service was retired (2021)

Data you get

What comes back: Token invalidation
Shape: event
How often: On next send

FieldTypeUnitRangePrecision
fcm_errorenumNoneUNREGISTERED, NOT_FOUNDNot listed
apns_statusintegerHTTP410, 400Not listed

Technical limits

  • Only a server inference; no device event
  • Can be a false positive if the token rotated

The story

What it is

Companies can tell later that you deleted their app because their push messages stop working.

For you

You never notice. After you delete an app, the company may learn a day or more later that you left. You may then get email or ads trying to win you back.

For makers

Makers use it to measure churn and run win back campaigns. It is quiet, cheap and works because the push service tells the server the address is dead.

Where you see it

TypeExampleApps
analyticsA product team charts how many people deleted the app after each update.None named
adsA marketer sends a win back ad to someone who just uninstalled a shopping app.None named
gamesA game studio spots players who quit after level 5 and sends a come back offer by email.None named
shoppingA store sees an uninstall and moves you to an email only plan.Amazon
mediaA streaming service learns viewers left and tries a free month offer.None named
securityA bank sees that a registered phone no longer has the app and may flag the device as gone.None named
developerMeasurement tools like Firebase and AppsFlyer report uninstall counts to teams.Firebase, AppsFlyer

Risks

  • Retargeting after you leave
  • Hard to notice or stop

Android and iPhone in short

  • Android: Detection can lag hours to days because it relies on Play services.
  • iPhone: Apple returns an error code once the app is removed. The old feedback service was retired in 2021.

Good uses and abuse

Legitimate uses

  • Churn analytics
  • Win back

Known abuse

  • Retargeting people who deleted the app

Scores

ScoreValueMeaning
Sensitivity3 of 5How revealing the data is
Utility4 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

History

  • 2021-03, iPhone APNs: Binary Feedback Service retired; 410 responses are the signal
  • 2024-07, Android FCM: Legacy API errors replaced by HTTP v1 error codes

Sources

How well checked: Based on official documentation.

On this page