Skip to content

docs(privacy): state exactly what the site's analytics record - #339

Merged
vishr merged 1 commit into
mainfrom
docs/privacy-analytics
Oct 17, 2026
Merged

vishr merged 1 commit into
mainfrom
docs/privacy-analytics

Conversation

@vishr

@vishr vishr commented Oct 17, 2026 •

Copy link
Copy Markdown
Member

Summary

  • The privacy page said outbound link clicks record only which control was used. site/src/components/Analytics.astro also sends link_text and link_url for tagged links in the header, footer and landing page. The page now states that; copying the install command records only the control.
  • It also states what leaves a self-hosted instance: no usage reports to LabStack, but the built-in agent sends conversation content and tool results to the configured AI provider, and MCP clients receive the results of the tools they call.
  • Consent behaviour is unchanged and described as implemented: in the EEA, UK, Guernsey, Isle of Man and Jersey the analytics tag loads and stores its identifier only after a visitor allows analytics.

Split out of the larger docs refresh so the correction ships now.

Verification

  • Claims checked against Analytics.astro (click and copy handlers).
  • npm --prefix site run build with its checks; just check in the pre-push hook.

The privacy page said outbound link clicks record only which control was
used. The analytics code also sends the link text and destination URL,
for links in the header, footer and landing page. The page now states
that, and that copying the install command records only the control.

It also says what leaves a self-hosted instance: no usage reports to
LabStack, but the built-in agent sends conversation content and tool
results to the configured AI provider, and MCP clients receive the
results of the tools they call.

Claude-Session: https://claude.ai/code/session_018HfyEXHyGD1utmKF4CQtyQ
@vishr
vishr merged commit 70ce89b into main Oct 17, 2026
16 checks passed
@vishr
vishr deleted the docs/privacy-analytics branch October 17, 2026 23:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant