ajdnikov Dashboard

Privacy Policy

Last updated: October 2026

1. Introduction

This Privacy Policy explains how ajdnikov-dev.com ("we", "the website") handles data when you visit it. We keep data collection to a minimum — this website does not have user accounts, contact forms that store personal data, or any registration system. Our licensing service, AnziLock, does have accounts; it is covered separately in section 5.

2. Cookies and Browser Storage

This website uses cookies and browser local storage to store data on your device. Specifically:

  • Theme preference — your choice of light or dark mode is saved in your browser's local storage (key: theme) so the site remembers it between visits. This data never leaves your device.
  • Analytics storage — Vercel Analytics (see below) may store small identifiers in cookies or browser storage to measure page views and performance.

You can delete this data at any time by clearing your browser's cookies and site data for this website. Blocking cookies or local storage will not break the website, but your theme preference will not be remembered.

3. Vercel Analytics and Speed Insights

This website uses Vercel Web Analytics and Vercel Speed Insights to understand how visitors use the site and to monitor performance. These tools collect anonymized, aggregated data such as:

  • Pages visited and referral source
  • Approximate geographic region (country level)
  • Browser, device type, and operating system
  • Web performance metrics (page load timings)

Vercel Analytics is privacy-focused: it does not track you across other websites and does not build advertising profiles. Data is processed by Vercel Inc. in accordance with Vercel's Privacy Policy.

4. Discord Bot

We operate the Bot on our Discord server. It manages support tickets, giveaways, custom messages and embeds (welcome messages, ticket panels, announcements), and moderation logging. When you interact with the bot, the following data is processed:

  • Ticket transcripts — when a ticket is closed or deleted, its message history (message content, usernames, mentions, and attachment links) is saved as an HTML transcript and posted to a staff-only log channel.
  • File vault — attachments posted in ticket channels are automatically copied to a staff-only vault channel so they remain available after a ticket is deleted.
  • Giveaway entries — Discord user IDs of participants, the prize, and the end time are stored until the giveaway ends.
  • Server configuration — role, channel, and category IDs set by server staff through the bot's configuration panel.
  • Moderation events — joins, leaves, kicks, and bans are logged to a staff channel.

This data is stored as plain JSON files and transcripts on our own server — not in a third-party database — and is only accessible to server staff. It is used solely to operate the ticket, giveaway, and moderation features; it is never sold or shared with advertisers. Ticket transcripts may be retained for moderation record-keeping; you may request deletion of your ticket transcripts by contacting staff on our Discord server. Your use of Discord itself is governed by the Discord Privacy Policy.

5. AnziLock Licensing

Our premium plugins check their licence with AnziLock, our licensing service at license.ajdnikov-dev.com. Unlike this website, AnziLock has accounts: you sign in to its portal with Discord to see your licences, claim purchases, open tickets and manage your networks. It runs on our own server, reached through a Cloudflare Tunnel. How the service works is explained on the AnziLock page; this section covers the data it handles.

Licence checks

When a plugin checks its licence (at start-up and then at regular intervals), it sends:

  • Licence key — stored encrypted and looked up by a keyed hash. Staff can only reveal a key through an action that is written to the audit log.
  • Product — which plugin is asking.
  • Hardware ID — a one-way SHA-256 hash of the server's folder path, host name, network card (MAC) addresses, operating system and system user name. Only the hash is sent; the values it is made from never leave your server.
  • Nonce — a random value used once. It is kept for 10 minutes so the same request cannot be replayed.
  • Plugin version, server name, port and online player count — shown on your licence page so you can tell your servers apart.

AnziLock also sees the public IP address the request comes from, which is what a licence's IP limit counts. A licence check sends no player names, UUIDs, chat or world data.

