1. What the bot collects
The bot processes interactions you initiate, including slash commands, autocomplete, buttons, menus, form submissions, and direct replies to an active /chat answer. When public chat is enabled, Discord provides server message events so the bot can identify those replies. It disregards unrelated messages.
- Discord account and interaction data. The bot receives your Discord user ID and username, interaction ID, and, when available, server and channel IDs, installation information, and permissions. It uses this information to handle interactions, associate saves with your account, and check who can use controls or share a result.
- Character profiles and season saves. If you create a profile, the bot stores its name, season, and the values you enter, such as a game player number, progression, equipment, and resources. It uses these details to retrieve your saved settings and run calculations across Discord contexts.
- Game knowledge contributions. When you use
/remember game_info, the bot screens and masks the text, then stores accepted text and its search vectors with your Discord user ID, a contribution ID and a timestamp. Other players can retrieve or see excerpts of the accepted text and its contribution ID through/askand/chat. Optional links and image files are kept as supporting material for the operator. Private memories submitted before this change remain private. - Diagnostic logs. To troubleshoot errors and track whether replies were delivered, the bot records account and interaction metadata, command names, timestamps, trace IDs, timings, errors, and applicable inputs and results. The bot masks selected values such as recognized credentials and full game player numbers in logs. For
/askand/remember, the logs record metadata such as result type, source IDs, or which types of memory content were saved. The question and answer text and the contents of memories are omitted from those logs. - Public chat and moderation. For
/chatand replies to its answers, the bot records Discord user, server, channel and message IDs, timestamps, moderation decisions and delivery status. It stores text that passes screening after masking recognized sensitive values. Rejected text is omitted. When a confirmed violation triggers a block, the bot keeps a separate account-level record to enforce it across servers for/chatand/ask.
2. How /ask and /chat work
For /ask and /chat, the bot sends masked text to Wafer for safety classification, directly or through OpenRouter. For public chat, the requests can include recent accepted messages from the reply chain. Wafer also generates the public answers. Classification can receive text that is subsequently rejected. The bot keeps the Discord identifiers it uses for access checks separate from model requests.
When you run /ask and the feature is enabled, the bot applies masking for recognized sensitive patterns and sends the resulting question text to its configured embedding service. This service converts the question into a representation the bot uses to look up relevant game information.
When the answer service is enabled and the bot generates an answer, it sends the masked question and matching game knowledge excerpts to that service. The bot can also return a source excerpt directly or report that it found no match.
For /remember, the bot sends the masked text to its safety classifier and sends accepted text to its configured embedding service to build the search index. The provider receives the text separately from your Discord account ID and supporting attachments.
When public chat looks up information, it first checks the bot’s local knowledge database. If that database lacks enough information, the bot can send DuckDuckGo a short, screened search query. It can send selected excerpts to the chat model and include sources in the public answer. Avoid sharing credentials or sensitive personal information in either AI feature. Masking covers recognized patterns only.
4. Storage and retention
The bot stores profiles, private memories, knowledge contributions, diagnostic logs, chat turns and AI access blocks in PostgreSQL. It keeps profiles, private memories and knowledge contributions until they are removed. It retains access block records while the block is in effect, subject to applicable deletion requirements.
The software defaults to 30 days for chat and diagnostic logs. The operator can configure a different period. The bot periodically deletes expired records. A local queue temporarily holds diagnostic events until the database accepts them.
5. Your data choices
Use /profile edit to update a profile or /profile delete and its confirmation prompt to delete that profile and its season saves. This command applies to the selected profile. Private memories and diagnostic logs are stored separately.
Use the private Discord contact below to request access to, correction of, or deletion of your bot data, including knowledge contributions, chat records, private memories and logs. Provide your Discord user ID and enough detail to identify the records. Include relevant contribution, message or memory IDs if available. The operator may verify that you control the account before processing a request. Keep passwords and access tokens out of any request.
Uninstalling the bot stops your use of it. To request removal of data already stored by the bot, use the deletion options above. Discord manages requests for information it holds separately.
6. Operator and contact
For privacy questions and data requests, contact either maintainer below. Policy updates will appear on this page with their effective date.
- Operator
- Primostar Calculator project maintainers
- Private contact
- Send a Discord direct message to
@gary05cxor@adi1210.