Skip to content

Google Play Data safety rejection for installed apps: how to find the SDK and fix it

Why Google Play flags installed apps data, what QUERY_ALL_PACKAGES has to do with it, how to find which SDK is responsible, how to update the Data safety form and privacy policy, and how to resubmit.

By our team. Published . 11 sources.

This rejection means Google Play found that your app, or code inside it, reads the list of apps installed on the device and sends it off the device, while your Data safety form says it doesn't collect "Installed apps". Google treats that list as personal and sensitive data. The fix is to find which part of the app reads it (usually a third-party SDK, not your own code), then either stop the collection or declare it accurately in the Data safety form and privacy policy, add an in-app disclosure where needed, and submit a corrected release.

Send us the Google Play message

Paste what Google sent you. We read it against the policy and reply with what it will take and a fixed price, the same working day if it reaches us before 2pm UK time. Free, and no access needed yet.

We use your details only to reply about this; see our privacy notice.

What does Google's policy say?

Three rules meet in this rejection.

The Data safety form must include your SDKs. Google says all developers must declare how they collect and handle user data, and that "this includes data collected and handled through any third-party libraries or SDKs used in their apps" [1]. "Collect" means "transmitting data from your app off a user's device", including data sent "by libraries and/or SDKs used in your app, irrespective of whether data is transmitted to you or a third-party server" [1].

"Installed apps" is its own data type. In the form it sits under App activity, described as "Information about the apps installed on a user's device" [1]. It is separate from App info and performance (crash logs, diagnostics) and from Device or other IDs [1].

The list of installed apps is personal and sensitive data. Google's User Data policy lists "inventory of other apps on the device" as personal and sensitive user data [2]. One of its examples of a violation is "an app that accesses a user's inventory of installed apps and doesn't treat this data as personal or sensitive data subject to the above privacy policy, data handling, and prominent disclosure and consent requirements" [2]. Another is "an app with an SDK that collects personal and sensitive user data and doesn't treat this data as subject to this user data policy" [2].

There is also a related permission policy. Google says it "regards the inventory of installed apps queried from a user's device as personal and sensitive information", and that the QUERY_ALL_PACKAGES permission "is only permitted when your app's core user-facing functionality or purpose requires broad visibility into installed apps on the user's device" [3].

Why was my app flagged?

Google says that "only you possess all the information required to complete the Data safety form", but that when it "becomes aware of a discrepancy between your app behaviour and your declaration", it may take action [1]. In the notices we see, Google says the declared data doesn't match what the app does, and often names the data type.

In the cases we fix, the cause is usually one of these:

  • An SDK reads the installed apps list. Ad mediation adapters, attribution and anti-fraud libraries are the usual suspects. Your own code never touches it, so nobody thought to tick the box.
  • A library added QUERY_ALL_PACKAGES or a broad queries element to your manifest. Gradle merges every library's manifest into yours [5], so a permission can appear in the final app without anyone adding it.
  • The form was filled in once and never updated. An SDK was added or upgraded since, and its data collection changed.
  • The form says "Installed apps: shared" but the privacy policy doesn't mention it, or there is no in-app disclosure.

From Android 11, an app that targets API level 30 or higher sees a filtered list of other apps by default, and has to declare what it needs to see with a queries element in its manifest [4]. QUERY_ALL_PACKAGES removes that filter, which is why Google restricts it [3].

How do I find which SDK collects it?

  1. Read your merged manifest. In Android Studio, open AndroidManifest.xml and select the Merged Manifest tab, which shows "the results of the merged manifest on the left and information about each merged manifest file on the right" [5]. Search for QUERY_ALL_PACKAGES and for any queries element. Use the right-hand panel to trace which library each one came from.
  2. Check each SDK's Data safety guidance. Google suggests you "refer to your SDK providers' published Data safety information" and check the Google Play SDK Index to see "if your provider has provided a link to their guidance" [1]. Each SDK Index listing can include "a URL for SDK providers to link to any guidance that they're making available to help app developers complete their Data safety forms", and lists the Android permissions recent versions of the SDK use [6].
  3. Compare like with like. Providers' pages usually only cover the latest SDK version. For example, Google's own page for the Google Mobile Ads SDK says it "lists the end-user data collected by only the latest version" [7]. If you are several versions behind, the page may not describe what your build does.
  4. Look at the network traffic from a test device if the documentation doesn't settle it, for the SDKs that remain after the first three steps.

