This policy covers chat.sh: the help center, the messenger, the inbox, and the Stripe app that reads a customer's plan beside a conversation. It is written for the people who run a workspace and for the visitors who write to them.
Questions: support@chat.sh.
Who we are
chat.sh is operated by the team behind chat.sh. We process the information described here to run the service you signed up for.
Information we collect
We collect what you give us, what your visitors send through the product, and a little that the browser and our processors need in order to keep the site working.
- Account. Email address, name, and avatar when the sign-in provider sends them. A password if you choose one. The workspace you own, your role, and who you invite.
- Workspace content. Help center articles, files, settings, the messenger, and the inbox: conversations, notes, attachments, and the attributes your site sends with identify(), such as a name, email, plan, or other facts you chose to attach.
- Visitors. What a visitor types in the messenger or emails to the help center's forwarding address, plus the token that keeps their conversation. We do not put a tracking pixel on their page. Analytics on a help center, if any, are the ones you configured.
- Payments for chat.sh. If you buy a plan, Stripe processes the card. We store the Stripe customer and session ids we need to issue licenses. We do not store card numbers.
- A connected Stripe account. If a workspace owner installs the Stripe app, we store encrypted OAuth tokens for that Stripe account. When a teammate opens a conversation, we look up that person in Stripe by customer id or email, and we read their plan, subscription status, monthly amount, customer since date, and latest invoice. We do not charge, refund, or change the Stripe account. Tokens stay until an owner disconnects the app.
- Imports. If you import from Notion, Intercom, or Help Scout, we use the token or key you provide to copy collections, articles, and media into your workspace. Notion access is read-only. We do not keep those keys longer than the import needs, except the Stripe tokens above.
- Agents. If you connect Cursor, Claude, or another client through MCP, that client acts as you, in the workspaces you granted. We store the grant, not the client's own chat logs.
- Support mail. If you write to support@chat.sh, we keep the thread long enough to answer it.
The Stripe app
The Stripe app exists so a teammate answering a conversation can see the live account, not a plan the customer's website sent months ago. It only reads. The permissions it asks for are customer, subscription, price, product, coupon, and invoice, all read-only.
We match a conversation to a Stripe customer by the Stripe customer id your site sent, or by email. We cache that lookup for about a minute. We do not sell Stripe data, use it to train a public model, or show it outside the workspace that connected the account. A card in the inbox appears only when Stripe has a plan that is being billed, including a trial.
An owner disconnects the app from Integrations. That deletes the tokens. Uninstalling the app in the Stripe Dashboard also ends access; disconnect from chat.sh as well so the stored tokens go.
How we use it
- To run the help center, messenger, and inbox you opened.
- To sign you in, keep you signed in, and send mail you asked for.
- To bill chat.sh itself, and to show Stripe billing beside a conversation when you connected that account.
- To draft answers and sort the inbox. That sends the relevant article or conversation to the model providers we use (today Anthropic, through OpenRouter, and OpenAI).
- To see, in aggregate, whether the marketing site is working. That is Simple Analytics on chat.sh. It does not use cookies and is not tied to an account.
We do not sell personal information. We do not use a visitor's messages to advertise to them.
Who we share it with
Processors that run parts of the service, under their own terms, only as needed for that part:
- Supabase, for sign-in, the database, and files.
- Stripe, for chat.sh payments and, if you install the app, for reading your Stripe account.
- OpenRouter, Anthropic, and OpenAI, for answers, embeddings, and inbox drafts.
- Resend, for email we send on your behalf.
- Simple Analytics, for visits to chat.sh.
- Vercel, for hosting.
- Notion, Intercom, or Help Scout, only when you start an import from them.
A teammate you invite sees the workspace. An agent you connect sees what its grant allows. We share information if the law requires it, and we will tell you when we can.
Cookies
- Sign-in cookies, so the dashboard knows who you are.
- A first-touch cookie on chat.sh (
chatsh_src), kept up to 90 days, so we know which campaign a signup came from. It is not used for ads. - A timezone cookie, so timestamps in the inbox match your clock.
The messenger on a customer's site uses a token to find the visitor's conversation. That is how replies reach the same person, not a third-party ad cookie.
How long we keep it
Account, workspace, and conversation data last as long as the workspace does. Delete the workspace, or write to support@chat.sh, and we remove what we can from our systems. Stripe tokens go when you disconnect. Backups expire on their own cycle. Model providers keep prompts only as their own policies say.
Your choices
- Correct your email and name in the account menu.
- Disconnect Stripe, Notion, or an MCP client from the dashboard.
- Ask a visitor's data to be deleted; we will do that in the workspace you name.
- Email support@chat.sh to export or delete an account. We will ask enough to be sure it is you.
If you are in the EEA, UK, or a similar regime, you can also object to processing, restrict it, and complain to a supervisor. We process workspace data to provide the contract you signed up for, and a little of it (sign-in, security, first-touch) because we have a legitimate interest in running and understanding the product.
Children
chat.sh is for teams running a product. It is not directed at children under 16, and we do not knowingly collect their information.
Changes
If this policy changes in a way that matters, we will update this page and the date above. The current version is always at https://chat.sh/privacy.