Repository navigation
docs: link the shared privacy policy from the footer - #258
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Problem This Solves
Adds a discoverable link to the shared website privacy policy from the docs footer.
User Impact
Readers find Privacy policy in the existing Resources group, linking to https://openclaw.ai/privacy with the standard footer styling and navigation behavior.
Why This Change Was Made
The shared policy is intended to cover all five sites. This draft depends on the policy-coverage changes in openclaw/openclaw.ai#396 before merge.
The change adds only the link and its existing footer smoke assertion. Policy copy, layout, analytics/consent behavior, repository variables and deployment workflows are unchanged.
Evidence
npm test: 274 passed; one optional SDK test skipped.This remains a draft pending the shared policy dependency; no merge or deployment is included.