Some published examples, as each provider states it on 17 November 2026:

SDKInstalled apps, per the provider's pageOther data types the provider lists
Google Mobile Ads SDK (Legacy)Not listedIP address, user product interactions, diagnostic information, device and account identifiers [7]
Unity Ads"Does the SDK collect data on installed apps?" NoPage views and taps during the ad, app diagnostics, device or other identifiers, and app usage times when Acquire Optimization is on [8]
ChartboostInstalled apps: NoSee the provider's table [9]

A provider saying "No" doesn't settle it on its own. Their pages cover their SDK only: Unity says its disclosures "are for the Unity Ads SDK only" and that you are "responsible for providing any additional disclosures for your app, including other Unity SDKs and/or third-party SDKs used in your app" [8]. Mediation set-ups often pull in several more networks' adapters, each with its own behaviour.

How do I fix it?

You have two routes, and the right one depends on whether the collection is worth keeping.

Route 1: stop the collection. Remove or replace the SDK, upgrade to a version that doesn't collect installed apps, or switch off the feature in the SDK's settings. If a library added QUERY_ALL_PACKAGES and your app doesn't need it, you can remove the permission from the merged manifest with tools:node="remove", which Android's documentation describes for elements "provided by a lower-priority manifest file that's out of your control (such as an imported library)" [5]. Google is clear that if your app doesn't meet the acceptable uses for QUERY_ALL_PACKAGES, "you must remove it from your app's manifest" [3]. Test that the SDK still works afterwards.

Route 2: declare it accurately. If the collection stays, update the Data safety form:

  1. In Play Console, open App content, then Data safety [1].
  2. In Data types, select App activity > Installed apps [1].
  3. Say whether it is collected, shared, or both. Data sent by an SDK straight to the SDK provider is "sharing" unless the provider is acting as your service provider, processing it "on behalf of the developer and based on the developer's instructions" [1]. Read the provider's guidance for how they describe themselves.
  4. Choose the purposes: for an ad or attribution SDK that is typically Advertising or marketing, Analytics, and Fraud prevention, security and compliance. Google defines Advertising or marketing as "used to display or target ads or marketing communications, or measuring ad performance" [1].
  5. Say whether it is optional or required. You can only call it optional if "all users – regardless of device or region – can either optionally provide information, opt out or opt in" [1].
  6. Check the Store listing preview and submit [1].

You can also export the form to CSV, edit it and import it again; Google warns that "answers already entered into your form will be overwritten when you import a CSV" [1].

Then match the privacy policy and in-app disclosure. The Data safety section "must be consistent with the disclosures made in the app's privacy policy", and the policy must disclose "the types of personal and sensitive user data that your app accesses, collects, uses and shares; and any parties with which any personal or sensitive user data is shared" [2]. Because installed apps is personal and sensitive data, collection people wouldn't expect also needs a prominent in-app disclosure that is "displayed in the normal usage of the app" and followed by consent through "affirmative user action" [2]. Google can ask for evidence: where an SDK collects this data by default, you must provide proof of disclosure and consent "within two weeks of receipt of a request from Google Play" [2].

If you keep QUERY_ALL_PACKAGES, your app must qualify (Google names device search, antivirus apps, file managers and browsers as permitted uses) and you must declare it in the Permissions Declaration Form in Play Console [3]. Sharing the inventory "for analytics or ads monetisation purposes" is listed as a use that won't be allowed [3].

How do I resubmit?

  1. Check Policy status in Play Console. It shows "any active enforcement against your app, such as rejection, removal or suspension" and any extra detail Google gives [11].
  2. Fix everything before resubmitting. Google says: "Do not attempt to resubmit a rejected app until you've fixed all the policy violations" [10]. Removal notices "may not indicate each and every policy violation", so check the rest of the app too [10].
  3. Upload a new build if the code changed, to every track that has the old version, and submit the updated Data safety form with it.
  4. Wait for review. Google says some apps "may be subject to expanded reviews, which may result in review times of up to seven days or longer in exceptional cases" [1].

If an update was rejected, the last approved version stays live, and Google says "rejections don't impact the standing of your Google Play Developer account" [10]. Suspensions are different: they "count as strikes against the good standing of your Google Play Developer account" [10]. If you think Google made a mistake, the enforcement email and Policy status page explain how to appeal [10][11].

