Data and privacy
What the stingsby Discord bot stores about each server, for how long, and how staff can reset or delete it.
Stingsby keeps a small database with only what it needs to protect your server. Nothing is shared with anyone other than Discord.
- Per server: the trap, log and join log channel IDs, the delete window, whether the trap is on, the language, the action and its durations, the new-account limit, the incident settings, and exempt role IDs.
- Join-spike detector: only the time of recent joins, and whether each account was brand-new, kept in memory for 10 minutes. Nothing about joining members is saved by it.
- Join log (only if you turn it on): each join is saved to the event log with the member's name and ID, and the inviter's name and ID with the invite code; each leave with the member's name and ID and when they had joined. To tell which invite was used, stingsby keeps each invite's code, use count, creator and channel in memory only.
- Event log: time, kind, user ID and username, and details. The trigger message is the only message content stored, only for accounts that fell into the trap, cut to 1000 characters.
- Strikes (escalating action only): user ID, how many times caught, and when last.
- Events are deleted automatically after 90 days; strikes once they expire.
- Removing stingsby from your server keeps its settings, events and strikes for 30 days, in case it's added back, then deletes them. If it's added back in time, everything is restored and the trap comes back paused until your staff arm it again.
- 🗑️ Reset or delete data in
/config: Reset settings, keep log deletes the settings but keeps the event log, so you keep your audit trail. 🔥 Delete all data deletes everything straight away. stingsby stays in the server either way.
The full details are in the Privacy Policy, and the rules for using stingsby are in the Terms of Service.