rivethub

Privacy

The website is not the product.

rivethub.io may record anonymous pageviews and named install-CTA clicks so we can see which pages and setup paths are useful. RivetHub and RivetOS, running on your hardware, do not phone that usage home.

This marketing site

When a PostHog project key is configured at build time, rivethub.io records pageviews: which page was opened, and when the visitor leaves. Named install-CTA clicks use fixed event strings only (cta_setup_agent, cta_install_local, cta_install_server, path_local, path_datahub, cta_cloud) plus the page path. We use that to see which setup path people choose. There is no RivetHub account on this site, and we do not collect names, emails, form fields, or other account data here. Anonymous visitors are not turned into marketing profiles. There is no session recording.

This is website analytics only. It is not product telemetry from the hub, the desktop app, or the Android app.

Your hub stays yours

RivetHub and the RivetOS runtime are software you install and run on your own infrastructure. They do not send session history, conversations, memory, or usage telemetry to us. There is no central server that sees your agents. The RivetOS privacy page covers the runtime in more detail.

Your agent providers still see the prompts you send them. Optional embedding or compaction services you configure process the content you send them. That is your configuration, not a Rivet phone-home channel.