Free tool · nothing stored
Privacy policy URL checker
Paste the link you are about to put into Google Play, App Store Connect, Meta Ads, Google Ads or a directory listing. We open it the way their reviewers do and show you every check, pass or fail, before they do.
What platforms actually check
- It loads, publicly, over HTTPS. Google Play says the policy must be active, publicly accessible and not geofenced. A login wall, a 403, or plain http fails on the spot.
- It is a web page, not a PDF or a homepage. Play rejects PDFs outright, and Meta's lead form checker and App Store reviewers reject links that land on a storefront or a generic legal page with no privacy heading.
- It names what you use. Reviewers compare the policy to the SDKs, pixels and processors they can see: analytics, ads, payments, support chat. A policy that names none of them reads as a template.
- It has a contact and a date. Slack, Play and Meta all expect a way to reach you (an email, not only a postal address) and an effective or last-updated date.
- It stays put. Redirect chains and moved pages are the most common reason a once-approved link gets flagged later. The URL you submit should be the page that loads.
Where the link goes next
Frequently asked questions
What does the checker test?
Whether the URL is public and well formed, loads with a 2xx status, is served over HTTPS without redirects or downgrades, is a web page rather than a PDF, is not behind a login, reads as a privacy policy, names the third-party tools a site typically uses, gives a contact method and an effective or updated date, and has enough text to be a real policy.
Why does a PDF fail?
Google Play's User Data policy says the privacy policy must be an active, publicly accessible web page and not a PDF, and App Store Connect expects a web link too. Reviewers also cannot read a PDF on a phone the way they read a page.
Why is a redirect a warning?
The URL you paste into a store or ad platform is the one their checker opens. If it bounces through redirects, some tools time out and others record the first URL. Paste the final URL so the field passes on the first try.
Does the checker store the URL or the page?
No. We fetch the page once from our servers, run the checks in memory and return the report. Only a per-visitor and per-site rate limit counter is kept for a few minutes.
Can it check a homepage?
It can, and it will tell you what reviewers tell you: a homepage is not a privacy policy. The policy needs its own URL with the word privacy in the title or heading.