← All news and guides
Data protection

What Your App's Analytics and Ad SDKs Send: A DPDP Audit for Mobile Teams

Which analytics and ad SDKs in your app collect personal data, and how to audit them for DPDP: an inventory, traffic tests, consent gating and store forms.

Mono Team ·

A smartphone lying face down on a workbench beside a magnifying loupe and a loose tangle of thin cables, soft overhead daylight.

Short answer: audit your app's SDKs by building an inventory of every third-party library, then watching what each one sends over the network in four app states, and gating anything that needs consent until the user has given it. Analytics, crash, messaging, attribution and ad SDKs often start on app launch and send identifiers and event data to their vendors before your consent screen has appeared. Under the DPDP Act you are the Data Fiduciary for that data, and you must be able to prove notice and consent (Section 6(10)). So the audit has to find what leaves the device, match each flow to a purpose and a notice, and prove the result with captured traffic. The core DPDP duties start on 13 May 2027.

This is engineering guidance, not legal advice. Whether a given SDK flow needs consent or fits a Section 7 use is a question for your counsel. Here we cover how to find the flows, what the main vendors say they collect, and how to build the controls and evidence.

Why does DPDP care what your SDKs send?

Section 2(t) of the DPDP Act defines personal data as any data about an individual who is identifiable by or in relation to that data. A device or advertising identifier, tied to a profile, an account or a stream of events about one person, fits that wording on our reading. Edge cases go to counsel.

Three duties follow. Each lands on you, not on the SDK vendor.

  • You are responsible for processing done for you. Section 8(1) keeps the Data Fiduciary responsible for processing by a Data Processor on its behalf. Section 8(2) needs a valid contract with that processor. Section 8(5) covers safeguards.
  • You must prove notice and consent. Section 6(10) puts the burden on the fiduciary in any proceeding. Rule 3 asks for a standalone notice with an itemised description of the data, the purposes and the services.
  • There is no legitimate-interests basis. Section 4 allows consent or one of the closed list of Section 7 uses. Unlike GDPR, DPDP has no general legitimate-interests ground (see DPDP vs GDPR for SaaS). So "everyone uses this SDK" is not a basis.

The usual failure is simple. The notice says "to run the service", but the app also ships growth, attribution and ad SDKs that nobody listed. The audit finds that gap before a user, a customer's security team or the Board does.

What do the common mobile SDKs collect?

A tray of tiny mechanical watch parts laid out in neat separate rows on a green cutting mat, soft overhead light, shallow depth of field.

Below is what each vendor's own documentation says, checked on 20 November 2026. Vendors change defaults, so re-check the versions you ship. We could not read AppsFlyer's documentation, so we give no field list for it.

SDKWhat the vendor documentsHow to hold it back until consentOn Apple's manifest list?
Firebase Analytics (Google Analytics for Firebase)What the vendor documents: Creates an app-instance ID automatically. Collects the iOS IDFA only if available, otherwise the Vendor Identifier. Collects the Android Advertising ID by default.How to hold it back until consent: Set `FIREBASE_ANALYTICS_COLLECTION_ENABLED` to `NO` in Info.plist, then call `setAnalyticsCollectionEnabled(true)` after consent. Check Firebase's docs for the Android setting.On Apple's manifest list?: FirebaseCore, FirebaseInstallations and others, yes
Firebase Crashlytics and Cloud MessagingWhat the vendor documents: Crash and diagnostic data, and push registration. Read the current Firebase data disclosure for exact fields.How to hold it back until consent: Check the Firebase docs for the collection switch in your version.On Apple's manifest list?: FirebaseCrashlytics and FirebaseMessaging, yes
Meta (Facebook) SDKWhat the vendor documents: Logs app installs, app launches and in-app purchases automatically. Has a separate setting for advertiser ID collection.How to hold it back until consent: Set `FacebookAutoLogAppEventsEnabled` and `FacebookAdvertiserIDCollectionEnabled` to `NO` in Info.plist. Turn them on in code after consent.On Apple's manifest list?: FBSDKCoreKit, FBSDKLoginKit and FBAEMKit, yes
AppsFlyer and other attribution SDKsWhat the vendor documents: Typically collects device and advertising identifiers and install and event data. Check the vendor's current docs for the exact fields.How to hold it back until consent: Delay SDK start until consent, or use the vendor's documented opt-out or stop controls.On Apple's manifest list?: AppsFlyer is not on the list
Ad network SDKsWhat the vendor documents: Usually advertising IDs, device data and ad interaction events. Check each network.How to hold it back until consent: Do not initialise until consent. Never for child users.On Apple's manifest list?: Check the list per SDK

