How to Fix Targeted Push Issues in Listing Review

Read the original article：How to Fix Targeted Push Issues in Listing Review

Problem Description

When submitting an app update for release on the AppGallery, AGC feedback stated:
“Your app contains a targeted push feature but does not prominently indicate the targeted push service within the app.”
How should this targeted push issue in the rejection notice be resolved?

1. Your app explicitly contains a targeted push function but does not meet the following requirements: clearly stating the targeted push function in the privacy policy, prominently labeling the targeted push service in the app, and providing an option to disable it. This violates item 7.7 of the Huawei AppGallery Review Guidelines.

Background Knowledge

Targeted Push:
This refers to activities that recommend or display content, provide search results, or push commercial advertisements to an individual based on their personal information such as browsing history, interests, consumption records, and habits. In business practice, targeted push is also referred to as personalized display or personalized recommendation.

If an app has a targeted push feature, it must meet the following three criteria:

1. Clearly state the targeted push feature in the privacy policy.
2. Prominently label the targeted push service in the app.
3. Provide an option to disable the targeted push service.

Troubleshooting Process

1. If the app contains a targeted push feature, ensure the following three requirements are met:
   a. Clearly indicate the presence of a targeted push feature in the in-app privacy policy and in the privacy policy URL submitted on AppGallery Connect.
   b. Prominently label the targeted push service in the app.
   c. Provide an option to disable the targeted push service.

2. If the app does not contain a targeted push feature, remove all content that may suggest otherwise, including:
   a. The in-app privacy policy.
   b. The privacy policy URL submitted on AppGallery Connect.
   c. Any relevant in-app pages.

3. Note: Prominent differentiation of a targeted push service includes but is not limited to the use of terms such as “Personalized Recommendation,” “Recommended for You,” or “You May Like,” and other similar noticeable phrases.

Solution

If the app actually includes targeted push functionality:

That is, some features display different content to different users based on their browsing history, interests, consumption records, or habits:

• State the targeted push function in the privacy policy: Clearly explain which information is collected for targeted push, e.g., “XX App includes a targeted push feature that collects your XX information to recommend products or services that may interest you.” If the app uses personal data from third parties for targeted push, the third-party data source must also be clearly stated.
• Prominently label the targeted push service within the app: Clearly differentiate targeted push services within the app. Methods include labeling with terms such as “Personalized Recommendation,” “Targeted Push,” “You May Like,” or by displaying them in separate columns, sections, or pages.
• Provide an option to disable the targeted push service: If targeted push exists, users must be given a convenient option to opt out or disable the personalized display mode. Once a user opts out or disables this feature, their personal data must not continue to be used for targeted push or precise marketing.

If the app does not include targeted push functionality:

• Review the privacy policy and remove any references to “personalized recommendations,” “personalized services,” “targeted push,” etc.
• Check whether there are features named “Personalized Recommendation,” “Recommendation,” “Targeted Push,” or “You May Like.” If these sections display the same content for all users (i.e., not personalized), rename them to neutral terms like “Hot,” “Trending,” or “Top List.”
• The app does not need to provide an option to disable personalized display features.
• When resubmitting for review, include a note stating: “We have confirmed that the app does not contain any targeted push functionality.”

If you disagree with the review result, you may appeal through the Interactive Center.

Verification Result

Q: The app was rejected for “not providing an in-app option to disable targeted push,” but our settings page already has a “Push Notifications” toggle. Is that acceptable?

A: No. The “Push Notifications” toggle does not clearly relate to targeted push.
It’s recommended to use wording that explicitly distinguishes the targeted push service, or name the toggle consistently with the in-app module (e.g., if the app has a “You May Like” section, the toggle should be named “You May Like” switch).

Q: The “Merchant Recommendations” section is just a feature name and does not actually use targeted push. Do we still need to include targeted push descriptions in the privacy policy and add a toggle?

A: No.
If the content displayed in this module is the same for all users (i.e., not personalized), you can rename it to something less confusing like “Hot Products.”
If there’s no targeted push functionality, you do not need to mention it in the privacy policy or add a targeted push toggle.

If the app includes targeted push capability, it must meet all three key requirements — missing any one will result in rejection.
If the app does not include targeted push capability, avoid using confusing terms such as “Personalized Recommendation,” “Recommendation,” “Targeted Push,” or “You May Like,” and remove any mention of targeted push from the privacy policy.

Written by Egemen Ayhan