Privacy policy

Last updated · 2026-04-23

peepshow.dev ("the site") is a static marketing site for the open-source peepshow CLI / Claude Code plugin. The site is operated by Tom Taylor (@tom_taylor). This policy covers how visitor data is handled on the site. It does not govern the peepshow command-line tool — the CLI runs entirely on your own machine and collects nothing.

What we collect

When you accept analytics cookies, two tools record aggregated traffic information:

• Self-hosted Matomo (running at st.rs.thetomtaylor.co.uk). Records: page URL, document title, referring URL, device / browser / screen size, approximate location derived from IP (truncated to country/region), visit duration, link clicks. IP addresses are anonymised (last octet discarded) before storage. No data is shared with third parties.
• Google Analytics 4 (measurement ID G-VRND18LG0L). Records: page views, events, device class, approximate location, and anonymised IP (anonymize_ip flag is always on). Google may use aggregated, non-identifying data in line with their own policy.

If you reject analytics in the cookie banner, neither tool loads — no cookies are set, no requests are made. That's the default for new visitors until you click Accept.

peepshow CLI telemetry (v0.8.0)

Separate from the marketing site, the peepshow CLI sends a single anonymous beacon per run to the same Matomo + GA4 endpoints. The payload is fixed: an anonymous machine uuid (stored in ~/.peepshow/anon-id), the peepshow version, the OS family (darwin / linux / win32), and the run outcome. No paths, filenames, video bytes, frames, transcripts, video tags, or sink payloads ever leave the machine.

Telemetry is on by default. Any of these turns it off:

• peepshow config set telemetry off — persistent, saved to ~/.peepshow/config.json.
• PEEPSHOW_TELEMETRY=0 — per-invocation env var (also accepts false / off).
• DO_NOT_TRACK=1 — honoured globally.
• Saying "no" to the first-run wizard (peepshow config init).

The same opt-outs apply to peepshow serve page analytics. Setting PEEPSHOW_ANALYTICS=0 or peepshow config set serve.analytics false suppresses Matomo and GA4 on the served pages even before the consent banner is dismissed. Refusing the banner persists the choice in localStorage per browser profile.

Sink interaction logs (~/.peepshow/sink-log.ndjson) and run history (~/.peepshow/runs/index.ndjson) are local only — never beaconed.

Full reference, every switch, and the exact payload: docs/PRIVACY.md.

What we don't collect

• No account system — there's nothing to sign up for.
• No email capture, no newsletter, no lead forms.
• No tracking pixels beyond the two tools named above.
• No session recordings, heatmaps, or fingerprinting.
• No data passed from the peepshow CLI to the site.

Cookies

See the cookies page for the full list of cookies that Matomo and Google Analytics may set on acceptance.

Your rights

You can withdraw consent at any time via the Cookie preferences link in the footer — this deletes your stored choice and re-shows the banner. You can also clear cookies + localStorage for this site in your browser, which has the same effect.

For any request relating to your data (access, rectification, erasure, portability), email hello@thetomtaylor.co.uk. Note: because all stored data is fully anonymised in aggregate, we cannot link it back to an individual visitor.

Third-party links

The site links out to GitHub, npm, X, test-videos.co.uk (CC-BY video samples), and Blender Foundation films. Those sites have their own privacy policies; peepshow.dev has no control over them.

Changes

If this policy changes, the date at the top of the page is updated and the previous version stays in the site's git history at github.com/t0mtaylor/peepshow.