Summary
- Every 30 minutes the plugin sends technical facts about the server: software, versions, player count, storage and integrations.
- Separately, a licence check sends the BuiltByBit buyer id and download id written into the copy of the plugin, so that copies shared against the licence can be found. It is not anonymous: it identifies the purchase.
- No player names, player UUIDs, IP addresses, ports, server names or MOTDs are ever sent.
- Each server's latest report is kept for 30 days after it was last seen. Only totals are kept longer.
- The live totals (servers and players online, and how they change over time) are public on the live stats page; the detailed breakdowns are private.
Plugin telemetry
The plugin sends one report as JSON to https://nametags.minestar.me/api/v1/telemetry about 2 minutes after the server starts and then every 30 minutes. The report contains exactly these fields, and the receiving server rejects any report with a field that is not on this list:
| Field | Example | Why |
|---|---|---|
| schema | e.g. 2 | The version of this report format, so old and new plugin versions can be told apart (1.0.0 sends 1, without the last four fields). |
| serverId | e.g. a random UUID | Counts each server once instead of once per report. Generated randomly on first start and kept in plugins/AdvancedNametags/data/server-id; it is not derived from anything about the server. Delete the file and a new one is made. |
| pluginVersion | e.g. 1.0.0 | Shows how quickly updates are adopted and which versions still need support. |
| software | e.g. Paper, Folia, Purpur… | Decides which server platforms get tested first. |
| softwareVersion | e.g. the build string | Finds the builds that break things, so fixes target real setups. |
| minecraftVersion | e.g. 1.21.11 | Decides when an old Minecraft version can be dropped. |
| javaVersion | e.g. 21.0.5 | Decides which Java features the plugin can rely on. |
| players | e.g. 12 | The number of players online, not who they are. Used for the public player count and to size performance testing. |
| storage | e.g. YAML, MYSQL… | Which storage backends are worth the most work. |
| integrations | e.g. PlaceholderAPI, LuckPerms… | Which of the known integrations are installed, from a fixed list. Other plugin names are never sent. |
| customTemplates | e.g. 3 | How many templates were added beyond the defaults: whether people customise or keep the defaults. |
| customBadges | e.g. 0 | The same, for badges. |
| language | e.g. en | The configured message language if it is one of the seven bundled ones, otherwise just "other" (a custom file name is never sent). Decides which translations get attention. |
| templates | e.g. 9 | How many templates are loaded in total. |
| badges | e.g. 45 | How many badges are loaded in total. |
| features | e.g. badges, motions… | Which plugin features the configuration uses, as words from a fixed list of fourteen (cycling lines, text effects, badges, motions, transitions, item rows, conditions, per-world and group templates, reactions, through-walls hiding, view cone, player menu, self view). Never the text, names or values that use them. |
One question, one click
Does this telemetry put you off buying the plugin, or do you not mind it?
Anonymous: only a count per answer is kept. Details under "This website" below.
Licence check
When you download the plugin, BuiltByBit writes your user id, the resource id, an id for that download and the download time into the file. While the server runs, the plugin regularly sends those four values, the random server id described above, the plugin version and, if you were given one, the licence key from config.yml (stored on our side only as a hash) to this website. Nothing else is in the request, and the receiving server rejects any other field.
This is what lets us see when one download is running on far more servers than a licence allows, which is how leaked and reshared copies are found. For that purpose the sender's IP address is turned into a keyed one-way hash that tells networks apart; the address itself is not stored. The buyer id is the public numeric id of a BuiltByBit account; we do not receive your name, e-mail address or payment details from BuiltByBit.
The website answers with a signed status that the plugin keeps on the server. A connection problem never stops the plugin, and nothing is ever switched off while a server is running.
The status is one of three. Normally it is "ok". A download that runs on unusually many servers or networks is flagged automatically and gets "warning": the console and admins who join see a notice, and the plugin keeps working. Only a person can set "revoked", after a refund or a breach of the licence: from its next start that server leaves the nametags off and says why. If you bought the plugin and see either notice, contact us and it is corrected. Every such decision is logged with its reason.
The licence check is separate from the usage statistics and their setting. A record of which server ran which download is kept for 180 days after that server was last seen; a licence or a server that was warned, revoked, confirmed as legitimate or issued by hand is kept with its log for as long as that decision stands. The legal basis is our legitimate interest in enforcing the licence the plugin is sold under.
What is never collected
- Player names, player UUIDs, chat, or anything else about individual players.
- The server's IP address, port, domain, name or MOTD.
- The list of other plugins, beyond whether the five known integrations are installed.
- Configuration contents, template or badge contents, or log files.
IP addresses
Like any HTTP request, a report reaches our server from an IP address. That address is used only in memory, to limit how many reports one address can send. It is first turned into an anonymous key with a random secret that changes on every restart, it is never written to disk or to logs, and it is never linked to the report. The only exception is the keyed hash kept with a licence check, described above.
The website software writes no access logs. Requests reach it through Cloudflare, which processes IP addresses to deliver and protect the site, under Cloudflare's privacy policy.
Retention
We keep only the latest report of each server. A server that has not reported for 30 days is deleted. Hourly and daily totals (number of servers, number of servers that reported each day, new installations each day, number of players, and counts per software, Minecraft version and plugin version) contain nothing about any single server and are kept for up to 400 days.
Turning it off
The telemetry is on by default, because it is the only reliable way a small team learns which platforms, versions and features buyers actually use: it decides what gets tested before each release, when an old Minecraft or Java version can be dropped, and where work goes next. It also powers the public statistics. Set usage-statistics: false in config.yml and run /nametag reload: from then on no usage statistics are sent (this also turns off the plugin's bStats metrics; the licence check is separate, see above). The console says which state is active at startup.
The public statistics only show names from fixed lists (known server software, version numbers, storage types); anything else is counted as "Other".
bStats
Separately, release builds of the plugin use bStats, the anonymous metrics service most Minecraft plugins use. bStats is run by its own operator under its own privacy policy. On top of bStats' standard server data, the plugin adds its storage type, language, a template count range, the through-walls setting and the installed integrations.
bStats can be turned off for all plugins at once by setting enabled: false in plugins/bStats/config.yml. That setting does not affect the telemetry above.
Update check
At startup and every six hours the plugin downloads https://nametags.minestar.me/api/v1/version, a two-line text file with the latest version and its download page. That request sends nothing but the plugin version in its User-Agent and is handled under the same IP rules as above. Set update-checker: false in config.yml to turn it off.
This website
This website sets no cookies for visitors and uses no third-party analytics, trackers, advertising or third-party scripts; fonts and media are served from this domain. The browser tools run on your device: what you paste or design is not uploaded. A shared design link carries the design in the link itself. The only cookie this site can set is a strictly necessary login cookie for the operator's private statistics page; visitors never receive it.
The live stats page loads the public totals from /api/v1/stats once a minute while it is open.
To learn which pages are read, each page you open sends one small request to /api/v1/pageview with the page path and, on your first page, the website you came from (its host name only). The server adds a coarse device class (desktop, mobile or tablet) taken from your browser identification and, when the network in front of it provides it, your country. That is all that is kept, as counters per day: no cookie, no browser storage, no IP address, no full user agent and no query strings are stored. To count unique visitors per day, a one-way hash of your IP address and browser identification is made with a random key that is held only in memory and replaced every day; the hashes are used for that day's count and deleted when the day ends, so they cannot be matched across days. Your IP address is also used, in memory only, to limit the request rate. Visits with Do Not Track or Global Privacy Control turned on, crawlers, and the private admin area are not counted. The counters are kept for 400 days.
The question about telemetry on this page is optional. If you answer it, your click is sent to /api/v1/poll and only a count per answer and day is kept, for 400 days. The same daily hash makes one visitor count once a day, and your browser's local storage remembers only that the question was answered, so it is not asked again; clearing the site's data removes that.
Operator and contact
The plugin and this website are run by VicEntity. Questions about this page, or a request to see or delete what is stored about a server or a purchase (send its serverId): our Discord .
We will update this page before any change to what is collected, and change its effective date.