Terms of Service

1. What Licentry is

Licentry is licensing infrastructure. You (a "vendor") plug our API into software you sell, and we handle licence keys for it: issuing, activation, device binding, runtime sessions, revocation and the analytics around them. Your customers ("end users") interact with Licentry only indirectly, through your software or through the Licentry Discord bot in your server.

You keep full ownership of your software and your customer relationships. We provide the plumbing; we are not a party to any sale between you and your customers, and we do not handle their payments to you.

We also publish an integration plugin ("the plugin") that you install into your own AI coding agent. It reads our documentation as it stands at the moment you run it, reads your source to work out where licensing has to go, asks you the things it cannot work out from your code, and then writes client code into your own files. That last part is why the plugin is named separately from the rest of the service in the sections below: what it writes ends up compiled into a product you ship, so the terms that cover it cannot be the terms that cover a service you rent. Section 8 is where that is settled.

2. Your account

• Keep your registration details accurate and your credentials to yourself. We strongly recommend turning on two factor authentication.
• Everything done with your session, your API keys or your linked Discord server counts as done by you. Revoke keys you no longer trust and disconnect servers you no longer control.
• You must be at least 18, or the age of majority where you live, to open a vendor account.
• One account per business is the intended shape. Do not create accounts to dodge limits, trials or bans.

3. Plans, trial and billing

No plan can be bought at the moment: Licentry is in a demo state while the business behind it is set up, so what follows are the terms that apply to plans and payments once the service opens for sale.

• Dev trial. New accounts can start a free trial with reduced quotas. While Licentry is in its demo state the trial does not run out: nothing can be bought, so there is nothing for it to convert into, and it stays open with its full quotas until the product is released. Nothing of yours is deleted for age while that is the case. When the service opens for sale the trial is one week, and a trial that ends without a subscription has its data (products, keys, sessions, API keys) deleted, with the account itself deleted about a month after the trial period ends, whether or not you have been signing in. The trial exists to build an integration, not to run production on.
• Paid plans. Indie and Studio are prepaid, monthly or yearly, and priced in USD excluding VAT. You pay by card in the dashboard, on a form served by our payment provider inside that page, so your card number goes straight to them and never reaches us. VAT is added at checkout where it applies; which VAT applies depends on the country you are billed in and on whether you gave us a VAT number we were able to check. A card subscription renews at the end of each period and keeps renewing until you cancel it, so your licensing does not stop because a date went past while you were busy. Cancelling is one action in the dashboard and you can take it at any time: it stops the next renewal and nothing else, so access runs to the end of the period you have already paid for, and there is no refund for the part of that period you do not use.
• Paying in cryptocurrency. A blockchain payment is a single transfer and cannot carry a standing authorisation, so a crypto period does not renew itself: when it ends, you buy the next one the way you bought the first. That is a property of the payment method rather than a rule we made, and it is the real difference between the two ways of paying. A sale that carries VAT cannot go on this rail either, because the rail quotes the price before VAT and has no way to collect the tax on top of it; those are paid by card. The billing page is where you see which methods are open to your account, and cryptocurrency is being retired in favour of card.
• Crypto payments are final. On-chain transactions cannot be reversed by us. Send the exact quoted amount, to the address on the invoice, on the chain the invoice names; a payment matching all of that is credited when it confirms. One that is short, late, in another currency, or on a chain we did not quote is not credited automatically, and on some chains it cannot be recovered by anyone. Write to support with the transaction id and we will either put it towards a corrected invoice or send it back, less the network fee for sending it. If you are owed a refund we still make one; we just cannot reverse the original transaction, so we send a new one.
• Card charges and disputes. A card charge can be reversed by your bank, which is the one thing a crypto payment cannot do. If something is wrong with a charge, write to support first: we can usually fix it faster than your bank can, and a dispute takes weeks and costs us a fee whichever way it goes. If you raise one with your bank anyway, we may suspend the account while it is open, which stops new licence keys, new API keys, new builds and the Discord bot. Licence keys already in your customers' hands keep validating for 7 days from the suspension and stop at the end of them, the same 7 days a lapsed subscription gets and for the same reason: your customers are not the lever we collect with, and they are not a way to keep licensing running on money that has gone back to your bank. If the dispute is decided in our favour, or you withdraw it, the amount stays owed and the account comes back once the money has settled back to us. Where a dispute succeeds on a ground that turns out not to be true, the reversed amount stays a debt you owe us, along with the fee our payment provider charges us for it.
• Refunds. Paid periods are not refunded once started, except where the law of your country requires it. If we permanently shut the service down mid-period, we refund the unused part.
• Lapsing. If a subscription runs out, creating new products, keys and API keys pauses immediately. Licence keys already in your customers' hands keep validating for 7 days after the subscription lapses, and validation stops at the end of those 7 days. The 7 days are there because your customers are not the ones who owe us anything, and a renewal that fails on a Friday should not take their software down with it. They are not a free tier: serving licence checks costs us the same whether or not the account behind them is paid, so they run out on a date rather than staying open.
• Price changes. We can change prices for future periods with at least 14 days notice in the dashboard or by email. Founding rates stay locked while the subscription stays active.

