Skip to content
OmniCore
HomeFeaturesCommandsGuidebookAboutSupportAdd OmniCore to Discord ↗

Legal

Privacy Policy

How the OmniCore Discord Bot and this website handle information.

Effective October 3, 2026 Last updated November 8, 2026

Who operates OmniCore

OmniCore is an independent Discord bot developed by Shresht Hiremath and Arnay Kumar. This policy covers the bot and this informational website. Discord operates its own platform and has separate privacy terms.

Information the bot receives

Discord sends OmniCore command interactions and gateway events needed for its features. This can include user and server IDs, channel and role IDs, usernames, member and role details, command names and options, and message metadata. The bot requests Message Content and Guild Members privileged intents for text commands, AI mentions, and member-based moderation. It does not request Guild Presences or automod gateway events.

The bot sees new server messages for AutoMod, which is enabled by default and can be disabled by the server owner. A local screen selects messages that may need review; only those selected messages are sent to the configured Ollama endpoint for contextual classification. The current classifier sends the selected message and small non-content signals such as repeat and mention counts, not surrounding chat history. In an approved server, the bot also processes messages that mention or reply to OmniCore for conversational AI. The purge command fetches messages to delete them. The bot does not store every message it receives. For an explicit image question, it may receive image attachments from the invoking message or the exact Discord message directly replied to; it does not search channel history for images.

Information saved in MongoDB

OmniCore stores server settings, channel lock records, and a 24-hour warning record for repeat AutoMod violations. Approved servers using the existing locally hosted assistant also retain AI conversation turns for about 30 days. Flagged AutoMod message text is not saved in incident analytics or added to AI conversation history. A sanitized excerpt of up to 800 characters is kept temporarily in pending notification delivery records.

Moderation analytics and delivery records keep minimal metadata for up to 90 days: incident and server IDs, member ID and username, channel ID, category, severity, action, duration, time, recipient IDs, and delivery status. The incident analytics contain no offending message text. Pending delivery records can temporarily contain a sanitized excerpt; the bot removes it after successful delivery or final failure. If a server owner connects an AI provider, its API key is encrypted with AES-256-GCM before storage. The server's provider, model, limits, and request/token usage metadata are stored separately. AI usage records expire after up to 90 days and do not include prompts. Vision usage metadata also records whether a request succeeded and how many images were submitted, without image bytes or descriptions.

Private chat approval

A first written DM from someone without private-chat access creates a request for OmniCore bot owners. The bot sends the owners the sender's username, user ID, and a sanitized excerpt of the first message. The request record stores the username, ID, status, and time, but not the message text. Pending and denied request records expire after 30 days. Approved access and per-user bot-owner and user prompt preferences remain until revoked or deleted. Approved private text questions go to local Ollama without persistent conversation history; Discord retains the DM messages under its own policies. Bot-owner preferences take priority over user preferences. The separate DM image feature still requires a server owner's provider key and explicit billing opt-in. Use /delete_my_data to delete your stored access and prompt preferences, which also revokes private-chat access.

How information is used

Settings enforce server choices. AutoMod uses selected messages during a short-lived incident, then records metadata for analytics and a short excerpt for alert delivery. Successful warnings and timeouts send a DM to the server owner and to OmniCore's two developers. These alerts include the server, username and user ID, action, reason, time, status, channel, and a sanitized excerpt of the flagged message. A server owner can disable developer diagnostic alerts with /automod diagnostics; owner alerts can be controlled separately. If the owner DM fails, OmniCore tries an explicitly configured private moderation channel. Operators can access aggregate and per-server analytics; each server owner can see only their own server.

Operational logs may contain command names, Discord IDs, and error details. Hosting systems and Cloudflare may retain logs under their own settings. The OmniCore site Nginx access log is disabled for the secure pairing route. The public website has no ad tracker or analytics script.

AI and outside services

The existing approved-server assistant and AutoMod classifier use the configured local Ollama endpoint. AutoMod warns on a first confirmed violation and may time out an eligible member after another confirmed violation within 24 hours, subject to policy, Discord permissions, and a 48-hour maximum. Server owners and protected staff receive warnings but are not automatically timed out. Discord receives bot replies, DMs, and moderation actions and controls their retention.

If the server owner chooses a Bring Your Own Key provider, OmniCore sends an authorized member's submitted /ask question or bot mention to that server's selected OpenAI, Anthropic, or Gemini API. For an explicit image-analysis request, it sends the current question and only the validated images attached to that message or its exact direct reply target to the selected provider. The provider may process and retain it under its own policies; review OpenAI API data controls, Anthropic commercial terms, and Gemini API terms for the provider you choose. These requests use the server's key and may be charged by that provider. A ChatGPT subscription does not supply OpenAI API credits. OmniCore does not send AutoMod classification requests through a server's paid key. Existing locally hosted AI history remains subject to its separate 30-day retention. Wikipedia lookups can send search terms to Wikimedia.

Image analysis requires a direct invocation. In bot-owner-approved servers, explicit image questions use the configured local Ollama vision model without a server provider key. In unapproved servers, image questions use a server owner's connected vision-capable provider key when one is configured. OmniCore does not search older unrelated messages, other channels, other servers, AI history, or cached images for image content. A normal image post without an image question to OmniCore is not analyzed by vision. In DMs, a server owner must explicitly enable use of that server's key for vision, and the bot verifies ownership before billing it. Vision requests use the guild's existing request limits. Requests sent to a connected third-party provider may incur additional API charges. Downloaded image bytes and converted GIF frames are held only for the current request, with a roughly one-minute processing deadline, and are not saved to files, MongoDB, or future AI conversation context. Provider-side retention follows the selected provider's terms and is not controlled by OmniCore.

