Armr Privacy Policy
Last updated: November 20, 2026
This policy explains what the Armr Discord bot ("Armr", "the bot", "we") stores, why, how long, and how to have it removed. By adding Armr to a server or using its commands you agree to this policy.
Questions or deletion requests: https://discord.gg/QYv3gmcfWP
What Armr stores
Armr only stores what its features need to work. Nothing is sold, shared with advertisers, or used to train AI models.
Server settings (set by each server's staff): prefix, log channels, welcome/goodbye/boost messages, saved embeds and images, auto-responders and auto-reactions, ticket, partnership, giveaway, starboard, level, filter, antinuke, antiraid and verification settings, and similar configuration.
Information about members, stored per server:
| Data | Why | How long |
|---|---|---|
| User IDs in moderation records (warnings, cases, jail, temp bans, hard bans) | Moderation history for that server's staff | Until staff clear it, or the server's data is deleted |
| Level XP | Levels and leaderboards | Until reset by staff, or the server's data is deleted |
| Join and leave times, and voice chat time per day | The /serverstats graphs |
35 days (365 days for servers with Premium) |
| How many messages each member sends per day, and per channel; voice time per channel (counts only, never the message text) | The /userstats card (ranks, totals and top channels), and leaderboards a server chooses to post (,autolb, display names and totals only) |
35 days (365 with Premium); the per-channel counts 14 days |
| Per month, for the whole server: messages per hour of the day, messages per channel, and how often each emoji is used in messages and reactions (counts only, not who sent them) | Server Wrapped (,wrapped): the busiest hour, top channel and top emoji |
35 days (365 with Premium) |
| For members banned in the last 6 months: their user ID, username, display names, when they were banned, and a short fingerprint of their profile picture (a number, not the picture) | Ban-evasion alerts: telling staff when someone who looks like them joins | 180 days, or until they're unbanned |
| Time capsules: the message, who sealed it, the channel, and when it opens | Posting it when it opens | Until it opens or the person cancels it |
| A member's roles when they leave | Giving them back if they rejoin (,restore) |
Until they rejoin, or the server's data is deleted |
| Who sent each anonymous confession (last 1,000) | Letting staff mute abusers without seeing who they are | Rolling: older ones are forgotten |
| Ticket and partnership details (who opened a ticket, a partner's invite and ad) | Running tickets and partnerships | Until the ticket or request ends |
| Giveaway entries | Picking winners | Until the giveaway is removed |
| Ticket ratings (Premium): the stars, who rated, the ticket and who closed it | Showing staff how their tickets went | The latest 500 per server |
| Closed tickets: who opened, claimed and closed each one, and when (no messages) | Ticket stats for staff (,ticket stats) |
The latest 2,000 per server |
| User IDs on a server's ticket blacklist or log ignore list | Stopping those members opening tickets, or leaving them out of the logs | Until staff remove them, or the server's data is deleted |
| In a counting channel: the current number, who counted last and that message's ID | The counting game (,counting) |
Until staff turn counting off and reset it, or the server's data is deleted |
| Counts of what happened (raiders stopped, messages filtered, tickets opened, members verified), no message text | The weekly server report (Premium) | 15 days |
| Server backups (Premium): role and channel names, colours and permissions, including the user IDs of members with their own channel permissions | Restoring the server after a raid or nuke | Until staff delete them; automatic daily backups keep the newest 7 |
Information you choose to give, stored for you: AFK status, birthday, time zone and reminders. You can
remove these yourself (for example ,birthday remove, ,timezone remove).
Last.fm. If you link a Last.fm account (,fm set), Armr stores your Last.fm username and any now-playing
reactions you pick, for every server, and in each server the artists you hold the crown for (with your play count).
,fm unset removes your username and reactions; crowns pass to someone else or are removed when the server runs
,fm whoknows again, and are deleted with the server's data.
Other services Armr asks for you. Last.fm, Spotify and Roblox commands send what you look up (a Last.fm username, a song or artist name, a Roblox username) to that service to get the answer. Armr doesn't send them your Discord account details. Spotify's "listening now" reads the Spotify status Discord already shows on your profile.
Premium and payments. Card payments are handled by Stripe and Link, which handle the payment and sales tax under their own privacy policies. Armr never sees or stores card details. For each premium server Armr stores the server ID, the server owner's user ID, the plan, when it started and ends, the Stripe subscription or payment ID (to renew or cancel it), whether its free trial or its one transfer has been used, and the amount of each payment (for the developer's sales records, without names or emails). These are kept while premium is active and afterwards as a record of the purchase, and so each server only gets one free trial and one transfer.
Message content. Armr reads messages to run its features: commands, the word/link/spam filter, auto-responders, levels and similar. Message content is not stored, except:
- Snipe: the last 5 deleted, edited or reaction-removed messages per channel, kept in memory only, gone when the bot restarts.
- Logs: if a server turns on log channels, deleted and edited messages, moderation actions, joins and leaves and voice activity are posted in that server's log channels. Bulk-deleted messages (purge, nuke) are saved as a text transcript in the transcript log.
- Your logs stay in your server. Armr's developer does not receive copies of your server's messages, logs or transcripts. The developer only gets bot-wide information: which servers add or remove Armr (name, ID, owner, member count), premium purchases and renewals (server name, member count and amount paid), error reports from the bot's code, and alerts when a raid or nuke is detected.
Where it's kept
On a private server rented from Hetzner. A daily backup is kept on that server and in a private channel of the developer's Discord server. Backups are kept for 14 days.
Deletion
- If Armr is removed from a server, that server's data, including its server backups, is kept for 30 days (so being re-added restores everything), then permanently deleted. Backups containing it expire 14 days after that.
- Server staff can clear most data themselves with Armr's commands (warnings, levels, settings).
- Anyone can ask for their data to be deleted, or ask what is stored about them, through the support server above. Requests are handled within 30 days.
Children
Armr follows Discord's Terms of Service, which require users to be at least 13 (or the minimum age in their country).
Changes
If this policy changes, the date at the top changes too. Continuing to use Armr means you accept the new version.