Two points about the last column. Apple requires a privacy manifest for the listed SDKs when you submit a new app that includes them, or an update that adds one. An SDK missing from the list, such as AppsFlyer, is not thereby low-collection. And a manifest shows what an SDK declares, not what it sends on your build.

How do you build an SDK inventory?

Start from the build, not from memory. A marketing manager's list of tools will miss the libraries a developer pulled in transitively.

  • iOS: read `Podfile.lock` or `Package.resolved`, plus any vendored frameworks in the project. Look at each framework's `PrivacyInfo.xcprivacy` if it has one.
  • Android: run the Gradle dependency report for your release variant and read the merged manifest, which shows every permission and meta-data entry that libraries add. Look for the advertising ID permission.
  • Cross-platform: list plugins in `pubspec.yaml`, `package.json` or the equivalent, and then the native libraries each plugin pulls in.
  • Webviews and server calls: list the scripts loaded in any in-app webview and the calls your backend makes to analytics or attribution vendors. They send the same user data by another route.

Then record each SDK in one row. Keep it in version control next to the code, because it will change with every release.

FieldWhat to record
SDK, version and ownerWhat to record: Name, version, the engineer who added it and the business owner
PurposeWhat to record: The specific purpose, matched to a line in your notice
Data sentWhat to record: Identifiers, events, device fields, and anything the app passes in manually
DestinationWhat to record: Vendor domains and the countries they process in, from the vendor's docs and the traffic capture
Start conditionWhat to record: Starts on launch, after login or after consent. Names the code that starts it
Switch-off controlWhat to record: The flag or call that stops it, and who tested it
Vendor termsWhat to record: Contract reference, retention, deletion route
Store disclosuresWhat to record: Matching entries in the Apple privacy label, the Play Data safety form and the manifest

How do you see what actually leaves the device?

A thick bundle of colourful network cables running through a metal cable tray in a dim server room corridor, the far end softly out of focus.

Code review finds what you meant to send. Traffic capture finds what the app sends. Use a test build and a test device, route the traffic through an intercepting proxy such as mitmproxy or Charles, and install the proxy's certificate on the test device. Some SDKs pin certificates or use their own transport. Where a proxy cannot read a flow, you can still see the destination domain, which is often enough to identify the vendor.

Run the same script in each of these states, with a fresh install every time, and save the capture.

App stateWhat you expect to seeWhat counts as a finding
1. First launch, before any consent screenWhat you expect to see: Only what your notice and your counsel say is allowed without consentWhat counts as a finding: Any analytics, attribution or ad domain contacted
2. Consent screen shown, user declinesWhat you expect to see: No calls to the declined purposesWhat counts as a finding: Any request to a vendor for a declined purpose, or an identifier in a request body
3. User acceptsWhat you expect to see: Calls start, to the listed vendors onlyWhat counts as a finding: A vendor you did not list. Fields beyond your inventory
4. User withdraws consent laterWhat you expect to see: Calls stop within a reasonable time (Section 6(6))What counts as a finding: Traffic continues after withdrawal, or after the app restarts
5. Signed-in child or age-gate fail pathWhat you expect to see: No tracking or ad calls at allWhat counts as a finding: Any ad or behavioural analytics call (Section 9(3))

Then check the request bodies. A domain list is not enough. Look for the advertising ID, the app-instance ID, the email address, the phone number and any user ID your own code attaches to events. A customer ID attached to events "for debugging" turns an anonymous stream into data about a named customer.

Keep the captures and a short written result for each state. Under Section 6(10) you must be able to prove your position, and a dated capture beats a statement that the SDK is switched off.

