Skip to Content
Platform.Ontology

SDK signatures and the Play SDK Index

Apple requires signed copies of popular SDKs, and Google publishes data practices for listed SDKs.

Works without askingOther apps on the phoneStore transparencyAndroid and iPhone

In one line

Can check that popular add on tools were not changed, and show what they collect

Apple requires signed copies of popular SDKs, and Google publishes data practices for listed SDKs.

Cuts supply chain tampering and puts SDK data use on public record. Apple's list includes common ad and analytics SDKs. Google's SDK Index shows permissions and Data safety info per SDK.

What it can and can't do

What the user does: Nothing. It is checked when the app is built and uploaded

It can

  • Prove a popular tool came from its maker, on iPhone
  • Show what permissions and data each tool uses, on Google's SDK Index
  • Show the developer's own data notes on each tool

It cannot

  • Stop a tool from collecting data the app already can
  • Check every tool, since the list covers common ones
  • Change what you see in the app

How it differs between platforms: Apple requires signed copies of popular tools. Google publishes tool data practices in the SDK Index.

On Android and iPhone

AndroidiPhone
StatusSupportedSupported
First versionNot availableiOS 17.5
Permission or entitlementNot listedNot listed
Protection levelnonenone
How access is grantednonenone
What the user seesNot listedNot listed
How long it lastsNot listedNot listed
How to take it backNot listedNot listed
Store policyPlay SDK Index lists SDK versions and warnings; non-compliant SDK versions can block releasesSignature required for listed third party SDKs added as binaries from 1 May 2024
APIplay.google.com/sdks; Play Console SDK warningsXcode code signing, privacy report
NotesNoneNone

Data you get

What comes back: n/a
Shape: none
How often: n/a

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

Technical limits

  • Lists change over time
  • Does not stop exfiltration at runtime

The story

What it is

Rules that make popular code libraries signed and public about what data they use.

For you

You are safer without noticing. The tools that apps use to show ads and measure use are checked and listed, so fewer rogue code libraries can slip in.

For makers

Makers cannot just paste in any SDK. They pick from signed, documented ones, and the public record lets reporters and regulators see which SDKs read what.

Where you see it

TypeExampleApps
adsAn ad network ships a signed SDK with a manifest so game studios can add it without store trouble.AppLovin, Unity
analyticsA product team checks the SDK Index to see which permissions an analytics tool adds.Firebase, Mixpanel
socialA login SDK is signed so a copy edited by an attacker would fail the check.Facebook Login
gamesA game studio swaps an SDK flagged in the index for a safer one before launch.None named
securitySecurity teams use signatures to prove no one changed the code between release and install.None named
developerA developer reads the SDK Index warnings when picking a crash reporting tool.Sentry, Crashlytics

Risks

  • Only covers listed SDKs
  • Signatures prove source not intent

Android and iPhone in short

  • Android: Google's Play SDK Index is public and shows permissions and known issues.
  • iPhone: Apple requires signed copies of the popular SDKs on its list.

What the platform says

Good uses and abuse

Legitimate uses

  • Integrity of SDKs

Known abuse

None listed.

Scores

ScoreValueMeaning
Sensitivity2 of 5How revealing the data is
Utility3 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

  • 2021-10, Android Play: SDK Index launched
  • 2024-05, iPhone App Store: SDK signature requirement

Sources

How well checked: Based on official documentation.

On this page