Third-party SDK due diligence: its behavior is your signature
On both stores the SDK's crashes, permissions and data collection are your problem. The five checks before adding one, and the living inventory that answers 'are we affected?'
Every SDK you embed ships inside your app, with your signing key, in your users' pockets - and on both stores, its behavior is legally and practically your problem. A crashed analytics SDK is your crash rate; its data collection is your privacy declaration; its permissions are your permission prompts. SDK due diligence is the discipline of knowing what you are actually shipping, and it takes an afternoon per SDK, not a quarter.
Why the stores make it your responsibility
Google Play's Data safety section is explicit: developers are required to disclose their apps' privacy and security practices via the Play Console form, the declarations appear on the store listing, and you alone are responsible for making them complete and accurate - Google does not determine on your behalf how your app, including its SDKs, handles user data. Apple applies the same logic to its privacy labels and its required reason APIs and privacy manifests: the app owner answers for everything in the binary. "The SDK does that, not us" is not a defense either store accepts.
The five checks before adding an SDK
- Size cost. Measure what it adds to your artifact - the APK Analyzer or App Thinning report shows the number in minutes. An SDK that adds megabytes for a feature you use at 5% is a product decision to make with open eyes.
- Data practices, from the horse's mouth. Read the vendor's data safety and privacy documentation, not the marketing page: what data is collected, where it goes, whether it is linked to identity, and whether it feeds advertising. This is the input to your Data safety form and privacy labels, and you sign those.
- Permissions and APIs. What runtime permissions does it require, and does it touch Apple's required reason APIs (which require declared reasons in the privacy manifest)? Each permission it needs becomes a prompt your UX owns.
- Maintenance signals. Release cadence, issue-tracker responsiveness, minimum-OS policy and the vendor's own store compliance history. An unmaintained SDK is a future emergency migration.
- Exit cost. What breaks if you remove it? SDKs that entangle themselves in your data model or UI are sticky; wrapping third-party calls behind your own interface keeps the exit open.
Keep the inventory alive
Due diligence is not a one-time gate. Keep a living SDK inventory - name, version, purpose, data collected, owner - and review it on a cadence: quarterly works for most teams. Play now offers the Google Play SDK Index to help evaluate SDKs, and both stores keep tightening SDK rules, so an SDK that was fine at adoption can become a compliance task later. The inventory turns "are we affected?" from an archaeology project into a lookup.
The two failure modes
Teams usually fail at the extremes: either no gate at all (anyone adds any SDK in a pull request) or a committee that says no to everything and gets routed around. The working middle is a one-page checklist, a named owner, and a rule that the Data safety form and privacy manifest get updated in the same pull request that adds the SDK. Boring, enforceable, and exactly what the stores assume you are doing.
Sources
Prepared with AI assistance and reviewed before publication. Data safety responsibility language is paraphrased from Google's Play Console Help checked on 19 November 2026; the five-check framework is editorial practice.