The pattern is the same for every SDK. Do not let the library start itself. Start it from your own code, after the consent state is known.

  • Disable auto-start. Use each vendor's documented switch, such as the Info.plist keys in the table. Without it, the library may initialise when the app loads.
  • Create one consent state in the app. Store it per purpose, with a notice version and a timestamp. Read it before starting any SDK.
  • Start SDKs from that state. On launch, read the stored consent and start only the permitted SDKs. After the user chooses, start or stop them without waiting for the next launch.
  • Make withdrawal as easy as consent. Section 6(4) requires this. A settings toggle that stops the SDKs and writes to your consent log fits. A buried email address does not.
  • Cover the backend too. If your server forwards events to an analytics or attribution vendor, apply the same check there, or the gate can be bypassed.

Keep the gate in one small module, and require every new SDK to be registered in the inventory and started through it. The same logic that we describe for marketing consent across WhatsApp, SMS and retargeting applies to ad and attribution SDKs. Our consent management work builds this module and the log behind it.

No. They are separate controls with different owners. Apple's App Tracking Transparency (ATT) permission is required to track users or to read the IDFA on iOS 14.5 and later. That is a platform rule. DPDP consent is a legal ground for processing under the Act, and it needs a notice that meets Section 5 and Rule 3.

An ATT "Allow" does not replace a DPDP notice, and DPDP consent does not unlock the IDFA if the ATT answer is no. Build both.

ControlOwnerWhat it needs from your audit
DPDP notice and consent (Sections 5 and 6, Rule 3)Owner: The ActWhat it needs from your audit: Itemised data and purposes that match the SDK inventory. A consent log you can produce.
ATT promptOwner: AppleWhat it needs from your audit: Ask before tracking or reading the IDFA. Do not read the IDFA when the answer is no.
Privacy manifestOwner: AppleWhat it needs from your audit: Required for listed SDKs. Keep it aligned with the real collection.
App Store privacy labelOwner: AppleWhat it needs from your audit: Developers must disclose SDK data. Update it when an SDK changes.
Google Play Data safety formOwner: GoogleWhat it needs from your audit: Mandatory. It covers data collected by third-party SDKs. "Collect" means data leaving the device.

The risk is a mismatch. A label that says no data is collected, a Play form that omits the ad SDK and a notice that mentions neither are three statements that your traffic capture can contradict. Align all three to the inventory. Note that Google's Data safety form says a transfer to a service provider acting for you is not "sharing", and that an SDK building advertising profiles across multiple customers would not count as a service provider. That is Google's form definition. It is not the DPDP test, so do not use it to decide your DPDP position.

What should SDK vendor contracts say?

Decide for each SDK whether the vendor processes data only for you, or also for its own purposes. That affects what your notice can truthfully say. A vendor that pools data across customers to build profiles is acting partly for itself. Your counsel should classify each one.

For vendors that act for you, Section 8(2) needs a valid contract. Ask for the following, and keep the answers with the inventory row.

  • the purposes the vendor may use your data for, and a ban on other uses
  • retention periods and a deletion route you can call for one person, so erasure and withdrawal can reach the vendor
  • safeguards that match Rule 6, including encryption, access control and logging
  • breach notice to you in time for you to meet Rule 7. Every breach must go to the Board and to each affected person, with no risk threshold
  • sub-processors and processing locations

On location, DPDP does not require data to stay in India. Section 16 lets the government restrict transfers to countries it notifies, and none are notified as of November 2026. Sector rules still apply. If your app handles payments, the RBI's April 2018 direction on storage of payment system data says that data must be stored only in India. So check whether a payments or fraud SDK sends payment data abroad.

What changes if your app is used by children?

Section 9(3) bars tracking, behavioural monitoring and targeted advertising directed at children, and the penalty can reach ₹200 crore. A child is anyone under 18. Section 9(1) also needs verifiable parental consent before processing.

For an SDK audit, the practical result is blunt. If children can use the app, ad SDKs and cross-app attribution should not start for them. Behavioural analytics needs careful review, because the Act does not define behavioural monitoring. Part B of the Fourth Schedule exempts confirming that a user is not a child, so the age gate itself is allowed. Part A exempts some classes, such as educational institutions for their educational activities and safety. Edtech firms should not assume that exemption applies to them. Read our guide to verifiable parental consent before you decide.

