Privacy policy
Last updated: November 13, 2026
This document is from Kaumô (“Kaumô”, “we”, “us”). This Policy explains how we process personal data on the website, in the dashboard and in the moderation service, in line with the Brazilian General Data Protection Law (Law 13,709/2018, LGPD).
In short: we do not store your chat messages. Each message is checked on the spot and discarded. We only keep an excerpt of the messages that triggered a moderation action, for your team's log.
1. Who is responsible for the data
There are two different roles:
- Controller: for the data of people who have a Kaumô account (streamers, moderators, website visitors), we decide how the data is processed.
- Processor: for the messages and data of people taking part in the chat of a connected channel, the streamer who connected the channel decides. We process that data on their behalf, following their dashboard settings.
Data protection officer: contact@kaumo.app.
2. What data we process
| Category | What it is | Where it comes from |
|---|---|---|
| Account | Email, password (stored only in encrypted form), account identifier and, if you sign in with Twitch, Google or Discord, the name, picture and email supplied by that provider. | You and the sign-in provider |
| Workspace and team | Workspace name, rules, punishment ladder, lists (blocked terms, trusted users, allowed links), members, roles and invites. | You and your team |
| Connected channels | Channel identifier and name on Twitch or Kick, permissions granted and access tokens, stored encrypted in a vault. | The platform, with your authorization |
| Chat messages | Message text, the author's name and identifier, and their chat roles (moderator, VIP, subscriber). Processed in memory for checking and not stored. | The platform, in real time |
| Moderation log | For each message that triggered an action or went to review: an excerpt of up to 500 characters, author, rule triggered, action, the AI's confidence, date, and who undid or reviewed it. | Generated by Kaumô |
| Usage | Daily count of messages and checks per workspace, for the allowance and billing. | Generated by Kaumô |
| Billing | Plan, currency, subscription status, Stripe customer identifier and invoice history. Card details stay with Stripe only. | You and Stripe |
| Dashboard assistant | The questions you ask the assistant and the workspace context used to answer (rules, settings and figures from recent days). | You |
| Technical data | IP address, browser and device type, pages visited, date and time, and error records. Error records do not include chat message text. | Your browser and our servers |
| Usage analytics | With your permission, browsing events linked to an identifier stored in a cookie and, in the dashboard, if an error happens, a recording of that session, with input fields and sensitive data on screen (emails, documents, card details and webhook addresses) masked: nothing you type is recorded. Without permission, anonymous counting only, with no cookies and no recording. | Your browser |
| Service events | Account usage milestones, linked to the account identifier: channel connection, subscription and use of a promo link. No chat text or email. | Generated by Kaumô |
We do not ask for or intentionally process sensitive personal data. Chat messages may contain that kind of information at the initiative of whoever writes them; they are checked and discarded like any other message.
3. Why we use it and on what legal basis
| Purpose | Legal basis (LGPD) |
|---|---|
| Create and maintain your account, connect channels, moderate chat according to your rules and show activity to your team | Performance of a contract (art. 7, V) |
| Charge the subscription and overage, issue invoices and prevent payment fraud | Performance of a contract (art. 7, V) and legal obligation (art. 7, II) |
| Send service notices: allowance at 80% and 100%, post-stream summary, billing, security and changes to the Terms | Performance of a contract (art. 7, V) and legitimate interest (art. 7, IX). Allowance notices and the summary can be turned off in the dashboard. |
| Keep the service secure, investigate abuse, fix errors and measure usage in aggregate | Legitimate interest (art. 7, IX) |
| Understand how accounts use the service (channel connections, subscriptions) to improve the product | Legitimate interest (art. 7, IX) |
| Usage analytics with cookies and masked recording of the dashboard screen when an error happens | Consent (art. 7, I), which you can withdraw at any time |
| Keep access records and tax documents | Legal obligation (art. 7, II) |
| Moderate the messages of people taking part in chat | The streamer's legitimate interest in keeping the community safe (art. 7, IX). Kaumô acts as processor. |
We do not sell personal data, we do not use chat messages for advertising, and we do not use them to train artificial intelligence models.
4. Automated decisions
Moderation involves automated decisions: the AI estimates the chance that a message breaks a rule and Kaumô applies the action the streamer configured. These decisions only have effect within the channel's chat.
Every action is logged with the rule and confidence, can be reviewed by a person on the channel's team and can be undone. Anyone affected can ask the streamer or the channel's moderators for a review, or write to us and we will forward the request.
5. Who we share data with
We use suppliers that process data on our behalf, only for the purposes below and under contract:
| Supplier | What for | Data involved |
|---|---|---|
| Supabase | Database, sign-in and credentials vault | Account, workspace, channels, moderation log, usage |
| Railway and Cloudflare | Servers that receive chat (Railway) and serve the website and dashboard (Cloudflare) | Messages in transit, technical data |
| TypeSafe (Jev model) and OpenAI | AI checking of messages and the dashboard assistant's answers | Message text, the author's name, recent chat messages as context and your rules; questions to the assistant |
| Stripe | Payments and invoices | Billing and card data |
| PostHog | Usage analytics, error tracking, server technical logs and masked recording of the dashboard screen when an error happens | Technical data, browsing and service events, account identifier, masked recording |
| Resend | Sending service emails | Email, workspace name and notice content |
| Twitch and Kick | Receiving chat and carrying out moderation actions | Channel, message and user identifiers, action and reason |
| Discord | Alerts for your team, only if you set up a webhook | Message excerpt, author, rule and action |
| Google Fonts | Fonts for the website and dashboard | IP address and browser data |
We may also share data to comply with the law, a court order or a request from a competent authority, to protect our rights and those of third parties and, in a merger, acquisition or sale of assets, with the successor, which will be bound by this Policy.
Members of your team see the workspace's activity according to the role you gave each of them.
6. International transfers
Several of these suppliers are located in the United States or other countries. When data leaves Brazil, the transfer is made with the safeguards provided for in the LGPD (arts. 33 to 36), such as data protection contractual clauses, and only for the purposes of this Policy.
7. How long we keep it
| Data | Period |
|---|---|
| Chat messages | Not stored. They stay in memory only during checking. The most recent messages of each channel are held in memory only, as context, and are replaced by the following ones. |
| Moderation log | For as long as the workspace exists. It is deleted when the workspace is deleted, or earlier at the owner's request. |
| Account, workspace and channels | While the account is active. A channel's tokens are deleted when it is disconnected. |
| Billing and tax documents | For the period required by tax law and for the defense of legal claims, generally 5 years. |
| Access records | At least 6 months, as required by Brazil's Internet Civil Framework (Marco Civil da Internet). |
| Usage analytics and errors | For as long as needed for the purposes described, and then deleted or anonymized. Screen recordings after an error: up to 30 days. Server technical logs: up to 14 days. |
After that period, data is deleted or anonymized. Backups may keep data for a limited additional period, until they are overwritten.
8. Cookies and similar technologies
On your first visit, we ask whether you accept analytics cookies. Before you choose, we only count the visit anonymously, with no cookies and no identifier stored on your device, as when you decline. You can change your mind at any time under “Cookie preferences”, in the website footer and in the dashboard's Settings.
| Item | Type | What for | Duration |
|---|---|---|---|
| Sign-in session (browser local storage) | Necessary | Keep you signed in to the dashboard | Until you sign out |
| kaumo:prefs and kaumo:* keys (local storage) | Necessary | Remember language, currency, open workspace and steps already completed | Until you clear your browser |
| kaumo_consent (cookie) | Necessary | Store your cookie choice | 6 months |
| PostHog cookies and storage (ph_*) | Analytics, only with your permission | Understand how the website and dashboard are used and fix errors | Up to 1 year |
| Stripe cookies (on payment pages) | Necessary | Process the payment and prevent fraud | Set by Stripe |
If you decline, we count visits anonymously, with no analytics cookies and no identifier stored on your device; only your refusal is recorded. We do not use advertising cookies. The masked recording of the dashboard screen, only when an error happens, depends on your permission.
9. How we protect data
- Encrypted connections (HTTPS) for all traffic.
- Platform tokens stored encrypted in a vault, read only by the moderation service.
- Each person only sees the workspaces they belong to, with access rules enforced in the database.
- Platform and Stripe webhooks accepted only with a valid signature.
- Internal access restricted to those who need it to run the service.
No system is completely secure. If there is an incident that may cause relevant risk or harm, we will notify the people affected and the Brazilian data protection authority (ANPD), as the LGPD requires.
10. Your rights
Under the LGPD (art. 18), you may at any time request:
- confirmation that we process your data, and access to it;
- correction of incomplete, inaccurate or outdated data;
- anonymization, blocking or deletion of data that is unnecessary or processed unlawfully;
- data portability;
- deletion of data processed on the basis of your consent;
- information about who we share your data with;
- withdrawal of consent, and an explanation of the consequences of not consenting;
- review of decisions made solely by automated means.
To exercise these rights, write to contact@kaumo.app. We reply within 15 days. We may ask for information to confirm your identity. If you live in the European Economic Area, the United Kingdom or another place with its own data protection law, you have the equivalent rights under that law and can use the same contact.
If you take part in a channel's chat and want to know, correct or delete your data in the moderation log, the request should go to the streamer responsible for the channel. If you write to us, we will forward the request and help the streamer respond.
You can also complain to the ANPD (gov.br/anpd) or to your local data protection authority.
11. Children and teenagers
Kaumô is purchased by people aged 18 or over and is not directed at children. Younger people may take part in a channel's chat, according to each platform's age rules; in that case we process only what moderation requires, as described above.
12. Changes to this Policy
We may update this Policy. The date at the top shows the version in force. We will announce material changes by email or in the dashboard before they take effect.
13. Contact
Questions about privacy or this Policy: contact@kaumo.app.