Legal

Privacy Policy

Effective 20 October 2026. This policy explains what data Licentry ("we", "us") handles when you use licentry.cc, the vendor dashboard, the Licentry API, the Licentry Discord bot and the Licentry integration plugin, and what your choices are. The controller is the private individual who operates Licentry from Sweden. No business is registered behind it yet, so the registered name, address and numbers a controller would normally give you do not exist yet either; section 12 of the Terms of Service sets out what is published today and what is added when a business is registered, and this page is updated in the same change. Contact for anything privacy related: [email protected].

For vendor accounts (the businesses that sign up), we are the controller and decide how the data is used. For end user licensing data (the people who run software licensed through a vendor), we process technical data on the vendor's behalf to provide licensing. The vendor is the controller of that data and your first point of contact about it.

1. Data we collect from vendors

  • Account. Email address, a hash of your password (never the password), optional company name, two factor secrets stored encrypted, and backup code hashes.
  • Security history. Sign in events with IP address and browser user agent, kept so you can spot an account takeover.
  • API keys. Name, scopes, a display prefix, a hash of the key, and the IP address a key was created from and last used from. The full key is shown to you once and never stored.
  • Billing. Invoices record the plan, USD amount, billing period and country, any VAT number you provide, the result and reference of the EU registry check, and the resulting VAT treatment. Card details are entered in a Stripe-served form embedded in our page and sent directly to Stripe. We never receive or store any part of your card number. We receive a customer reference for your account and a payment reference for the invoice. All payments now go through Stripe; we no longer accept cryptocurrency directly. Earlier on-chain invoices retain their currency, generated payment address and the transaction details needed to recognise a payment. Unmatched transfers to those addresses are kept with the sending address so they can be returned. We do not perform KYC or ask for identity documents. Stripe performs its own card-payment checks, including strong customer authentication and fraud screening, to meet the rules that apply to it as a payment provider, not to us.
  • Support. Emails you send to support, so we can answer them. They reach us through Cloudflare Email Routing, which forwards them to a mailbox the operator reads.

The integration plugin, and where your source code goes. The plugin runs in your own AI coding agent. It reads your source on your machine to find where to add licensing, then writes code into your files. Your source goes to the AI provider configured in your agent under your agreement with that provider. It does not reach us. The provider is not our subprocessor, we do not contract with it on your behalf, and we receive nothing from it. We also do not receive the plugin's plan file, your answers to its questions, or your file names.

The plugin requests our public documentation pages and its manifest over HTTPS. These requests are identical to a browser's requests for the same pages and pass through Cloudflare, as section 6 describes. We log the source address, method, path, status and user agent, as we do for other requests to licentry.cc. Logs are kept for up to 90 days, or less if they reach the size limit. These pages need no sign in, so the log identifies a request from an address, not an account. The hardening guide requires a dashboard sign in and the plugin cannot fetch it. Instead, it asks you to save a local copy and keep it out of version control, for the reason given in section 4 of the Terms.

2. End user licensing data we process for vendors

When software licensed through Licentry activates or validates a key, the API records:

  • licence keys as keyed one way hashes (the plaintext key is never stored server side);
  • device identifiers as the hash your vendor's client computes and sends. We do not receive a raw hardware serial through the licensing API. Our documentation and integration plugin suggest identifiers and describe their stability. The vendor chooses which to include in the hash and is responsible for telling you what their software reads from your machine;
  • IP address, user agent and timestamps of licensing calls;
  • runtime session records: activation, heartbeat and refresh times, and why a session ended;
  • tamper reports, when the vendor's software sends them: the reason it gives, the address it came from and, if the software includes one, a screenshot of the screen at that moment. We do not store the screenshot. It is passed to the Discord webhook the vendor set up and then dropped, and if the vendor has none it is dropped at once. The reason and the address are delivered to the vendor's own webhooks.

If a vendor ships the optional Licentry desktop loader, that component reports much more on every launch: the network adapter (MAC) address; the address the request came from and every other address the loader can see on the machine, including one it looks up through a STUN server, which can show the real address behind a VPN; the VPN adapters present and whether one is active; the computer name and the operating system user name; a hardware identifier; the email address of the account signed in to the loader (the "account address"); a linked Discord user id and username; location derived from the IP down to postal code along with the internet provider and the network operator; and a snapshot of the running environment used to detect tampering. The adapter address and the account address arrive as they are and are kept only as keyed hashes; unlike the licensing API, the hashing happens on our side rather than in the client, so those two values do reach us in readable form before they are stored. Keyed hashing means we can tell whether two reports came from the same machine without being able to read the underlying identifier. Each launch report is also delivered to the vendor the licence belongs to, through the webhooks they set up, with everything above except the adapter address and the account address. Vendors who integrate the API directly, which is the normal case, send none of this.

Purpose: making licence checks work, enforcing the device and session limits the vendor configured, and giving the vendor evidence when one key is shared by many people. We never sell this data or use it for advertising.

