BotPrivacyPolicy

Gor Discord Bot

Privacy Policy

Effective Date: August 2, 2026
Last Updated: August 2, 2026

This Privacy Policy explains what information the Gor Discord Bot may collect, why it is collected, how it is used, how long it may be retained, and how users may request access to or deletion of their information.

Privacy Summary: The Bot collects only information reasonably needed to provide its Discord, roleplay, moderation, security, and game-integration features. Discord information is not sold to advertisers or data brokers. Optional third-party artificial-intelligence processing is disabled unless enabled by the Bot Operator.

1. Scope of This Policy

This Privacy Policy applies to the Gor Discord Bot and related services operated by the Gor administration team.

This may include:

Discord slash commands.
Message commands such as =say, =Menu, and =bio.
Character profiles and avatars.
Webhook-based character speech.
Conversation memory and personality systems.
Gossip, sensory, knowledge, and relationship systems.
Moderation and role-management features.
Security, diagnostic, and watchdog logging.
Optional third-party artificial-intelligence features.
Optional RunUO, NPC, item, equipment, or game-server integrations.
Optional player-profile websites or administrative interfaces.
JSON, MySQL, MariaDB, PostgreSQL, or MongoDB storage systems.

This policy applies only to information processed by the Bot and its Operator. Discord and other third-party services maintain their own privacy policies.

2. Information We May Collect

The exact information collected depends on which Bot features are enabled and how you interact with them.

2.1 Discord Account and Server Information

The Bot may receive and store information supplied through the Discord API, including:

Discord user ID.
Discord username.
Discord display name or nickname.
Discord avatar reference.
Discord guild or server ID.
Discord channel ID.
Discord message ID.
Discord role IDs.
Discord thread or forum-post ID.
Discord locale or language setting.
Server membership information.
Permissions relevant to Bot commands.
Information indicating whether an account is a bot or application.

The Bot primarily uses numeric Discord identifiers to associate information with the correct user, server, channel, message, or role.

The Bot does not need your Discord password and will never intentionally ask you to provide it.

2.2 Messages and Commands

When you interact with the Bot, it may process:

Slash-command names and options.
Message-command text.
Messages beginning with configured Bot prefixes.
Messages directed at a conversational character, NPC, or item.
Character dialogue submitted through =say.
Biography text submitted through =bio.
Button, menu, autocomplete, and context-menu selections.
Messages involved in moderation or security review.
Messages needed to maintain conversation continuity.

The Bot does not necessarily store every Discord message it can see.

Message content is normally processed only when it is relevant to a configured feature, such as:

A Bot command.
Character roleplay.
A direct mention.
A configured roleplay channel.
NPC interaction.
Moderation.
Security investigation.
Conversation memory.

2.3 Character Profile Information

Character profiles may contain:

Character ID.
Character name.
Discord-owner ID.
Active-character selection.
Biography.
Avatar URL or locally cached avatar.
Activation prefix or suffix.
Gender.
Pronouns.
Roleplay status.
Free-person, master, mistress, kajira, kajirus, or other fictional role.
Fictional owner or relationship information.
Caste.
Profession.
Culture.
City or homeland.
Speech style.
Personality traits.
Lore and background.
Preferred forms of address.
Profanity or mature-content preferences.
Privacy and visibility settings.
Preset-profile selection.
Creation and modification dates.

Character profiles may be displayed publicly in Discord when a user chooses to speak through that character.

A future player-profile website may permit authorized users to view or modify this information.

2.4 Conversation and Roleplay Memory

The Bot may maintain limited memory to improve conversational continuity.

Conversation records may include:

User or player identifier.
Character, NPC, equipment, or conversation-partner identifier.
Recent messages.
Summarized conversation topics.
Important remembered statements.
Relationship state.
Personality development.
Mood or disposition.
Trust, familiarity, hostility, respect, dominance, or submission values.
Preferred names and forms of address.
Fictional ownership or slavery-role context.
Gossip or knowledge learned during roleplay.
Sensory or environmental context.
Conversation timestamps.
Response-quality and watchdog information.

