Privacy & analytics

This notice covers the marketing website, operated by Robert Sreberski—not agents you run yourself or the separate documentation website.

Optional analytics are not configured in this build. No PostHog events are sent.

You choose whether to share analytics

When configured, optional analytics use PostHog’s EU ingestion service. Nothing is sent to PostHog before you choose “Allow analytics”. “No thanks” leaves analytics off. Global Privacy Control and Do Not Track signals also keep it off.

Use “Analytics preferences” in the landing-page footer to change your choice. Withdrawal stops future events; it does not erase events already received. Analytics choices are stored locally for up to 180 days. A random, per-tab session identifier is created only after consent and renewed after 30 minutes of inactivity or 24 hours total. It is not an account or a cross-device identity.

What is measured

• Page views and page departure, broad mobile/desktop viewport category, and which main sections were viewed.
• GitHub, documentation and blueprint clicks; successful install-command copies; which FAQ was opened.
• Referring hostname and short campaign tags (utm_source, utm_medium, utm_campaign) when supplied. Do not put personal information in campaign tags.

Page addresses exclude query strings and fragments. We do not capture form contents, email addresses, session recordings, account identities, or arbitrary click text. Person-profile creation and location enrichment are disabled. Like any network service, the hosting and analytics providers receive connection information, including your IP address, when a request reaches them.

Hosting and third-party links

Vercel serves this site and may process request/security logs under its own policies. GitHub and the documentation site have their own behavior when you follow a link. This site does not currently offer a newsletter signup.

PostHog privacy policy · Vercel privacy policy

Last updated: 20 September 2026.