gradient
Azura Logo

Privacy Policy

Last updated: November 8, 2026

1. Overview

This Privacy Policy explains exactly what information AzuraDLC collects when you use our website, dashboard, Discord bot, and client loader, and how that information is used to provide your license and protect the software from unauthorized distribution.

2. Information We Collect

We only collect the minimum data required to authenticate your account, verify your license, and prevent piracy:

  • Discord Account Details: When you create an account or sign in to the dashboard by linking your Discord, we store your Discord User ID, username, display name, avatar identifier, and account creation/login timestamps.
  • Hashed Hardware Identifiers (HWID): When you launch Minecraft with the Azura loader, the loader generates one-way SHA-256 cryptographic hashes of system hardware identifiers (composite machine hash and component hashes) and sends those hashes to our authentication server to bind and verify your license on your computer.
  • Network & Authentication Logs: When you interact with our API, redeem a license key, download a loader, or authenticate on launch, our server logs the event timestamp, IP address, license ID, and authentication status (such as successful sign-ins or hardware mismatch attempts).
  • Session Records: While the client is running, our server keeps a record of each session: the IP address you connected from, the two-letter country code of that address (supplied by our network provider, Cloudflare, with no separate location lookup), when the session started and was last active, how many keep-alive signals it sent, and how many client files it downloaded. This lets us tell one running copy of a license from several at once and spot downloads that look like scraping.
  • Runtime Safety Signals: The loader checks only whether a Java debugger, a Java agent, or a debugger attach request is present in the game process that runs AzuraDLC, and reports a simple yes or no for each. It does not read your files, browse your processes, record your screen, keyboard or chat, or look at anything outside that Java process.
  • Download Records: We log which license downloaded which client file and version, and when, so a leaked build can be traced to the license that received it.
  • Community Configs: If you voluntarily publish a configuration through the in-client community config browser, we store the config name, your chosen author label, the module settings JSON, and the license ID that uploaded it.

3. How We Use Your Information

Your information is used strictly for the following operational and security purposes:

  • To link your license keys to your Discord account and download your loader in the dashboard.
  • To verify that your license is active and running on the authorized hardware it was bound to.
  • To detect and prevent license sharing, credential stuffing, unauthorized multi-IP abuse, leaking, and piracy, and to enforce our Terms of Service and DMCA rights.
  • To refuse a second simultaneous session of one license, and to end a session whose access token turns up in several different countries.

Changing Wi-Fi networks, a rotating home IP address, or moving between networks in the same country is normal and is not treated as a problem. We do not use your location for anything else, and we do not build profiles or make decisions about you beyond protecting the license.

4. Automated Protection & Your Options

Repeated unusual activity, such as several simultaneous sessions, repeated hardware mismatches, scraping-style downloads, or running the client with a debugger or agent attached, can cause an automatic temporary lock on the affected license, usually between one hour and one day. A lock does not delete your license or data. Our owner is alerted and can lift it. If you think a lock is a mistake, open a ticket on our Discord server and we will review it by hand.

5. Retention

  • Session records are kept for 7 days.
  • Download records are kept for 45 days.
  • Protection strikes and lock records are kept for 30 days.
  • Authentication logs, license records and Discord account details are kept while your license or account exists.

6. Cookies & Third-Party Sharing

  • Essential Security & Session Cookies Only: Our website uses signed HttpOnly cookies (azura_clearance to remember that you passed our security check and azura_web to keep you logged in to your dashboard account). We do not use advertising trackers, third-party analytics pixels, or profiling cookies.
  • Cloudflare: Our website and API sit behind Cloudflare, which sees your IP address and requests in order to deliver and protect the service.
  • Lyrics (optional): The Media Player and Custom Skys modules read the title, artist, position and cover art of the track playing on your own computer. That stays on your computer. Only when you turn on the Lyrics option in Custom Skys, which is off by default, the client asks the public lyrics service lrclib.net for that track by sending its title, artist and length from your computer directly to them. Our servers never receive or store this, and nothing is sent unless you turn that option on.
  • No Other Third Parties: Apart from Cloudflare and the optional lyrics lookup above, we send your information to no other third party.
  • No Data Selling: We never sell, rent, or trade your personal information to third parties. Data is only disclosed if required by law or when necessary to enforce copyright/DMCA takedown notices against unauthorized piracy or redistribution.

7. Contact & Support

If you have questions regarding this Privacy Policy or your account data, please contact us through our official Discord server at discord.gg/SvRBMaqTeE.