Privacy Policy

Last updated: September 5, 2026

1. Introduction

MiaCat ("the Bot") is a Discord bot operated by its developer for the SealStats Discord community. In this policy, "we", "us" and "our" mean the MiaCat team.

This policy explains what information the Bot collects when you use it in a Discord server or in direct messages, how we use and share that information, how long we keep it, and how you can see, correct or delete it. It also covers the websites that go with the Bot (Section 5.5).

  • The current version is always published at https://docs.miacat.ai/privacy. Our Terms of Service are published at https://docs.miacat.ai/terms.
  • The Bot runs on Discord and is subject to Discord's Terms of Service and Developer Policy. This policy does not cover Discord itself, which has its own privacy policy, and it never overrides Discord's terms.
  • The Bot holds cryptocurrency balances and sends payouts. It is intended for adults only (Section 9).
  • Contact details are in Section 12.

2. Information We Collect

2.1 Discord Account Information

  • User ID: Your Discord user ID. Every record the Bot keeps about you is keyed by it.
  • Username and display name: Used to address you in replies, to label your entries in games, leaderboards and game records, in the operational message log (Section 2.4), and in the text the Bot sends to language-model providers when it answers you.
  • Roles: The Discord roles you hold in the server. The Bot uses them to decide which commands you may run, whether you hold Premium, affiliate or staff status, and how certain deposits are credited (Super Affiliate members receive faster Litecoin credit). The Bot also adds and removes roles automatically: Premium (including trials), Active Affiliate and Super Affiliate roles, a poker tournament registration role, and one reaction role.
  • Join, leave and account dates: When you joined the server, when you left it (if you leave), the creation date of your Discord account, and timestamps of your interactions with the Bot. Account and server age are used for Premium trial eligibility and for giveaway anti-fraud checks.
  • Avatar: Your Discord avatar may be shown in the Bot's embeds. We do not store it.

2.2 Cryptocurrency and Payment Data

PurrPay is the Bot's payment system, and it is custodial: the Bot creates and controls the deposit wallet or ledger balance it assigns to you. - Deposit accounts: For SOL and USDC on Solana, the Bot creates a deposit wallet for you and controls its keys; your balance is that wallet's on-chain balance. For XRP, all deposits go to one account the Bot controls and yours are identified by a destination tag assigned to you. For Litecoin, deposits are received by nodes we run and your balance is an entry in an internal ledger. Live assets are SOL, USDC on Solana, XRP and Litecoin. Other assets exist in the Bot but are switched off; additional assets may be enabled later, and the Bot shows which are available. See Section 6.3. - Payout wallet addresses: The external addresses you register with /setwallet to receive withdrawals and prizes, for Solana (SOL and USDC), XRP (address and destination tag) and Litecoin. These wallets are yours; the Bot never holds their keys. If you are a SealStats affiliate and have not registered a payout wallet, the Bot uses the Solana address on your affiliate record. - Transaction history: Records of deposits credited to your balance, withdrawals, Premium purchases and gifts, prizes you funded as a game host, prizes and payouts you received, and swap orders you placed through MiaSwap, with payment amounts, timestamps, USD values, the exchange rates used, payment status and the on-chain transaction IDs. - Fee records: Fees applied to your account are recorded with your transaction history. They are: a one-time $1.00 wallet opening fee (charged in SOL and added to your first outgoing SOL debit), a 0.002 SOL reserve withheld from your spendable Solana balance, a service fee withheld from real-currency Kemeow prizes (1.0% for prizes under $100, 1.5% for prizes of $100 or more), and blockchain network fees. Fees are described in full in the Terms of Service. - Swap records: If you use MiaSwap, the Bot stores your user ID and the FixedFloat order reference (encrypted), and an audit record with your user ID, username, display name, destination address, the deposit address FixedFloat issued and the on-chain transaction IDs. - Premium membership data: Whether you hold Premium, its expiry date, purchases, gifts, trials and free grants. - Affiliate record: If you are a SealStats affiliate, our staff maintain a record of you in our affiliate database: your Discord user ID, Solana payout address, Kick username and Kick user ID, casino account usernames, and whether you are an active affiliate. The Bot reads this record to grant affiliate roles, to show you your Kick payout profile, and as a fallback payout address. The Bot does not create or change this record; our staff do. The Bot does not calculate or pay affiliate commissions.

2.3 Games, Giveaways and Activity Data

  • Game and giveaway records: Which games and giveaways you entered or hosted, your entries (for example the numbers or coordinates you typed, with timestamps and attempt counts), results, prizes won, and, for real-currency games, the payout address and transaction ID. Kemeow and MiaShips keep the text of your entry messages (the first 400 characters for Kemeow, the first 64 for MiaShips) with your user ID. For each Kemeow and MiaShips game the Bot also keeps a proof file listing the participating players' Discord user IDs and the random seeds, so the result can be verified. Proofs, results and replays are published as described in Section 5.8.
  • Giveaway join records: When you join a MiaDrop giveaway, the Bot records the join together with the anti-fraud signals described in Section 2.5.
  • Prediction data: The figures you submit for casino bonus predictions (your reported wager, profit or loss, VIP level and predicted bonus), the actual results you report, your accuracy history and rate-limit counters.
  • Virtual economy data: MiaCoin balances, daily claims and transaction history; cosmetics you own or have equipped; MiaMarkets stock and prediction-market positions and trades. MiaCoin and MiaMarkets are play money with no monetary value; MiaCoin cannot be withdrawn, traded or redeemed.
  • Leaderboard data: Your positions on dice, trivia, TopRoll, MiaMines and other leaderboards.

