Discord Bot Privacy Policy

Overview

Atlas is the Discord bot of the AtlasOS Discord server . It is operated by the AtlasOS project ("we", "us"). This policy explains what Atlas collects, why, where it is kept, for how long, and how to have it corrected or deleted. For the AtlasOS website, see our main privacy policy .

Atlas's server features only operate inside the AtlasOS server. Atlas also processes direct messages sent to it and may retain records about former members and people involved in moderation.

Contact: email contact@atlasos.net or talk to a support representative in the AtlasOS Discord server .

Summary

• Atlas stores your Discord user ID next to a small amount of data about your activity in the server: your level, moderation cases, which invite you joined with, and a few counters.
• Atlas does not keep a database archive of ordinary server messages. It caches messages in memory to run its features. Suggestion text, moderation reasons and staff-configured content are stored separately. Selected deleted/edited messages and DMs are copied to restricted Discord log channels (see Discord log channels ).
• When a member invokes Jarvis or Translate, selected text and relevant context are sent to Groq. This may include messages written by other members. Search links can also contain message text, which is sent to the linked service when someone follows the link.
• We do not sell data, use it for advertising, or use it to train AI models.
• You can ask us to see, correct or delete your data at any time.

Data Linked to Your User ID

Aggregate Statistics and Message Links

Atlas keeps counters that are not linked to any user ID, for example: how many current members have each onboarding status or profile badge, members by the year their Discord account was created, messages per monitored channel, how often configured keywords are mentioned per channel, new forum posts per tag, AutoMod blocks, server boosts, and the most used emojis of a Wrapped season. These counters are kept indefinitely. Atlas also retains individual message IDs and links with reaction counts for Wrapped. These links can lead back to an identifiable author; they are not anonymous totals and are not automatically removed by /privacy delete.

Submitted and Configured Text

Atlas stores suggestion text and moderation reasons, including reasons received from Discord's audit log. It also stores staff-configured auto-responses, custom commands, scheduled messages and settings. These fields may contain names, mentions, quotations or other personal information. Staff-configured content remains until staff change or remove it. A privacy request may require manual review of text referring to you, including text submitted by someone else.

Processing and Temporary Caches

• Ordinary message content is read in memory to run auto-responses, count configured keywords, and check attachments and images (file type checks and reading the text in images to block scams). Message activity also earns XP. The message cache holds up to 200 messages per channel; an hourly sweep removes messages older than six hours. Images are checked locally with OCR, without an external OCR service, and the downloaded bytes are not archived.
• Presence (online status and active platforms) is cached in memory for /userinfo, the online count in /serverinfo, and aggregate online, idle and do-not-disturb counts. Atlas stores no individual presence history. Aggregate presence counts are retained in Prometheus for up to one year. There is no per-user tracking opt-out.
• Voice states are used to count occupants of configured voice channels. Aggregate counts are retained in Prometheus for up to one year; Atlas does not record voice audio.
• Usernames, display names and avatars are shown in replies and logs as Discord provides them; structured user references in the database use IDs. Submitted or configured text may also contain names or other identifiers.

Ko-fi Supporters

When you support AtlasOS on Ko-fi, Ko-fi notifies Atlas and Atlas posts a thank-you message in the server with the amount and, only if you made your support public on Ko-fi, your Ko-fi name and message. Ko-fi's notification also includes other details, such as your email address; Atlas ignores them. None of this is stored in Atlas's database.

Discord Log Channels

To moderate the server, Atlas copies some events into restricted log channels in Discord:

• selected content from deleted or edited messages, with attachment names where available,
• direct messages you send to Atlas,
• moderation actions and their reasons,
• messages removed by the scam-image filter (who posted it, where, and the matched keyword),
• use of Atlas's commands and level-ups, and
• a record that a data deletion request was carried out (with the user ID it was for).

Log text is truncated, and earlier content may be unavailable if a message was not cached. DM logs can include image previews. Some bots also share the bot role, which gives them access to the logs channel. These copies are stored by Discord and stay there until staff delete them. They are not part of Atlas's database, so deleting your data with Atlas does not remove them automatically. You can ask us to remove log messages about you; we will do so unless we need them to handle a moderation case.

Other features also create Discord copies: starboard posts, Save message bookmarks sent to the requester's DMs, suggestions and decision notices, translations and Jarvis replies. These copies are not removed by /privacy delete; tell us if you want us to review copies about you.

Third Parties