Conversation memory may be stored separately for each combination of user and conversation partner.

The Bot is designed to limit memory growth through:

Per-conversation storage limits.
Maximum entry counts.
Duplicate removal.
Text-length limits.
Age-based retention.
Periodic trimming.
Aggregate storage limits.

2.5 Gossip, Knowledge, and Sensory Information

Administrators may add roleplay information that the Bot can use during conversations.

This may include:

Fictional rumors.
World lore.
Location descriptions.
Cultural information.
Historical information.
Relationship facts.
Character observations.
Environmental details.
Sounds, smells, weather, or nearby events.
Information learned from roleplay interactions.

Administrators should not enter sensitive real-world personal information into the Bot’s gossip or knowledge systems.

2.6 Moderation Information

When moderation features are enabled, the Bot may store:

Warning records.
Moderation reasons.
Staff-member ID.
Affected user ID.
Relevant message or channel ID.
Timeout, mute, kick, or ban information.
Dates and timestamps.
Appeal or review notes.
Evidence reasonably needed to enforce server rules.

Moderation information may be retained longer than ordinary conversation history when necessary to enforce server rules, investigate abuse, or protect users.

2.7 Operational and Diagnostic Information

The Bot may create operational logs containing:

Startup and shutdown information.
Gateway connection events.
Discord REST API requests and failures.
Rate-limit responses.
Reconnection attempts.
Heartbeat delays.
Command usage.
Feature errors.
Unhandled exceptions.
Webhook failures.
Queue size or processing delays.
Storage errors.
Database migration status.
Memory-pressure warnings.
Health-check results.
Configuration changes.
Administrative actions.
Security events.
Suspicious or unusual activity.

Log records may include relevant Discord IDs and limited message context when needed to understand an error or incident.

The Bot is designed to redact sensitive credentials such as:

Discord Bot tokens.
Webhook tokens.
Discord interaction tokens.
Third-party API keys.
Database passwords.

Users should nevertheless avoid posting credentials or other secrets through Discord commands.

2.8 Conversation Watchdog Information

The conversation watchdog may record interactions where a response appears to have failed or behaved unexpectedly.

A watchdog record may contain:

User message.
Bot response.
Character or conversation-partner ID.
Detected problem.
Possible cause.
Confidence estimate.
Suggested improvement.
Relevant personality, topic, or intent information.
Date and time.

Examples of detected issues may include:

Empty responses.
Repeated responses.
Responses that echo the user.
Responses that are unusually short or long.
Out-of-character responses.
Generic or unresolved responses.
Contradictory responses.
Responses that fail to use known roleplay information.

Watchdog suggestions are intended for staff review and are not automatically applied.

2.9 Avatar Information

When users provide character avatars, the Bot may:

Store the original avatar URL.
Download a copy of the avatar.
Validate its content type and size.
Cache it locally.
Serve it through a configured avatar-proxy address.
Associate the cached image with a character profile.

Cached avatars may remain available until:

The character changes its avatar.
The character is deleted.
An administrator clears the avatar cache.
A retention or storage limit removes the file.
The Bot service is discontinued.

Users should upload only avatars they have permission to use.

2.10 Optional Game-Server Information

If game integration is enabled, the Bot may process:

RunUO player serial.
Character serial.
NPC serial.
Equipment or item serial.
NPC name and profile.
Player name.
Character gender.
Location, map, region, or environmental information.
Speech directed toward NPCs.
Item or equipment interaction.
Relationship and conversation history.
Game-account linkage information.

NPC, attachment, equipment, and EventSink integration are optional and may be disabled.

2.11 Optional Website Information

A future character-profile or administrative website may process:

Authentication information.
Discord account linkage.
Website session identifiers.
IP address.
Browser and device information.
Profile-editing requests.
Character-ownership checks.
Security and audit records.
API access logs.

