Privacy Policy
Draft — last updated 2026-09-09. This has not yet had a formal legal review; treat it as a good-faith statement of how the service actually works, not a finished legal document.
1. What we collect
To operate, Guild Manager stores, per server: your Discord server (guild) id, channel ids it posts to, the Discord user ids and role ids of members who RSVP or are tracked for attendance/voice presence, and the event/schedule/settings data your server configures. It does not read message content, and it does not request the Administrator permission.
Voice presence is recorded as join/leave timestamps for channels a server explicitly opts into tracking with /voice channel add — never audio, never a stored duration, only the boundary events a report is computed from.
2. Where it lives
All of the above is stored in the Service's own self-hosted database. Nothing is sold or shared with third parties. The only data shared outward is what a payment processor (Polar) needs to process a subscription for a server that chooses to pay — see Section 4.
3. Discord data
The Service reads member and role information already visible to it through Discord's own API (the guild member list and role membership), only to resolve who a configured attendance role or RSVP restriction covers. This is read on demand, not stored as a separate copy beyond what a feature (RSVP response, attendance record) itself needs.
4. Payment data
Subscription billing is handled entirely by our payment processor, Polar. We do not receive or store your card details. We store only what Polar reports back: the subscription status, tier, and provider it applies to, so /subscription status can show it to you.
5. Data removal
Removing the bot from your server does not immediately delete its data — configuration is archived so re-adding the bot restores it rather than starting over, per how the Service is designed to behave. To request permanent deletion, contact us at the address below.
6. Contact
Questions about this policy: support@discordmanager.xyz.