4. Acceptable use

You may not use Licentry to:

• license, distribute or protect malware, spyware, ransomware or software designed to harm the people running it;
• break the law of the countries you operate in, or infringe someone else's intellectual property;
• attack the service itself: probing other tenants' data, evading rate limits, reselling raw access to the API, or reverse engineering our hosted components;
• spam or harass people through the Discord bot or its log webhooks;
• republish documentation we keep behind a vendor sign in. The hardening guide is that page, and it is written for the account holder: it sets out what Licentry detects, how much slack each protection allows and what defeats each control, so a copy of it in a public repository is a copy an attacker reads. The plugin cannot fetch that page at all and will ask you to save your own copy locally instead. Keep that copy out of version control and out of anything you publish. Reading it, quoting it to your own team and pasting it into your agent are all fine; it is redistribution that is not.

We can suspend or terminate accounts that break this section. Where practical we warn first; for anything that endangers other tenants or the platform we act first and explain after.

5. The Discord bot

• The Licentry bot is part of the Studio plan. One Discord server can be connected per account, by someone who has Manage Server permission there.
• You are responsible for what the bot does in your server with the permissions you grant it: the redeem panel you publish, the role it assigns, the channels it writes logs to.
• Your use of Discord itself is governed by Discord's own Terms of Service and Community Guidelines; the bot does not exempt you from them.
• If your plan lapses, the bot stops serving your server until the subscription is active again.
• We may remove the bot from a server that abuses it or that breaks section 4.
• What the bot collects and stores is described in the Privacy Policy, including how to have that data removed.

6. Your data and your customers

• You own the data you bring: products, licence keys, notes, and your relationship with your customers.
• To run the service we process technical data about your end users on your behalf (hashed device identifiers, IP addresses, session telemetry). Details and retention are in the Privacy Policy.
• You are responsible for your own legal basis and disclosures towards your end users, including telling them that licensing and anti abuse checks are performed by your licensing provider.
• Your source code does not reach us. The plugin runs inside your own AI coding agent, on your own machine, and reads your files there. Whatever it reads goes to whichever AI provider you have that agent configured to use, under the agreement you already have with that provider rather than under this one; we are not a party to it and we receive nothing from it. What reaches Licentry is the plugin fetching our public documentation over HTTPS, which is the same request a browser makes for the same pages. The Privacy Policy says what those requests record and how long it is kept. We do not receive your code, the plan file the plugin writes, or the answers you give its questions.
• The client the plugin writes computes a device hash from identifiers on your customer's machine. The plugin proposes candidates and says which ones hold still across a reboot; which ones you use is your decision, because only you know what your target hardware offers. It is your software that reads them and your binary that ships, so telling your customers what it reads is yours to do rather than ours.
• On the Studio plan we can point your tenant at a PostgreSQL database you control. You are then responsible for that database's availability and backups; the service degrades or stops if it becomes unreachable.

7. Availability and support

We run Licentry with care: hardened hosts, encrypted backups, monitoring. Still, the service is provided without an uptime guarantee. Where we plan maintenance that will interrupt the service, we tell you in the dashboard or by email beforehand; the status page reports what is happening now and carries no scheduled windows. Build your client integrations with the offline grace tokens the API offers so short outages do not lock your users out.

There are two ways to reach support, and the one to prefer is the ticket system in the dashboard, under Support. A ticket arrives attached to your account, so we can already see your plan, your invoices, your products and your recent errors, and you do not have to describe your setup before anyone can help. Ticket messages are encrypted at rest. The subject line is not, because it has to appear in your ticket list and in the mail that tells us you wrote, so keep the subject general and put the detail in the message. Do not paste API keys, passwords or private keys into a ticket: we check for them and refuse the message rather than store it, because we never need one to help you. Everyone on your team can read your tickets, and you can keep a few open at once; the page shows the limit and how many you are using.

[email protected] is the other route, and it is the one that still works when the dashboard does not: write there if you cannot sign in, have lost your two factor device, or the service itself is down. A lapsed subscription closes neither route, and a payment that has not landed is exactly the kind of thing to open a ticket about. We usually answer within one business day and Studio accounts are answered first, but neither of those is a guaranteed response time. Licentry is run by one person on one server, and we would rather you know where that leaves you than read a promise here we cannot keep on a bad week.

An integration the plugin wrote is supported on the same footing as the documentation it was written from: ask us about the platform, about the protocol, and about anything the plugin got wrong, through either of the two routes above. The public repository the plugin is published from is not one of those routes. What we cannot do is take on your product. The code the plugin writes lands in your files, in your version control, and you are the one who ships it, so the plugin having typed it does not move responsibility for it from you to us.

8. Intellectual property

The service. Licentry's own code, design and documentation belong to Licentry. We give you a limited, non exclusive, non transferable right to use them while your account is in good standing. That right ends when your account does, which is the right shape for something you rent and the wrong shape for something you compile into a binary and send to your customers. Hence the next paragraph.

