Privacy
What rness.dev collects (no cookies, analytics in the EU), what the command sends (nothing), and whom to ask.
This note says, in plain words, what the site at rness.dev and its documentation collect. There is no account to create, no form to fill and no cookie. The note was last updated on 2026-10-01; it changes with the site.
Analytics without cookies
The site and the docs measure their audience with PostHog, hosted in the European Union and loaded without cookies: nothing is written to your browser. Visitors are counted with a hash that PostHog computes on its servers from your IP address, your browser's description and the day; it changes every day and is stored nowhere on your side. The requests go to PostHog through rness.dev/rly, an address of this site.
What an event holds: the page viewed, the page that linked to it, the utm_* parameters of the link you followed and, for a click, which control it was: the install command copied (and which package manager), a documentation or GitHub link (and where on the page), the demo played or paused, a code block copied in the docs (and which page). No text you type, no form field, no name, no email: nothing identifies a person.
Not collected: session recordings, heatmaps, surveys, the content of the page you see.
Errors
When the site breaks in your browser, the error (its message, its stack trace and the page) is sent to PostHog's error tracking, so that it can be fixed.
The command
The rness command collects nothing and sends nothing to us: no usage data, no telemetry. It talks to GitHub, to npm and to your git remotes for the operations you run, with your own credentials, which stay on your machine.
Hosting
The site and the docs are served by Vercel, which handles every request to rness.dev.
Questions
Write to hello@rness.dev.