Any public website should use authenticated, permission-checked profile interfaces rather than direct access to Bot storage.

Additional website-specific notices may be provided if such a website is launched.

3. Information We Do Not Intentionally Collect

The Bot is not designed to intentionally collect:

Discord passwords.
Payment-card information.
Banking information.
Government identification numbers.
Social Security numbers.
Private authentication tokens supplied by users.
Medical records.
Precise real-world location.
Biometric information.
Advertising profiles.
Information for sale to data brokers.

Do not submit this kind of information through the Bot.

If sensitive information is submitted accidentally, contact the Operator and request its removal.

4. How Information Is Used

Information may be used to:

Authenticate and associate Discord users with their profiles.
Operate slash commands and message commands.
Register, edit, and select characters.
Display character names, biographies, and avatars.
Relay messages through Discord webhooks.
Delete original command messages after successful webhook replacement.
Maintain conversation continuity.
Develop character or NPC personality traits.
Apply gender-aware and role-aware speech.
Provide gossip, sensory, relationship, and knowledge features.
Operate moderation and role-management tools.
Enforce Discord and server rules.
Detect spam, abuse, security threats, and misuse.
Investigate technical failures.
Diagnose connection and database problems.
Improve Bot responses.
Review watchdog suggestions.
Maintain backups.
Synchronize supported storage providers.
Protect the Bot, Discord server, game server, and users.
Comply with legal requirements.

Information will not intentionally be used for unrelated advertising or sold to data brokers.

5. Legal and Operational Basis for Processing

Depending on the jurisdiction and circumstances, information may be processed because:

Processing is needed to provide a feature requested by the user.
Processing is needed to operate the Discord server.
The user or server administrator has consented to a feature.
The Operator has a legitimate interest in operating, securing, and improving the Bot.
Processing is needed to enforce server rules.
Processing is needed to investigate abuse or security incidents.
Processing is required by law.

Optional features that materially change how information is processed should be disabled unless configured by an authorized administrator.

6. Webhook Character Messages

When a user submits a command such as:

=say Hello.

the Bot may:

Read the user’s active-character selection.
Read the character’s name and avatar.
Create or use a Discord webhook.
Post the supplied dialogue through that webhook.
Delete the original command after successful delivery.
Record operational information about the request.

Webhook messages may display the character’s identity instead of the Discord user’s visible identity.

The Bot still associates the character profile internally with its Discord owner.

Discord server administrators and authorized Bot staff may be able to determine which user controls a character.

7. Optional Third-Party Artificial Intelligence

Third-party artificial-intelligence integration is disabled by default.

If an authorized administrator enables it, information sent to the provider may include:

The current user message.
Recent conversation context.
Character name and biography.
Personality traits.
Roleplay role and gender.
Relationship state.
Relevant memories.
Gossip or knowledge.
A draft response generated by the local conversation engine.
Watchdog information submitted for improvement suggestions.

Information transmitted to a third-party AI provider is governed by that provider’s terms and privacy practices.

The Operator should:

Enable the feature only when necessary.
Use the minimum context reasonably needed.
Avoid transmitting credentials or highly sensitive information.
Review the provider’s data-retention controls.
Inform users when third-party processing is active.
Disable provider-side training or retention where supported and appropriate.

Users should not submit sensitive personal information to AI-enabled conversations.

8. Storage Locations and Providers

The Bot may store information using one or more of the following:

Local JSON files.
Local avatar-cache files.
Local log files.
MySQL.
MariaDB.
PostgreSQL.
MongoDB.
Backups or emergency snapshots.

JSON is the default local storage option.

External database storage may be enabled by an administrator.

When external storage is used, connection information may include:

Database hostname.
Port.
Database name.
Username.
Password.
Connection-string options.
Encryption or TLS settings.

Database credentials are administrative secrets and are not intended to be disclosed to ordinary users.

9. Data Retention

Information is retained only as long as reasonably needed for the feature, security purpose, moderation requirement, or legal obligation for which it was collected.

