Privacy Policy

Simple, transparent information on how Darklin3 protects your community data with zero chat logging and encrypted credentials.

Last updated: October 2026

1. Zero Chat Logging & Ephemeral Processing

Darklin3 does not record, archive, or database private message chat history or user Direct Messages (DMs).

When your dedicated bot instance receives message events from Discord, they are processed strictly in volatile memory (RAM) within ~10 milliseconds to evaluate configured Radar anti-raid patterns or custom bot commands. Once evaluated, message payloads are immediately dropped from memory. We do not build behavioral profiles, member activity graphs, or sell data to advertisers.

2. What Information We Collect

We only store the bare minimum technical data required to run your custom automation:

Discord Identity: When you log in via Discord OAuth2, we receive your public Discord Snowflake ID, username, and avatar to verify that you are the legitimate owner or administrator of the server.
Guild Configuration: Your Discord Server ID, designated announcement channel IDs (such as `#welcome`), designated starter role IDs, and your custom welcome text copy.
Custom Assets: Canvas background images or logos you upload to personalize your welcome graphics.
Bot Credentials: The Discord Bot Token you create in the Discord Developer Portal to link your dedicated worker.

3. How Your Bot Token is Protected

Your bot token is encrypted at rest using industry-standard AES-256-GCM encryption with unique initialization vectors. Decryption keys are stored exclusively in isolated environment secrets and are never exposed in frontend browser bundles or logged in plain text.

4. Discord Developer Policy & Privileged Gateway Intents

In accordance with the Discord Developer Policy, our use of privileged intents is strictly limited to legitimate server management features:

Server Members Intent (GUILD_MEMBERS): Used solely to detect when a new member joins your server, in order to render their 1080p welcome canvas card, assign configured newcomer roles, and update milestone member counters. Member records are not stored.
Message Content Intent (MESSAGE_CONTENT): Used strictly in-memory for the Radar anti-raid filter, phishing link detection, and custom message command execution. All message content is cleared from RAM immediately after evaluation.
Dedicated Isolation (Public Bot OFF): We recommend keeping the "Public Bot" toggle turned OFF in your Discord Developer Portal. This guarantees that your dedicated bot instance cannot be added to unauthorized external servers.

5. 1-Click Data Erasure (GDPR & CCPA)

You retain full control over your data. When you click "Decommission Bot" in the web dashboard or delete your tenant account, all associated encrypted bot tokens, server configurations, and canvas assets are permanently wiped from our systems immediately.

6. Third-Party Service Providers & Payment Data

We only connect to necessary core infrastructure to operate the bot:

Discord Inc.: Delivers events and receives bot actions via the official Discord Gateway WebSocket and REST API.
Zero Payment Data Collection: Darklin3 currently does not collect, process, or store credit card numbers, bank details, or payment credentials. When commercial billing is activated, transactions will be handled through a compliant third-party payment gateway, and payment methods will never be stored on Darklin3 servers.

7. Contact Information

If you have any questions about this Privacy Policy or wish to request a data audit, please reach out to us at [email protected] or join our Official Discord Server.