Certification Process to customize the consent dialog

Application Cannot Use grantUserConsent() or denyUserConsent() Until Custom Consent Dialog Is Certified
=======================================================================================================

Symptoms
--------

Customers may report one or more of the following:

Unable to use grantUserConsent() or denyUserConsent() in HERE SDK production workflows.
Application collects location-related signal data but has not completed HERE certification.
Uncertainty about what information must be displayed in a custom consent dialog.
App review or certification feedback indicating missing consent controls or privacy information.
Users cannot view or change a previously selected consent status.
Questions about required screenshots, UI mockups, or App ID certification steps.

Answer
------

Applications using HERE SDK LocationEngine data collection features must obtain explicit user consent before LocationEngine begins collecting nearby Wi-Fi or cellular signal information. If an application uses a customized consent experience instead of the standard HERE consent flow, the consent dialog must meet HERE certification requirements and be reviewed before the associated App ID can be certified.

Products Affected
-----------------

HERE SDK for Android Navigate Edition
Applications using:
+ LocationEngine
+ ConsentEngine
+ grantUserConsent()
+ denyUserConsent()

Root Cause
----------

The HERE LocationEngine can collect information about nearby Wi-Fi and mobile network signals to improve HERE services. Because this involves collecting device-environment signal data, applications must provide users with a clear consent experience that satisfies HERE privacy and certification requirements.

A customized consent dialog that does not meet the required criteria cannot be certified for use with the corresponding App ID.

Certification Requirements
--------------------------

To certify an App ID for a customized consent flow, the application must:

1. Request user consent before the application starts using HERE SDK LocationEngine signal data collection functionality.
2. Require the user to explicitly choose whether to allow or deny consent.
3. Allow the user to view their current consent status at any time.
4. Allow the user to change or revoke a previously selected consent decision at any time.

Required Information in the Consent Dialog
------------------------------------------

The customized consent experience must communicate the following topics:

1. The application wants to collect information about nearby Wi-Fi and cellular signals.
2. The information is sent to HERE Technologies to improve HERE services.
3. The information does not identify the user and only anonymized information is retained.
4. The user can change or revoke consent at any time.
5. A link to HERE privacy information must be provided:
* HERE SDK Privacy Supplement
6. Neither option may be preselected. Users must actively choose Allow or Deny.

Example Consent Text
--------------------

> This application collects information about nearby Wi-Fi and mobile network signals to help locate the device.
> With your permission, this signal information is sent to HERE to improve HERE services. This information does not identify you, and HERE only retains anonymized information.
> You can revoke or change your consent at any time.
> Learn more: HERE SDK Privacy Supplement
> Would you like to provide HERE with this information?
> Allow
> Deny

Shorter customer-specific wording may be accepted if all required topics remain clearly communicated.

Recommended Actions
-------------------

1. Design the customized consent dialog according to the certification requirements.
2. Prepare screenshots, UI mockups, or UI designs showing:
* Consent acquisition screen
* Consent status visibility
* Consent change or revocation capability
3. Create a ServiceNow ticket to start the certification process.
4. Submit the UI evidence for review.
5. After approval, provide the application App ID (here.client.id) for backend certification.
6. After certification is completed, use:
* grantUserConsent()
* denyUserConsent() to communicate the user’s selection to HERE SDK.

Expected vs. Unexpected Behavior
--------------------------------

Expected Behavior

Users are asked for consent before signal data collection begins.
Users can review and modify their consent decision at any time.
The consent dialog contains all required privacy disclosures and links.
Certified App IDs can use the consent APIs as designed.

Unexpected Behavior

Signal data collection starts before consent is obtained.
Consent status cannot be viewed or modified.
Allow or Deny is preselected.
Required privacy disclosures are missing.
Certification evidence is not provided prior to App ID certification.

Reference Documentation
-----------------------

HERE SDK Developer Guide - Handle User Consent
* HERE SDK Privacy Supplement

Keywords/Tags:

HERE SDK, ConsentEngine, LocationEngine, grantUserConsent, denyUserConsent, consent dialog, App ID certification, here.client.id, privacy consent, Wi-Fi signals, cellular signals, Android Navigate SDK, LocationEngine certification, HERE privacy, ServiceNow ticket