tl;dr
swag only stores what it needs for the features you or your server enable. By using swag or adding it to a server, you agree to this policy.
what we store
Everything below is tied to Discord IDs (numbers that identify users, servers, channels, roles and messages) only.
server settings
Prefixes, logging, welcome and goodbye messages, auto and reaction roles, tickets, starboard, voicemaster, antinuke, leveling, triggers, aliases, sticky messages, timers, social feeds and every other setting a server's staff configures.
moderation
Moderation cases (who did what to whom, the reason and when), forced nicknames and lost boosters are all kept so staff have a history to work from.
activity
Level XP and message counts, economy balances, giveaway entries, suggestions, starboard entries and Last.fm crowns.
things you set
Your AFK status, birthday, timezone, personal prefix, reminders, highlight keywords, tags, Fortnite item reminders and crypto transactions you track.
name history
Your previous usernames and nicknames, so they can be looked up with the namehistory command. You can clear it at any time.
connected accounts
If you link Last.fm, Spotify or Discogs, we store your username and the access tokens those services give us, plus your Last.fm play counts so library commands are fast.
message content
swag reads messages to respond to commands and to power features like triggers, highlights, sticky messages, leveling, honeypots and logging. Messages are not saved to our database, with these exceptions:
snipe
Deleted and edited messages and removed reactions are held in memory for up to one hour, then discarded. Staff can opt members out.
logging & tickets
If a server enables logging or ticket transcripts, swag posts those messages into that server's own channels. We don't keep a copy.
commands you run
Things you save on purpose, like reminders, tags or AFK statuses, are stored until you remove them.
third-party services
Some commands only work by sending data to another service. Only the data needed for that command is sent, and only when you run it:
ai
Prompts for the ai command and audio for the transcribe command are sent to Groq.
media
Files converted with mp3 or togif may be uploaded to our CDN at cdn.kaido.one so they can be shared as a link.
lookups
Search terms are sent to the service being searched, such as Last.fm, Spotify, YouTube, SoundCloud, Twitch, Kick, Discogs, GitHub or Urban Dictionary.
Each of those services has its own privacy policy. Music is played through Lavalink, and code from the eval command runs in an isolated sandbox on our own servers.
how long we keep it
Data is kept for as long as the feature is in use. Server settings stay until staff remove them, personal data stays until you remove it or ask us to. Short-lived data, like snipes, expires on its own within minutes to an hour.
who can see it
Server data is visible to that server's members through the bot's commands, as the feature intends (a leaderboard shows levels, a case log shows cases). Only the swag developers have direct access to the database. We never sell or share it, except where required by law.
your choices
Most data can be removed with the command that set it: unlink Last.fm, Spotify or Discogs, clear your name history, remove reminders or reset settings. For anything else, or to have all of your data deleted, contact us on Discord and we'll remove it. Users who abuse the bot may be blacklisted, in which case we keep their ID and a note so the blacklist works.
changes
If this policy changes, the date at the top will change with it. Continuing to use swag after that means you accept the new version.