9.1 Conversation Memory

Available conversation-memory retention settings may include:

Two months.
Three months.
Six months.
Twelve months.
Permanent retention.

The actual setting is chosen by the Bot Operator.

“Permanent” means no automatic age-based expiration is configured. It does not guarantee that information will never be deleted, lost, trimmed, migrated, or removed.

Conversation information may still be removed because of:

Per-partner size limits.
Aggregate storage limits.
Duplicate removal.
Administrative deletion.
Character deletion.
User deletion request.
Database maintenance.
Service discontinuation.
Security requirements.

9.2 Logs

Logs stored under:

Gor\Logs\DiscordBot

are subject to the Bot’s configured log-retention controls.

The intended maximums are:

No more than approximately 50 MB of Discord Bot logs.
No log file retained for more than approximately eight months.

Logs may be removed earlier during maintenance, troubleshooting, or storage cleanup.

Security, moderation, or legal records may be retained separately when reasonably necessary.

9.3 Character Profiles

Character profiles may remain stored until:

The user deletes the character.
Staff removes the character.
The Discord account is no longer authorized.
The server removes the Bot.
The user submits a valid deletion request.
The Service is discontinued.
Retention is no longer necessary.

9.4 Backups

Deleted information may remain temporarily in backups or database snapshots.

Backups are removed according to the Operator’s backup schedule and are not normally restored solely to recover an individual deleted record.

If a backup is restored, previously deleted data may be deleted again during the next cleanup process.

10. Sharing and Disclosure

Information may be disclosed only as reasonably necessary to:

Operate the Bot.
Display user-requested content in Discord.
Relay messages through Discord webhooks.
Use a configured storage or hosting provider.
Use an optional third-party AI provider.
Investigate abuse, fraud, or security incidents.
Comply with a valid legal obligation.
Protect users, the Operator, Discord, or the Service.
Complete a user-directed integration.

Information may be accessible to:

The Bot Operator.
Authorized Discord server administrators.
Authorized game-server administrators.
Developers maintaining the Bot.
Hosting or database service providers.
Discord.
An optional AI provider when enabled.
Legal authorities when disclosure is legally required.

Discord information is not intentionally:

Sold.
Rented.
Licensed to data brokers.
Shared with advertising networks.
Used for unrelated targeted advertising.

11. Public Information

Some information is intentionally displayed publicly or to other Discord members.

This may include:

Character name.
Character avatar.
Character biography.
Character speech.
Roleplay profile fields.
Public command responses.
Selected roles.
Publicly displayed relationship or lore information.
Messages posted through a webhook.

Do not place private or sensitive information in fields intended for public display.

12. Security Measures

The Bot may use safeguards including:

Permission checks.
Allowed-guild restrictions.
Command cooldowns.
Input-length limits.
Queue limits.
Storage-size limits.
Rate-limit handling.
Secret redaction.
Encrypted webhook-token storage.
Restricted administrative commands.
Loopback-only administrative or health services.
Avatar size and content validation.
URL and redirect validation.
Database revision checks.
Database leases or synchronization controls.
Audit and security logs.
Automatic error recovery.
Memory and resource guardrails.

No method of electronic storage or transmission is completely secure.

Users are responsible for protecting their Discord accounts and should report suspected unauthorized access promptly.

13. Children’s Privacy

The Bot is intended for an adult roleplay community and is not directed toward children.

Users must satisfy:

Discord’s age requirements.
The age requirements of the applicable Discord server.
Any higher age requirement stated in the Gor Discord Bot Terms of Service.

The Gor community may require users to be at least eighteen years old because of mature roleplay content.

The Operator does not knowingly intend to collect personal information from children through the Bot.

If information belonging to an underage user is discovered, the Operator may suspend access and remove the information where reasonably possible.

14. International Processing

Discord, hosting providers, database providers, and optional third-party services may process information in locations outside the user’s state, province, or country.

Those locations may have different privacy laws.