How do withdrawal and erasure reach your SDK vendors?

Section 6(6) says that after withdrawal, the fiduciary and its processors stop processing within a reasonable time. Section 8(7) needs erasure on withdrawal or when the purpose is no longer served, and it needs your processors to erase what you gave them, unless a law requires retention. SDK vendors hold event data you cannot see, so record for each one the stop control, the deletion route and the evidence you keep.

Add SDK vendors to the deletion queue described in our post on automating DPDP erasure. A vendor with no per-user deletion route is a risk to record, and a reason to question whether you need that SDK.

What should you build before 13 May 2027?

  • An SDK inventory for every app and webview, kept in version control and updated on each release.
  • A traffic capture for the five app states, saved with the build number and date, and a written result for each.
  • One consent state in the app that gates every SDK, with a settings toggle and a consent log.
  • A DPDP notice, an Apple privacy label, a privacy manifest check and a Play Data safety form that all match the inventory.
  • A contract and deletion route for every SDK vendor, or a decision to remove the SDK.
  • A rule that stops any SDK entering the build without an inventory row, and a child-user path that starts no ad or tracking SDK.

Mono's tech audit is a technical review. It can inspect your apps and backend and produce the inventory and traffic evidence, but it is not a DPDP certificate. The legal reading of each flow goes to your counsel, and Mono is not a law firm.

Sources: Digital Personal Data Protection Act, 2023, Sections 2(t), 4, 5, 6, 7, 8, 9, 16. Digital Personal Data Protection Rules, 2025, Rules 3, 6, 7, 10, 15 and the Fourth Schedule. Apple, Third-party SDK requirements and App Store user privacy and data use pages. Google Play Console Help, Provide information for Google Play's Data safety section. Google Analytics Help, Data collected by Google Analytics for Firebase, and Firebase documentation on configuring data collection. Meta for Developers, automatic event collection and iOS SDK getting started. RBI notification RBI/2017-18/153, 6 April 2018. Last reviewed 20 November 2026.

FAQ

Do analytics and ad SDKs need consent under the DPDP Act?

DPDP has no legitimate-interests basis. Processing needs consent or one of the closed Section 7 uses. Ad and attribution SDKs are the clearest case for consent. Whether a crash reporter or basic analytics fits a Section 7 use is a question for counsel. Your notice must describe each SDK's data and purpose, and you must be able to prove consent under Section 6(10).

How do I find out what data my app's SDKs send?

Build an inventory from your dependency files and merged manifest, then run a test build through an intercepting proxy such as mitmproxy or Charles. Capture traffic on first launch, after declining consent, after accepting and after withdrawing. Read the request bodies for advertising IDs, app-instance IDs, emails and any customer ID your own code attaches to events.

Does Apple's App Tracking Transparency prompt count as DPDP consent?

No. ATT is an Apple platform rule that controls tracking and access to the IDFA on iOS 14.5 and later. DPDP consent needs a notice that meets Section 5 and Rule 3 and a consent record you can produce. Build both, and do not read the IDFA when the ATT answer is no.

Can I keep Firebase or the Meta SDK in my app under DPDP?

Yes, if the use is covered by your notice and a valid ground, and you control when the SDK starts. Firebase Analytics can be held back with FIREBASE_ANALYTICS_COLLECTION_ENABLED set to NO until consent. The Meta SDK's automatic logging and advertiser ID collection have Info.plist switches. Test with traffic capture that the switches work on your build.

What must be different in a children's app for DPDP?

Section 9(3) bars tracking, behavioural monitoring and targeted advertising directed at children, who are under 18. Ad and attribution SDKs should not start for them. Section 9(1) also needs verifiable parental consent before processing. The age gate itself is exempt under the Fourth Schedule. Edtech firms should not assume the educational institution exemption applies to them.

Do Google Play and the App Store forms replace a DPDP notice?

No. The Apple privacy label, the privacy manifest and the Google Play Data safety form are store requirements. A DPDP notice is a legal requirement with its own content rules. All of them should match your SDK inventory, because a mismatch between them and your actual traffic is easy to spot.

Find out what your app really sends before 13 May 2027.