Privacy
What we record, and what we never see.
Your sessions stay on your hardware. The websites count pageviews and a fixed list of button clicks, only if you accept. The runtime reports crashes and a daily anonymous count unless you turn that off. This page lists all of it.
These websites
This applies to rivethub.io, rivethub.dev and rivethub.org, which share one analytics script. Analytics run on our hosted sites only after you accept the notice; self-hosted builds without a PostHog key omit them.
Your choice comes first
Until you accept, the analytics script is not loaded. Nothing is stored in your browser for it, no source label is read, no links are tagged for analytics, and no request goes to the analytics server. A slim bar along the bottom of the page asks once, with Accept and Decline side by side. If your browser sends Do Not Track or Global Privacy Control, we treat that as a decline and do not ask. You can still turn analytics on from the footer.
The link in the footer of every page, Enable analytics or Disable analytics, changes your choice at any time. Disabling removes the anonymous visitor ID, the source label and the other analytics data from your browser, then reloads the page so nothing already under way can finish. Your choice itself is kept in your browser's storage under rivethub.analytics.consent.
One choice covers all three sites. Browsers keep each site's storage apart, so when you follow a link from one of them to another, the link adds your choice and nothing more about you: ?rh_consent=granted or ?rh_consent=declined. (After an accept, a source label you arrived with also travels, as described below.) The site it opens checks that you came from one of the other two sites, saves the choice, removes it from the address, and does not ask again. That applies to a decline as well as an accept, and to a change you make later in the footer. A decline that comes only from Do Not Track or Global Privacy Control is not carried. If you reach another of the sites some other way, for example by typing its address or following a link from elsewhere, nothing is carried: that site keeps any choice you already made there, and otherwise asks once (or, if your browser sends Do Not Track or Global Privacy Control, treats it as a decline without asking).
What is recorded once you accept
- Pageviews: which page was opened, on which of the three sites, and when you leave it.
- Named clicks: a click on a button, link or copy button that we have tagged sends its fixed name and nothing else. Copying a command records that the command was copied, never the text. The complete list of names is below.
- With each of those: the page address without its query string or fragment, the domain (not the full address) of the site that linked you here, your browser, operating system, device type, language, and screen and window size.
- An anonymous visitor ID: a random identifier that PostHog keeps in your browser's storage, so that two pageviews from one browser count as one visitor on that site. It is not shared between the three sites and is not tied to a name, an email or an account.
- A source label, sometimes: if you accepted and the link you followed ends in
?src=and one of these exact words, that word is recorded for the rest of that browser tab's visit:bluesky,blog,discord,docs,github,hn,linkedin,lobsters,mastodon,newsletter,producthunt,reddit,x,youtube. Any other value is ignored, and nothing else in the address is read. - "It worked" and "I'm stuck": the two buttons at the end of the setup guide each record one named click, if you choose to press one.
What is not recorded
- No automatic capture of clicks, typing or scrolling. Only the named clicks below.
- No session recording or replay.
- No form fields. The sites have no forms and no accounts.
- No query strings, click IDs, campaign parameters or full referring addresses. They are stripped in your browser before anything is sent.
- No advertising or cross-site tracking, and no data sold or shared for marketing.
The analytics run on our own server, a copy of the open-source PostHog at analytics.rivethub.dev. No analytics company receives the data. Our server sees your IP address with each request, as any web server does. We do not store it with events or use it to identify anyone.
Every named click
Across rivethub.io, rivethub.dev and rivethub.org:
activation_confirmed, activation_stuck, copy_agent_prompt, copy_connect_harness, copy_install_manual, copy_install_omarchy, copy_install_script, copy_mcp_config, copy_merge_store, copy_start_local, copy_verify_capture, cta_community, cta_connect_tools, cta_docs, cta_download, cta_get_started, cta_how_it_works, cta_install_steps, cta_setup_agent, cta_support, download_rh_all_releases, download_rh_linux_arm64, download_rh_linux_x64, download_rh_macos, family_dev, family_io, family_org, outbound_github, outbound_installer_source, path_datahub, path_local, support_email, support_issue, support_x
The code is public: the list and the filter that strips everything else are in design/posthog.js on each site, and tests fail if a page uses a name that is not on the list above.
Turning it off
Decline in the notice, use Disable analytics in the footer, or send Do Not Track or Global Privacy Control without having accepted on one of the three sites, and nothing is sent. A content blocker that blocks analytics.rivethub.dev works too. Every page works the same without it.
The installer and downloads
Fetching get.rivethub.io/local.sh is an ordinary web request, and our web server logs it like any other: time, IP address and user agent. The installer then downloads rh from GitHub, which keeps its own download counts. Neither is linked to anything you did on the websites.
The runtime, rh
Your sessions and memory never leave your hardware. RivetHub does not send session history, conversations, summaries or wiki pages to us. There is no account, and no central server that sees your agents' work.
From version 0.8.0, rh sends two things to rivethub.cloud unless you turn them off:
- Crash reports: the
rhversion, operating system, which part crashed, and where in our code, as module names and line numbers. The crash message, file paths, hostnames, user names and memory text are never read into a report. - A daily usage count: the
rhversion, operating system, and that day's number of searches and app opens.
Each report carries a random install ID. The service stores only a keyed hash of it, does not store IP addresses, keeps no table that links an install to a person, and deletes reports after a retention period (90 days by default).
telemetry:
disabled: trueTo disable all communication with rivethub.cloud (sign-in, crash reports, usage counts, cloud update checks and cloud sharing), install with -s -- --no-cloud (or RIVETHUB_CLOUD=off), start with rh local --no-cloud, or set cloud: {disabled: true} in ~/.rivethub/config.yaml.
The model and embedding endpoints you configure for summaries and search receive the session text you send them. That is your configuration and your choice of provider. Your agent providers, as always, see the prompts you send them.
Questions
Write to rivetphilbot@gmail.com.