Link to your terms of service in the footer

SkillWeb & browsing

Terms-of-service is a skill for AI agents that reviews whether a website or web application has a visible Terms of Service link accessible from every page. It checks the footer on all pages, verifies that registration includes an explicit acceptance step, and explains how terms become enforceable.

Available today. Use it from your connected AI after setup.

Have an AI agent that can load and use agent skills.

Then ask your AI: use the Link to your terms of service in the footer skill

What your AI can do with it

  • Check that the site footer contains a Terms of Service link on every page, including inter
  • Verify that user registration includes a checkbox or explicit acceptance step for the term
  • Confirm the terms page has a stable URL
  • Explain browsewrap versus clickwrap agreements and why terms must be discoverable before u
  • Review server config, headers, and forms for responses or behaviors that violate the rule

Getting started

  1. Have an AI agent that can load and use agent skills.
  2. Add the terms-of-service skill to the agent's available skills.
  3. Ask the agent to review a website or web application for a visible Terms of Service link on every page.
  4. Review the agent's findings on footer links, registration acceptance steps, and the terms page URL.

What this skill tells your AI

The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/terms-of-service/SKILL.md and read by ahel’s review.

Terms of Service protect your business by limiting liability, establishing jurisdiction, setting rules for user conduct, and specifying your rights to user-generated content — but only if users could reasonably discover and read them.

Quick Reference

  • Link to Terms of Service from the site footer on every page
  • Terms of Service (ToS) are not legally required in most jurisdictions, but they are best practice for any service with user accounts
  • Courts have found ToS unenforceable when they were not clearly presented or linked before the user took action
  • For enforceable acceptance, require users to check a checkbox 'I agree to the Terms of Service' during signup
  • Keep terms up to date — outdated terms that contradict current practices can create legal liability

Check

Check whether the website footer contains a link to a Terms of Service page. Verify the link is present on all pages including interior pages. Check that during user registration there is a checkbox or explicit acceptance step for the terms.

Fix

Add a 'Terms of Service' link to the site footer on every page. For services with user accounts, add an explicit acceptance checkbox during registration that links to the terms. Ensure the terms page has a stable URL.

Explain

Explain what Terms of Service are for, why they need to be discoverable before a user takes action, and the difference between browsewrap (just a link) and clickwrap (explicit acceptance) agreements.

Code Review

Review server config, headers, forms, and integration points related to Link to your terms of service in the footer. Flag exact responses, cookies, or browser behaviors that violate the rule, and verify them against the effective production-like response.


For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/en/rules/security/terms-of-service

Signals

GitHub stars
74k
Forks
7k
Last commit
Aug 2026

Questions

Are Terms of Service legally required?
ToS are not legally required in most jurisdictions, but they are best practice for any service with user accounts. Courts have found them unenforceable when not clearly presented or linked before the user took action.
How do I make the terms enforceable?
Require users to check a checkbox saying 'I agree to the Terms of Service' during signup, and keep the terms up to date so they do not contradict current practices.
What should I fix if the check fails?
Add a 'Terms of Service' link to the site footer on every page, add an explicit acceptance checkbox during registration for services with user accounts, and ensure the terms page has a stable URL.
Advanced
Item type
skill
Key
terms-of-service
Source
github.com/thedaviddias/front-end-checklist