Ir para o conteúdo

Private Information Usage in DialMyApp

Implement the prominent disclosure and consent page

DialMyApp uses the user's phone number for different purposes. This includes the linkage between phone number and push registration ID inside the application. Current Google's regulation doesn't allow sending user's private information without a dialog for the user, that notifies users about the privacy and how information is used. For details on the valid prominent disclosure requirement, please review the "Prominent Disclosure & Consent Requirement" section under the User Data policy. According to the article:

Prominent disclosure: You must provide an in-app disclosure of your data access, collection, use, and sharing. The in-app disclosure:

  • Must be within the app itself, not only in the app description or on a website;
  • Must be displayed in the normal usage of the app and not require the user to navigate into a menu or settings;
  • Must describe the data being accessed or collected;
  • Must explain how the data will be used and/or shared;
  • Cannot only be placed in a privacy policy or terms of service; and
  • Cannot be included with other disclosures unrelated to personal and sensitive user data collection.

Consent and runtime permissions: Requests for in-app user consent and runtime permission requests must be immediately preceded by an in-app disclosure that meets the requirement of this policy. The app's request for consent:

  • Must present the consent dialog clearly and unambiguously;
  • Must require affirmative user action (for example, tap to accept, tick a check-box);
  • Must not interpret navigation away from the disclosure (including tapping away or pressing the back or home button) as consent;
  • Must not use auto-dismissing or expiring messages as a means of obtaining user consent; and
  • Must be granted by the user before your app can begin to collect or access the personal and sensitive user data.

To meet policy requirements, it's recommended that you reference the following example format for Prominent Disclosure when it's required: "[This app] collects/transmits/syncs/stores [type of data] to enable ["feature"], [in what scenario]." Example the prominent disclosure page from the DialMyApp application:

Screenshot not available — this image was not included in the original document export. See the DialMyApp app on Google Play for a live example of the Prominent Disclosure page.

Share Privacy Policy and "Data Safety" section in Play Console

According to the article "Best practices for prominent disclosure and consent" you must post a complete privacy policy in both the Privacy policy section in Play Console and within the app itself and you must complete the Data safety section in Play Console.

Adding a privacy policy to your app's store listing helps provide transparency about how you treat sensitive user and device data.

The privacy policy must, together with any in-app disclosures, comprehensively disclose how your app collects, uses, and shares user data. This includes the types of parties with whom it's shared. You should consult your legal representative to advise you of what is required.

For apps that request access to sensitive permissions or data: You must link to a privacy policy on your app's store listing page and within your app. Make sure your privacy policy is available on an active URL, applies to your app, and specifically covers user privacy.

Add a privacy policy in Play Console:

  1. Open Play Console -> Policy and programs (in the right menu) -> App content

  2. Under "Privacy Policy," select Start.

    Note

    If you've previously added a privacy policy and want to make changes, you'll see and select Manage instead of starting in Actioned tab.

  3. Enter the URL hosting the privacy policy online.

  4. Save your changes.

In scenarios where the SDK receives the phone number from an IVR or SIP system, it uses that number to retrieve the user's push registration ID. This enables the SDK to send the correct push notification that triggers the menu during a call.

After the user accepts, store the flag by calling:

RequestSendPrivateInfoHelper.setSendPrivateInfoValue(context, true);

RequestSendPrivateInfoHelper.setSendPrivateInfoValue(context, true)

This internally stores the value true in SharedPreferences using the key "DMA_SEND_PRIVATE_INFO".

To check whether the user has already accepted the Prominent Disclosure screen, use:

if (!RequestSendPrivateInfoHelper.isSendPrivateInfoApproved(context))
    showProminentDisclosure();// Custom screen implementation

if (!RequestSendPrivateInfoHelper.isSendPrivateInfoApproved(context))
    showProminentDisclosure() // Custom screen implementation

For a real-world example, see the implementation in the "DialMyApp" demo app (available on Google Play). It includes a compliant version of the Prominent Disclosure page and logic.

Important Notice: Avoid Deprecated Method

If your app includes any usage of the deprecated method TelephonyManager.getLine1Number(), we strongly recommend removing it. This is especially important when using React Native with the popular plugin react-native-device-info, which includes this method internally.

Why?

  • getLine1Number() is deprecated and unreliable:
    • Often returns null or outdated values
    • May cause privacy policy violations if misused
  • It is not required for any SDK feature
  • Its presence may trigger Google Play warnings or prevent approval during review