Checking your sign-in…

Internal

Admin

Everything here is for running the shop, not for customers.

Signed inYour account

  • Read the diagnostic bundles customers send from the plug-in, by reference code. Search by host, version or licence state. Kept for 90 days, then deleted.

  • Issue a key, see which machines each one is activated on, release a seat, and revoke it. Requests from signed-in customers arrive here too. To download the installer yourself, issue a key to your own address. Downloads go to any account that holds an active key; being an admin does not grant one.

  • Sales and refundsNeeds the payment account

    Orders, what was paid, and refunds, read from the payment provider.

    Needs a live payment account and a server that can hold its API key. That key can never live in this site.

  • Set the price, version number and the other undecided values without editing a file. Saving records a value; publishing rebuilds the site with it. The installer is not set here: the licence gateway serves it to buyers.

What the sign-in does and does not do

It hides these tools from anyone who is not signed in with an approved email. It does not make the page itself private — this is a static site, so the file is published and can be fetched by anyone who knows the address.

That is survivable because this page holds nothing but links. The tools behind them read customer data from the licence gateway and the support intake, which check your sign-in themselves, so the data is protected where it is stored, not on this page. Setup and the full reasoning are in ADMIN.md.