Privacy Policy

Discord account and server identifiers

User IDs, guild IDs, role IDs, channel IDs, usernames, avatars, and OAuth profile fields needed for login and permissions.

Server configuration and feature state

Module settings, command policy, channel rules, onboarding settings, tickets, moderation records, and owner-managed plan settings.

Operational and billing records

Audit logs, health signals, trial requests, subscription state, invoices, checkout status, webhook processing status, and provider object references.

Content processed by enabled features

Messages, attachments, ticket transcripts, AI prompts, moderation context, presence activities, voice-state events, and shared voice-session totals only for enabled workflows.

Email verification records

When a server enables Email Verification, Abhi processes an encrypted normalized address, a separately keyed lookup fingerprint, a masked display value, and bounded OTP and delivery metadata. The current OTP is stored encrypted only while needed for SMTP delivery and bounded retries; a keyed digest is retained for validation. The encrypted OTP is cleared after terminal delivery or challenge expiry, and terminal challenge records are deleted after 48 hours.

Server Members

Join, leave, screening, profile, nickname, and role changes used for welcome messages, autoroles, role rules, member audit trails, and ticket-owner cleanup.

Presence

Non-bot status and activity transitions, including game, stream, Spotify, and rich-presence fields Discord provides, used to build activity sessions and server-level reports.

Message Content

Ordinary messages in configured ticket channels, staff-requested moderation scans, transcripts, enabled message games, and derived activity measurements such as message length and writing-style summaries. AI features do not train models on Discord messages.

How we use data

• Authenticate dashboard access through Discord OAuth and enforce server permissions.
• Run Discord bot commands, automations, moderation, tickets, analytics, private voice, AI controls, and billing workflows.
• Detect abuse, debug incidents, reconcile billing state, and protect the platform from unauthorized access.
• Generate operational reports for server staff and owner-only support views.

Sharing and processors

• Discord provides platform APIs and OAuth identity information used by the bot and dashboard.
• Payment and Merchant-of-Record providers handle checkout, receipts, taxes, payment method collection, and provider webhooks.
• Hosting, database, logging, and deployment providers process data as needed to operate the service.
• When Email Verification is enabled, the configured SMTP provider receives the destination address and verification message needed to deliver the one-time code, along with ordinary mail delivery metadata.
• When a server administrator activates External API eligibility, their configured directory provider receives the normalized email and server ID (unless omitted by an existing-API mapping), plus the Discord user ID only if the administrator opts in. This happens before each requested code, not when the code is entered. Provider failures never grant eligibility. Ask server staff about that provider’s data practices; information already sent cannot be recalled by Abhi.
• We do not sell personal data. We do not publish private server records outside authenticated views.

Module controls and opt-out

• Server administrators choose which modules are enabled and which channels or categories those modules may process.
• Disabling Community Analytics stops new analytics collection for that server after the setting reaches the bot runtime.
• Individual users can enable User Privacy below to stop future user-linked analytics collection and permanently delete stored activity analytics plus existing Email Verification records covered by the request. Erasing verification state queues removal of access controlled by Email Verification, so the member may need to verify again.
• User Privacy does not prevent a member from deliberately starting a later verification flow. Members may also contact Support for an applicable access or deletion request; server staff can revoke access or release a reserved account slot without viewing the full address.
• Removing the bot stops new gateway collection. Users may also contact Support for privacy requests that extend beyond activity analytics.

Security

• Dashboard access uses Discord OAuth and role-aware backend checks.
• Sensitive backend secrets stay server-side and are not stored in the dashboard application.
• Email verification addresses are encrypted before database storage and lookup uses a separately keyed fingerprint. The current OTP is stored encrypted only while needed for SMTP delivery and bounded retries; a keyed digest is retained for validation. The encrypted OTP is cleared after terminal delivery or challenge expiry, and terminal challenge records are deleted after 48 hours.
• External eligibility credentials are encrypted, write-only, and excluded from exports. Check inputs are encrypted until completion; raw provider responses are never stored. Masked runtime checks are deleted after 48 hours and administrator test receipts after 24 hours. Member and tenant erasure also remove applicable check records. Existing encrypted binding history follows the separate verification retention policy.
• Managed database and object-storage providers encrypt stored data at rest; sensitive ticket content is additionally encrypted by the application before database storage.
• Payment method details are handled by the payment service; Abhi stores bounded billing references and state, not raw card data.