1. Scope and responsible operator
This policy explains how Gary05CX, the maintainer of Kurone (“we”, “us”), processes information through the Discord bot and this documentation website. Contact: Discord gary05cx. It applies to this bot’s deployment; other companion bots have their own policies and separate records.
The bot can process messages in server text channels it can access, including messages from members who never mention it. Installing the bot is not a substitute for notifying affected members or obtaining consent where required. Do not assume an accessible channel is private from the bot.
2. Information the bot may collect
- Discord identifiers and metadata: user, bot, server, channel, message, reply-reference, attachment, and command-interaction IDs; display names or server nicknames; timestamps; channel age-restriction and installation state; and relevant permission or delivery results.
- Message content: received text, selected recent or older same-channel messages, conversations between other members, the bot’s replies, and completed replies from specifically allowed peer bots. Accessible human messages can be logged even when no reply is triggered or the bot chooses silence.
- Attachments and OCR: filenames, Discord CDN URLs, media types, sizes, and image dimensions. Eligible images may be downloaded temporarily for local text extraction. Extracted text can be stored and included in model context. The bot does not intentionally archive original image files as a separate media library; stored URLs and logs may still expose attachment information.
- AI and retrieval records: actual model inputs and selected context; prompts; draft, final, and refusal outputs; model identifiers; provider-returned reasoning where available; token use; optional message embeddings; response decisions; and safety-review results.
- Tool and operational records: search queries, result titles, URLs and snippets, tool arguments and outcomes, history retrieval, errors, delivery status, peer-interaction limits, and command execution records. Private command responses are also logged.
- Support requests: information you choose to provide when you contact the maintainer.
3. Sources and collection boundaries
Information comes from Discord events and permitted history requests, messages already stored by this bot, configured AI and embedding services, optional public search, and your support requests. When assembling a reply, the bot may fetch recent channel history and retrieve relevant older saved messages from the same channel. It does not promise to capture every event during downtime.
Regular human messages may be logged in accessible server text channels regardless of whether /install is enabled. The current chat flow excludes direct messages, voice, forum posts, and threads; arbitrary bots and webhooks do not participate in conversation intake. Allowlisted peer-bot messages can still be recorded when they are not allowed to trigger a reply. Each companion bot has a separate database and local event queue.
4. Why we process information
We use information to generate contextual replies, select whether to answer, perform safety checks, extract image text, optionally retrieve memories or search public information, maintain channel settings, estimate model usage, diagnose failures, prevent abuse, and respond to support or data requests. Logs include silence, refusals, and failed actions so the operator can understand what happened.
Where data protection law requires a legal basis, the relevant basis may be providing a service you request, legitimate interests in reliable and secure operation after considering affected members’ rights, compliance with legal obligations, or consent where required. Consent can be withdrawn by contacting us; withdrawal does not invalidate earlier lawful processing. We do not treat a server administrator’s action as every member’s consent.
5. Recipients and external processing
- Discord carries messages, history, attachments, command interactions, and public replies under its own Privacy Policy.
- The configured language-model provider receives selected message content, context, relevant identifiers and names, OCR text, and instructions needed for generation, reply decisions, search gating, or safety review. A locally hosted model keeps this inference on the operator’s infrastructure; a remote endpoint sends it to that provider.
- The optional embedding provider receives selected message text and OCR text to create vectors used for same-channel retrieval. It can be a different local or remote service.
- Self-hosted SearXNG and upstream search engines receive a short public-topic query when search is enabled. The bot attempts to exclude private quotations, personal identifiers, links, and credentials through checks, but automated filtering is not infallible. Search results return to the bot and may be included in model input.
- Hosting, database, and backup providers may process the information needed to host and secure the bot. Only authorized operators and necessary service providers should access private operational records.
The identity, location, and retention terms of model and infrastructure providers depend on the running deployment; a character name does not identify them. Contact the maintainer for the current providers before submitting information if that affects your choice. Local OCR does not itself send original images to a separate vision service; its extracted text may be sent to model or embedding services.
We do not sell personal information, share it for targeted advertising, or train or fine-tune models on Discord messages. Model services must be used under arrangements that do not permit training on this data. Information may also be disclosed when legally required or necessary to address a security incident, subject to applicable law and Discord’s requirements.
6. Public replies and private logs
A reply is posted in the originating Discord channel and can be seen by people with access to that channel. Because replies use shared context, they may summarize or refer to other members’ messages in that channel. Public replies omit internal reasoning and source lists, but those details, where returned, may remain in private logs. The absence of a public reply does not mean nothing was processed or stored.
The documentation website does not publish the bot’s conversation database or private audit logs. Other installed companion bots with access to the channel may independently receive and retain the publicly posted reply under their own policies. We do not merge their databases by enabling peer conversations.
7. Storage and retention
The bot stores conversation and audit records in PostgreSQL. An on-disk event queue temporarily retains events before they are written to the database, including during a database outage. Optional vectors and copies of actual context may be stored alongside operational records. Backups may contain earlier copies where the operator maintains them.
The current software has no automatic time-based deletion schedule or fixed retention period. Cleanup is performed by the operator. Records may remain while needed for the stated conversation, safety, and operational purposes; we will delete data when it is no longer necessary, when the Service ends, or following a valid request, subject only to lawful retention requirements. Backups and pending queues must also be addressed so removed data is not silently restored. Contact us for the retention details of the running deployment.
8. Your controls and their limits
/uninstall turns off unsolicited automatic replies in that channel. It does not stop message collection in channels the bot can still access, erase history, or remove vectors or logs. Removing a Discord message, editing it, or removing the bot does not automatically synchronize deletion or correction to existing stored copies.
To stop future channel access, ask an administrator to revoke View Channel or remove the bot from the server. To remove stored data, contact the maintainer. There is no self-service deletion, export, reset, or per-user logging opt-out command. Leaving the server does not automatically delete existing records. We can coordinate a request with the server administrator where needed, while considering other members’ rights.
9. Access, correction, and deletion requests
Contact Discord gary05cx privately and identify Kurone. Describe your request and provide your Discord user ID and relevant server, channel, message, or interaction IDs if available. We may ask for proportionate identity or authorization verification. Do not send passwords, account tokens, or unnecessary copies of private messages.
You may ask for access, correction, or deletion of your data. Depending on applicable law, you may also have rights to portability, objection, restriction, withdrawal of consent, or a complaint to your local data protection authority. We will respond within applicable legal deadlines and explain any lawful limit, rather than promise a universal response period.
A deletion review must consider original messages, copied context in other turns, embeddings, model and tool logs, command records, local queued events, posted bot replies, backups, and applicable service-provider copies. We may redact other people’s information or retain only what law requires. To prevent deleted material from being imported again through Discord history, the original message may also need deletion in Discord or the bot’s channel access may need to remain disabled. No bot command performs this end-to-end cleanup automatically.
10. Security and international processing
Access to databases, queues, and backups should be restricted to authorized operators. Deployment guidance calls for protected credentials, appropriate transport security, and encrypted storage. The application does not itself guarantee that every host or provider implements those controls, and no system can guarantee absolute security. Please report suspected exposure privately to the maintainer.
Processing locations depend on the bot host, model, embedding, search, and backup services and may be outside your country. Where required, appropriate transfer safeguards must be used. Contact us for the current deployment locations and relevant safeguards. We will handle security incidents and required notifications under applicable law and platform requirements.
11. Children and age-restricted content
The Service is not intended for anyone below Discord’s minimum age or a higher local minimum. Age-restricted content is only for adults aged 18 or over where lawful. We do not request government identity documents or dates of birth through the bot. Discord channel settings and automated reviews are not independent proof of age. If you believe ineligible-user data has been collected, contact us for review and deletion as appropriate.
12. Website data
This static documentation site has no sign-in, advertising, embedded third-party media, application analytics, or cookies added by its code. It stores only your chosen light or dark appearance in your browser’s localStorage under companions-color-mode; this preference stays on your device, is not sent to the bot or a server, and can be removed by clearing site data. The site defaults to dark mode if no preference is saved or storage is unavailable. Language controls are ordinary links, and copying a command uses the browser clipboard only when you press its copy button. Fonts, artwork, scripts, and styles are served with the site.
When hosted on Cloudflare Pages, Cloudflare may process network information such as your IP address, request URL, browser headers, and security events to deliver and protect the website under its Privacy Policy. Host-level settings and logs are separate from this site’s code. Following an external link, such as to Discord, is governed by that destination’s policies. Visiting these pages does not grant them access to your Discord chats.
13. Changes and contact
We will update this page and its revision date when practices change and give additional notice for material changes where required. For the current providers, retention details, security reports, or any privacy request, contact Discord: gary05cx and specify Kurone. See the Terms of Service for usage rules.