Rejection Fixes

Meta App Review Rejected Because of the Privacy Policy? Here Is What to Check

Meta App Review Rejected Because of the Privacy Policy? Here Is What to Check

Privacy policy rejections are among the easiest to prevent. These are the checks I run on every policy URL before an app goes to review.

Why Meta rejects apps for the privacy policy

Meta reviewers check two things about a privacy policy: that it is reachable, and that it explains how the app handles data received from Meta. A generic policy copied from a template often fails the second check, because it says nothing about Facebook, Instagram, Messenger, or WhatsApp data.

Privacy policy rejections are frustrating because they block an otherwise good submission. The good news is that they are among the easiest to prevent. I run the checks below before every App Review submission.

Technical checks for the privacy policy URL

  • The URL is public and loads without a login, cookie wall, or region block.
  • It is a normal web page, not a downloadable PDF or a document link with restricted access.
  • The same URL is set in the app's Basic Settings and in any login dialogs that show it.
  • It loads over HTTPS without certificate warnings.
  • It does not redirect to the homepage or to a different language version based on location.
  • It renders without JavaScript errors, because some automated checks fetch the page directly.

A quick test: open the URL in a private window on a different network, such as a phone on mobile data. If it does not load there, it may not load for the reviewer either.

Privacy policy content Meta expects

  • The business or app owner's name and a contact method, such as an email address.
  • The specific data collected through Meta products, such as profile name, Page data, messages, comments, or WhatsApp phone numbers.
  • Why that data is used, matching the use cases in the App Review submission.
  • How long data is stored and how it is protected.
  • How users can request deletion, with a link to the data deletion instructions or callback status page.
  • Whether data is shared with third parties, such as hosting providers, analytics, or AI model providers.
  • The date the policy was last updated.

A privacy policy outline for Meta integrations

This is the structure I use as a starting point. It is not legal advice, and the final policy should reflect your real data practices and the laws that apply to your business.

1. Who we are (legal name, contact email)
2. Data we receive from Meta products
   - Facebook Login: name, email, app-scoped user ID
   - Pages / Instagram: Page or account ID, messages, comments
   - WhatsApp: phone number, message content, delivery status
3. How we use this data (one line per feature)
4. Third-party processors (hosting, AI providers, analytics)
5. Storage, retention, and security
6. Your choices: disconnecting accounts, deleting data
7. Data deletion requests and status page link
8. Changes to this policy and last-updated date

Match the policy to your App Review use cases

Reviewers compare the policy with what they see in the screencast. If the video shows the app reading Instagram comments but the policy never mentions comments, that is a gap. I go through the permission table from the submission and confirm that every type of data appears in the policy, with the same purpose described in plain language.

This also helps after approval. Meta can run periodic data use checkups, and a policy that matches the product makes those easier to complete.

Extra requirements for AI products

If the app sends message content or comments to an AI model to generate replies, say so clearly. Name the category of provider, explain what data is sent, and say whether it is used to train models. Reviewers and users both expect transparency here. A policy that hides third-party processing is both a rejection risk and a trust problem.

I cover the rest of the AI-specific design, including disclosure and escalation, in building an AI reply agent without breaking Meta policies.

Keeping the privacy policy accurate over time

A privacy policy that was accurate at approval can drift as the product grows. A new AI feature, a new analytics tool, or a new permission can change what data you collect and who processes it. I add a step to the release checklist: if a change touches Meta data or adds a third-party processor, the policy is reviewed in the same release.

This matters beyond App Review. Users read the policy when deciding whether to connect their accounts, and enterprise customers often check it during procurement. Keeping it current is cheaper than explaining an outdated policy later.

Fixing the rejection and resubmitting

  • Read the rejection note to see whether the issue is access or content.
  • Fix the URL issues first, then update the content to cover every Meta data type you use.
  • Update the last-updated date and verify the URL in a private window.
  • Mention in the resubmission notes what changed and where the relevant section is.
  • Run the full resubmission audit so a different issue does not cause the next rejection.

Frequently asked questions

Can I host my privacy policy on a free page builder or Google Doc?

A public web page on your own domain is the safest choice. Shared documents often require access or change URLs, which can cause rejections.

Does the privacy policy need to mention Facebook or Meta by name?

It should clearly describe the data you receive from Meta products. Naming the products, such as Facebook Login, Instagram, or WhatsApp, makes this much easier for reviewers to confirm.

Do I need a separate policy for each app?

No, one policy can cover several apps if it accurately describes the data each one uses.

How do I mention data deletion?

Explain how users can request deletion and link to your data deletion instructions page or callback status page.