MooseChat is an AI chat widget for small-business websites. This page says what MooseChat keeps about the people who use it, why, for how long, and who else handles it.
MooseChat is operated by Mohammad Yusuf Khan (“MooseChat”, “we”). Questions about this policy go to support@getmoosechat.com.
Two kinds of people
Account holders are the businesses and agencies who sign up, and their team members. For their account data, MooseChat is the controller.
Visitors are people who chat with a MooseChat widget on a business’s website, or on its share page. What a visitor types belongs to that business: the business is the controller and MooseChat processes it only on the business’s behalf, to run the service for it. A visitor who wants their chat or contact details deleted should ask the business whose website they used. MooseChat will help the business do it.
What MooseChat keeps about account holders
- Account: name, email address, and a hashed password, or the Google account used to sign in.
- Workspace: its name, members and their roles, its plan, its timezone, and settings.
- Billing: the plan and its state. Payments are taken by Dodo Payments, the merchant of record, who holds the card details. MooseChat never sees a card number.
- Content: the websites a bot is built from, the files uploaded to it, the Q&A pairs and business details entered in the dashboard.
- Usage: conversation and lead counts, and the model cost of each workspace.
- Security records: an audit log of member, key, bot, destination, client and plan changes; API keys, stored only as a hash.
What MooseChat keeps about visitors
- The conversation: what the visitor typed, the bot’s replies with the pages it cited, and the page the chat started on. Transcripts and their two-line summaries are encrypted at rest with a key for the business’s workspace.
- Contact details the visitor chooses to send: the lead form’s fields (usually a name, an email address or phone number, and a message). These are encrypted at rest too; the name, email address and phone number are also kept in clear so the business can search its inbox.
- Technical data: a random visitor identifier and the IP address, both kept only as salted hashes, used to hold a conversation together across pages and to apply the rate limits; the country and the browser family, for the business’s analytics.
- Questions: each question, encrypted, grouped with similar ones so the business can see what its bot couldn’t answer.
The widget sets no cookies. It keeps the visitor identifier, the open conversation and any contact details waiting to be resent in the browser’s local storage on the business’s website (cookies).
Why
To run the service: answer visitors from the business’s own content, pass leads to the business, show the business its conversations and gaps, bill the plan, send the emails the account asks for, and keep the service safe from abuse. MooseChat does not sell personal data, does not use it for advertising, and does not train AI models on it.
How answers are written
A visitor’s question and the relevant passages from the business’s content are sent to an AI model provider to write the reply: OpenAI, or Anthropic if OpenAI is unavailable. Requests go through Cloudflare’s AI Gateway with its logging switched off.
How long
- Transcripts: 12 months from the conversation, then deleted automatically.
- Question history: as long as the plan’s analytics history (14 days on the trial, 90 days on Solo, 12 months on Pro and Agency), then deleted.
- Leads: until the business deletes them.
- A bot’s content, files and conversations: deleted within 24 hours of the bot being deleted.
- Account and workspace data: until the account is deleted. To delete an account, write to support@getmoosechat.com.
- Billing records: as long as tax law requires.
Who else handles it
| Subprocessor | What for |
|---|---|
| Cloudflare | Hosting, the database and file storage, AI Gateway, text embeddings and reranking, rendering JavaScript websites, converting uploaded files, and the bot challenge shown during traffic floods |
| OpenAI | Writing replies |
| Anthropic | Writing replies when OpenAI is unavailable |
| Google sign-in when an account holder chooses it, measuring visits to getmoosechat.com with Google Analytics, and which visit led to a sign-up (the visit’s Analytics id, never the email) | |
| PostHog | Product analytics for account holders: which features are used, and recordings of dashboard screens that hold no visitor data (paused on conversations, leads and other screens with visitors’ data). United States region |
| Postmark | Sending email: account email, lead notifications and the weekly digest |
| Dodo Payments | Taking payments, as merchant of record |
Where the data is stored: on Cloudflare’s network, and with the subprocessors above, mainly in the United States.
Security
Traffic is encrypted in transit. Transcripts, summaries and lead details are encrypted at rest with a key for each workspace. Visitor identifiers and IP addresses are stored only as salted hashes. API keys are stored only as hashes and shown once. Access to production is limited to the operator.
Your rights
Depending on where you live, you can ask to see, correct, export or delete personal data, or object to how it is used. Account holders can do most of this in the dashboard, or by writing to support@getmoosechat.com. Visitors should write to the business whose website they used; MooseChat will act on the business’s instruction. You can also complain to your data protection authority.
Children
MooseChat is not meant for children, and account holders must be adults. A business whose website is aimed at children must not use MooseChat on it.
Changes
The date at the top is when this policy last changed. A material change is announced to account holders by email before it takes effect.
Contact
Write to support@getmoosechat.com.