No privacy policy link found
The homepage and a small set of conventional paths did not reveal a privacy policy.
Why it matters
Visitors need a clear way to understand how a service handles personal information. A policy should be easy to find from the site and should describe the service’s actual practices.
How ShipReady detects it
What it inspects
ShipReady examines links in the fetched homepage, then—if it finds no likely policy link—requests six conventional policy paths and checks successful response bodies for a privacy-related term.
What triggers a finding
The rule reports a missing policy only when no homepage anchor matches its privacy/legal link or text tokens and every safely requested conventional path answers without an unanswered status or a matching privacy term.
What the evidence shows
The homepage’s fetched HTML did not contain a matching policy link, and none of the answered conventional paths returned a body containing the expected privacy term.
Limits of this check
This is a passive, heuristic check. It does not render JavaScript, inspect every route, judge policy completeness or legal sufficiency, or discover every custom URL. If a candidate request is blocked, fails, is rate-limited, or otherwise goes unanswered, the scanner marks coverage incomplete instead of claiming absence. A generic privacy word in a successful response can count as a match even if that response is not a complete policy.
How to fix it
Publish and link a policy that matches your practices
Write or obtain a privacy policy that accurately describes the personal information your service collects, uses, shares, and retains.
Publish it at a stable URL and add a clearly labelled link to the homepage or shared footer. Make sure the link works in the rendered page.
How to verify the change
Verify the page and link
Open the policy URL without signing in and follow the homepage or footer link to it.
Expected: The link reaches the current privacy policy, and the document accurately describes the service’s actual data practices.