Code we give you to put in your product. This means the sample code in our documentation and everything the plugin writes into your files, together the "generated output". You get a perpetual, irrevocable, worldwide, royalty free, non exclusive licence to use, modify, compile, distribute and sublicense the generated output as part of your own software, and to keep doing every one of those things after your subscription lapses, after you cancel, and after we terminate your account for any reason. That licence survives the end of this contract and we cannot take it back. It has to work that way: generated output is already inside builds sitting on your customers' machines, and a licence that expired with your account would leave you distributing a product you no longer had the right to distribute. Nothing in section 9 or anywhere else in these terms cuts it short. It covers the output and nothing more, so it does not let you republish our documentation, and it does not let you package the generated output on its own and sell it as an integration kit.

Your side. Nothing here transfers any right in your software to us. Running the plugin transfers nothing either: we do not receive your source, and we claim no interest in the files it edits or in the product you build with them. Feedback you send us can be used to improve the service without obligation to you.

The plugin itself. The plugin is a set of instructions and configuration rather than compiled software, and it is published under the Apache License 2.0. That licence, not this section, governs what you may do with the plugin's own files. It is distributed in two places, a public repository anyone can install from and a download in your dashboard, and they are the same plugin. Installing the public copy gives you the plugin and nothing else: no account, and no access to anything behind a sign in, including the hardening guide the plugin points at, which stays tied to a vendor account under section 4.

9. Ending things

• You can stop any time. Cancel from the billing page in the dashboard, or ask support to do it for you. Cancelling stops the next renewal and leaves the period you are in alone: the account keeps working until the period you have already paid for runs out, there is no refund for the part of it you do not use, and after that the account lapses on the terms in section 3, including the 7 days of licence validation your customers get. If you want the account itself deleted rather than left lapsed, ask support, and read the rest of this section first.
• We can terminate or suspend your account for breach of these terms, for legal reasons, or if the service is discontinued. For discontinuation we give at least 30 days notice.
• Export what you want to keep before the account closes. While it is open the dashboard exports your licences as a CSV, in batches of up to 5000 rows; that file covers licence records and nothing else, so it holds no products, invoices, API keys, customers or order history. Deletion runs as a single operation and cannot be undone. There is no holding period after it and no export route once you can no longer sign in. What remains is whatever we must keep for legal or accounting reasons, and the administrative record of the deletion itself.

10. Disclaimers and liability

The service is provided as is and as available. To the extent the law allows, we disclaim implied warranties of merchantability, fitness for a particular purpose and non infringement. Licensing enforcement raises the cost of piracy; no system prevents it entirely, and we do not promise yours will never be bypassed.

That covers the plugin and everything it writes. We do not warrant that generated code is correct, secure or fit for what you are building, and you are the one who reviews it and tests it before it ships, the same as any other change in your repository. A plugin run is not a security audit. The command named audit is a checklist read of source against our published rules, which is a useful thing and a different thing: it certifies nothing, and presenting a plugin run to your customers, to an insurer or to anyone buying your company as an audit or a certification is not something we stand behind. One practical warning as well, because it will otherwise arrive as a support ticket. The plugin drives an AI coding agent that edits real files in your repository. Commit your work before you run it and read the diff afterwards, which is why every command that changes a file lists what it changed and why.

To the extent the law allows, our total liability for all claims in any 12 month period is capped at the fees you paid us in those 12 months, and neither side is liable for indirect, incidental or consequential damages, or for lost profits, revenue or data. Nothing in these terms limits liability that cannot be limited by law.

11. Changes and contact

We can update these terms as the service evolves. For material changes we notify you in the dashboard or by email at least 14 days before they apply; continuing to use the service after that means you accept them. The date at the top always tells you the current version.

These terms are governed by Swedish law, and disputes belong to the Swedish courts. If you are a consumer, that does not take away the protection of the mandatory consumer law of the country you live in, and you can bring a claim in the courts there.

Questions about these terms: [email protected].

12. Who you are contracting with

Licentry is run from Sweden by a private individual. No business is registered behind it yet: there is no company, no organisationsnummer and no VAT registration. That is why nothing here is for sale. The service is in a demo state, accounts and the free trial work, and no plan can be bought. A business is registered before anything goes on sale, and the entries below that do not exist today are published here at that point.

• Trading as. Licentry, at licentry.cc.
• Contact. [email protected], which reaches a person, and which is also where complaints go.
• Legal form. None yet. Until a business is registered, whoever operates licentry.cc does so personally.
• Registered name and address. Do not exist yet. Published here when the business is registered.
• Registration number. Does not exist yet. The organisationsnummer is published here when the business is registered.
• VAT number. Does not exist yet. The momsregistreringsnummer is published here when VAT registration exists. No VAT is charged in the meantime, because nothing is sold.

lag (2002:562) om elektronisk handel, 8 §, requires a trader to keep details of this kind easy for you to find, and this page is where Licentry keeps them. The contact address and the name the service trades under exist today and are above. The rest come into existence with the registration, and they are added here in the same change that puts anything on sale, so that this page never describes a business that can take your money before it says who it is.