Privacy

What Rinhelp stores, and how analytics is scoped.

This policy covers rinhelp.com, the workspace console, and the hosted chat widget. It is written from the current product, not from a generic template. If a sentence would not survive contact with the code, it is not here.

Who this applies to

Rinhelp is operated as an independent software product at https://rinhelp.com. This notice is for people who create a workspace, teammates invited into that workspace, and visitors who chat with a Rinhelp widget on a customer’s site. Privacy requests go to hello@rinhelp.com.

Account and workspace data

When you sign up we store the name, email, and password hash needed to authenticate you. Workspaces can invite teammates by email. Session cookies keep you signed in on the console. We host on Cloudflare Workers with Postgres for application data.

A workspace also stores the website URLs you add as sources, the pages crawled from those sites, derived embeddings used for retrieval, widget appearance settings, and a publishable key for the embed snippet. Source content is the customer’s published pages, not a license to train a public model on that corpus.

Conversations

Widget chats are stored so the workspace inbox can show what visitors asked, what the agent cited, and which threads were unanswered or handed off. A handoff can collect a visitor email and an optional note for the teammate who picks up the thread. That email belongs to the workspace’s conversation record, not to a Rinhelp marketing list.

Visitor questions and agent answers stay in the workspace inbox. Conversation logs stay with the workspace that collected them.

Analytics and errors

The web console uses PostHog for product analytics. Events are workspace-scoped. They do not include email addresses, question text, answers, or full source URLs in custom properties. Session replay is enabled with input and text masking. The API emits a short list of product events (workspace created, source added, indexing completed, query submitted or answered, widget conversation started) with the same redaction.

PostHog captures browser and server exceptions so crashes can be fixed, while Cloudflare retains Worker observability and forwards structured logs to PostHog Logs. Better Stack monitors public availability and publishes service status.

Cookies, retention, and sharing

Essential cookies run authentication. Analytics cookies are used by PostHog as configured for the console.

We keep account, source, and conversation data for as long as the workspace exists, and for a short period after deletion while backups rotate. Personal information stays with the workspace and the infrastructure processors named above, and is shared if required by law. A workspace owner can ask hello@rinhelp.com for export or deletion of their account data. Visitor conversation deletion is handled with the workspace that collected it.