Privacy
Written from the data the platform actually holds, not from a template. If you find something we collect that is not listed here, that is a defect and we want to know.
Last updated 14 August 2026
1Who is responsible
The data controller is [LEGAL ENTITY NAME], [REGISTERED ADDRESS]. For anything on this page, write to [PRIVACY EMAIL].
2What we hold, and why
Account — email, display name, password (stored only as a scrypt hash, never in readable form). Needed to give you an account at all. Legal basis: performance of the contract.
Purchases — what you bought, when, how much, and the licences issued. Needed to sell you something and to prove you own it. We never see or store card numbers: payment happens at Stripe.
Licence activations — a one-way hash of the hostname and username of the machine using a licence. It counts installations; it does not let us learn the hostname or the username, and it is not used for anything else.
Installs — that a plugin was downloaded, and when. Publishers see totals; nobody sees who. Legal basis: legitimate interest in reporting to publishers.
Publishers — display name, bio, payout details including IBAN. Needed to pay you.
Submitted plugins — the archives you upload and the review findings on them.
Abuse counters — a hashed key and a count, to limit sign-in attempts and licence checks. Legal basis: legitimate interest in keeping the service usable.
3Cookies
Two, both strictly necessary, neither used for analytics or advertising:
- the session cookie, which keeps you signed in — it holds a random token, nothing about you;
- a short-lived cookie that shows a freshly generated manifest token once, then expires within minutes.
There is no tracking, no advertising network, no third-party analytics. That is also why you are not being asked to accept anything.
4Who else sees it
Stripe — payment processing. They receive what a payment needs; we receive back only the outcome and a reference.
Publishers — aggregate numbers about their own plugins. They do not receive your email or your identity. Where a plugin verifies its licence at startup, it sends us the key and the machine hash; it does not send us anything about you that we did not already hold.
Our infrastructure providers — hosting and database, under contract and instruction. [LIST PROVIDERS AND REGIONS]
We do not sell data. There is nobody else.
5How long
Account and purchase records for as long as you have an account, then for the period tax law requires us to keep them — typically ten years for anything with an amount on it.
Sessions expire and are swept automatically. Abuse counters are deleted once their window has passed. Licence activations disappear when the licence is released or the licence itself is deleted.
6What you can ask for
Access to your data, correction, deletion, restriction, portability, and objection to processing based on legitimate interest. Write to [PRIVACY EMAIL] and we answer within a month.
Deleting your account removes your personal data, but not records we are legally required to keep, and not the fact that a purchase happened where that is needed for accounting.
If you think we have handled your data badly you can complain to your national supervisory authority — in Italy, the Garante per la protezione dei dati personali.
7Security
Passwords are hashed with scrypt and a per-password salt. Session and manifest tokens are stored only as hashes, so a copy of our database does not yield a working token. Licence keys are signed with Ed25519. Traffic is encrypted in transit.
Uploaded plugin archives are executed only inside a container with no network access and a read-only filesystem, as part of the review. See the security policy.