Privacy policy

Page views on the website

fkdr.dev and docs.fkdr.dev keep a server-side log of page views so the owner can see what gets read. It is built from the request your browser already sends; nothing runs in your browser to make it. Each view records:

• The page you viewed. Query strings are dropped before anything is stored, so a licence key or a checkout link is never logged.
• The time of the request.
• Your IP address and an approximate location (country, region, city), looked up on this server. It is coarse, often wrong for mobile, VPN and proxy connections, and never sent to a third party.
• The referring page, if your browser sent one, without its query string.
• Your browser's user-agent string, and the browser, operating system and device type read from it.

You are counted as one visitor for a day and a new one the next, without being identified. Records are deleted automatically after a set number of days (90 by default) and can be deleted earlier by the owner at any time. Nothing from the admin area, downloads, images or fonts is recorded. Separately, the web server keeps ordinary access logs that include your IP address; those roll over after 14 days.

Your licence, the mod and the overlay

• The licence record. A fkdr licence works on the computer it is set up on, so a device identifier is kept for each computer a key is used on. It is not your name, and it does not identify you. The IP addresses a key has connected from are kept as a security record and shown only in masked form; they never limit where you can play. You can move the key to another computer yourself from your key page, twice, and ask through the contact above to remove an address.
• Minecraft accounts. Each Minecraft account that plays on a key is recorded against it: the account's UUID and username, when it was first and last seen, and the fkdr version it ran. Only the most recent accounts per key are kept.
• “Playing now”. While you play, your key page and your friends can see your session: your Minecraft name and the server you are on. You can choose to appear offline (below). Your IP address is shown only in masked form. This live status is not kept after you stop playing.
• Module states. While you play, fkdr reports which modules you have switched on, with your Minecraft name, so your key page can show your session and turn modules on, off or lock them. Any settings the owner has locked are stored against your account.
• Licence checks. When fkdr starts, and when it fetches stats or an update, it sends your licence key and your Minecraft UUID and name so the licence can be checked. It also sends basic technical information about your game setup: where fkdr was launched from (which can include your computer's account name) and which other add-ons are running with it. This keeps fkdr working and protects licences. The result of the check is recorded against the key.
• Discord. If you link the key to Discord, your Discord user id and tag are stored with it. A key from a Discord boost is tied to the boosting account.
• Purchases. A purchase stores the order id and, if you gave one, the email you typed at checkout, next to the key it paid for.
• Your social account. The overlay's social features create one account per licence key: the username you choose, the Minecraft names you have played under, and when you were last seen.
• Appearing offline. You can choose to appear offline in the overlay. Other players then see you as offline, with no location or Minecraft account and a last-seen time that stops when you turned it on. This hides you from other players only: the administrator can still see your real status and which account you are on. Things you actively do, such as messages and friend requests, still carry their own times.
• Friends and messages. Friend lists, friend requests and blocks are stored. Direct messages are kept until they are deleted. The administrator can read any message and can delete messages and accounts; this is how abuse is handled. Treat overlay messages as moderated chat, not private correspondence.
• Scripts and comments. A script you upload or share stores its name, description, source code, version and share code, plus who installed or voted on it and any comments. The administrator can open any script, including a private one. A script you install is code written by another user and can send data anywhere it likes, so only run ones you trust.
• Player tags. Tag sharing is on by default. When you tag another player, the tag stores your Minecraft UUID and name, their UUID and name, the label, any note you wrote and when you added it; only the Friend label stays on your computer. Tags are public as soon as you post them, with no approval step, shown with your Minecraft name and the date. Write tags and notes on that basis, or switch sharing off in the module's settings. Other players can react to a tag and comment under it, and anyone can report a tag or comment; a report stores the reporter's account, name, reason and time. The owner can delete any tag or comment and can withdraw a key's ability to post tags, comments or both, for a time or permanently; that record keeps the Minecraft names on the key, the reason (which is shown to you), and when and by whom it was set.
• Other players. To show stats and tags in a lobby, the mod sends this site the UUIDs and names of the players around you, and the site asks Hypixel and Mojang about them; those answers are not stored. Depending on which sources you enable, your own copy of the mod may also ask Hypixel, Mojang and the third-party stats services directly, using keys you supply. Nothing about another player's gameplay or chat is recorded here.
• On your own computer. fkdr keeps your licence key, your settings, your tags and notes, and a year of your own match history on your own computer. The match history is never uploaded.
• Retention and deletion. All of the above is kept for as long as the key exists; there is no automatic expiry. Ask and the key, the licence record, the social account, its messages, scripts and tags are deleted, and the key stops working.

Payments

Crypto payments on the store are made on a payment processor's own page, under its own privacy policy. This site only receives what it needs to deliver the key: the plan, the amount, whether the payment confirmed, the email if you gave one, and the network address the order came from, which is used to stop abuse of referral codes. Zelle and Venmo payments are arranged in a ticket in the fkdr Discord and made in those apps. This site never sees card or bank details. What is stored against a key is the key itself, when it was issued, the order it came from and any note the owner writes on it. Older card purchases also keep their order id and the email given at checkout.

Cookies and storage

• Four cookies are strictly necessary for something you asked for: hwic_gate remembers the licence key you entered on the key page (6 hours), hwic_docs keeps you signed in to docs.fkdr.dev (30 days), hwic_admin keeps the site administrator signed in, and hwic_consent remembers your answer to the notice below for a year. None of them is shared with anyone.
• One cookie is not necessary and is only set if you allow optional analytics: hwic_vid, a random visitor id kept for a year, mirrored in local storage, with a matching session id in session storage. Choosing “Essential only” deletes it. Nothing else is stored in your browser.
• The small notice in the corner asks once whether optional analytics may run, and you can change your answer any time from the “Cookies” link in the footer. “Essential only” is a complete answer; a browser that sends the Global Privacy Control signal is treated as having said it without being asked.

Analytics with your consent

If you choose Allow on the notice, a small script on this site (first-party, nothing from any other company) records, for the pages you visit here: the page, its title and the page that referred you, including any campaign tags in the link; a random visitor id (the hwic_vid cookie) and a session id; your device and browser: screen, window and pixel size, colour depth, orientation, touch or mouse, dark or light mode, reduced-motion and contrast preferences, languages, time zone, processor count, memory class, platform, connection type and speed, whether the page is installed as an app, and the browser, operating-system and device-model details your browser is willing to hand over; how you use a page: how long it was open, how long it was in front of you, how far you scrolled, and which links or buttons you tapped, by their text and address, never anything you typed; whether a licence-portal attempt succeeded or failed (never the key itself), and if it succeeded, that this visitor holds that key; page speed measurements and any script errors, with the file and line they came from; and your IP address and the same approximate location as the page-view log. A dated record of your decision, with your IP address, is kept as proof of consent. It is used to understand how the site is used and to fix what breaks; it is never sold or shared, and it is deleted on the same schedule as the page-view log. Choose Essential only from the “Cookies” link in the footer and it stops at once and everything recorded under your visitor id is deleted. A browser that sends Global Privacy Control or Do Not Track never runs it.

Where data goes

Nothing is sold, and nothing is shared for advertising or cross-context behavioural advertising in the CCPA sense. For that reason there is no “Do Not Sell or Share” setting: there is nothing to opt out of. Everything described above lives on the owner's own servers. It leaves them in only a few ways: a payment processor handles crypto payments on the store; Mojang and Hypixel are asked about Minecraft UUIDs and usernames so names, skins and stats can be shown, and two avatar services are asked for a head image by UUID; Discord holds whatever you do in the Discord itself. The Discord bot keeps its own records for the things it does: verification (your Discord id with the Minecraft name you gave and who invited you), moderation cases, levelling and voice activity, giveaway entries and winners. Those are kept indefinitely, while joins, leaves, nickname changes and bridged chat are posted into Discord log channels and then live under Discord's own retention. Links to Discord and Instagram are ordinary links; those sites only learn about you once you visit them.

Your rights

Wherever you are, you can ask what is held about you, have it corrected or deleted, get a copy of it, or object to the page-view log. Some of it you can do yourself: free a device from your key page, choose “Essential only” to erase your analytics visitor id, delete your own tags, scripts and comments, and switch off tag sharing and the stats sources in the mod's settings. There is no self-service button for the rest, so ask through the contact above and the owner will do it by hand; expect an answer within 30 days, usually much sooner. Deleting page-view records for your IP address needs only the address. Under the GDPR / UK GDPR the legal basis for the visit log, the licence and security records and the moderation of messages and tags is our legitimate interest in running and protecting the service; for purchases it is the contract with you; for the optional analytics it is your consent, which you can withdraw at any time. You also have the right to complain to your local data-protection authority. Under the CCPA/CPRA you have the rights to know, delete and correct, and you will never be treated differently for using them.

Children

This site is not directed at children under 13 and does not knowingly collect personal data from them; the store is for adults, or for minors buying with a parent or guardian's permission. If you believe a child under 13 has given us personal data, contact us and it will be deleted.

Questions

Ask in the Discord at discord.gg/fkdr. This page changes when the site does; the date below says when.