Permissions and APIs that access sensitive information

SMS and call log permissions are regarded as personal and sensitive user data subject to the personal and sensitive Information policy, and the following restrictions:

Restricted permission	Requirement
Call log permission group (for example, READ_CALL_LOG, WRITE_CALL_LOG, PROCESS_OUTGOING_CALLS)	It must be actively registered as the default Phone or Assistant handler on the device.
SMS permission group (for example, READ_SMS, SEND_SMS, WRITE_SMS, RECEIVE_SMS, RECEIVE_WAP_PUSH, RECEIVE_MMS)	It must be actively registered as the default SMS or Assistant handler on the device.

 

Apps lacking default SMS, Phone or Assistant handler capability may not declare use of the above permissions in the manifest. This includes placeholder text in the manifest. Additionally, apps must be actively registered as the default SMS, phone or Assistant handler before prompting users to accept any of the above permissions, and must immediately stop using the permission when they’re no longer the default handler. The permitted uses and exceptions are available on this Help Centre page.

Apps may only use the permission (and any data derived from the permission) to provide approved core app functionality. Core functionality is defined as the main purpose of the app. This may include a set of core features, which must all be prominently documented and promoted in the app’s description. Without the core feature(s), the app is 'broken' or rendered unusable. The transfer, sharing or licensed use of this data must only be for providing core features or services within the app, and its use may not be extended for any other purpose (for example, improving other apps or services, advertising or marketing purposes). You may not use alternative methods (including other permissions, APIs or third-party sources) to derive data attributed to call log- or SMS-related permissions.

Device location is regarded as personal and sensitive user data subject to the Personal and sensitive information policy and the Background location policy, and the following requirements:

• Apps may not access data protected by location permissions (for example, ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION, ACCESS_BACKGROUND_LOCATION) after it is no longer necessary to deliver current features or services in your app.
• You should never request location permissions from users for the sole purpose of advertising or analytics. Apps that extend permitted usage of this data for serving advertising must be in compliance with our ads policy.
• Apps should request the minimum scope necessary (for example, coarse instead of fine, and foreground instead of background) to provide the current feature or service requiring location, and users should reasonably expect that the feature or service needs the level of location requested. For example, we may reject apps that request or access background location without compelling justification.
• Background location may only be used to provide features beneficial to the user and relevant to the core functionality of the app.

Apps are allowed to access location using foreground service (when the app only has foreground access for example, 'while in use') permission if the use:

• has been initiated as a continuation of an in-app user-initiated action, and
• is terminated immediately after the intended use case of the user-initiated action is completed by the application.

Apps designed specifically for children must comply with the Designed for Familiespolicy.

For more information on the policy requirements, please see this help article.

Files and directory attributes on a user’s device are regarded as personal and sensitive user data subject to the personal and sensitive information policy and the following requirements:

• Apps should only request access to device storage that is critical for the app to function, and may not request access to device storage on behalf of any third-party for any purpose that is unrelated to critical user-facing app functionality.
• Android devices running R or later will require the MANAGE_EXTERNAL_STORAGE permission in order to manage access in shared storage. All apps that target R and request broad access to shared storage ('all files access') must successfully pass an appropriate access review prior to publishing. Apps allowed to use this permission must clearly prompt users to enable 'All files access' for their app under 'Special app access' settings. For more information on the R requirements, please see this help article.

The inventory of installed apps queried from a device are regarded as personal and sensitive user data subject to the personal and sensitive information policy,  and the following requirements:

Apps that have a core purpose to launch, search or interoperate with other apps on the device, may obtain scope-appropriate visibility to other installed apps on the device as outlined below:

• Broad app visibility: Broad visibility is the capability of an app to have extensive (or 'broad') visibility of the installed apps ('packages') on a device.
  • For apps targeting API level 30 or later, broad visibility to installed apps via the QUERY_ALL_PACKAGES permission is restricted to specific use cases where awareness of and/or interoperability with any and all apps on the device are required for the app to function.
    • You may not use QUERY_ALL_PACKAGES if your app can operate with a more targeted scoped package visibility declaration(for example, querying and interacting with specific packages instead of requesting broad visibility).
  • Use of alternative methods to approximate the broad visibility level associated with QUERY_ALL_PACKAGES permission are also restricted to user-facing core app functionality and interoperability with any apps discovered via this method.
  • Please see this Help Centre article for allowable use cases for the QUERY_ALL_PACKAGES permission.