Your account

  • Discord sign-in — your Discord user ID, username, display name, avatar and email address (Discord's identify and email permissions), plus your role and the time you last signed in.
  • Sessions — the IP address and browser user agent of each signed-in session. A session is deleted when you sign out, or when it expires after 30 days.
  • BuiltByBit username — only if you add it under Account, so your purchases can be matched to you.

Purchases and claims

  • BuiltByBit purchases — when you buy a plugin, BuiltByBit sends AnziLock a webhook with the purchase ID, your BuiltByBit username and user ID, the resource bought, and the price and currency. The message is stored as received, as the record of the purchase, and the licence created from it carries the same details.
  • Claims — when you claim a purchase, we store your BuiltByBit username, the product, the outcome and any note from staff. Staff may confirm the purchase through BuiltByBit's own API.

Tickets

Tickets opened from the portal or from Discord store the subject, your opening message, any form answers, and a snapshot of the conversation (taken when the ticket closes, and daily while a ticket stays open). Files you send in a ticket are recorded with their name, type, size and uploader, and copied into a staff-only vault channel on our Discord server so they stay readable after the ticket channel is gone.

Networks (AjdnikovPanel)

An AjdnikovPanel hub with a licence connects out to AnziLock so you can open it from Networks. Every 5 minutes AnziLock records whether the network is online and how many players are on it; these samples are deleted after 30 days. It also keeps the latest number of servers and how many are up. When you open a network, its own dashboard is passed through live and is not stored, except that changes made through it are written to the audit log (who, when, and the request path). People you share a network with can open it; staff can open it read-only, and only while a support grant you gave is running.

Phone app

If you switch on notifications in the AnziLock Android app, we store the phone's name, the notification types you picked, your pinned networks, when the phone last checked in, and a push token for Firebase Cloud Messaging when instant push is set up. Notifications (title, text and the portal link they open) are only stored for accounts with a phone switched on, and are deleted after 14 days. Switching the phone off removes it straight away; a phone not heard from in 90 days is removed automatically.

Logs

  • Request log — each licence check is logged with its time, IP address, hardware ID hash, plugin version, product, licence and result. These entries are deleted after 90 days.
  • Audit log — staff actions (such as revealing, suspending or resetting a licence) and some account actions (such as signing up, opening a ticket or sharing a network) are logged with who did it, what changed, when, and from which IP address.

How long we keep it

Request logs, network samples, phone notifications and phone registrations are deleted automatically as described above. The IP addresses and servers a licence has been used from stay on the licence until they are reset or the licence is deleted. You can reset IPs yourself with Reset IPs; staff can reset both. Your account, licences, purchase records, claims, tickets and the audit log are kept while your account exists.

You can ask for your data to be deleted by opening a ticket. We will delete your account, sessions, phone registrations and tickets, and remove your personal details from the rest, within 30 days. Purchase and licence records may be kept, without your personal details, where we need them to honour a licence or settle a payment dispute. Deleting a licence stops its key from working.

Who sees it and who processes it

You see your own account, licences, tickets and networks. Staff see licences, claims and tickets to provide support; administrators can see everything above. AnziLock data is never sold or shared with advertisers. These services process it on our behalf or as part of the feature you use:

  • Discord — sign-in, the ticket bot and the attachment vault (Discord Privacy Policy).
  • BuiltByBit — purchase webhooks and purchase checks (BuiltByBit; its privacy policy is linked from its site).
  • Cloudflare — all traffic to AnziLock passes through Cloudflare (Cloudflare Privacy Policy).
  • Google Firebase Cloud Messaging — delivers instant phone notifications, only when push is set up and you switched notifications on (Google Privacy Policy).

6. Third-Party Services

This website embeds or links to third-party services that may collect data under their own privacy policies:

  • Discord — a server widget is embedded on the home page (Discord Privacy Policy).
  • Google Fonts — fonts are loaded from Google's servers (Google Privacy Policy).
  • GitHub, BuiltByBit, TikTok — outbound links; their policies apply once you leave this website.

7. Data We Do Not Collect

We do not collect names, email addresses, passwords, payment information, or any other personal data through this website. Purchases of plugins are handled entirely by third-party platforms such as BuiltByBit, under their own terms and privacy policies.

8. Data Retention

Data stored in your browser (theme preference) remains on your device until you clear it. Analytics data is retained by Vercel according to their retention policy and is not accessible to us in a form that identifies individual visitors. How long AnziLock keeps its data is set out in section 5.

9. Your Rights

Because we do not collect personally identifiable information, there is generally no personal data for us to access, correct, or delete. You may clear cookies and local storage through your browser settings at any time, and you may block analytics scripts using a content blocker. This applies to this website; for AnziLock, which does hold personal data, see section 5 for what it keeps and how to have it deleted.

10. Changes to This Policy

We may update this Privacy Policy from time to time. Changes take effect when posted on this page. The "Last updated" date above reflects the most recent revision.

11. Contact

If you have questions about this Privacy Policy, contact us through our Discord server. See also our Terms of Service.