Atlas

Privacy Policy

Last updated: September 2026

This Privacy Policy describes what information Atlas (the "Bot") and its web dashboard (the "Dashboard", together the "Service") collects, how it's used, and how it's stored.

1. Information We Collect

  • Discord account data — your Discord user ID, username, and avatar, obtained via Discord OAuth2 when you log into the Dashboard, or via the Bot when you interact with it in a server.
  • Server & membership data — the ID and name of servers the Bot is in, and which of those servers you belong to (used to decide what the Dashboard shows you).
  • Moderation & activity data — cases (warns, timeouts, kicks, bans), tickets, appeals, automod violations, and audit log entries generated by the Service's normal operation within a server.
  • Role & permission data — which Discord roles are linked to which staff permission tiers on a server, and any manual permission grants or overrides.
  • Website form responses — if you fill in a form on a server's website page, the answers you give, your Discord ID and username, and the Roblox account you link or type are stored and shown to that server's staff, along with their decision and any note. Files you attach are stored and shown only to that server's staff, and unsent files are deleted after a day. If the server turns on its member portal, you can see your own cases, tickets and form responses for that server at /me. You can see your own responses on the form page. Servers can also show a public profile card for you (your level, rank, badges and linked Roblox account) at /u/<your Discord ID>; you can hide it, or just the Roblox link, from Your history. If you sign up for a shift, your name is visible to that server's staff, and bans a server shares with the other servers in its group include your Discord ID and the ban reason.
  • Session data — a single encrypted cookie that keeps you logged into the Dashboard. It is not readable without the Service's own encryption key.

2. How We Use This Information

We use this information solely to operate the Service: authenticating you, showing you the servers and data you have access to, running moderation and automation features, and enforcing the permission tiers a server's staff have configured.

3. Data Storage & Retention

Data is stored in a Postgres database and a short-lived cache, operated for the Service. Moderation records (cases, audit log entries) are kept as a server's history unless removed by that server's staff or upon request. If the Bot is removed from a server, that server's configuration and history are retained in case the Bot is re-invited, but are no longer accessible through the Dashboard.

4. Cookies

The Dashboard uses one session cookie to keep you logged in, and (optionally) a local browser preference for light/dark theme, stored only in your own browser. We do not use advertising or third-party tracking cookies.

5. Third-Party Services

The Service relies on Discord's API for authentication and to act on servers, and on infrastructure providers (hosting, database, and cache) to run. These providers process data only as needed to operate the Service, under their own privacy terms.

6. Data Sharing

We do not sell your data. Information within a server (cases, tickets, audit logs) is visible only to that server's own staff, based on the permissions that server has configured.

7. Your Rights

You can revoke the Dashboard's access to your Discord account at any time from Discord's own Authorized Apps settings, which also ends your Dashboard session. To request removal of your data from a specific server, contact that server's staff, or reach out through the Bot's support server.

8. Children's Privacy

The Service is intended for use consistent with Discord's own age requirements and is not directed at children under that age.

9. Changes to This Policy

We may update this Privacy Policy from time to time. Continuing to use the Service after an update constitutes acceptance of the revised policy.

10. Contact

Questions about this policy can be directed to a server's staff, or through the Bot's support server.