Discord authenticates server owners for secure key pairing; the portal checks current ownership, keeps short-lived session data in memory, and never shows a stored key. Cloudflare routes the HTTPS site and may process connection metadata under its privacy policy.

Former voice assistant

OmniCore’s voice assistant is currently unavailable. Earlier opted-in voice sessions used local speech recognition and text-to-speech. Transcripts and bot replies posted to Discord text channels remain subject to Discord and server retention practices. Raw voice audio and transcripts were not saved to OmniCore’s database; limited guild/day usage counts and timing metadata could remain for up to 90 days. Text sent to a connected AI provider during an earlier session remains subject to that provider’s terms.

Retention and deletion

OmniCore keeps different kinds of data for different periods. The periods below describe the bot's current storage, not information retained independently by Discord or hosting providers.

Data retention summary
DataRetention
AI conversation historyAbout 30 days from each turn's creation; automatic MongoDB expiration.
Temporary AI chat contextRecent AI turns from the same 30 day history; no separate chat session collection.
AutoMod incident contextSelected message content is held in memory for the current incident and removed after processing or approximately 60 seconds; no persistent incident content is saved.
AutoMod warning stateServer and member IDs, warning time, and expiration time are used for 24 hours to decide whether the next confirmed violation is timed out; background deletion may occur shortly afterward.
Server settingsWhile OmniCore remains installed and the settings are needed; deleted on confirmed removal.
Channel lock mappingsWhile a lock is active; removed on unlock or confirmed server removal.
Application and website logsNo fixed bot-controlled expiration period; host log settings apply.
Moderation analytics and delivery recordsMetadata for up to 90 days. A sanitized message excerpt is kept in pending delivery records until delivery succeeds or reaches final failure; undelivered records expire after at most 90 days.
BYOK provider credentialUntil the owner disconnects or removes the bot; encrypted before storage.
BYOK usage recordsUp to 90 days; no prompts or image content.
Voice audio and transcriptsIn memory only for the current voice turn; not saved to files or MongoDB. Segments are bounded to 10 seconds. Temporary conversation text clears on opt-out, departure, or disconnect.
Former voice usage recordsGuild/day counts and timing metadata from earlier sessions for up to 90 days; no audio or transcripts.
Vision image bytesOnly in memory for the current request, subject to a roughly one-minute deadline; no local image file or database record.

Each saved AI turn has an expiration date 30 days after it was created. MongoDB removes expired turns in the background, so physical deletion can occur shortly after that date. AI replies use only recent, unexpired turns from the same server. The bot has no separate temporary AI chat session collection or MongoDB log collection. AutoMod uses a bounded in-memory incident cache and removes raw classification context when processing finishes or after approximately 60 seconds, whichever comes first. Confirmed incidents also produce a bounded alert excerpt in pending delivery records; that excerpt is removed after delivery or final failure. Warning records expire through a MongoDB TTL index after 24 hours; the bot also checks expiration before using a record. Its in-memory Discord object cache expires after 10 minutes.

When Discord reports that OmniCore has been removed from a server, the bot deletes that server's saved settings, lock mappings, AI history, AutoMod warning records, BYOK credentials and usage, voice usage, and moderation metadata. Temporary unavailability does not trigger cleanup. Records from servers that left before this cleanup was added may need a verified support request. Bot removal does not erase messages, moderation actions, or audit records held by Discord, or logs kept by hosting systems.

A server administrator can use /delete_memory to remove the server's saved AI history without removing its settings or lock mappings. A user can use /delete_my_data to remove AI turns linked to the invoking account, including linked replies and tool turns, and to remove their private-chat access record and prompt preferences. Older tool output and text that only mentions a person may need manual review. For a fuller user or server deletion request, use the verified support process below.

Request access, correction, or deletion

You can run /delete_my_data for AI records linked to your own account. For access, correction, a fuller user deletion, or deletion of server data by an owner or administrator, open a request at OmniCore support issues and ask the team to arrange private contact. Do not put Discord IDs, message content, or other sensitive data in a public issue. The team verifies account or server authority before acting on stored records and reviews any relevant operational logs separately. You can also ask how your data is used or request correction of a server setting.

Security and age

Provider keys are encrypted before database storage with a separately configured master key. The pairing form uses HTTPS, Discord OAuth sign-in, server-owner checks, short-lived single-use links, session cookies, and CSRF protection. No system can guarantee absolute security. The encryption claim applies to provider credentials, not to all bot records or infrastructure logs.

OmniCore is for people eligible to use Discord under Discord's age rules. It is not designed to collect information from children below the minimum age for Discord use.

Changes and contact

We may update this policy as the bot changes. The last updated date above will reflect revisions. For questions, use the support issue route.

OmniCore

Practical tools for Discord communities.

Explore

HomeFeaturesCommandsGuidebookAboutSupport

Legal

Privacy PolicyTerms of Service

Discord

Add OmniCore to Discord
© 2026 OmniCore contributors. Source: GPL-3.0.Discord is a trademark of Discord Inc. OmniCore is not affiliated with or endorsed by Discord Inc.