1. Who is responsible for your data
ConverseKit is software that other businesses install on their websites. That makes two different organisations responsible for different things, and which one you need depends on who you are.
If you chatted with a ConverseKit widget on some company's website, that company is the data controller. They decided to collect your information, they decide what to do with it, and they are who you should contact first about it. ConverseKit is the data processor: we store and transmit that data under their instructions and do not use it for our own purposes. We will still help — see Your rights — but if you ask us to erase something we will normally act on the instruction of the business whose widget you used.
If you have a ConverseKit account, we are the controller for your own account data (section 2c).
ConverseKit is operated by Mukerem Shifa. Contact details are in section 13.
2. What we collect
a. What you type into a chat widget
Every message you send to a ConverseKit chat widget, and every reply it sends back, is stored as a transcript. If you volunteer personal details in conversation — your name, your email address, your phone number, what you are asking about — those are stored too, both inside the transcript and, where the business has switched on lead capture, as a separate contact record they can export.
The widget has no form fields and asks for nothing up front. It only ever holds what you chose to type, so please do not type anything into a chat widget that you would not want the business running it to read.
b. Technical data
- A session identifier. Issued and signed by our server, valid for 7 days, and used to keep one conversation together so the bot can follow what you said a moment ago. It is not linked to any profile of you and does not follow you to other websites.
- Your IP address, used transiently for rate limiting — stopping one source from flooding the service. It is not written into the transcript or the contact record.
- Your question, logged for search quality. When the bot searches a business's documents to answer you, the question is logged verbatim along with whether the search found anything, so the business can see which questions their bot cannot answer. This log is deleted after 90 days.
- Usage counters. Token counts per AI call, for billing. Numbers only — no message text.
c. Account data (ConverseKit customers)
If you sign up, we store your email address, an authentication record, your organisation name, and the configuration of the bots you create — including any documents you upload as knowledge for your bot to answer from.
d. What we do not collect
No advertising trackers, no analytics pixels, no third-party cookies, no cross-site profiling, and no fingerprinting. We do not sell personal data, and we do not share it for cross-context behavioural advertising, under any definition of "sell" or "share" including those in California law.
3. Why we process it, and on what legal basis
| Data | Purpose | Legal basis (UK/EU GDPR) |
|---|---|---|
| Chat messages | Answering your question; letting the business review what their bot said | Legitimate interests of the business operating the widget |
| Contact details you volunteer | Letting the business respond to your enquiry | Legitimate interests, or your consent where the business asks for it |
| Session identifier | Keeping one conversation together | Strictly necessary for a service you requested |
| IP address | Rate limiting and abuse prevention | Legitimate interests (service security) |
| Search-quality log | Showing a business which questions their bot fails | Legitimate interests (service improvement) |
| Account data | Providing the service to a customer | Performance of a contract |
A note on consent, stated plainly. A business can configure their bot to ask for your agreement before recording your contact details, and we record that the bot was instructed to ask. That flag is not proof that you agreed: there is no checkbox in the widget, and we cannot verify what the model actually said or how you replied. We do not present it as consent, and neither should any business relying on it.
4. AI providers
To answer you, your message — along with recent messages in the same conversation and any relevant passages from the business's own documents — is sent to an AI provider, which generates the reply.
Which provider depends on the business whose widget you are using. Each one chooses from a list that currently includes OpenAI, Anthropic, Google (Gemini and Vertex AI), Groq, OpenRouter, DeepSeek, Mistral, Together AI, Cloudflare Workers AI, self-hosted options (Ollama, LM Studio), and any OpenAI-compatible endpoint they configure themselves. Because the choice is theirs, the business operating the widget is who can tell you which provider received your message, and the current list with links to each provider's own terms is at Sub-processors.
We instruct providers not to train on this data and select API tiers where that is the contractual default. We cannot independently audit them, and where a business configures a custom or self-hosted endpoint, that endpoint is outside our control entirely.
5. Who else sees your data
- The business running the widget — they can read every transcript and export the contact records.
- Our infrastructure providers — Cloudflare (hosting, and the network your request travels over) and Supabase (the database). Listed with details at Sub-processors.
- The AI provider chosen by that business (section 4).
- Anywhere a business forwards their own leads. A business can configure a webhook so new contact records are posted to a system of their choosing. What happens there is governed by their privacy policy, not this one.
- If the law requires it — a valid legal order, or to establish or defend legal claims.
6. How long we keep it
| What | Kept for | Why |
|---|---|---|
| Chat transcripts | 180 days, then deleted automatically | Long enough for a business to look into a complaint about what their bot said |
| Contact records (leads) | Until erased or deleted by the business | A business record the business is entitled to keep; not deleted on a timer |
| Search-quality log | 90 days, then deleted automatically | Shorter, because it holds what you typed and needs no longer |
| Usage counters | 400 days | Billing history; contains no message text |
| Account and bot configuration | While the account is open | Needed to provide the service |
The 180-day and 90-day deletions are automatic and run daily. When a business deletes a bot, everything that bot ever recorded goes with it.
Backups. Deleted data may persist in our database provider's encrypted backups for a short period after deletion before those backups roll over. We do not restore backups to recover data that was deliberately erased.
7. Your rights
Depending on where you live, you may have the right to access a copy of your data, correct it, have it erased, restrict or object to how it is used, receive it in a portable format, and complain to a regulator. Under GDPR these are Articles 15 to 22; California residents have comparable rights under the CCPA/CPRA, including the right not to be discriminated against for exercising them.
How to exercise them. Contact the business whose chat widget you used — they are the controller and can act on your request directly. If you cannot identify or reach them, contact us at mukeemoha@gmail.com and we will help identify the right business or act on their instruction.
Erasure works at the level of one conversation. A business can erase a single visitor's session, which deletes that conversation's transcript and the contact record captured from it together, in one action. We built this specifically so answering an erasure request does not require deleting anything belonging to anyone else.
One honest limitation. The search-quality log (section 2b) stores questions without a session identifier attached, so it cannot be searched for one person's entries and is not covered by that erasure action. It deletes itself after 90 days, which is sooner than transcripts. We would rather state this than imply an erasure reaches further than it does.
We respond within 30 days. We do not charge for this, and we may ask for enough information to locate your data — usually the website you used and roughly when.
8. Browser storage
The chat widget sets no cookies. It stores one
value, the session identifier described in section 2b, in your
browser's sessionStorage — which your browser
clears when you close the tab. It is strictly necessary to hold a
conversation together and is not used for tracking, so under the
EU ePrivacy Directive and the UK PECR it falls within the
strictly-necessary exemption and does not require a consent
banner.
Our own website and dashboard store your light/dark theme preference locally in your browser. That never leaves your device.
9. Security
Data is encrypted in transit (TLS) and at rest. Each business's data is isolated at the database level by row-level security keyed to organisation membership, rather than by application code that a future change could quietly drop. Each bot is locked to an explicit list of websites it will answer from, and a request from anywhere else is refused before any AI provider is called. Access to production systems is limited to personnel who need it.
No system is perfectly secure. If a breach affects your personal data we will notify the affected businesses and, where the law requires, the relevant regulator and you.
10. International transfers
Our infrastructure runs on globally distributed networks, and the AI providers listed in section 4 operate in various countries including the United States. Your data may therefore be processed outside the country you live in. Where data leaves the UK or EEA, transfers rely on Standard Contractual Clauses or an adequacy decision, as offered by the provider concerned.
11. Children
ConverseKit is a business tool and is not directed at children. We do not knowingly collect personal data from anyone under 16. If you believe a child has provided personal data through a chat widget, contact us and we will delete it.
12. Changes to this policy
We will update the date at the top when this policy changes. For changes that materially affect how we handle personal data, we will notify account holders by email before the change takes effect.
13. Contact
Privacy questions, data requests, or anything else about this policy: mukeemoha@gmail.com.
If you are in the UK or EEA and are unhappy with how we handled your request, you have the right to complain to your local data protection authority. In the UK that is the Information Commissioner's Office at ico.org.uk.
See also Terms of Service and Sub-processors.