Privacy Policy for Canary M. Burns. Last updated: September 28, 2026.
1. Overview
We respect your privacy and are committed to protecting the data connected to Canary M. Burns. This policy explains Canary M. Burns’ current data practices and your rights under applicable data protection laws and Discord’s Developer Policy.
2. Information We Collect
Discord identifiers
Canary M. Burns does not currently process user commands or store active user data. Discord identifiers are not actively collected or retained by Canary M. Burns at this time.
Feature-specific data
Canary M. Burns has no active badge, economy, inventory, or leveling features at this time.
3. Privileged Intents & Message Content
Canary M. Burns does not currently use presence data for active user-facing features.
Canary M. Burns does not currently perform member-tracking operations for active user-facing features.
Canary M. Burns does not currently inspect or store message content.
4. Data Storage & Security
Persistent data, including user IDs, badge inventories, leveling statistics, and economy balances, is stored in a protected MongoDB instance hosted on Google Cloud Platform. We use strict access controls, secure connections, and encrypted database connections. We do not collect, store, or track IP addresses.
5. Data Retention
User profiles, economy balances, and badge inventories are retained while a user or server uses the Bot. Message data is processed immediately or held only in volatile memory for anti-spam and cooldown checks. On a valid data deletion request, records are purged from our databases.
6. Third-Party Sharing
We do not sell, trade, or rent user data. Data is shared only with Google Cloud Platform for secure runtime and database operations, and with our official Framer web interface through secure REST APIs when displaying public Discord IDs, avatars, or bot-specific statistics.
7. User Rights & Data Deletion Requests
You may request access to or permanent deletion of your stored data. To request erasure, join the Support Discord Server and open a support ticket, email the developer, or submit a request through the web contact form. Associated inventory, XP, and economy records are purged within 30 days.