• Limited app visibility: Limited visibility is when an app minimises access to data by querying for specific apps using more targeted (instead of 'broad') methods(for example, querying for specific apps that satisfy your app’s manifest declaration). You may use this method to query for apps in cases where your app has policy-compliant interoperability, or management of these apps.
• Visibility to the inventory of installed apps on a device must be directly related to the core purpose or core functionality that users access within your app.

App inventory data queried from Play-distributed apps may never be sold nor shared for analytics or ads monetisation purposes.

The Accessibility API cannot be used to:

• Change user settings without their permission or prevent the ability for users to disable or uninstall any app or service unless authorised by a parent or guardian through a parental control app or by authorised administrators through enterprise management software; 
• Work around Android built-in privacy controls and notifications; or
• Change or leverage the user interface in a way that is deceptive or otherwise violates Google Play developer policies. 

The Accessibility API is not designed and cannot be requested for remote call audio recording. 

The use of the Accessibility API must be documented in the Google Play listing.

Guidelines for IsAccessibilityTool

Apps with a core functionality intended to directly support people with disabilities are eligible to use the IsAccessibilityTool to appropriately publicly designate themselves as an accessibility app.

Apps not eligible for IsAccessibilityTool may not use the flag and must meet prominent disclosure and consent requirements as outlined in the user data policy as the accessibility-related functionality is not obvious to the user. Please refer to the AccessibilityService API Help Centre article for more information.

Apps must use more narrowly scoped APIs and permissions in lieu of the Accessibility API when possible to achieve the desired functionality. 

The REQUEST_INSTALL_PACKAGES permission allows an application to request the installation of app packages.​​ To use this permission, your app’s core functionality must include:

• Sending or receiving app packages; and
• Enabling user-initiated installation of app packages.

Permitted functionalities include:

• Web browsing or search
• Communication services that support attachments
• File sharing, transfer or management
• Enterprise device management
• Backup and restore
• Device migration/Phone transfer
• Companion app to sync phone to wearable or IoT device (for example, smart watch or smart TV)

Core functionality is defined as the main purpose of the app. The core functionality, as well as any core features that comprise this core functionality, must all be prominently documented and promoted in the app's description.

The REQUEST_INSTALL_PACKAGES permission may not be used to perform self updates, modifications or the bundling of other APKs in the asset file unless for device management purposes. All updates or installing of packages must abide by Google Play’s device and network abuse policy and must be initiated and driven by the user.

Health Connect may only be used in accordance with the applicable policies, Terms and Conditions and for approved use cases as set forth in this policy. This means that you may only request access to permissions when your application or service meets one of the approved use cases.

Approved use cases include: fitness and wellness, rewards, fitness coaching, corporate wellness, medical care, health research and games.

Only applications or services with one or more features designed to benefit users' health and fitness are permitted to request access to Health Connect permissions. These include:

• Applications or services allowing users to directly journal, report, monitor and/or analyse their physical activity, sleep, mental wellbeing, nutrition, health measurements, physical descriptions and/or other health or fitness-related descriptions and measurements.
• Applications or services allowing users to store their physical activity, sleep, mental wellbeing, nutrition, health measurements, physical descriptions and/or other health or fitness-related descriptions and measurements on their device.

Access to Health Connect may not be used in violation of this policy or other applicable Health Connect Terms and Conditions or policies, including for the following purposes:

• Do not use Health Connect in developing, or for incorporation into, applications, environments or activities where the use or failure of Health Connect could reasonably be expected to lead to death, personal injury or environmental or property damage (such as the creation or operation of nuclear facilities, air traffic control, life-support systems or weaponry).
• Do not access data obtained through Health Connect using headless apps. Apps must display a clearly identifiable icon in the app tray, device app settings, notification icons, etc.
• Do not use Health Connect with apps that sync data between incompatible devices or platforms.
• Do not use Health Connect to connect to applications, services or features that solely target children.
• Take reasonable and appropriate steps to protect all applications or systems that make use of Health Connect against unauthorised or unlawful access, use, destruction, loss, alteration or disclosure.

It is also your responsibility to ensure compliance with any regulatory or legal requirements that may apply based on your intended use of Health Connect and any data from Health Connect. Except as explicitly noted in the labelling or information provided by Google for specific Google products or services, Google does not endorse the use of or warrant the accuracy of any data contained in Health Connect for any use or purpose and, in particular, for research, health or medical uses. Google disclaims all liability associated with use of data obtained through Health Connect.

When using Health Connect, data access and use must adhere to specific limitations:

• Data use should be limited to providing or improving the appropriate use case or features visible in the application's user interface.
• User data may only be transferred to third parties with explicit user consent: for security purposes (for example, to investigate abuse), to comply with applicable laws or regulations, or as part of mergers/acquisitions.
• Human access to user data is restricted unless explicit user consent is obtained, for security purposes, to comply with laws, or when aggregated for internal operations as per legal requirements.
• All other transfers, uses or sale of Health Connect data is prohibited, including:
  • Transferring or selling user data to third parties, like advertising platforms, data brokers or any information resellers.
  • Transferring, selling or using user data for serving ads, including personalised or interest-based advertising.
  • Transferring, selling or using user data to determine creditworthiness or for lending purposes.
  • Transferring, selling or using user data with any product or service that may qualify as a medical device, unless the medical device app complies with all applicable regulations, including obtaining necessary clearances or approvals from relevant regulatory bodies (e.g. US FDA) for its intended use of Health Connect data, and the user has provided explicit consent for such use.
  • Transferring, selling or using user data for any purpose or in any manner involving Protected Health Information (as defined by HIPAA) unless you receive prior written approval to such use from Google.

You must only request access to the permissions that are necessary to implement your product's features or services. Such access requests should be specific and limited to the data which is needed.

Health Connect manages health and fitness data, including sensitive information, and requires all applications to have a comprehensive privacy policy. The privacy policy must transparently disclose how the app collects, uses and shares user data. Beyond legal requirements, developers must have the following information in the privacy policy:

• Accurately depict the app's identity, outlining the data accessed and its connection to prominent app features or recommendations
• Data retention and deletion practices
• Data-handling procedures. For example, transmitting it using modern cryptography (for example, over HTTPS)

For more information on requirements for apps connecting to Health Connect, please see this Help Centre article.

The VpnService is a base class for applications to extend and build their own VPN solutions. Only apps that use the VpnService and have VPN as their core functionality can create a secure device-level tunnel to a remote server. Exceptions include apps that require a remote server for core functionality, such as:

• Parental control and enterprise management apps.
• App usage tracking.
• Device security apps (for example, anti-virus, mobile device management, firewall).
• Network-related tools (for example, remote access).
• Web browsing apps.
• Operator apps that require the use of VPN functionality to provide telephony or connectivity services.

The VpnService cannot be used to:

• Collect personal and sensitive user data without prominent disclosure and consent.
• Redirect or manipulate user traffic from other apps on a device for monetisation purposes (for example, redirecting ad traffic through a country different to that of the user).

Apps that use the VpnService must:

• Document use of the VpnService in the Google Play listing, and
• Must encrypt the data from the device to VPN tunnel end point, and
• Abide by all Developer Programme Policies , including the Ad fraud, Permissions and Malware policies.

A new permission, USE_EXACT_ALARM, will be introduced that will grant access to exact alarm functionality in apps starting with Android 13 (API target level 33). 

USE_EXACT_ALARM is a restricted permission and apps must only declare this permission if their core functionality supports the need for an exact alarm. Apps that request this restricted permission are subject to review, and those that do not meet the acceptable use case criteria will be disallowed from publishing on Google Play.

Acceptable use cases for using the exact alarm permission

Your app must use the USE_EXACT_ALARM functionality only when your app’s core, user-facing functionality requires precisely timed actions, such as:

• The app is an alarm or timer app.
• The app is a calendar app that shows event notifications.

If you have a use case for exact alarm functionality that’s not covered above, you should evaluate if using SCHEDULE_EXACT_ALARM as an alternative is an option.

For more information on exact alarm functionality, please see this developer guidance.

For apps targeting Android 14 (API target level 34) and above, USE_FULL_SCREEN_INTENT is a special apps access permission. Apps will only be automatically granted to use the USE_FULL_SCREEN_INTENT permission if the core functionality of their app falls under one of the below categories that require high-priority notifications:

• Setting an alarm
• Receiving phone or video calls

Apps that request this permission are subject to review, and those that do not meet the above criteria will not be automatically granted this permission. In that case, apps must request permission from the user to use USE_FULL_SCREEN_INTENT.

As a reminder, any usage of the USE_FULL_SCREEN_INTENT permission must comply with all Google Play developer policies, including our mobile unwanted software, device and network abuse and ads policies. Full-screen intent notifications cannot interfere with, disrupt, damage or access the user’s device in an unauthorised manner. Additionally, apps should not interfere with other apps or the usability of the device.

Learn more about the USE_FULL_SCREEN_INTENT permission in our Help Centre.