How do I stop it happening again?

  • Review the Data safety form every time you add, remove or upgrade an SDK. Google says you should "update regularly information in your app's Data safety section and your privacy policy as you change how your app handles user data" [2].
  • Check the merged manifest for new permissions and queries elements before each release.
  • Keep a short register of SDKs, versions and what each provider says it collects, with links to their Data safety pages.
  • Pin SDK versions, so an automatic update can't change what the app collects without anyone noticing.

Pre-submission checklist

  • The merged manifest has been checked for QUERY_ALL_PACKAGES and queries elements, and each one is needed.
  • Every SDK's Data safety guidance has been read for the version you ship.
  • The Data safety form lists every data type the app and its SDKs collect or share, including App activity > Installed apps if applicable.
  • Each data type has the right collected/shared answer, purposes and optional/required setting.
  • The privacy policy names the same data types and the parties they are shared with.
  • An in-app disclosure and consent screen appears before any unexpected collection.
  • If QUERY_ALL_PACKAGES remains, the Permissions Declaration Form is complete and the use is permitted.
  • A new release with the fixes has been uploaded to every track that had the old one.

Questions we get asked

Where is Installed apps in the Data safety form?
Under the App activity category, in the Data types section of the form. Google describes it as information about the apps installed on a user's device. It is separate from App info and performance, which covers crash logs and diagnostics.
My code never reads installed apps. Why is Google flagging me?
Because the Data safety form covers data collected by any SDK or library in your app, sent to you or to a third party. A library can also add QUERY_ALL_PACKAGES or queries elements to your merged manifest without you adding them yourself. Check the merged manifest and each SDK's Data safety guidance.
Should I just tick Installed apps to make the warning go away?
Only if the app really does collect it. The form must be accurate, and declaring installed apps also means your privacy policy must cover it and you may need an in-app disclosure and consent. If the data isn't needed, removing the SDK or feature that collects it is usually cleaner.
Is installed apps data collected or shared?
If it leaves the device, it is collected. If an SDK sends it to its own company, that is sharing, unless that company processes it for you as a service provider, on your instructions. Check the SDK's own guidance for how it describes its role.
Can I keep the QUERY_ALL_PACKAGES permission?
Only if your app's core purpose needs to see all installed apps, such as device search, antivirus, file managers and browsers, and you complete the Permissions Declaration Form. Using it to collect app inventory for analytics or advertising is not allowed. Otherwise, remove it from the manifest.
Does a Google Play rejection hurt my developer account?
Google says rejections don't affect the standing of your developer account, and the last approved version stays live. Suspensions do count as strikes, and repeated rejections or removals can lead to suspension, so fix everything before resubmitting.

Sources

Checked on 17 November 2026.

  1. 1.Google, Play Console Help, "Provide information for Google Play's Data safety section": https://support.google.com/googleplay/android-developer/answer/10787469
  2. 2.Google, Play Console Help (Policy Centre), "User data": https://support.google.com/googleplay/android-developer/answer/10144311
  3. 3.Google, Play Console Help, "Use of the broad package (app) visibility (QUERY_ALL_PACKAGES) permission": https://support.google.com/googleplay/android-developer/answer/10158779
  4. 4.Android Developers, "Package visibility filtering on Android": https://developer.android.com/training/package-visibility
  5. 5.Android Developers, "Manage manifest files" (merge rules, tools:node, Merged Manifest view): https://developer.android.com/build/manage-manifests
  6. 6.Google, Play Console Help, "Make informed choices with Google Play SDK Index": https://support.google.com/googleplay/android-developer/answer/12034434
  7. 7.Google for Developers, "Google Play data disclosure" (Google Mobile Ads SDK, Legacy): https://developers.google.com/admob/android/privacy/play-data-disclosure
  8. 8.Unity, "Google Play data safety section for Unity Ads": https://docs.unity.com/en-us/grow/ads/privacy/google-data-safety
  9. 9.Chartboost, "Data Safety Details" (Android): https://docs.chartboost.com/en/monetization/integrate/android/data-safety-details/
  10. 10.Google, Play Console Help, "Enforcement process": https://support.google.com/googleplay/android-developer/answer/9899234
  11. 11.Google, Play Console Help, "Check your app's policy status": https://support.google.com/googleplay/android-developer/answer/9842754

Planning something similar?

Tell us what you're building. We'll give you an honest view of cost and timing, and the simplest way to start.