Privacy policy
RoomChime runs live audience polls. This policy describes what we collect from hosts, who create events and open rooms, and from guests, who answer in a room. It covers roomchime.com, its rooms and its connector for AI assistants.
- Hosts
- Guests
- Billing
- Technical data
- AI assistants
- How we use data
- Processors
- Retention
- Your choices
- Contact
Hosts
Your account
You sign in through WorkOS AuthKit, our sign-in provider. Your email address, your name and your credentials stay with WorkOS. Our own database keeps only your WorkOS user id, a RoomChime user id, a workspace id and the times they were created.
When you sign in, WorkOS gives us a sealed session. We keep it on our servers for at most 30 days and give your browser a cookie that points to it.
Cookies
| Cookie | Purpose | Lasts |
|---|---|---|
rc_session |
Keeps a host signed in to the studio | 30 days |
rc_auth_state |
Protects a sign-in while it is in progress | 10 minutes |
rc_guest_<room> |
Lets a guest rejoin the same room | 7 days |
All three are strictly necessary. We use no advertising or analytics cookies.
What you create
We store the events you create: titles, questions, options, private host notes and settings, up to 200 events per workspace. When you open a room, we keep a frozen copy of the event, the room code and the times the room opened and ended.
Guests
Guests do not create an account. When you join a room, we keep:
- A random credential for that room. We store only its SHA-256 hash.
- Your answers.
- A name of 1 to 40 characters, only when the host asks for names. It is optional unless the host makes it required.
- An email address of up to 200 characters and a note of up to 1,000 characters, only when the host asks for them. This form appears after the room ends, and you can skip it.
The host sees totals, and sees names, emails and notes when they asked for them. Other guests never see your answers. Phones show no totals.
Billing
Paid plans are sold through Stripe. Stripe Checkout and the Stripe customer portal collect your card, billing name, address, email and any tax id. Card details never reach RoomChime.
We keep the Stripe customer and subscription ids, the price, the subscription status, the period and cancellation dates, a link to the last invoice, the time of any failed payment and the ids of the Stripe events we have processed.
Technical data
- Operational logs record the operation, the method, the status, the duration and a random request id. They never record request bodies, full URLs, cookies or IP addresses.
- Rate limits count requests by a hash of the connecting IP address, inside Cloudflare's rate limiter. We do not store the address.
- Your browser keeps some state on your device. Local storage holds studio drafts that are not yet saved and your layout choices. Session storage holds the room a guest joined, whether a guest skipped the name prompt, and a key that stops a checkout from being started twice.
AI assistants
A host can connect RoomChime to an AI assistant, such as Claude or ChatGPT, through our MCP connector. When they do:
- RoomChime receives the arguments of each tool call and a sign-in token. We check the token on every call and do not store it. We never receive the conversation, the assistant's memory or the host's files.
- Tool results, which can include results from the host's rooms, go to the host's AI client. That provider handles them under the host's own agreement with it.
- Guests' emails and notes are returned only when the host's assistant asks for them with a separate tool.
- RoomChime does not call any AI model and uses no AI provider.
How we use data
We use data only to run RoomChime, keep it secure, bill for it and answer support requests. We do not show ads, we do not sell or share personal data for advertising, and we do not use your content or guests' answers to train AI models.
Processors
| Company | What it does for RoomChime |
|---|---|
| Cloudflare | Hosting, the database, room storage, logs, rate limits and email routing |
| WorkOS | Host sign-in |
| Stripe | Payments, invoices and the billing portal |
An AI client a host connects acts at the host's direction, not as our processor.
Retention
- Events and rooms stay until the host deletes them. There is no automatic expiry yet. Plan limits on how long a report stays open limit access, not storage.
- Deleting a room removes its answers, names, emails and notes from our application stores. We keep a minimal record of ids and times so the room cannot be recreated.
- Deletion does not reach copies already downloaded, such as a CSV, or provider backups before they expire.
- To delete a whole account, write to privacy@roomchime.com. We complete account deletion within 30 days.
- Stripe keeps billing records as the law requires for payments.
Your choices
You can ask for a copy of your data, a correction or deletion by writing to privacy@roomchime.com. A host can delete a room from run history at any time. A guest who wants their answers removed can ask the host, or write to us with the room code and the time of the room.
Children
RoomChime is not directed at children under 13. A host who runs a room with minors, such as a class, must have the authority to do so, and should keep names off or ask for first names only.
Security
Traffic is encrypted, each workspace is isolated, guest credentials are stored only as hashes, and access links expire. To report a vulnerability, see security reports.
Changes
When this policy changes, we update the date below. We describe a material change on this page before it applies.
Contact
Privacy questions and requests: privacy@roomchime.com. Everything else: support@roomchime.com.