Privacy Policy
Your privacy matters. Understand exactly what data we collect, how we use it, and your rights to control it.
Full Transparency
Open source code. See exactly what we collect and why.
Secure Storage
Encrypted infrastructure. Your data stays protected.
Minimal Data
Only essential data. Never sold or shared with others.
1Introduction
Your privacy is important to us. This Privacy Policy explains how Discord Role Guardian collects, uses, stores, and protects your data when you use our bot.
Discord Role Guardian is designed with privacy in mind. We only collect data necessary to provide bot functionality and do not sell or share your data with third parties.
2Information We Collect
Discord Role Guardian collects the following types of data:
●Server Configuration Data
- Server ID (Guild ID)
- Channel IDs for bot features (welcome, leave, leveling, tickets)
- Role IDs for reaction roles and level rewards
- Custom messages and embed configurations
- Reaction role setups (message IDs, emoji, role mappings)
- Scheduled message configurations
- Ticket system settings and categories
●User Activity Data (Leveling System)
- User ID
- Server ID (Guild ID)
- XP (experience points) earned
- Current level
- Message timestamps (for XP cooldown, not message content)
We do NOT collect or store message content. Only metadata for XP calculation is tracked.
●Ticket System Data
- Ticket ID and number
- User ID (ticket creator)
- Ticket channel ID
- Ticket status (open, claimed, closed)
- Creation and closure timestamps
- Assigned staff member ID (if claimed)
We do NOT collect:
3How We Use Your Data
We use collected data exclusively to provide bot functionality:
- Reaction Roles: Store emoji-to-role mappings to automatically assign roles
- Welcome/Leave Messages: Store channel IDs and custom messages to send notifications
- Leveling System: Track user XP and levels to assign level-based roles
- Ticket System: Manage support tickets and track ticket history
- Scheduled Messages: Store and execute timed message delivery
- Bot Operation: Maintain configurations across restarts and updates
Your data is NEVER used for marketing, analytics, profiling, or sold to third parties.
4Data Storage and Security
All bot data is stored securely on Railway.app infrastructure with persistent volumes. Data is stored in JSON format and is only accessible by the bot application.
Security Measures:
- Data stored on secure, encrypted infrastructure (Railway.app with persistent volumes)
- No database exposed to the public internet
- Access restricted to bot application only
- Regular backups via persistent volume snapshots
- Secure environment variable management for sensitive tokens
- HTTPS-only communication with Discord API
While we implement industry-standard security practices, no method of data storage is 100% secure. We cannot guarantee absolute security but take all reasonable precautions.
5Data Retention
We retain server data as long as the bot remains in your server. Data retention periods:
- Active Servers: Data is retained indefinitely while bot is active in the server
- Removed Bot: Data is retained for 30 days after bot removal (in case of accidental removal)
- Manual Reset: Server administrators can delete all data using the
/resetcommand - Data Deletion Requests: We honor data deletion requests within 7 business days
Leveling data, ticket history, and other user activity data is retained as long as the bot is in the server. Users can request personal data deletion at any time.
6Data Sharing and Third Parties
We do NOT sell, trade, or share your data with third parties. Your data remains private and is only used for bot functionality.
Third-Party Services We Use:
- Discord API: Required to operate the bot and access server data. Subject to Discord's Privacy Policy.
- Railway.app: Hosting infrastructure for bot deployment and data storage. Subject to Railway's Privacy Policy.
We may disclose data if required by law, court order, or to protect our rights and safety.
7Your Rights and Control
You have full control over your data:
- Access: Server administrators can view all stored configurations via bot commands
- Modify: Update configurations at any time using setup commands
- Delete: Use
/resetcommand to delete all server data - Remove Bot: Kick the bot from your server to stop data collection
- Data Export: Request a copy of your data by contacting us on GitHub
- Opt-Out: Individual users can request removal from leveling system
For data deletion requests or questions about your data, please contact us via GitHub issues.
8Open Source Transparency
Discord Role Guardian is fully open source. You can review exactly how we handle data by inspecting the source code on GitHub.
Review the code
github.com/nayandas69/discord-role-guardianInspect our privacy practices, audit data handling, and verify that we do exactly what we say.
Self-hosting gives you complete control over data storage and privacy. See our installation guide for details.
9Children's Privacy
Discord Role Guardian is designed for use on Discord, which requires users to be at least 13 years old (or older depending on location).
We do not knowingly collect personal information from children under 13. If you believe we have collected data from a child under 13, please contact us immediately, and we will delete the data.
10Discord's Privacy Policy
Discord Role Guardian operates within Discord's platform and is subject to Discord's Terms of Service and Privacy Policy.
Discord collects its own data independently of this bot. Please review Discord's Privacy Policy to understand how Discord handles your data.
11Changes to Privacy Policy
We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated "Last updated" date.
For significant changes that affect how we handle your data, we will make reasonable efforts to notify users through our GitHub repository or Discord support server.
Continued use of the bot after changes constitutes acceptance of the updated Privacy Policy.
Questions About Your Privacy?
If you have questions, concerns, or requests regarding this Privacy Policy or your data, please contact us on GitHub.
Open GitHub Issue