• Discord. Atlas runs on Discord. Everything you post is also processed by Discord under Discord's privacy policy .
• Groq. When a member invokes Jarvis or Translate, Atlas sends selected text and relevant context to Groq over HTTPS to generate the reply. Translate can process another member's message; Jarvis can include up to ten messages from a reply chain. Text may contain mentions, URLs or personal information. We have enabled Zero Data Retention for the Groq organization used by Atlas's inference API key. Under that setting, Groq does not retain inference inputs or outputs for reliability or abuse monitoring. Groq retains usage metadata that does not contain those inputs or outputs. We do not authorize training on Discord content. Processing is subject to Groq's data controls and service terms , including applicable legal obligations. Nothing is sent to Groq unless a member invokes one of these features.
• Infrastructure providers. AtlasOS operates the bot on hosted infrastructure. The hosting provider supplies the underlying server. Cloudflare handles traffic to our public endpoints and authenticated monitoring services through Access and Tunnel, including monitoring results containing Discord IDs.
• Search links. /lmgtfy and a configured reaction can create a link containing a query or text from a member's message. The bot posts the link in Discord; following it sends that text to letmegooglethat.com and may lead to a search provider.
• We share data for the features and infrastructure described in this policy, and never sell it.

Metrics

Atlas exports operational and community metrics (for example member counts, message counts per channel and per-moderator action counts) to a private Prometheus and Grafana instance operated by AtlasOS. Only AtlasOS staff can view them. Some series are labelled with Discord user IDs: moderators' IDs on moderation action counts and invite creators' IDs on invite usage. Metrics are kept for up to one year. Administrators attempt to delete the series labelled with your user ID and verify the result. Related moderator series are retained when moderation records are kept. Aggregate counts cannot be separated back into individual contributions.

Storage & Security

Atlas's database, metrics, persistent application logs and local backups are stored encrypted at rest on a LUKS2 volume on infrastructure operated by AtlasOS. Administrative access is restricted to the team members who run the services. This encryption protects stored volumes; it does not make a running server inaccessible to its administrators or control storage held by Discord or other providers.

Before database migrations, Atlas can create a backup in /data/backups; it keeps the three most recent copies. A separate infrastructure dump tool can create copies in /srv/vault/dumps and keeps the ten most recent dump sets. Rotation happens when new copies are created, without a fixed maximum age. Deleted data may remain in these copies until they are removed or replaced. Deleting database rows does not guarantee immediate physical erasure of old database or journal bytes.

Application logs are intended to contain operational events, errors and Discord IDs rather than message bodies; exception text can include details supplied by underlying services. They have a configured 30-day retention period, with routine deletion processing afterward. Privacy deletion does not purge these logs, and creates an operational record that the request was carried out.

Moderation Records

If you ask us to delete your data, we delete your moderation cases as well, unless keeping them is necessary to protect the server, for example to prevent someone who was banned from returning under a new account or to handle an ongoing report. If we keep moderation records, we tell you which records we kept and why. Unless moderation records are retained, your user ID is replaced with Deleted where you acted as a moderator, and your moderator counters are merged into a total labelled Deleted. When moderation records are retained, these identifiers and related metric series are retained too.

Your Choices & Rights

You can ask us to:

• see what Atlas stores about you,
• correct something that is wrong (for example a moderation case reason),
• delete your data,
• stop using your data for a specific purpose.

Contact us at contact@atlasos.net or talk to a support representative in the AtlasOS Discord server . We may ask you to confirm the request from your Discord account so we know it is yours. We respond within 30 days.

Administrators use /privacy info to see counts of stored database rows and /privacy delete to remove your level, per-user Wrapped counts, invite attribution, starboard database entries and suggestions, and replace your ID with Deleted where you created invites, invited other members or decided suggestions. Moderation handling follows the exceptions above. The command then attempts to purge matching Prometheus series; administrators check the result and follow up on failures separately.

The command does not remove Discord copies, backups, application logs, Wrapped message links or references in arbitrary text. Staff separately review these parts of your request and explain any retained records. There is no automatic per-user exclusion from future collection. If you stay in or rejoin the server, Atlas starts collecting the data described above again as you use it.

Leaving the server does not delete your data automatically: your level is kept so it can be restored if you come back. Ask us if you want it deleted.

Atlas is part of a Discord server, so it is subject to Discord's minimum age requirements. We do not knowingly collect data about anyone below them.

Changes to This Policy

We will update this policy when Atlas starts collecting something new or uses data differently. The effective date at the top always shows the latest version, and significant changes are announced in the AtlasOS server.