45 lines
1.8 KiB
Text
45 lines
1.8 KiB
Text
compsigh Minecraft — Privacy Policy
|
|
|
|
Last updated: 2026-03-14
|
|
|
|
1. What We Collect
|
|
- Minecraft username and UUID (required to join the server)
|
|
- Discord username and user ID (used for chat bridging and admin
|
|
commands)
|
|
- Chat messages sent in-game and in the bridged Discord channel
|
|
(relayed between platforms in real time)
|
|
- In-game actions (block placement, breakage, chest access, etc.)
|
|
logged by the Ledger mod for grief prevention
|
|
- Server logs (connection IPs, join/leave times, errors)
|
|
|
|
2. How Data Is Used
|
|
- Chat messages are bridged between Minecraft and Discord and are
|
|
visible in both platforms.
|
|
- Action logs are used solely for grief investigation and rollback.
|
|
- Server logs are used for debugging and moderation.
|
|
- Admin Discord user IDs are stored in the bot configuration to
|
|
control who can run server commands from Discord.
|
|
|
|
3. Data Storage
|
|
- World data and action logs are stored on the server and backed up
|
|
to Backblaze B2 cloud storage.
|
|
- Chat messages are stored by Discord per their own retention
|
|
policies. The server does not independently archive chat.
|
|
- Server logs are stored on the server and rotate automatically.
|
|
|
|
4. Data Sharing
|
|
We do not sell, share, or provide your data to any third party.
|
|
Backblaze B2 is used solely for encrypted backup storage.
|
|
|
|
5. Data Retention
|
|
- World backups are retained per our Backblaze B2 lifecycle policy.
|
|
- Server logs are retained for up to 30 days.
|
|
- In-game action logs persist in the world data indefinitely.
|
|
|
|
6. Your Rights
|
|
You may request to see what data we have about you or ask for its
|
|
deletion by contacting a server admin on Discord. Deleting your
|
|
data may require removing you from the whitelist.
|
|
|
|
7. Contact
|
|
For privacy questions, reach out to a server admin on Discord.
|