Retention. Validation logs are deleted after 90 days, dashboard sign in history after 180 days, loader reports after 90 days, download records after 365 days, records of what was delivered to a vendor's webhooks after 30 days, and the security audit trail after 365 days. The separate record of a Licentry administrator acting on a vendor's account includes the vendor's id and email address and is kept for 730 days to investigate incidents. A sweep runs once a week, and each kind of record has its own window rather than a window shared with the sweep: a runtime session goes 30 days after its refresh window expires, a device record only once a vendor has cleared it and then 90 days later, expired sessions and used one time codes a week past their expiry, and queued notifications after 30 days. Encrypted backups on the server itself are kept as the three most recent copies of each kind rather than by age, and the off site copies for up to 30 days, sooner if that store reaches its size limit. The off site copy of the security audit trail and of vendor sign in events is kept separately for 365 days in storage that nobody, including us, can alter or delete before then, and it is deleted the day after.

Invoices are the exception to all of that. Under bokföringslagen (1999:1078) 7 kap. 2 §, we must keep invoices and their supporting records for seven years from the end of the calendar year in which the financial year ended, not from the invoice date. An invoice raised during 2026 is therefore kept into 2033. This legal obligation continues after account deletion, so we retain these records for the required period even if you ask us to delete your account.

3. Why we are allowed to use it

For the data where we are the controller, each use rests on one legal basis under the GDPR:

  • Running your account, meaning sign in, two factor, API keys, the dashboard and answering support: the contract with you, Article 6(1)(b). Where you act for a company rather than for yourself, it is our legitimate interest in running the relationship with that company, Article 6(1)(f).
  • Keeping the platform and your account safe, meaning sign in history, rate limits, the security audit trail and its off site copy, and the request log described in section 1: our legitimate interest, and yours, in catching account takeovers, abuse and tampering, Article 6(1)(f).
  • Invoices, the records behind them and the VAT number check: a legal obligation, Article 6(1)(c), under bokföringslagen and the VAT rules.
  • Verifying vendor owners and staff through Discord and adding them to the Licentry server: the contract with the vendor and our legitimate interest in knowing who acts for an account, Article 6(1)(b) and (f).

Nothing is based on consent, and nothing is used for advertising or profiling. To have an account you must give an email address, a password and the country you are billed in; a company name, a VAT number and a Discord link are optional.

For the licensing data in section 2, and for what the bot does on a vendor's behalf in section 4, we act for the vendor. The vendor decides why that data is processed and needs its own legal basis for it, including any consent the law requires before its software reads information from a device. We use that data only to provide the service to the vendor.

4. The Licentry Discord bot

The bot connects a vendor's Discord server to their Licentry account. This section is the complete inventory of what it touches.

  • Server link. The server id and name, the id and username of the admin who ran /link-account, and when. Channel ids you point logs at, and the role id the bot grants after a redeem.
  • Redeems. When a customer redeems a key (panel button or /redeem), we store their Discord user id and username on that licence, with time and server id, so the vendor can see which Discord account a key belongs to.
  • Commands. Staff key commands (generate, reset, ban, unban, revoke, extend) are written to the vendor's audit log with the acting person's Discord username and id.
  • Account verification. Vendor owners and their staff verify through Discord sign-in with the identify and guilds.join permissions. We store the verified user id and username, and the sign-in tokens encrypted at rest; guilds.join is used for one thing, adding verified vendor people to the official Licentry server.
  • Log posts. Activity embeds queued for delivery are held only until posted, then only the delivery outcome is kept.

What the bot does not do. It does not read messages (it is built without the message content intent), does not collect member lists or presence, does not track voice, and only sends a DM when the vendor turned on DM confirmations and you redeem a key. It never posts publicly on your behalf.

Sharing. Discord bot data is visible to the vendor whose server and keys are involved, and to us for operating the service. It is not sold and not shared with anyone else. Discord itself processes everything you do inside Discord under its own privacy policy.

Removal. A vendor can detach any customer from a key in the dashboard, and can disconnect the whole server at any time; kicking the bot from the server ends all collection for that server. If you are a customer and want your Discord link removed, ask the vendor who sold you the key, or email [email protected] with the server name and we will handle it.

5. Cookies

The dashboard sets one session cookie so you stay signed in, plus a short lived cookie during two factor sign in and another while you connect a Discord account. The customer portal sets its own session cookie for end users who sign in there. Every one of them is needed for the page it belongs to, so none of them asks for consent. On the pages where you pay by card, Stripe's own script runs and sets its own cookies, which Stripe uses to detect fraud across the sites it serves; that is part of taking a card payment rather than something we could turn off and still charge a card. Beyond that we run no advertising cookies and no analytics scripts, ours or anyone else's.

