Principles
- Collect only what is necessary for the service to function or to protect it.
- Prefer transient data; avoid persistence unless required.
- State clearly what is not collected.
What We Collect
Discord Bots
- User and server identifiers (IDs, usernames, server metadata).
- Command or interaction payloads needed to execute features.
- Message content only when strictly required for the requested action.
- Error and performance logs limited to the event context.
Minecraft Plugins
- Player UUIDs and usernames provided by Mojang.
- In-game events needed for plugin behavior (e.g., actions, stats).
- Server configuration relevant to the plugin.
Experimental or Custom Work
- Inputs defined by the feature or contract, documented per engagement.
- Operational metadata (timestamps, error traces) for stability.
Web Presence
- Basic server logs (IP, user agent, timestamp) for security and reliability.
- No trackers, ads, or behavioral profiling.
When We Collect
- When you invoke a command, interact with a bot, or use a plugin feature.
- When errors occur and diagnostics are necessary to fix or secure a service.
- When configuration or preferences are explicitly set for a service.
What We Do Not Collect
- No advertising or analytics profiles.
- No broad message or chat history archiving.
- No payment information (handled by third parties when relevant).
- No biometric or sensitive categories of data.
Retention Signals
Collection is paired with minimal retention: transient where possible, short-lived logs for troubleshooting, and configuration data only while the feature is active. See Data Storage for details.