2.4 Messages and Conversations

  • Operational message log: The Bot keeps a log of every message it can see: every channel in every server it is in, and direct messages sent to it. Each entry holds the message text, embeds, attachment links (file name, type and size), the author's display name and user ID, the channel and server, and the time. The Bot's own messages and messages from other bots are logged as well. A staff dashboard indexes the log so server staff can search recent history by keyword, author and channel; direct messages are stored but excluded from the staff dashboard's search results. The log is used to operate and debug the Bot, to investigate scams, abuse and payout disputes, and to support staff moderation. It is not used to build SafeChat conversation context. Opting out of SafeChat does not remove your messages from this log. It is kept for 30 days (Section 3.6).
  • Messages addressed to the Bot (SafeChat): When you mention the Bot in a channel where SafeChat is enabled, or message it directly when direct-message replies are switched on, the Bot stores your message and its reply under your user ID so it can continue the conversation. With each request the Bot sends the language-model provider your message, your display name, username, user ID and role names, the message you replied to (if any), the three most recent messages in the channel with their authors' display names, and your stored conversation summary and recent turns. Use %optout to stop this storage (Section 2.9).
  • Conversation summary: Once enough of your SafeChat messages have accumulated, the Bot sends the older ones to the language-model provider to write a short summary. It keeps the summary and uses it together with your recent stored messages in later replies. You can view it with %mycontext. Other users cannot see it; our staff can.
  • Images: If you attach a PNG, JPEG or WebP image (up to 4 MB) to a message that mentions the Bot, the image is sent to the language-model provider so the Bot can respond to it. Images are not stored; the operational message log keeps their links.
  • Support tickets: The Bot watches support-ticket channels in enabled ticket categories (currently PurrPay payment support). When you send the first message in a new ticket, the Bot automatically reads the ticket's messages (up to 100: author names, text and attachment links) and sends them, together with your PurrPay records (payout wallet, balance, recent payments and Premium status), to the language-model provider to draft a first reply and to help staff. It keeps the ticket in memory while the ticket is active (up to 24 hours of inactivity) and does not write ticket contents to a separate database. Ticket messages also appear in the operational message log.
  • Swap requests in direct messages and ticket channels: In a direct message to the Bot or in a support-ticket channel, a message that names a supported coin together with swap or transfer wording is treated as a possible swap request even if you did not mention the Bot. Its full text, which may include a wallet address, is sent to the language-model provider to extract the coins, amount and destination. No order is created until you confirm it.
  • Game entries: While a message-driven game is running in a channel (Kemeow, MiaShips, MiaMines, CatnipGuesser, MiaChess, Mute-or-No-Mute, Plinkatto), the Bot reads messages in that channel to pick up entries, picks and moves. Entry text is kept as described in Section 2.3.
  • Registration replies: If you register a PokerNow profile, each reply you send to the Bot's registration questions, including rejected input, is recorded in a registration log with your user ID and display name (Section 2.6).
  • Staff summaries and exports: Moderators can ask the Bot to summarize a channel. The Bot sends the recent messages in that channel (up to 500, with authors' display names) to the language-model provider; the summary is posted to the channel and is not stored. A staff command can also save a channel's message history to a file on our server; such exports are deleted after 30 days.
  • Command and technical logs: Commands you run and their parameters, natural-language requests the Bot parsed (for example a giveaway you asked it to run or a swap you described), payment events and errors are recorded in the Bot's technical logs for troubleshooting and security. A SafeChat request log records each request and the text sent to the provider, including the nearby channel messages.

2.5 Security and Anti-Fraud Data

To keep giveaways and games fair and to protect the community, the Bot collects and processes the following. - Double Counter verification results: The SealStats server uses the third-party Double Counter verification bot. When Double Counter posts a verified, blocked or kicked result for an account, the Bot records the result, the time, the account's user ID and username, the reason Double Counter gave, and the verification identifier string Double Counter attaches to the result, and counts how often the same identifier has been seen. These identifiers come from Double Counter, not from the Bot. Double Counter's handling of your data is governed by its own privacy policy. - Alt-account lookups (Doogle): When Double Counter blocks or kicks an account, and when staff request it, the Bot sends that account's Discord user ID to the Doogle alt-detection service and receives the list of accounts Doogle associates with it, Doogle's verification and VPN counts, its identifier string, avatar and account creation date. Results are posted to a staff-only channel, where the post remains, and are held in the Bot's memory for up to one hour. The Bot does not keep Doogle's results in its own databases; the staff-channel post appears in the operational message log for 30 days like any other message. A record of each lookup (the requesting staff member if any, the looked-up user ID and the time) is kept. If you have opted out with Doogle, the Bot receives no data about you from it. - Giveaway join signals: When you join a MiaDrop giveaway, the Bot records your account age, how long you have been in the server, how many times you joined in the last hour and day, how quickly you clicked after the drop opened, click bursts and repeat clicks, and, at payout, your payout wallet address, how recently it was set, and whether the same wallet is registered by other accounts. From these it computes a score with signal labels that is used only to help staff review that giveaway. Scores and signals are shown to staff for review. They never block entry or payment on their own and are not used for anything else. Joins are refused only by an active suspension, a giveaway ban, a maintenance window, or capacity, duplicate and closed-drop checks. - Join and leave records: When members join and leave the server and which roles they held, recorded from Discord member events and from the server's join and leave log messages. The Bot does not track invite links. - Rejoin detection: If you leave the server while holding a warning or restriction role and later rejoin, the Bot notes this, alerts staff, and re-applies those roles once you are verified. - Suspension and moderation records: Game suspensions and giveaway bans: your user ID, the scope, reason, duration, who issued them and when you were notified, and each blocked attempt (which game, channel and message, and the time; not the message text). Reasons typed by staff are reworded by a language-model service (Cerebras) before they are stored and sent to you. You receive one direct message with the reason, expiry, a summary of your recent entries and an appeal link. The list of active suspensions is posted in a staff-only channel. Staff can also place you on a SafeChat restriction list. - Game-entry moderation: During Kemeow entry the Bot counts how many different members you mention. Repeated mass-mentions lead to a warning and then to your entries being paused for the next games; the state and each event are recorded. The Bot deletes repeat entries, applies a ten-minute Discord timeout if you re-post your picks a second time after your entry is confirmed, and applies a sixty-second timeout for repeated entry spam in Mute-or-No-Mute. - Link checks and scam alerts: Links in messages are checked against lists of known scam and blocked domains kept by the Bot; no outside service is queried automatically. A message containing a blocked-list link is deleted with a channel warning. A link to a known scam domain triggers a reaction, a public warning, and an alert to staff containing your display name, user ID, where you posted and the first 500 characters of your message. Links carrying one specific referral tracking parameter are deleted and reposted without it, crediting you.

This information is used only for safety, fraud prevention and rule enforcement, and is handled as described in Sections 4 and 5.

2.6 Information You Give the Bot for a Feature

  • PokerNow profile: Your PokerNow profile ID or link when you register for a poker tournament by replying to the Bot's direct message. It is stored with your Discord user ID, and past tournaments you played are kept in a tournament archive.
  • Kick account link: If you link your Kick account through the Kemeow Kick portal (a Discord login), the link between your Kick user ID and your Discord user ID is stored so MiaCoin earned in Kick streams can be claimed in Discord.
  • Reminders: The text of reminders you set, with your user ID and the channel. The text is sent to the language-model provider to work out the time.
  • Bonus predictions: The predictions you submit and the results you report.
  • Swap details: The destination address, any refund address, currencies and amounts of a swap you request through MiaSwap.
  • Premium trial requests: Your user ID, display name, account creation date and join date when you request a trial with /premiumtrial. Trials require an account at least 30 days old that was not created on the day you joined the server.
  • Ban appeals: If you submit a ban appeal on https://miacat.ai, the form collects your Discord ID, username and the reason you give. It is stored by our website and visible to staff.

2.7 Information About Other Members

Some features process messages or identities of members who did not address the Bot: - When a member mentions the Bot in a channel, the three most recent messages in that channel, with their authors' display names, are sent to the language-model provider as context. - Moderators can ask the Bot to summarize a channel; the messages of any author in that channel are sent to the language-model provider. - Any member can run the %wenmia roast command, which sends up to the last ten messages in the channel, from any author, to a language model running on a server we operate. - Some games choose participants from members who recently spoke in the channel. Wenner's Dilemma drafts recent speakers who have a registered payout wallet. CatnipGuesser picks three recent speakers and sends their display names to an image-generation service (NanoGPT) to create images based on those names; players guess which member each image refers to. - Random-pick commands can repost a recent message with its author's name. - Alt-detection results may name other accounts that Doogle associates with the account being checked. - The Kemeow ping guard records which members you mentioned during entry.

These uses are limited to the features described in this policy and are not affected by the SafeChat opt-out.

2.8 What the Bot Does Not Collect

  • The Bot does not collect or store your IP address, device, browser or network information, location, online status, typing activity or voice activity, and it does not track invite links.
  • The Bot does not receive or record IP addresses. Our web servers keep standard access logs, and our staff dashboard records the IP address of each staff login (Section 5.5).

2.9 SafeChat Opt-Out and Opt-In

  • %optout stops the Bot from storing your SafeChat conversations and from building a conversation summary about you, and deletes the SafeChat history and summary already stored for you. %optin turns storage back on.
  • When you opt out, your Discord user ID is kept on an opt-out list so the Bot remembers your choice.
  • The Bot still reads your mention or direct message in real time to reply to you.
  • Opting out does not remove your messages from the operational message log (Section 2.4), does not stop your channel messages being included as nearby context when another member talks to the Bot, does not stop staff summaries, and does not stop support-ticket triage or swap-request parsing. It does not affect game, payment or security records. You can ask us to delete your entries from the operational message log at any time (Section 7.4).

3. Storage Locations and Data Retention

3.1 Data Stored on Our Server

The Bot runs on a server we operate, hosted with Microsoft Azure. It stores the following there, in database files and structured log files: - Member cache: user ID, username, display name, roles, join and leave dates, account creation date and Premium status for members of the server. Members who leave are kept and marked as left. - Payout wallet registry: your registered payout addresses and active coin. - PurrPay ledger: deposit addresses and destination tags, ledger balances, deposits, withdrawals, fees, game funding, payouts and their transaction IDs. - Premium records: membership status and expiry, purchases, gifts, trials and grants. - Game records: entries and entry text, results, proof files, payout records, replays and leaderboards for each game; MiaDrop join records with the anti-fraud signals in Section 2.5; per-entry event logs. - Virtual economy: MiaCoin, cosmetics, MiaMarkets positions and Kick account links. - SafeChat conversations and summaries (Section 3.2). - Security records: Double Counter verification results, Doogle lookup records, suspensions, giveaway bans, blocked attempts, ping-guard records and the SafeChat restriction list. - Identity links you create: PokerNow registrations and the registration log. - Feature data: reminders, bonus predictions, trial requests and grants. - Swap records: encrypted MiaSwap order references and the swap audit log. - Operational logs: the message log described in Section 2.4, the SafeChat request log, the Bot's technical and payment logs, and a log of messages staff send through the dashboard. - Staff records: staff dashboard login records with IP addresses (staff only).

3.2 SafeChat Database

  • Stores each message you addressed to the Bot and the Bot's reply, with your user ID, timestamp and role, plus your conversation summary. It is not shared outside our team and the language-model providers in Section 5.1.

3.3 Operational Logs and the Staff Message Archive

  • The operational message log is written to rotating log files and indexed into a database that only logged-in server staff can search. Staff can search by keyword, author and channel and see a live feed of current messages. Direct messages are stored but excluded from the staff dashboard's search results and live feed. Support-ticket channel messages are searchable.
  • The SafeChat request log and the Bot's technical logs are kept in the same place and are readable only by our team.

3.4 Microsoft Azure Cosmos DB

We keep three sets of records in Azure Cosmos DB, a cloud database service: - Affiliate records: Discord user ID, Solana payout address, Kick username and ID, casino account usernames, and active status (Section 2.2). - Bonus prediction records: your predictions, actual results and rate-limit counters, and website login records (a login phrase and a short-lived session token) for the bonus-prediction website. - Bonus code records: promotional codes submitted by staff, with the submitting staff member's user ID and the time.

3.5 Our Second Server, Blockchain Nodes and Restart Copies

  • Our second server (MiaServer): We operate a second server that runs a staff assistant. Messages posted in one staff-only channel are sent to it so the assistant can answer staff. It also keeps synchronized copies of the Bot's databases, refreshed about every ten minutes, including the SafeChat database, the message archive, the PurrPay ledger, the payout wallet registry, PokerNow registrations, security records and ban-appeal records, for the assistant to consult when answering staff questions. The assistant uses language models hosted by NanoGPT (Section 5.1); data it reads from these copies to answer a staff question may be included in the text it sends to NanoGPT. This server is part of our infrastructure and is covered by this policy. The retention periods in Section 3.6 apply to these copies as well.
  • Our blockchain nodes: The Litecoin nodes we run (and Bitcoin nodes, if that asset is enabled) label each deposit address and payment with the Discord user ID it belongs to.
  • Restart copies: When the Bot is restarted, copies of its log files and databases are saved on the same server as the Bot. They follow the same retention rules as the originals.

3.6 Retention Periods

  • Operational message log, SafeChat request log, technical logs and the staff message archive: deleted after 30 days.
  • SafeChat conversations: stored messages are deleted after 30 days. Your conversation summary is kept until you opt out or ask for deletion. %optout deletes your stored history and summary immediately.
  • Member cache: kept while the Bot is in the server. Records of members who have left are kept, marked as left, so that restrictions can be re-applied if they rejoin. Deleted on request.
  • Payout wallet addresses: kept until you remove them with /clearwallet or ask us to delete them. Addresses used in past payouts remain in payment records.
  • Payment, payout, deposit, fee and swap audit records: kept for as long as they are needed for financial audit and dispute resolution, including after you stop using the Bot. Blockchain records cannot be deleted by anyone. Encrypted MiaSwap order references are deleted after 14 days.
  • Premium records: kept for billing and refund purposes.
  • Game records, including proof files, results, replays and leaderboards: kept as long as needed for leaderboards, fairness verification and payout history, including the public pages in Section 5.8.
  • Affiliate records: maintained by our staff for as long as you are an affiliate. Changed or removed by staff on request.
  • Security, moderation and anti-fraud records: kept as long as needed for enforcement and fraud prevention. Suspensions expire at the end of their duration; the record of them is kept.
  • Doogle results: held in memory for up to one hour; the record of the lookup is kept with security records.
  • Support tickets in triage: held in memory until 24 hours after the last activity. Ticket messages in the operational log follow the 30-day rule.
  • Channel exports made by staff: deleted after 30 days.
  • PokerNow registrations: your current registration is removed by staff on request. Records of past tournaments you played remain in the tournament archive.
  • Predictions, reminders, MiaCoin, cosmetics and trial records: kept until you ask us to delete them.
  • Ban appeals: kept for handling the appeal; deleted on request.

3.7 If the Bot Leaves a Server

  • If the Bot is removed from a server, it can no longer see that server and stops collecting data from it. Message-log entries from that server are deleted under the 30-day rule. Other records tied to that server are deleted on request.
  • Data you gave the Bot directly (PurrPay balances, payout wallets, game and payment records) is not tied to a server and is kept as described in Section 3.6.

4. How We Use Your Information

4.1 Service Delivery

  • Message processing by language models: The Bot sends text and images to the language-model providers in Section 5.1 to:
  • answer you when you mention it or message it directly (your message, any attached image, your display name, username, user ID and roles, your conversation summary, the message you replied to, and the three most recent messages in the channel);
  • draft replies in support tickets (the ticket conversation and your PurrPay records);
  • summarize a channel when a moderator asks for a summary;
  • understand natural-language requests, such as a giveaway you ask it to run or a swap you describe in a direct message or ticket channel;
  • remove tracking parameters from a link you give it;
  • work out the time of a reminder you set;
  • reword staff moderation notes before they are stored;
  • narrate MiaRoyale games using players' display names;
  • generate CatnipGuesser images from entrants' display names, and generate trivia questions from Wikipedia text;
  • search the web, when that option is turned on, using a query the model derives from your question.
  • Fixed-phrase responders: The Bot scans channel messages for a few fixed phrases (for example questions about monthly bonuses or whether a coin's network is slow) and posts a reply. These checks store nothing.
  • Game operations: Your data is used to:
  • register your entries and determine outcomes with the Bot's provably fair mechanisms. Games are free to enter for players: there is no buy-in, wager or entry fee;
  • fund prizes from a host's PurrPay balance, withhold the Kemeow service fee, and pay winners. Some staff-hosted games are funded from our own treasury instead;
  • maintain leaderboards and rankings;
  • detect duplicate entries and abuse;
  • publish proofs, results and replays so games can be verified (Section 5.8).
  • Premium services: Your data is used to verify Premium status, track expiry, grant access to Premium features and manage the Premium role.

4.2 Cryptocurrency and Payment Processing

  • Wallet addresses and transaction data are used to:
  • credit deposits to your PurrPay balance and process withdrawals to your registered payout wallet (withdrawals can only go to that wallet);
  • pay prizes to your registered payout wallet, or credit them to your PurrPay balance when you have no wallet registered or the amount is below the on-chain minimum;
  • convert USD prices to cryptocurrency amounts using live market rates;
  • record Premium purchases and transaction history;
  • process refunds where our refund policy allows.
  • The Bot checks that payout addresses are validly formatted for their network. It does not verify that you own them.

4.3 Affiliate Features

  • Your affiliate record is used to:
  • grant and remove the Active Affiliate and Super Affiliate roles in the server;
  • show you your own Kick payout profile on request (/kickprofile);
  • send payouts to your affiliate Solana address when you have not registered a separate payout wallet.
  • The Bot does not calculate or pay affiliate commissions.

4.4 Operating and Improving the Bot

  • Technical logs, error reports and hourly status reports with aggregate interaction counts are used to keep the Bot running, find bugs and check that games behave fairly.
  • We do not use your messages or any other data obtained from Discord to train artificial-intelligence or machine-learning models, and we do not share that data with anyone for that purpose.

4.5 Security and Fraud Prevention

  • Your data is used to:
  • detect alternate and duplicate accounts and shared payout wallets in giveaways;
  • identify fraudulent transactions and abuse of games;
  • re-apply restrictions to members who leave and rejoin;
  • warn the community about links to known scam domains;
  • enforce suspensions, giveaway bans and entry pauses;
  • keep audit records of payments and moderation actions.
  • Your data may be used to comply with applicable law, respond to lawful requests, enforce our Terms of Service, and protect the rights and safety of the Bot, its users and the public.

4.7 Communication

  • The Bot contacts you only through Discord. It sends you direct messages for:
  • payment instructions, deposit addresses, balances and support replies;
  • notices about suspensions, restrictions or warnings applied to you, with the reason and evidence;
  • notices that a prize was credited to your PurrPay balance because you have no payout wallet or the amount was too small to send;
  • warnings about repeated game entries or mass-mentions;
  • PokerNow registration messages, and your context summary when you request it;
  • bonus reminders, only if you turned them on with /bonusremind;
  • replies in support tickets.
  • Changes to this policy or the Terms are posted at https://docs.miacat.ai and, for significant changes, announced in the SealStats server (Section 8). The Bot does not send policy-change notices by direct message.

5. Data Sharing and Third-Party Disclosure

We share data only with the service providers below, when the law requires it, or when you ask us to, for example by placing a swap order or by entering a game whose proof, result and replay pages are public (Section 5.8). We do not sell, rent or license your personal information, and we do not share it with advertising networks or data brokers.

5.1 Language-Model and AI Providers

  • Text and images described in Section 4.1 are sent to and processed by:
  • Microsoft Azure OpenAI Service: the primary provider for SafeChat replies, support-ticket drafts, channel summaries, reminder parsing, link cleaning, game narration and natural-language command parsing. It also receives the text sent to Cerebras when Cerebras is unavailable.
  • Cerebras: parsing of short natural-language commands (for example giveaway requests) and rewording of staff moderation notes about you.
  • NanoGPT: image generation for CatnipGuesser using entrants' display names; trivia question generation from Wikipedia text (no user data); the staff assistant on our second server (Section 3.5); and, when the web-search feature is switched on, the search query the model derives from your question.
  • Anthropic: configured as an alternative provider for the same features as Azure OpenAI; used only if our staff switch the Bot to it.
  • A language model we host ourselves on a server we operate, used by the %wenmia command. Data sent to it does not leave our infrastructure.
  • These providers process the data on our behalf, only to return a response to us, and we remain responsible for the data we send them. We send providers text and images only to obtain a response, and we do not send your data to any provider for the purpose of training models.
  • When your SafeChat message looks like a question, the Bot also sends its text to the help-article search on our own website (Section 5.5) to find relevant help articles.

5.2 Blockchain Networks and Market Data

  • Public ledgers: Your payout addresses, the Bot's deposit addresses and every payment the Bot makes to you are recorded on public blockchains (Solana, the XRP Ledger, Litecoin). Blockchain records are permanent, public and cannot be changed or deleted by anyone.
  • Blockchain node providers: The Bot reads balances and submits transactions through Solana RPC and XRP Ledger RPC services operated by QuickNode, which see the addresses and transactions involved. Litecoin (and Bitcoin, should that asset be enabled) deposits and payouts go through nodes we operate ourselves; the wallet labels inside those nodes contain your Discord user ID.
  • Market data services: The Bot fetches prices and network statistics from Twelve Data, CoinAPI, Kraken's public API, Blockchair, Blockstream, mempool.space and BlockCypher. These requests are made by the Bot and contain only asset symbols. They include no information about you.

5.3 Hosting (Microsoft Azure)

  • The Bot's server, its databases and logs are hosted with Microsoft Azure, and the records in Section 3.4 are stored in Azure Cosmos DB. Microsoft, as our hosting provider, has technical access to the servers and is bound by its own data protection commitments. Microsoft is a US company.

5.4 Other Third-Party Services

  • Discord: The Bot operates through Discord's API. It receives your user ID, username, display name, roles and messages from Discord, and sends Discord the messages, role changes, timeouts and staff relay posts described in this policy.
  • Doogle: Receives Discord user IDs for alt-account lookups as described in Section 2.5, automatically when Double Counter blocks or kicks an account and on staff request.
  • Double Counter: The server's verification bot. The Bot reads the results Double Counter posts; it sends Double Counter nothing.
  • urlscan.io: Receives links that staff submit manually for a safety scan. No links are sent automatically and no data about you is included.
  • PokerNow: When you register for a tournament, the Bot asks PokerNow whether the profile ID you gave exists (only that ID is sent). When tournament hosting tools are enabled, the Bot reads the entrant list from PokerNow and sends PokerNow the entries of registered players to approve them. No Discord data is sent to PokerNow.
  • FixedFloat: When you create a swap through MiaSwap, the Bot sends FixedFloat the currencies, direction and amount, your destination address, any refund address, and the Bot's referral code. FixedFloat processes the swap under its own terms, which you accept when you confirm the order. Our referral code is attached to every order, and any optional support fee you choose to add is paid to our FixedFloat affiliate account, so we earn affiliate revenue on swaps made through the Bot. The Bot also uses FixedFloat to convert its own reserve funds.
  • Shuffle.us: Staff may look up an affiliate username against Shuffle's public affiliate list. No Discord data is sent.
  • Wikipedia: Fetched for trivia questions. No user data is sent.
  • Google Fonts: The docs.miacat.ai site loads fonts from Google Fonts, so your browser makes a request to Google when you open it.
  • Casino sites: The Bot posts links to casino sites that carry our referral code. It has no integration with those sites and sends them no data about you; if you are an affiliate, your affiliate record can include your casino account usernames (Section 2.2).

5.5 Systems and Websites We Operate

The Bot exchanges data with other systems we run. They are part of "us" and are covered by this policy: - docs.miacat.ai: documentation, including this policy. It has no accounts and sets no cookies for visitors; its pages load fonts from Google (Section 5.4). - miacat.ai: the game proof verifier, public game result pages (Section 5.8), the ban-appeal form (Section 2.6), and a help-article search that SafeChat queries with the text of your question. - kemeow.miacat.ai and the Kemeow Kick portal: game replays (Section 5.8) and the Kick account link created through a Discord login (Section 2.6). - Staff dashboard (dashboard.miacat.ai): our staff tools, behind a separate staff login: the message search described in Section 3.3, lookups of the records in this policy, and a relay that lets staff post messages through the Bot. Staff logins record the IP address and time. The same host also serves public game result and proof pages (Section 5.8). - MiaServer: the staff assistant and synchronized database copies described in Section 3.5. - Litecoin and Bitcoin nodes we run for PurrPay (Section 5.2). - A notice receiver: hourly health statistics from the Bot, and messages you ask the Bot to pass to the developer (with your display name and user ID). - A self-hosted language model (Section 5.1).

5.6 No Sale of Personal Data

  • We do not sell, rent or license your personal information, and we do not share it with advertising networks or data brokers.
  • The affiliate revenue we receive from FixedFloat (Section 5.4) is paid on swap volume, not on your data.
  • We may disclose your information if required by law, including in response to court orders, lawful government requests or law-enforcement investigations, to protect against fraud or abuse, or to enforce our Terms of Service.

5.8 Public Game Pages and Staff Access

  • To let anyone verify that games were fair, the Bot publishes, for each Kemeow and MiaShips game, a proof file that includes the Discord user IDs of participants and the random seeds. It is reachable from the verifier at https://miacat.ai/verify and from a public proof address.
  • Result pages at https://miacat.ai/kemeow/games show each real-currency game's host display name, channel, winners and amounts. Discord IDs on these pages are masked. Result pages served from dashboard.miacat.ai show the same information with winners shown by Discord mention.
  • Replays at https://kemeow.miacat.ai show each Kemeow player's display name and picks.
  • These pages are public and are kept as part of the game record (Section 3.6).
  • Server staff can view the records described in this policy through staff commands and the staff dashboard, including searching the last 30 days of the operational message log, and viewing your PurrPay deposit address and balance, your payout wallets, your Kick payout profile, your PokerNow registration and your suspension history. Staff access is limited by Discord role and by a separate dashboard login. Messages staff send through the dashboard are logged.
  • Alerts about scam links, suspensions, rejoins with restriction roles and alt-detection results are posted to staff-only channels and include the user IDs and names involved.

5.9 Business Transfers

  • If operation of the Bot is transferred to a new operator, the new operator takes over the Bot under Discord's developer terms and this policy, and only the data needed to keep operating the Bot moves with it. We will announce any such change in the SealStats server and at https://docs.miacat.ai.

6. Data Security

6.1 Security Measures

  • Connections between the Bot and Discord, and between the Bot and the outside services in Section 5, use HTTPS.
  • The Bot's databases and logs are stored on Microsoft Azure managed disks, which Azure encrypts at rest.
  • The private keys of the Bot's own wallets are stored in password-encrypted files. Your Solana deposit wallet's key is derived when needed and is never written to disk. MiaSwap order references are encrypted by the Bot before they are stored.
  • Access to our servers is limited to our team. Staff tools require a Discord staff role, and the staff dashboard requires a separate staff login.
  • Payout wallet changes are rate-limited: two changes per hour, and after five changes in 24 hours further changes are locked until an administrator unlocks them.

6.2 Limitations of Security

  • No method of storage or transmission over the Internet is completely secure. We cannot guarantee protection against unauthorized access, phishing attacks targeting you, breaches affecting us or our service providers, or attacks on the blockchain networks we use.

6.3 Cryptocurrency-Specific Risks

  • Custodial balances: Your PurrPay balance is held by the Bot, not by you. For Solana assets the Bot controls the deposit wallet assigned to you and its private key; XRP deposits are received into an account the Bot controls and attributed to you by destination tag; Litecoin deposits are received into wallets on nodes we operate and credited to an internal ledger. If our keys or servers are compromised, funds held in PurrPay balances are at risk. Deposit only what you intend to use.
  • Your payout wallet: The payout addresses you register with /setwallet remain under your control; the Bot never holds their keys. If that wallet is compromised, your funds are at risk independently of our security.
  • Irreversible transactions: Once a cryptocurrency transaction is confirmed it cannot be reversed, even if it was unauthorized or sent to the wrong address. Funds sent to a wrong or compromised address cannot be recovered.
  • Blockchain transparency: All blockchain transactions are permanently visible to anyone. Addresses cannot be made private.
  • On-chain program risk: Token transfers and other on-chain operations may be affected by bugs or exploits in the underlying networks and programs that are beyond our control.

6.4 Breach Notification

  • If we become aware of unauthorized access to your personal information, we will notify affected users as required by law, notify Discord, describe what happened and what you should do, and cooperate with law enforcement where required.

7. Your Privacy Rights and Choices

7.1 Access Your Data

  • In the Bot: %mycontext shows your stored SafeChat summary and recent context; /payoutwallet shows your registered payout wallets; /purrpaybalance shows your PurrPay balances and deposit addresses; /checkpremium shows your Premium status; /kickprofile shows your Kick payout profile.
  • For anything else, contact us (Section 12). We respond within 30 days.

7.2 Opt Out of SafeChat Storage

  • %optout stops the Bot storing your SafeChat conversations and building a summary about you, and deletes what is already stored. %optin turns storage back on. Your Discord user ID stays on the opt-out list so the Bot remembers your choice.
  • Opting out does not affect the operational message log, nearby-context use of your channel messages, staff summaries, support-ticket triage, swap-request parsing, or the game, payment and security records described in this policy (Section 2.9). You can ask us to delete your entries from the operational message log at any time (Section 7.4).

7.3 Correct Your Information

  • Payout wallets: /setwallet, /clearwallet and /setactivecoin. Wallet changes are limited to two per hour; after five changes in 24 hours further changes are locked until an administrator unlocks you.
  • Bonus reminders: /bonusremind on or off.
  • PokerNow registrations, affiliate records and Kick links are corrected by our staff on request.
  • For anything else, contact us (Section 12).

7.4 Delete Your Data

  • Ask us to delete your data by email or through a support ticket (Section 12). Within 30 days we will delete your SafeChat history and summary, your member-cache record, your payout wallet registry entry, your PokerNow registration, your reminders, predictions, MiaCoin and cosmetics, and your entries in the operational message log and its copies, including the copies on our second server.
  • We keep payment and payout records, including blockchain records (which cannot be deleted by anyone) and the proof files that let anyone verify a game's result; moderation, suspension and anti-fraud records needed for enforcement; and aggregated statistics that do not identify you.
  • Before deletion you may withdraw any remaining PurrPay balance to your registered payout wallet.

7.5 Export Your Data

  • You can request a copy of the data we hold about you in a portable format by contacting us (Section 12). We provide it within 30 days.

7.6 Jurisdiction-Specific Rights

  • EU/EEA and UK users (GDPR and UK GDPR): You have rights of access, correction, erasure, restriction, portability and objection.
  • California users (CCPA/CPRA): You have rights to know, delete and correct your personal information and to opt out of its sale. We do not sell personal information.
  • Brazil (LGPD) and other jurisdictions: You may have similar rights under local law.
  • Contact us (Section 12) to exercise any of these rights.

7.7 Data Held by Others

  • Discord holds its own records of your account and messages under Discord's Privacy Policy. The third parties in Section 5 hold the data described there under their own policies. Requests about that data should be made to them.

8. Changes to This Privacy Policy

  • We update this policy when the Bot's features or data practices change or when the law requires.
  • Changes are posted at https://docs.miacat.ai/privacy with a new "Last updated" date at the top. Significant changes are announced in the SealStats server.
  • Continued use of the Bot after a change means you accept the updated policy. Review it periodically.

9. Age Requirement (18+)

  • The Bot is intended only for adults aged 18 or older, because it holds cryptocurrency balances and sends payouts. It is not designed for or directed to minors.
  • The Bot does not verify your age. We rely on your representation that you are 18 or older and on Discord's own minimum-age requirements.
  • If we learn that a user is under 18, we remove their access to the Bot's services and delete their personal information, apart from the records we must keep (Section 7.4).
  • Parents or guardians who believe a minor has provided information to the Bot should contact us (Section 12).

10. International Data Transfers

  • We operate from the United States. Your information is stored on servers we operate, hosted with Microsoft Azure and at our own premises, and is processed by the providers in Section 5, some of which operate in the United States and other countries.
  • These countries may have data protection laws that differ from those where you live. By using the Bot you agree to your information being transferred to and processed in them.

11. Discord and Third-Party Services

  • The Bot is subject to Discord's Terms of Service and Developer Policy. Nothing in this policy overrides Discord's terms, and Discord's handling of your data is described in Discord's own privacy policy.
  • The Bot posts links to and works with services we do not run, including blockchain explorers, FixedFloat, PokerNow, Kick and casino sites. Their privacy policies, not ours, govern what they do with your data; review them before using those services.
  • If you have a problem with the Bot, report it through the support ticket channel in the SealStats server or by email (Section 12).

12. Contact Us

Use either of these routes to ask questions about this policy, to exercise your rights (access, correction, deletion, export), or to report a problem with the Bot:

  • Email: ruby@stakestats.net
  • In Discord: open a support ticket in the SealStats server. For payment issues, /paymentsupport points you to the PurrPay support ticket channel.

We respond to privacy requests within 30 days.

Changes in this version (September 2026): This version replaces the policy dated June 2026. It describes the operational message log and its 30-day retention, the custodial nature of PurrPay balances and the current list of assets, every provider and service that receives data, the anti-fraud system as it runs, the scope of %optout, the public game pages, our second server, the fees recorded with transactions, and the routes for access, correction, deletion and export requests.