VibeCoder

01Information processed and its purpose

• Development requests: messages, follow-up instructions, submitted code, images, audio, files and attachment links; author, server, channel, thread and message identifiers; and relevant task context. These are used to understand and carry out authorized requests, continue the conversation and return results. Tasks are accepted only from the owner in explicitly connected channels and threads of the development server. Ordinary messages and attachments, including follow-up messages without mentioning the bot, provide the task instructions and context.
• Staff membership and roles: Discord IDs, display names, server membership and current role names and IDs support a joint directory for the main Anteiku server, Anteiku staff server and GTA VI. People are matched across servers only by Discord ID. Positions use configured role IDs and combination rules specific to each server. The directory includes all current roles of each identified staff member on all three servers, even where that person holds no staff position. Minecraft is not connected yet. Guild Members supplies full member lists and membership/role changes; complete available-server member lists are temporarily cached in memory for matching. Separately, guest-role assignment uses join time, screening completion and permissions; joining does not authorize task submission.
• Presence coverage: the owner enables a main-server direction with /staff watch. When no member holding its base position role is Online, the bot posts in the selected management channel or thread. When someone is Online again, it updates that same message; subsequent transitions also update it. Idle, Do Not Disturb and Offline do not count as Online; Invisible is indistinguishable from Offline. Missing membership data or a disconnected Gateway is not reported as zero Online; an existing message is marked unconfirmed. The function checks current status, not a history of games, conversations or work performed. Roles and Online status do not establish actual staff activity.
• Operational records: task settings, conversation references, generated files, delivery state, message copies needed for recovery or restoration, and diagnostic records. Authorized administration tasks may also require server configuration and other Discord objects explicitly relevant to the request. These records support task execution, recovery, troubleshooting and restoration.

02AI processing and other recipients

Authorized request content and necessary context are sent to the configured AI coding service, including OpenAI, to generate answers and carry out development work. Submitted audio may be sent for transcription. If a requested task uses an external integration, the information necessary for that operation is sent to that integration. Results are returned to the relevant Discord conversation and are visible to people with access to it.

The application itself does not train or fine-tune AI models on Discord messages. This statement does not guarantee that every external provider excludes all submitted information from its own training: provider handling depends on the service and account settings. See OpenAI's privacy policy and Discord's privacy policy. Inference, provider retention and provider training are separate matters.

The owner operates the assistant and may access its records to carry out tasks, recover work and handle requests about personal data. Hosting and processing providers handle data as necessary to provide their services. We do not sell Discord data or provide it to advertising networks or data brokers. Disclosure may also be required by applicable law.

03Storage and retention outside Discord

• Current directory and coverage records: the current file contains staff IDs, display names, membership, positions and roles by server. Membership and role updates replace it; someone who no longer holds any tracked staff position leaves the current directory. Watch settings, channel/message IDs, notification state and delivery-reconciliation details are stored. Messages are copied before and after edits. These copies and exports have no automatic expiry. This function does not write individual status, game or activity timelines to disk; current member and presence caches reside in memory.
• Onboarding: member IDs and join timestamps are saved to prevent repeating guest-role assignment for the same join. These records currently have no automatic expiry.
• Task history, files and recovery copies: requests, results, exported directories and administrative backups may be retained for operation and recovery. There is no uniform automatic deletion period. Replacing the current directory does not delete older exports, Discord messages or backups.
• Discord messages: notifications, files and other results remain until deleted through Discord. Stopping a watch does not delete previously delivered messages or files.

04Your choices and deletion requests

Only the owner uses /staff watch, /staff stop, /staff status and /staff list. Watch enables the selected direction in the current channel; Stop disables it there and marks any existing message closed. The three-server membership/role directory, other enabled directions and development assistant continue operating. List returns a current CSV to the owner; an unavailable server is marked unknown rather than absent. To stop the directory entirely, the operator disables staffWatch in configuration and its connection. Stop does not erase task history, copies or exports. The former /availability commands have been removed, pending personal reminders cancelled and panels closed. If Discord prevents editing, the watch is already disabled and message closure is retried approximately every minute.

For access, correction, deletion or a request to stop further processing, contact the operator above. Provide your Discord user ID and enough information to locate the affected feature or conversation; do not send passwords or authentication credentials. The operator may verify that the request concerns your data, then review it and delete or correct records under its control as applicable. This is a manual process, not an automatic deletion command. Any information that must remain for a specific operational or legal reason, including backup limitations, will be explained in the response. A request to this operator does not itself delete information held independently by Discord or an external provider.

05Security

Access is limited by application authorization, channel permissions and host access. Current-directory and coverage-state files have restricted filesystem permissions. Secrets are excluded from responses. These measures do not guarantee that no incident can occur. Do not include passwords, access tokens or unrelated confidential information in tasks.

06This policy page and updates

This page has no analytics scripts, advertising trackers, forms or application cookies. The web server processes technical request information, including IP address, requested path, browser information, response status and request time, for delivery and security logging. Rotated access logs are limited to ten files and configured for seven-day retention; the active log and separate security records can have different lifetimes. Privacy requests about these records can be sent to the same contact.

Updates are published at this URL with a revised date. This policy describes VibeCoder's processing and does not grant access to additional servers, channels or projects.