Privacy Policy

01 / Who is responsible

Chorus is independently operated by Devin O’Brien / BVLDERDVSH. Contact the operator through the contact and privacy request form. Discord, OpenAI / ChatGPT Sites and Cloudflare also process information under their own terms and privacy policies when providing their services.

02 / Information we process

• Encounter reports: gamer handles, game names, flags, notes, reporter Discord user IDs and display names, server IDs, and submission or update timestamps.
• Imported history: selected message content is fetched for review. Saved reports also contain original author IDs and names, source channel and message IDs, original dates, source links, import dates and the importing administrator’s identifier. The import reader may encounter attachment counts or embed text; it does not automatically interpret images.
• Mention entry (when the listener is enabled): messages explicitly mentioning Chorus are verified with Discord and processed to identify a handle, game, flag and note. Short conversation references are held in listener memory for up to ten minutes. Confirmed reports use the same registry as slash commands. The listener host holds the bot token as a secret; Chorus receives it transiently over HTTPS for verification and does not store it. This feature does not use an AI provider.
• Owner access: the owner-only tools receive a ChatGPT account identifier, email and optional display name to verify authorized access. Normal Discord users do not need a ChatGPT login to use the bot.
• Operation and security: command interaction IDs and timestamps help avoid duplicate processing. Hosting providers may process IP addresses, browser details, request paths, response codes, authentication cookies and security logs.
• Requests: if you submit our contact form, we store your contact email, request type and message, with any server ID, game or handle you choose to include. An obscured network identifier is used to limit spam.

Do not submit real-world identity details, financial or health information, passwords, tokens or other sensitive information in encounter notes or support requests.

03 / Why we use it

We use this information to save and retrieve reports, attribute entries, separate server records, review authorized imports, prevent duplicate entries and abuse, provide owner tools, handle requests and meet applicable obligations. We do not sell encounter records, use Discord message content to train AI models, or use report data for advertising profiles.

04 / Who can see it

Members can request reports from the server where those records are stored. A lookup reply can be visible to other people in the channel where the command is used. Discord permissions and server administration affect who can use the app and view replies. Records are not published as a searchable global database on this website.

The operator and necessary infrastructure providers can process stored information to run, secure and support Chorus. Information may be disclosed where required by law or to address security and abuse. Data may be processed outside your country; storage location depends on the hosting providers.

05 / Tokens and imports

Owner tools may ask for a Discord bot token to register commands, update the bot profile or read the specifically authorized source channel. The token is sent over HTTPS to the Chorus backend and then to Discord for the selected task. Application code does not intentionally store it in the database, browser storage or logs, and clears the form after the request finishes. Never enter a personal Discord account token.

Raw channel history is returned to the authorized owner’s browser for review. It is not automatically saved as encounter records. The current importer saves only reviewed entries; exported staging files remain under the downloader’s control. Administrators must have permission to import logs and provide appropriate notice to their communities.

06 / Local storage and providers

The website demo stores sample and user-entered demo reports in browser local storage. Demo records are separate from the bot registry. Use Reset demo or clear the site’s browser storage to remove them. Hosting sign-in and security features may use cookies or similar technologies. Chorus does not add advertising trackers.

See the privacy information from Discord, OpenAI and Cloudflare for their processing.

07 / Retention and deletion

Reports currently have no automatic expiry. They are retained while needed for the server’s field guide unless removed through commands, moderation or an operator request. They will be deleted when no longer needed for the stated service, on applicable valid deletion requests, when the service stops operating, or as required by Discord or law. Limited records may be retained where legally required.

Use /unflag to remove reports attributed to your Discord account for a handle and game. Moderators with Manage Server can use /purge to remove that handle’s reports within their server. Removing the app or deleting a Discord source message does not currently trigger automatic database deletion. Contact the operator for server-wide deletion, records about your handle, historical entries you cannot control, or deletion after leaving a server.

Support requests and security records are retained only while reasonably needed to handle the request, protect the service or satisfy legal obligations. Provider backups and operational logs may be retained under the providers’ own schedules.

08 / Your choices and requests

Depending on your location, you may have rights to access, correct, delete, receive a copy of or object to processing of personal information, and to withdraw consent where applicable. Use the request form and include enough information to locate the records, such as the server ID, game and handle. We may ask for proportionate verification before changing or disclosing records. You can also contact a server moderator for a correction or removal, and your local privacy authority for concerns about your rights.

Chorus is not intended for anyone below Discord’s minimum age or the applicable minimum age in their location. If you believe we have processed a child’s information inappropriately, contact the operator for review.

09 / Updates

The update date appears above. If our data practices materially change, we will update this policy and provide additional notice or request consent where required. Policy text does not expand the bot’s permissions or replace Discord’s own privacy controls.