wisp

legal

privacy policy

last updated September 22, 2026

This describes what wisp ("the bot", "we") actually stores when you or your server uses it, in plain terms — not a generic template. If a data point isn't listed here, wisp doesn't collect it.

what gets stored

Depending on which features a server turns on, wisp stores:

  • Server configuration — channel/role IDs for moderation, logging, tickets, leveling, voicemaster, counters, and every other configurable feature. This is settings, not personal data.
  • Moderation history — case records (who was actioned, by which moderator, and why) for commands like ban, kick, mute, and jail, tied to Discord user IDs.
  • Leveling data — a running XP count per member per server, derived from message frequency, not message content.
  • AFK status and reminders — the text you set with afk or remind, until it's cleared or fires.
  • Ticket transcripts — generated on demand from a ticket channel's own message history when it closes, and delivered to your server's configured transcript channel. Wisp doesn't keep a separate permanent copy once that's sent.
  • Starboard entries — which message got starred and its current star count, not the message content itself (wisp reads that live from Discord each time, it isn't duplicated into our database).
  • Last.fm links — if you run lastfm login, your Last.fm username, after you've approved the connection on last.fm's own site. Wisp never sees or stores your Last.fm password — the whole point of that login flow is that we can't.
  • Fun feature data — small things like autoresponder triggers, reaction-role mappings, giveaway entries, and similar server-configured features, scoped to what each feature needs to work.

what we don't do

  • Wisp does not read, log, or store the content of regular messages. Logging features record that an event happened (a message was edited/deleted, a role changed) along with metadata (who, when, where) — not a running archive of everything said in your server.
  • This website doesn't use tracking cookies, ad trackers, or third-party analytics. The only thing it talks to on your behalf is the bot itself, for the live status page.
  • We don't sell data. There's nothing to sell it to, and no reason to.

third-party services

Some commands call out to external APIs to do their job. When they do, only what's needed for that specific lookup is sent — never your message history or account details.

  • Discord — the platform wisp runs on. Everything wisp can see is governed by Discord's own permission model and Discord's Privacy Policy.
  • Last.fm — only for members who explicitly link an account, to look up scrobble data they've made public.
  • TMDB, OMDB, RAWG — for movie, TV, and game lookup commands. Only the search term you typed is sent.

deleting your data

Kick wisp from a server and its server-specific configuration (settings, moderation history, tickets, starboard entries, leveling data for that server) is deleted automatically. Account-level data that follows you between servers — AFK status, reminders, a linked Last.fm username — can be cleared yourself at any time: afk to clear an AFK status, lastfm logout to unlink Last.fm.

Want everything gone faster, or have a question this page doesn't answer? Reach out through the support server and we'll handle it directly.

children's privacy

Wisp is not directed at children under 13, in line with Discord's own age requirement for using their platform at all. We don't knowingly collect data from anyone below that age beyond what Discord itself already provides us (a user ID), and we don't attempt to determine anyone's age.

changes to this policy

If what wisp collects changes in a meaningful way, this page gets updated and the "last updated" date above moves. There's no separate mailing list — this page is the source of truth.