vams.dev / G.U.R.T.
Privacy Terms
G.U.R.T. · Discord bot

Privacy Policy

Effective date: 10 October 2026

This policy explains what information G.U.R.T. (General Utility & Roblox Tool) processes when you use the bot in a Discord server, why it is used, and how to contact the operator about it.

Who operates G.U.R.T.

G.U.R.T. is operated by the owner of this site for Roblox Events Community features on Discord. Discord separately processes your Discord account and activity under its own Privacy Policy. This notice covers the bot’s processing and is not a replacement for Discord’s policy.

Information the bot processes

  • Discord identifiers and server details: your Discord user ID and, where a feature needs it, username/display name, guild ID, channel or thread IDs, roles, and interaction details.
  • Feature records: verification and role state, Roblox account IDs/usernames linked through verification, clan or event participation, virtual economy balances and inventory, purchases or payment status, and leaderboard records.
  • Messages and support tickets: message text, attachment URLs, authors and timestamps in Contact a Staff tickets are relayed to staff and saved so a ticket transcript can be produced. Closing a ticket deletes its private user thread, while the staff record and transcript may remain.
  • Usage and activity statistics: the recap feature records message counts and patterns, frequently repeated short phrases, channels and time patterns, commands, reactions, mentions, replies, and voice-channel join/leave times and durations. It does not record voice audio. Recap documents are grouped by user, server, and year.
  • AI chat inputs: in configured AI channels, the current message, up to ten recent messages used as chat context, and attached images may be sent to Google Gemini to generate a reply.

How information is used

The bot uses this information to respond to commands, provide Roblox verification and event features, apply server roles, enforce server link and attachment rules, operate support tickets, maintain virtual economy and leaderboard features, and produce activity recaps. AI chat inputs are used to generate a response. The operator does not use bot data to train or fine-tune a model.

Where information is processed

Bot records are stored in a MongoDB database configured by the operator. Discord data is also transmitted to Discord to operate the bot and server features. Roblox account and game features use Roblox services and APIs; Roblox identity lookups may use Bloxlink. Where payment-related features are enabled, the bot may keep a Discord ID, payment status, and timestamp; payment card details are handled by the payment provider and are not stored by the bot.

AI chat content is sent to Google’s Gemini API. Google’s handling depends on the API project and service plan: under Google’s current Gemini API terms, inputs and outputs from unpaid services may be used to improve Google products and machine-learning technologies, while paid Gemini API services do not use prompts and responses for that purpose. The operator should keep the bot’s deployed billing configuration and Google terms current. Do not send sensitive or confidential information to the AI feature.

These providers process information under their own terms and privacy notices. The bot operator does not sell personal information.

Retention and deletion requests

The bot does not currently publish a fixed automatic deletion period for every database record. Recap records are organized by calendar year, but the source does not schedule their automatic deletion. Closed ticket conversations may remain in the staff archive after the private user thread is removed. Other feature records may remain while they are needed to provide the feature or administer the server.

You can ask the operator to review or delete records associated with your Discord account. Send a request through the server’s Contact a Staff feature or message the operator at their Discord profile. The operator may need to verify that you control the account and may retain information where required for security, moderation, financial records, or legal obligations. Leaving a server or stopping use of the bot does not automatically erase existing records.

Choices and opt-outs

Some users are excluded from recap collection through an operator-managed list. There is currently no general self-service opt-out that stops all message processing: commands, moderation, AI chat, and tickets process relevant messages to provide their features. You may avoid optional features such as AI chat and may contact the operator with a data request. Server administrators can remove the bot from their server.

Security and changes

The operator uses service and database access controls intended to limit access to bot records. No internet service can guarantee complete security. This policy may be updated when the bot or its data practices change; the effective date above will be revised when that happens.

Contact

For privacy questions or account-data requests, use Contact a Staff in the server where G.U.R.T. is used, or contact the operator through Discord.

This notice describes the bot’s current implementation. It does not describe separate data processing performed by Discord, Roblox, Google, MongoDB, Bloxlink, or payment providers.

© 2026 G.U.R.T. · vams.dev Privacy Policy · Terms of Service