The invisible SDK layer
An SDK may automatically send device identifiers, IP address, approximate location, events, crash records or advertising IDs. Teams that inspect only their own API calls miss this layer.
Google explicitly holds developers responsible for embedded code. Apple likewise states that responsibility covers SDKs, libraries and other third-party code.
Every SDK update can reopen the risk
A vendor can change endpoints, data types or defaults in a new release. A minor dependency update may therefore change Data Safety, Privacy Labels, notices and consent.
Versions with critical or policy issues can block releases. Treat the dependency list as a living privacy and security inventory.
Four evidence layers
Package analysis shows what code exists; traffic analysis shows what leaves the device; configuration review shows what is enabled; user-flow review shows when notice and consent occur. Missing one layer turns the conclusion into guesswork.
- Dependency and version inventory
- Network record by domain and data type
- Default and remote configuration
- Before/after consent comparison
Less data means less operational risk
Remove unused SDKs, disable unnecessary collection by default and send only events needed for the feature. Data minimisation reduces attack surface, declaration complexity and performance cost.
Have unused SDKs been removed?
Are data and transfer destinations known?
Is consent applied before SDK initialisation?
Do version changes trigger a privacy review?
Is Firebase automatically non-compliant?
No. Risk depends on modules, configuration, purposes, region and the notice/consent flow.
Is the vendor's privacy policy enough?
No. Your product must explain its own use and reflect it in store declarations.
Official sources and references
This is general technical information, not legal advice. Obtain advice from a qualified legal professional for your specific circumstances.

