Privacy Policy
Effective July 25, 2026. This policy explains what Abhi processes when the bot, dashboard, billing tools, and support workflows are used.
Data
Information we process
The exact data depends on the modules a server owner enables and the permissions granted in Discord.
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.
Discord gateway data
Privileged data is feature-scoped
Abhi requests privileged gateway access only for administrator-enabled workflows that cannot be implemented from application commands alone.
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.
Your control
User Privacy
A global Discord-account control for message, reaction, voice, video, presence, and activity analytics.
Enabling User Privacy immediately excludes your Discord account from member analytics and queues deletion across every server where Abhi has activity data for you. The job cannot be stopped and deleted records cannot be restored.
This control does not delete Discord-managed data, server roles, moderation or support records that must be retained for safety or legal obligations, or server/channel aggregate totals that no longer identify an individual.
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.
- 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 their stored activity analytics.
- 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.
- 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.
Retention
How long data is kept
The service does not represent privileged Discord data as universally retained for 30 days or less. Default windows and operational exceptions are disclosed below.
| Data | Default window | Why |
|---|---|---|
| Raw message, reaction, voice, and activity source events | Up to 400 days by default | Includes user-linked source events and completed activity sessions used to build bounded analytics views. |
| User, presence, activity, and member/pair daily facts | Up to two years (730 days) by default | Derived daily facts support historical reports and are included in the global User Privacy deletion workflow. |
| Server/channel aggregate and ranking history | While needed for the active workspace and reporting | Rollups without a user dimension may remain after user-linked records are deleted. |
| Ticket messages and transcripts | While the ticket or workspace record is retained | Support history is not represented as a 30-day-or-less data set. |
| Server configuration and role mappings | While the bot or workspace remains active | Needed to run the modules selected by server administrators. |
| Billing, security, and audit evidence | As required for accounting, disputes, abuse prevention, or law | Access is restricted to authorized operators and applicable server owners. |
Export and deletion requests
Server owners and individual Discord users may email the address below to request access, export, correction, or deletion of applicable Abhi-held data. Include the Discord user ID and server ID so we can verify the request without asking for message contents or account credentials.
We verify the requester's relationship to the account or server, review the affected records, and explain any limited records that must be retained for security, billing, disputes, or legal obligations. Revoking Discord OAuth or removing the bot stops future access but does not by itself erase records already stored by Abhi.
Privacy requests: support@abhi.gg.