Privacy Policy

Last updated: June 10, 2026

Nulled Data Systems (“NDS”, “we”, “us”, “our”) operates custom Discord bots and related services, including a Minecraft chat bridge and a support ticketing system. This Privacy Policy explains what information we collect when you add our bot to a Discord server, use linked game-chat features, open or staff a support ticket, interact with bot commands, or use our optional web dashboard at api.nulled.ac.

Our bots are independent third-party applications. We are not affiliated with, endorsed by, or sponsored by Discord Inc., Mojang Studios, or Microsoft.

1. Adding the bot to your server

When a server owner or administrator invites Nulled Data Systems to a Discord guild, they authorize us to access information required for the bot to function in that server. By adding or keeping the bot in a server, the person who authorized the invite (and the server’s administrators) accept this Privacy Policy on behalf of that community, to the extent permitted by Discord’s rules and applicable law.

If you do not agree with this policy, do not add the bot and ask your server staff to remove it.

2. Information the bot collects on Discord

Like other custom Discord bots (for example moderation or utility bots), we process Discord platform data only as needed to provide our features:

• Server (guild) information — guild ID, guild name, and channel IDs where the bot is used.
• User information — Discord user ID, username, display name, and server-specific nickname when you run a command or are granted permissions.
• Role and membership data — role IDs and membership needed to evaluate who may use restricted commands.
• Command and message content — text you send that invokes a command (prefix nds), including arguments you provide, and bot responses. We do not read your private direct messages unless you interact with the bot there in a supported way.
• Permission records — grants and revokes configured by server staff (user or role targets, permission names, rank, optional notes).

We use this data to authenticate commands, enforce permission ranks, display infrastructure status, run authorized admin actions, and maintain security audit records.

3. Minecraft chat bridge

Where enabled, our Service relays messages between a linked Minecraft server in-game chat and designated Discord channels so community members can communicate across platforms.

For this feature we may process:

• Minecraft player identity — in-game username (and UUID where available from the game server or link plugin).
• Message content — text you send in linked Discord channels or in-game chat that is relayed by the bridge, including timestamps and direction (Discord → Minecraft or Minecraft → Discord).
• Linking data — if you link a Discord account to a Minecraft account, we store the association so messages are attributed correctly and abuse can be moderated.
• Server connection metadata — Minecraft server address, bridge channel IDs, and connection health needed to keep the relay online.

Messages relayed through the bridge may be visible to players in-game, members in the linked Discord channel, and authorized staff. We use this data only to operate the relay, enforce server rules, and investigate abuse. Do not send passwords, personal addresses, or other sensitive information through the chat bridge.

We are not responsible for Mojang or third-party Minecraft server software. Your in-game activity remains subject to the Minecraft EULA and your server’s own rules.

4. Support ticketing system

One of our bots provides a ticketing system for Discord communities. When you open, reply to, or staff a ticket, we may process:

• Ticket metadata — ticket ID, category, status (open/closed), created and closed timestamps.
• Participant information — Discord user IDs and usernames of the member who opened the ticket and staff who respond.
• Ticket content — messages, transcripts, and attachments you send inside the ticket channel or thread.
• Channel data — private ticket channel or thread IDs created for your request.

Ticket data is used to provide support, let staff collaborate, keep a record of resolved issues, and protect communities from abuse. Server administrators control who may view and manage tickets. Closed ticket channels or transcripts may be retained for a limited time for accountability and training.

5. Optional web dashboard & Discord login

Some operators also use the NDS web panel. If you sign in with Discord OAuth, we request the identify scope only and receive your Discord user ID, username, and display name. We do not receive your Discord password or email through OAuth.

Panel accounts may store a username, bcrypt-hashed password, roles, and optional links between your Discord ID and a panel user ID. Dashboard and agent monitoring data (CPU, memory, hostnames, etc.) is collected from infrastructure you authorize and is separate from Discord’s platform data.

6. How we use information

• Operate bot commands and permission checks in servers where the bot is installed.
• Relay Minecraft and Discord chat where the bridge is configured.
• Create, manage, and archive support tickets for server staff and members.
• Let authorized staff monitor servers, run approved system commands, and manage accounts.
• Prevent abuse, debug failures, and protect the security of our systems.
• Comply with law and enforce our Terms of Service.

We do not sell Discord or panel data. We do not use your information for third-party advertising.

7. Who can see your data

Within a Discord server, administrators and users granted permissions may access bot features that expose operational data. Minecraft chat relay messages are visible to linked Discord channels and in-game players. Ticket contents are visible to the ticket opener and staff with access to that ticket category. Audit logs may be visible to service operators and designated panel owners. We share information with hosting providers that run our API and database, and with authorities when legally required.

8. Data retention

We keep bot, bridge, and permission data while features remain active for your server and for a reasonable period afterward for security and audit purposes. Minecraft relay logs and ticket transcripts may be retained according to server configuration or until deleted by administrators. When the bot is removed from a server, guild-specific runtime collection stops; stored permission rows, ticket archives, and audit history may be retained until deleted by an operator or no longer needed.

9. Removing the bot & your choices

• Server owners/admins can remove the bot from a guild at any time via Discord’s integration settings or by kicking the bot.
• Users can stop interacting with commands or leave servers where the bot is present.
• OAuth users can revoke our application under Discord → Settings → Authorized Apps.
• Disable or leave linked Minecraft chat channels if you do not want Discord messages relayed in-game.
• Close tickets and avoid sharing sensitive personal data in ticket messages.
• You may contact us to request deletion of linked account, ticket, or permission data, subject to verification and legal obligations.

10. Security

We use reasonable safeguards (access controls, hashed passwords, HTTPS, permission ranks). No online service is completely secure.

11. Children

Discord requires users to be at least 13. Our bot is not directed at children, and we do not knowingly collect data from anyone under 13.

12. International users

Data may be processed in countries where we or our providers operate. Discord also processes data under its own policies: discord.com/privacy.

13. Contact

Privacy questions: contact your server’s NDS administrator or the Nulled Data Systems operator through your organization’s official support channel.

Website: https://api.nulled.ac

14. Changes

We may update this policy. The date above will change when we do. Continued use of the bot after updates means you accept the revised policy.