Privacy & Retention
Bureaucramancer provides the processor-side controls, but each Discord server operator remains responsible for deciding and explaining how its guild data is used.
Before enabling Archive
- Define why the server needs searchable message history.
- Decide which channels genuinely need coverage.
- Limit staff who can search or export the archive.
- Tell members what is captured, why, and for how long.
- Choose the shortest retention period that meets the purpose.
Current retention controls
Archive: 7–30 days. Server History: 30–365 days. Structural Backups: 7–90 days. Closed Cases: 30–730 days. Web-action records: 7–90 days. Uninstall grace: 0–30 days. Defaults are 30, 365, 90, 730, 90 and 30 days respectively.
Privacy requests
The verified privacy portal binds a request to a Discord user ID. Server administrators can discover matching guild data, create a controller-review export and perform guarded erasure of eligible ordinary Archive/identity data. Retained moderation, security or audit records are shown separately rather than silently destroyed.
When the bot is removed
Guild-controlled data follows the configured uninstall grace period before deletion. Limited records can remain where a legal, security, accounting or dispute-resolution need applies, and infrastructure backup copies age out through their normal backup cycle.
Documents to give staff
The public Privacy Notice, Terms and Data Processing Agreement describe Bureaucramancer's service-level responsibilities. Your own server notice should still identify your server's specific purposes, enabled modules, covered channels and staff access.