← Back to Home

Privacy Policy

Last updated: July 26, 2026

Overview

Dune: Awakening Docker — Sentinel ("Sentinel", formerly "Arrakis Control Panel"/"ACP", formerly "Thumper", "the Bot") is a single, hosted Discord bot for Dune Awakening server operators — we run one bot instance that connects to your Discord server and your own game console. This Privacy Policy describes what data the Bot collects, where it is stored, and your rights regarding that data.

Key principle: Most of your game data (server status, inventories, character data) stays on your own console and is only relayed through the Bot at the moment you run a command — it is not copied into our database. A smaller set of connection data (listed in Section 5) is stored in our shared database so the Bot knows how to reach your console and which Discord roles map to which permissions.

1. Who We Are

The Bot is a community project maintained by a volunteer maintainer. It is not a commercial service. There is no company, no employees, and no data brokers involved.

• Project: Dune: Awakening Docker — Sentinel (formerly Arrakis Control Panel / ACP)
• Contact: Discord Community

2. Data Controller

The Bot's maintainer is the data controller for the connection data described in Section 5 (your console URL, adapter token, Discord role mappings, and any linked-character records cached by the Bot), since that data is stored in the Bot's own shared database, not on your infrastructure. You remain the data controller for the underlying game-server data itself (server status, inventories, character records) — the Bot only relays that data at the moment a command runs and does not retain a copy.

3. Data We Process

3.1 Discord Data

The Bot receives the following data from Discord when commands are used:

• User ID: Your Discord user identifier (required for role-based access control)
• Username: Your Discord display name (for logging purposes)
• Server ID: The Discord server where the command was issued
• Channel ID: The channel where the command was issued
• Role IDs: Your Discord role identifiers (for permission checks)

The Bot does not read message content. It only receives slash command interactions, which contain the command name and options you selected.

3.2 Game Server Data

When you run a command, the Bot queries your Dune Docker Console API and may process:

• Server status and health information
• Player counts and online status
• Character data (for linked accounts)
• Inventory and storage contents (for linked characters)
• Service container states
• Backup metadata
• Operational metrics (CPU, memory, etc.)

3.3 Character Links

When a user links their Discord account to an in-game character, the following association is created:

• Discord user ID ↔ In-game character name (and internal character/pawn identifiers)

This link is created on your game console via its own API, and a copy is also cached in the Bot's shared database (see Section 5) so it can be looked up per-server without querying your console on every command. It is used solely to determine which character's data to display when that user runs player commands.

3.4 Discord OAuth Setup Data

When a server owner connects a server through the web setup portal, the Bot receives and briefly stores a Discord OAuth access token and the list of servers that user manages, in order to verify they have permission to configure the server they select. This session data is used only to complete setup.

4. How Data Is Used

All data processing serves the following purposes:

• Authentication: Verifying your Discord identity to enforce role-based access control
• Authorization: Checking your Discord roles to determine which commands you may use
• Command Execution: Relaying your command to the Dune Console API and returning the result
• Character Linking: Associating your Discord account with your in-game character for player commands
• Logging: Recording command usage for cooldown enforcement and audit trails
• Scheduled Updates: Posting periodic server status to configured Discord channels

5. Data Storage

Data is split between the Bot's own infrastructure (which the maintainer operates) and your own console. The Bot does not maintain any third-party or cloud data repositories beyond what's described here.

• Stored in the Bot's own database (maintainer-operated): your console URL, your adapter token, Discord role-to-permission mappings for your server, per-server settings (schedule, cooldowns, faction theme), and a cache of Discord-user-to-character-name links.
• Stored on your own console: the authoritative game data itself — server status, player counts, inventories, backups — none of which is copied into the Bot's database; it is fetched live each time a command runs.
• Logs: Command-usage logs are written by the Bot's own hosting infrastructure for cooldown enforcement and audit; your console also writes its own logs locally.
• Secrets: Your adapter token is stored in the Bot's database (encrypted at rest where the maintainer's deployment is configured to do so) and, on your side, in a file with 0600 permissions on your console.

6. Data Sharing

The Bot does not share your data with any third party. Data flows only between:

1. Your Discord server (commands and responses)
2. The Bot's hosted infrastructure (operated by the maintainer)
3. Your Dune Docker Console API (running on your own infrastructure)

No data is transmitted to Funcom, Discord (beyond normal API interactions), or any other entity outside of this project.

7. Data Retention

Data retention is controlled by you:

• Character links: Persist until the user unlinks or the server is reset
• Command logs: Retained according to your logging configuration
• Scheduled posts: Stored in Discord's infrastructure per Discord's retention policies

8. Your Rights

For data stored on your own console (game data, logs), you have full, direct control — you can view, export, correct, or delete it yourself at any time. For connection data stored in the Bot's own database (your console URL, adapter token, role mappings, cached character links), you can:

• Access: Request a copy of the data stored for your server via the Discord community linked in Section 1
• Deletion: Remove the Bot from your Discord server to trigger deletion of your server's stored connection data, or request deletion directly
• Correction: Update your console URL, adapter token, or role mappings at any time through the setup portal

For Discord users who are not server administrators (e.g., linked character records), you may request data deletion from your server administrator, or directly via the Discord community linked in Section 1.

9. Security

The Bot implements the following security measures:

• Bearer-token authentication: All API requests require a secret token
• Role-based access control: Commands are restricted by Discord role
• Read-only by default: Server commands cannot modify your console's state; character linking writes a single association record on your console, cached in the Bot's own database
• Limited console access: The Bot only calls your console's read-only API endpoints plus the single character-link endpoint; it never queries your game database directly
• Encrypted secrets at rest: Adapter tokens and OAuth session data in the Bot's own database are encrypted where the maintainer's deployment has this configured; your own copy of the adapter token is stored in a file with 0600 permissions on your console
• No Docker socket access: The Bot cannot control containers
• Security scanning: Every code change is scanned for vulnerabilities

10. Children's Privacy

The Bot is not intended for children under 13. Discord's Terms of Service require users to be at least 13 years old. We do not knowingly collect data from children.

11. International Data Transfers

Your game data stays on your own console and does not leave your infrastructure. Connection data described in Section 5 is processed and stored on the Bot's hosting infrastructure. Discord's own data processing is subject to Discord's Privacy Policy.

12. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted in the project repository. Continued use of the Bot after changes constitutes acceptance of the updated policy.

13. Contact

For privacy-related questions or requests, contact us via the project's Discord server.

14. Acknowledgments

This Privacy Policy was drafted with reference to GDPR, CCPA, and Discord's Developer Privacy Policy requirements. It is intended to be clear, honest, and actionable.