Discord Bot Privacy Policy

Version: 2026-05-08 • Applies to Rozenvic Technologies and Breaking Dynamic Studios Discord bots and their connected portal services.

This policy covers our Discord bots, including Aegis Verification, Aegis Helper, Harris, and our moderation, support, linked-role syncing, ticketing, utility, logging, and purchase or service-notification bots that connect to Discord and the Rozenvic Portal.

What data the bots process

• Discord account identifiers such as user ID, username, global name, avatar hash, email address, email-verification state, locale, and Discord account flags when Discord provides them through approved scopes.
• Discord OAuth grant data and refresh metadata, including approved scopes, linked account timestamps, guild lists, guild-member snapshots in managed guilds, and linked third-party connection data such as Twitch, YouTube, Steam, or similar connection records when the user authorizes those scopes.
• Server, role, channel, and message metadata needed for verification, support, moderation, logging, linked roles, or workflow actions.
• Ticket content, command usage, audit-log actions, moderation notes, and bot interaction payloads.
• Harris AI interaction data such as prompts, replies, attachments, server/channel context, model tier selection, routing decisions, risk flags, and moderation or abuse-review notes.
• Portal-linked identity data only when required for the stated bot feature, such as Roblox username, linked Discord ID, entitlement status, department membership, invite or purchase references, and service-delivery records.
• Linked Roles metadata fields, linked-account sync results, OAuth grant outcomes, and verification or role-connection events for Aegis Verification and Aegis Helper.
• Invite-route and installation telemetry when a user opens our custom invite links, such as IP address, user agent, referer, requested guild ID, client/application ID, and the signed-in portal user when available.
• Technical events such as timestamps, action results, and internal error details needed to keep the bots stable and secure.

How we use bot data

• Verify staff, customers, and account ownership.
• Assign or sync roles, nicknames, linked-role metadata, and access controls.
• Allow or deny AI access, model tiers, and feature routing for Harris and any other portal-gated AI bot features.
• Operate ticketing, service fulfillment, moderation, safety, and internal audit logs.
• Operate Discord-linked portal features, including bot invite routing, linked-role dashboards, account linking, and per-application Discord API inventory pages inside the owner dashboard.
• Investigate abuse, platform misuse, fraud, impersonation, chargeback-related issues, unauthorized access attempts, unsafe AI requests, or other misuse of our bots and connected services.
• Maintain service health, debugging records, and compliance evidence for staff actions.
• Where a bot feature uses AI-assisted moderation or support tooling, process the minimum relevant text through our configured self-hosted AI stack or other disclosed provider for that specific feature.

How we do not use bot data

• We do not ask Discord users for Discord passwords, login tokens, or other account credentials through our bots.
• We do not use Discord API data for unrelated advertising, data brokering, or resale.
• We do not sell Discord API data.
• We do not use Discord message content obtained through the API to train AI models unless a platform provider expressly authorizes that use and the product feature states it separately.

Sharing and disclosures

• Bot data is shared internally with Rozenvic Technologies staff who need it to operate moderation, support, verification, billing, or security workflows.
• Bot logs may be copied into the Rozenvic Portal, Discord log channels, or internal records where required for operations or compliance.
• We may disclose data where required by law, to protect users or our services, or to respond to security incidents.
• Where a bot action relies on a connected service such as the Rozenvic Portal, Stripe, Roblox, Authentik/RT SSO, a self-hosted AI service, or Discord itself, only the minimum practical data is transmitted for that feature.

Retention

We retain bot-related records only as long as needed for moderation history, security investigations, fulfillment, billing support, dispute handling, linked-role integrity, or other legitimate operational needs. Some ephemeral bot events are not retained, while audit, invite-click, ticket, verification, or linked-role sync records may be retained longer when needed for staff accountability, fraud review, or legal compliance.

Security

We use HTTPS/TLS in transit where supported, restricted bot tokens and API keys, role-based staff access, and audit logging for sensitive actions. Internal bot APIs are protected and are intended for server-side use only, including localhost-only bridge calls protected by secret headers.

Your choices

• You can remove a bot from a server if you have the required Discord permissions.
• You can unlink your connected Discord account from the portal where unlinking is offered.
• You can request review or deletion of portal-stored bot-related personal data by contacting us, subject to security, fraud-prevention, moderation-history, and legal-retention requirements.

Discord OAuth scopes and linked-account note

Aegis Verification, Aegis Helper, Harris, and other connected portal flows may request approved Discord OAuth scopes such as identify, email, guilds, guilds.join, guilds.members.read, connections, and role_connections.write when those scopes are needed for account linking, role sync, DM workflows, server access, or abuse review. Bot installation flows can also use bot and applications.commands.

Aegis Verification and Aegis Helper rely on Discord Linked Roles, Discord OAuth, and portal account linking. Linked-role state can depend on the accuracy of the linked Discord account, the portal account, the relevant business or entitlement records, and the server’s own Discord-side Linked Roles configuration. Discord currently documents activities.read as not currently available for apps, so we do not rely on that scope unless Discord later makes it available to the relevant application.

Discord platform compliance

Our bots are intended to operate in line with Discord’s Developer Terms and Developer Policy. Discord may also collect and process data independently under Discord’s own policies when you use Discord or authorize an application.

Contact

For privacy or bot-data questions, contact enforcement@rozenvictechnologies.net.