No terms of service link found
No link to a terms of service was found on the homepage, and the conventional paths (/terms, /terms-of-service) did not resolve to one.
Why it matters
No link to a terms of service was found on the homepage, and the conventional paths (/terms, /terms-of-service) did not resolve to one. Published terms are something visitors and app stores commonly look for, and the absence is a frequent gap in quickly-shipped apps. If one exists at an unconventional URL or is added by client-side code it may not be visible to a passive scan — link it from your footer so it is easy to find.
How ShipReady detects it
Presence of the two policy documents almost every site is expected to publish. Origin-scoped: the footer that links these is served on every page including the homepage, so reading the seed once — plus a small, content-confirmed probe of the conventional paths — is enough. Absence findings carry MEDIUM confidence and name their own limit ("across the homepage and common paths"), because a passive read cannot see a link injected by client-side JS or one at an unconventional URL.
Detection is deterministic. ShipReady reports this only when it observes the condition directly, and prefers to miss a real problem over inventing one. Rule version 1.0.0.
How to fix it
This is the prompt ShipReady puts in your report — written to be pasted straight into Cursor, Claude Code, or whichever assistant built the app.
No terms of service link was found on your homepage and the conventional paths (/terms, /terms-of-service) did not resolve to one. Publish your terms of service (the agreement between you and your users) and link it from your global footer. If you already have one at a different URL, add a footer link so it is easy to find. This is product/legal hygiene rather than a security issue — prioritise it accordingly.
Frequently asked questions
- What does "No terms of service link found" mean?
- No link to a terms of service was found on the homepage, and the conventional paths (/terms, /terms-of-service) did not resolve to one.
- How serious is it?
- ShipReady rates this low. Worth fixing. Small individually, and they accumulate.
- How do I fix it?
- Paste the fix prompt on this page into Cursor, Claude Code or your AI editor. It is the same prompt ShipReady puts in your report.
- Can I check my own site?
- Yes — ShipReady scans up to ten pages of any public site for free and reports this alongside every other check. The free report lists every issue it finds and shows full evidence and a fix prompt for the critical and high-severity ones; medium and low findings are counted and unlock on Pro.
Related checks
- No privacy policy link foundmedium
- A device-fingerprinting script is presentmedium
- A form collecting personal data submits via GETmedium
- Session-replay or behaviour-recording script is presentmedium
- Tracking cookie is set before the consent banner can be answeredmedium
- Tracking cookie is set on the first responsemedium
Run this check on your site
ShipReady checks this and 193 other things across up to ten pages of your site, with an AI-ready fix for each. Free, no signup.