6. Where data lives and who touches it

  • Hosting. The service runs on DigitalOcean infrastructure in Frankfurt, Germany. Disk level encryption there is DigitalOcean's own, not something we configure on top of it; the backups are encrypted by us before they are written.
  • Cloudflare. DNS and the network edge, so every request to licentry.cc passes through Cloudflare before it reaches us. Off site encrypted backups and uploaded builds are stored in Cloudflare R2. Mail to our support address is received by Cloudflare Email Routing and forwarded to a mailbox the operator reads, so anything you write to support transits Cloudflare as well. Our security audit rows and vendor sign in events, which include IP addresses and browser user agents, are also copied into Cloudflare R2 storage held in the EU, as the off box copy of that trail. These copies preserve the audit record if someone changes records on the server.
  • Discord. When the integration is enabled, log embeds and command replies flow through Discord's platform, and so does anything a vendor routes to its own Discord log webhook, including tamper reports and their screenshots. Security alerts sent to the operator over Discord say only what kind of event happened and how serious it is; who was involved and where they connected from stay out of Discord. Discord decides for itself how it handles what passes through its platform, under its own privacy policy, so for that data it is a controller in its own right rather than acting for us.
  • Email. Transactional email (password resets, sign in codes) is delivered by Brevo.
  • Stripe. Card payments are processed by Stripe. When you pay by card, Stripe receives your card details straight from your browser, along with your email address, the amount, the invoice reference, and whatever its script collects in your browser, including your IP address, which it uses to detect fraud. Stripe is not acting on our instructions when it does that. It decides for itself what it needs to meet the rules that apply to payment providers, so for your payment data Stripe is a data controller in its own right and its own privacy policy governs what it does with that data. We contract with Stripe Payments Europe, Limited in Ireland, and some of the processing happens in the United States at Stripe LLC. Those transfers run under the EU to US Data Privacy Framework, with the European Commission's 2021 standard contractual clauses behind it as the fallback, so a transfer stays covered even if that framework stops applying. If you dispute a charge with your bank and we contest it, we send Stripe the record of the purchase, including when you bought and the address you bought from, and Stripe passes that to your bank.

All of those except Stripe and Discord handle data only to provide their service to us, on our instructions. Stripe, alongside what it does for us, also handles payment data for its own regulatory purposes, and Discord handles what passes through it under its own policy, as their entries above describe. We disclose data beyond that only if the law forces us to, and we tell you when we are allowed to.

We still monitor addresses from the earlier on-chain payment system so we can recognise and return payments sent to them. We query public blockchain explorers with those addresses. Their operators hold no account with you, and the transactions are already public on the blockchain. To identify the country a licensing call came from, we use a data file on our own server. No address is sent to a geolocation service.

7. Security

Secrets are encrypted at rest under a master key that is not held in the database, credentials are stored as hashes rather than as reversible values, session tokens are stored hashed so a copy of the database cannot be used to sign in as you, transport is TLS everywhere, and each vendor's licensing material is sealed with cryptographic material specific to that account. Administrative actions land in an audit log owned by a separate database role that the application can add to but cannot edit or delete, and each entry is chained to the one before it so a removal is detectable.

No system can prevent every breach. Anyone who compromised the running server could read what the server itself can read. If a breach ever affects your data we will tell you what we know, what we do not yet know, and what you should do, without undue delay. Where the law requires it we also report a breach to IMY, the Swedish supervisory authority, within 72 hours of becoming aware of it, and where the data is a vendor's licensing data we tell that vendor without undue delay so they can meet their own obligations.

8. Your rights

You can ask us for a copy of your data, ask us to correct it or delete it, ask us to restrict how we use it while a question about it is settled, and ask for the data you gave us in a machine readable form. You can object to any use that rests on our legitimate interests, listed in section 3, and we then stop unless our reason for it outweighs yours or we need the data for a legal claim. Vendors can self serve much of this in the dashboard: revoke keys, unlink Discord accounts, disconnect the server, or ask support to close the account.

If you use software a vendor licenses through Licentry, a request about that licensing data goes to the vendor, because they decide how it is used. If you write to us instead, we pass it on and help them answer.

Write to [email protected]. We confirm a request through the account or email address it concerns and do not ask for identity documents. We answer within one month; a complex request, or one of many from the same person, can take up to two months more, and if it will we say so within the first month. Two kinds of record cannot be deleted on request: invoices, for the reason given in section 2, and the off site security copy until its 365 days have run, because it exists to show what happened. You can complain to the supervisory authority where you live or work; in Sweden that is Integritetsskyddsmyndigheten (IMY), at imy.se.

9. Children

Vendor accounts are for adults, as the Terms require. Software that vendors license through Licentry may be used by younger people, and their licensing data is handled as section 2 describes, under the vendor's responsibility. If you believe a child opened a vendor account, write to support and we will close it and delete its data.

10. Changes

When this policy changes in a way that matters, we announce it in the dashboard or by email before it takes effect. The date at the top is always the current version. Earlier versions are available from support on request.