PRIVACY POLICY

• Your username, and the date you last changed it.
• Your email address, and whether and when you confirmed it.
• Your password, stored as an Argon2id hash. We cannot read it and nobody here has ever seen it.
• Your two-factor secret and recovery codes, if you turn 2FA on. Both are encrypted before they are stored, so a stolen copy of the database does not hand over working second factors.
• Your display timezone and your interface preferences.
• The date and time you last signed in, and the IP address you signed in from.
• Your account status — and if it has been suspended or banned, the reason, when, and which member of staff did it.

We record every sign-in attempt against your account, successful or not, and every failed attempt against a username that does not exist. Each record holds:

• the username that was typed
• whether it worked, and if not, why not
• the IP address it came from
• the browser's user agent string, and the browser and operating system we read out of it
• a device fingerprint calculated in your browser, where one is available

This is how account takeovers get noticed and how credential stuffing gets spotted. The failure reason is for staff only — somebody trying to guess their way in is never told which half they got wrong.

You can read your own sign-in history and see your active sessions on the Security page of your dashboard, and sign other sessions out from there.

A signed-in browser session is stored in our database with its IP address, its user agent, and how recently it was used. It expires after 120 minutes of inactivity.

We also email you when your account is signed into from a device we have not seen before.

• What you bought, which plan, at what price, and a frozen snapshot of the product as it was described on the day — so a receipt still means something after the catalogue changes.
• The IP address and the browser user agent the order was placed from.
• Which version of these policies was on screen when you ordered, and the moment you accepted it.
• For a crypto payment: the coin, the address we asked you to pay, the exact amount, the exchange rate we locked, the transaction ID once it arrives, and the confirmation count as it climbs.
• Any movement of your balance, with the reason for it.

We store no card or bank details at any point. There is no column in this database for one.

Please note that a cryptocurrency transaction is public by nature. A payment you make to us sits on a public blockchain permanently, is visible to anybody, and is not something we or you can remove.

• Which products you hold, when each term started, and when it ends.
• A hash of your machine's hardware fingerprint, not the fingerprint itself. It is a stable identifier for the machine and we treat it as personal data, which is why it is stored one-way.
• A short non-identifying label for the device, such as "Windows 11, 16 cores", so support can tell two machines apart.
• When it was bound, when it was last seen, and the IP address it was last seen from.
• Every device reset: when, by whom, and the reason given.
• Live sessions of the desktop software, with the IP address, the client version and the heartbeat times.

Licence keys are stored as SHA-256 hashes. The plain key exists only in the moment it is generated and shown to you once, which is also why we cannot recover one for you later.

Every download attempt is recorded, whether it was allowed or refused: which product, which release, which file and version, the IP address, the user agent, and the reason for any refusal.

The refusals matter more than the successes. A run of them against one account is somebody probing, and a run across many accounts from one address is somebody working through the catalogue.

Whatever you write in a ticket, and any file you attach to one, is stored with it. Staff replies are stored alongside.

Please do not paste passwords, recovery codes or wallet seed phrases into a ticket. We will never ask you for any of them.

Linking Discord is optional and exists only to give you roles in our server.

If you link it, we store your Discord user ID, your Discord username, the reference for your avatar image, and when you linked it.

We store no Discord tokens. The access token from the sign-in is used once, seconds later, to add you to the server, and is then dropped. There is deliberately nowhere in the database to keep one — a stored refresh token would be a permanent, silent capability against your Discord account, and that is not a trade worth making to save you a click.

You can unlink at any time from your dashboard.

Every privileged action taken by our staff is written to an audit trail: who did it, what they changed, what the value was before, the reason they gave, and the IP address they did it from.

That trail covers actions taken on your account, and it is kept for the reason you would want it kept — it is the only way to answer "who changed this" after the fact. Sensitive values are removed before anything is written: the trail records that a password changed, never what it changed to.

We use two cookies and both are strictly necessary: one holds your session so you stay signed in, and one carries the token that stops a third-party site submitting forms as you.

There is no analytics on this site. No Google Analytics, no advertising pixels, no tracking scripts, no third-party session recording. Nothing follows you around the internet on our behalf, which is also why there is no cookie banner to click through.

We do not sell your data and we do not share it for anybody else's marketing.

A short list of third parties are involved in running the service:

• Our hosting provider, whose servers the site and the database run on.
• Public blockchain explorers, which we query to see whether a payment has arrived. We ask them about our own receiving addresses, not about you.
• An exchange rate feed, for pricing a payment in coin.
• An email provider, to deliver account and order emails.
• Discord, if you have linked it.

Three things load in your browser from somebody else's server, which means those servers see your IP address when a page loads: Google Fonts serves the site's typeface, YouTube serves the video thumbnails on product pages, and Discord's CDN serves your avatar if you have linked an account.

We will also disclose what we have to if we are required to by law.

We do not currently delete any of it on a schedule.

We would rather tell you that than invent a retention period we do not enforce. There is no job that trims sign-in history, no job that trims download history, and no job that trims the audit trail.

Orders, payments and audit entries are kept permanently by design — they are the financial and accountability record of the business, and some of them we are required to keep for years in any case. Everything else stays until somebody removes it by hand.

The one exception is browser sessions, which expire after 120 minutes of inactivity and whose rows are cleared out as they are found.

Setting real retention periods for sign-in and download history is on our list. When we set them, this section will say what they are.

Open a ticket and ask, and we will deal with it.

• A copy of what we hold on you. We will put it together and send it.
• A correction. Your username, email, timezone and preferences you can change yourself from your dashboard.
• Deletion. We will remove what we can, and tell you what we cannot.

We should be straight with you about that last one. Accounts are never hard-deleted here, because orders, payments and audit entries all point at them and a deleted actor still has to be attributable. What deletion means in practice is that the account is closed and its records are taken out of view; staff can destroy specific records outright where that is the right answer, but the order and financial history stays.

If you are somewhere whose law gives you stronger rights than this — a right to erasure, a right to object, a right to complain to a regulator — those rights apply and we will honour them.

• Passwords are hashed with Argon2id.
• Two-factor secrets, recovery codes and payment credentials are encrypted before they are stored.
• Licence keys are stored as one-way hashes.
• Hardware fingerprints are stored as one-way hashes.
• Traffic to the site is encrypted in transit.
• Staff access is governed by named permissions, and every privileged action is logged.

No system is perfectly secure, and anybody who tells you theirs is has not thought about it hard enough. If you find a problem in ours, tell us in a ticket and we will take it seriously.

This service is not for anybody under 18. We do not knowingly hold data on a child, and if we find that we have, we will remove it.

When this policy changes, the version and date at the top of the page change with it, and the version in force is recorded against every order placed under it.

If we ever start collecting something materially new, or start sharing something with somebody new, we will tell you rather than quietly reissuing the page.