By using the Bot, users understand that information may be processed where the Operator or applicable service providers maintain systems.

15. User Rights and Requests

Depending on applicable law, users may have rights to:

Ask whether information about them is stored.
Request access to stored information.
Correct inaccurate profile information.
Request deletion.
Object to certain processing.
Restrict certain processing.
Withdraw consent for optional features.
Receive a copy of certain information.
File a complaint with an appropriate privacy authority.

Not every right applies in every jurisdiction.

The Operator may need to verify that the requester controls the relevant Discord account before fulfilling a request.

Verification may require:

A request from the affected Discord account.
Confirmation through an official support channel.
Discord user ID.
Character ID or name.
Other information reasonably necessary to prevent unauthorized disclosure or deletion.

16. Requesting Data Access or Deletion

To request access, correction, or deletion, contact the Gor administration team through an official support method.

Include:

Your Discord user ID.
Your Discord username.
The Discord server involved.
The characters or information involved.
Whether you are requesting access, correction, or deletion.
Any relevant details needed to locate the information.

Privacy Contact: Add your official email address or Discord support channel here.
Discord Support Channel: Add the official channel or ticket-system location here.
Expected Response Time: Requests will be reviewed within a reasonable period.

Deletion requests may not require removal of information that must reasonably be retained for:

Security.
Fraud prevention.
Moderation.
Legal compliance.
Exercise or defense of legal claims.
Protection of other users.
Temporary backup processing.

When retention is required, the information will be limited to the purpose requiring retention where reasonably possible.

17. Server Administrator Responsibilities

Discord server owners and administrators who install the Bot should:

Make this Privacy Policy available to members.
Configure only the permissions the Bot needs.
Enable only features appropriate for their community.
Inform users when optional AI processing is enabled.
Protect database and Bot credentials.
Limit access to the administration gump.
Review logs responsibly.
Avoid entering sensitive personal information into gossip or knowledge systems.
Respond appropriately to privacy and deletion requests.
Remove the Bot if they no longer accept these practices.

Server administrators may create their own additional privacy notices, but those notices should not conflict with this policy, Discord’s rules, or applicable law.

18. Data Breaches and Security Incidents

If the Operator becomes aware of unauthorized access that may materially affect user information, the Operator will take reasonable steps to:

Investigate the incident.
Secure affected systems.
Reset compromised credentials.
Limit further unauthorized access.
Preserve necessary evidence.
Notify affected users when legally required or reasonably appropriate.
Notify Discord when required.
Remove or correct exposed information where possible.

Users who discover a possible vulnerability should report it privately and should not publicly disclose credentials, personal information, or exploit details.

19. Removal of the Bot from a Server

Removing the Bot from a Discord server prevents it from receiving new events from that server.

Removal does not necessarily delete existing:

Character profiles.
Conversation memories.
Moderation records.
Logs.
Avatar-cache files.
Backups.
Database records.

A server owner or affected user should submit a deletion request if stored information should also be removed.

The Operator may automatically delete or archive information belonging to inactive or removed servers.

20. Changes to This Policy

This Privacy Policy may be updated when:

Bot features change.
Storage systems change.
Third-party providers change.
Discord requirements change.
Legal requirements change.
Security practices change.
A profile website or game integration is launched.

The latest version will be posted on this page with an updated revision date.

Material changes may also be announced through Discord or another official Gor communication channel.

Continued use of the Bot after a revised policy takes effect constitutes acknowledgment of the revised policy.

21. Related Policies

Use of the Bot is also governed by:

22. Contact Information

Questions or privacy requests should be directed to the Gor administration team.

Bot Operator: Gor Administration Team
Website: gor.onlyotaku.com
Privacy Contact: Add an official email address or support channel here.
Deletion Requests: Add your official Discord ticket or support process here.

Gor Discord Bot • Privacy Policy
This Bot is an independent community project and is not affiliated with or endorsed by Discord Inc., Electronic Arts, Broadsword Online Games, or the owners of Ultima Online.