No terms of service link found
The homepage and a small set of conventional paths did not reveal terms of service.
Why it matters
Terms explain the conditions under which people use a service. Visitors, app stores, and payment providers may look for them, but publishing terms does not by itself establish that they are complete or legally suitable.
How ShipReady detects it
What it inspects
ShipReady examines links in the fetched homepage, then—if it finds no likely terms link—requests seven conventional paths and checks successful response bodies for the word “terms”.
What triggers a finding
The rule reports missing terms only when no homepage anchor matches its terms/legal link or text tokens and every safely requested conventional path answers without an unanswered status or a matching terms token.
What the evidence shows
The homepage’s fetched HTML did not contain a matching terms link, and none of the answered conventional paths returned a body containing the expected terms token.
Limits of this check
This is a passive, heuristic check. It does not render JavaScript, inspect every route, judge legal completeness, 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 “terms” occurrence in a successful response can count as a match even if that response is not the terms document.
How to fix it
Publish and link terms that fit your service
Prepare terms that accurately reflect how your service operates and the conditions users agree to. Seek qualified legal review where appropriate.
Publish them at a stable URL and add a clearly labelled link to the homepage or shared footer.
How to verify the change
Verify the page and link
Open the terms URL without signing in and follow the homepage or footer link to it.
Expected: The link reaches the current terms, which reflect the service’s actual operation.