Skip to Content
Platform.Ontology

SDK Runtime (privacy sandbox)

Would have run ad SDKs in their own process so they could not read the host app's data.

Used to track youAds and install trackingAndroid Privacy SandboxAndroid and iPhoneWhile you use itIn the background

In one line

Can't run ad tools in a separate box on Android, since Google retired it

Would have run ad SDKs in their own process so they could not read the host app's data.

Isolation of third-party SDKs from host app memory and identifiers. Never reached general availability; retired in the Oct 2025 announcement.

What it can and can't do

What the user does: Nothing. It was a background feature that never reached wide release

It can

  • Have kept ad tools away from the app's data (Android 14, never released widely)
  • Have limited what ad tools could see
  • Fall back to the plain model, where tools share the app's access

It cannot

  • Run on iPhone; it is not an Apple feature
  • Count on it, since Google announced its retirement on 17 Oct 2025
  • Isolate ad tools today

How it differs between platforms: Android only. iPhone never had it.

On Android and iPhone

AndroidiPhone
StatusRemovedNot supported
First versionAndroid 14 (API 34)Not available
Permission or entitlementNot listedNot listed
Protection levelnormalnone
How access is grantednot-exposednot-exposed
What the user seesNot listedNot listed
How long it lastsNot listedNot listed
How to take it backNot listedNot listed
Store policyPrivacy Sandbox status page lists as scheduled for phaseout (page updated Aug 2026)None listed
APISdkSandboxManagerNot listed
NotesGoogle announced on 17 Oct 2025 it is retiring this along with most Privacy Sandbox APIs. No Android removal date was stated in the announcement.Not an Apple feature.

Data you get

What comes back: Not available going forward
Shape: none
How often: n/a

No individual data fields. The signal is the access itself.

Technical limits

  • Retired: do not build new features on this
  • Ad ID stays the main cross-app identifier

The story

What it is

A plan to run ad code in its own sealed room so it cannot read the host app's data.

For you

You would not have noticed it. Ads would have loaded as before, but the ad code would have run in a separate process.

For makers

It would have kept ad code from reading the app's memory and IDs. It never reached general availability and was retired in the October 2025 announcement.

Where you see it

TypeExampleApps
adsAn ad SDK runs in a sealed process and cannot read the host app's user ID.Google AdMob
gamesA game studio would have been able to add an ad network without fear it reads saves.None named
newsA news app would have stopped a rogue ad from scraping reading data.None named
securityIsolating code lowers the harm from a hacked SDK.None named
analyticsAnalytics tools would have gotten only what the app handed them.None named
developerDevelopers tested the beta and found it hard to adapt popular SDKs.None named

Risks

  • Never launched
  • Complex to adopt

Android and iPhone in short

  • Android: Retired in October 2025 before reaching general availability.
  • iPhone: iOS has no equal. SDKs run inside the app's process.

What the platform says

  • Google: SDK Runtime. Android Privacy Sandbox plan to isolate ad SDKs from the app. Google retired it in October 2025.

Good uses and abuse

Legitimate uses

  • Was meant as an ID-free ad system

Known abuse

  • Low adoption

Scores

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

History

  • 2022-02, Android Android 13: SDK Runtime preview
  • 2025-10, Android Android 16: Retirement announced

Sources

How well checked: Checked against real behavior.

On this page