LegalTerms of Service
Effective 20 October 2026. These terms are a contract between you and Licentry ("Licentry", "we", "us"), the trader described in section 12, for the use of licentry.cc, the Licentry dashboard, the Licentry API, the Licentry Discord bot and the Licentry integration plugin (together, "the service"). You accept them by creating an account or by using any part of the service. You can install the plugin without an account. That installation is governed by its published licence, not this contract. These terms apply to the plugin once you have an account, which is required to use its functionality. If you use Licentry for a company, you confirm you can bind that company, and "you" means the company.
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 licensing infrastructure. 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") for your own AI coding agent. It reads our current documentation and your source code, asks for information it cannot find in your code, then writes client code into your files. Because that code becomes part of the product you ship, its licence differs from your right to use the hosted service. Section 8 sets out both.
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 use. Do not create accounts to avoid 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 until you cancel it, keeping your licensing active. You can cancel at any time with one action in the dashboard. This stops the next renewal; access continues until the end of the period you have already paid for, with no refund for the unused part.
- Stripe only. Every payment goes through Stripe, our payment provider, on a checkout opened from your dashboard. We do not accept cryptocurrency sent to us directly, and no invoice of ours asks you to send funds to a wallet address.
- Card charges and disputes. A card charge can be reversed by your bank. 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 issued to your customers keep validating for 7 days from suspension, then stop. This is the same limited grace period that applies to a lapsed subscription, giving your customers time before their software is affected without providing continued unpaid licensing. 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. This gives your customers time before their software is affected by a failed renewal. It is a limited grace period, not a free tier; licence checks still cost us the same to serve.
- 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 that requires a vendor sign in. This includes the hardening guide, which describes what Licentry detects, the tolerances of its protections and how each control can be defeated. Publishing it would expose that information to attackers. The plugin cannot fetch the guide and asks you to save a local copy. Keep that copy out of version control and anything you publish. You may read it, quote it to your own team or paste it into your agent, but you may not redistribute it.
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 in your AI coding agent on your machine and reads your files there. The source it reads goes to the AI provider configured in your agent, under your agreement with that provider. We are not a party to that agreement and receive nothing from the provider. The plugin sends Licentry HTTPS requests for public documentation, identical to a browser's requests for those pages. The Privacy Policy describes the request logs and their retention. We do not receive your code, the plugin's plan file or your answers to its questions.
- The client the plugin writes computes a device hash from identifiers on your customer's machine. The plugin suggests identifiers and describes which remain stable across reboots. You choose which to use based on the target hardware. You are responsible for telling your customers which identifiers your software reads.
- Two optional features collect more from your customers' machines, and using them is your decision: tamper reports that carry a screenshot, and the Licentry desktop loader, whose full list of fields is in the Privacy Policy. If you use either, tell your customers what is collected, and get any consent the law where they live requires before your software reads information from their device. Both are delivered to you, through the webhooks you set up. We do not keep a screenshot, and we keep the rest only as the Privacy Policy states.
- 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.
The preferred way to contact support is through Support in the dashboard. Tickets are linked to your account, so we can see your plan, invoices, products and recent errors without asking you to describe your setup. Ticket messages are encrypted at rest. Subject lines are not encrypted because they appear in your ticket list and in email notifications, so keep the subject general and put details in the message. Do not paste API keys, passwords or private keys into a ticket. We do not need them to help you, and we check for them and reject messages containing them rather than store them. Everyone on your team can read your tickets. You can have a few tickets open at once; the page shows the limit and how many you are using.
Email [email protected] if you cannot sign in, have lost your two factor device, or the service is down. Both support routes remain open if your subscription lapses, including for questions about a payment that has not arrived. We usually answer within one business day and give Studio accounts priority, but neither is a guaranteed response time. Licentry is run by one person on one server.
Support for plugin-generated integrations is the same as for our documentation. Use either support route above for questions about the platform or protocol, or errors in the plugin's output. The plugin's public repository is not a support channel. You remain responsible for your product and the generated code you ship from your files and version control; using the plugin does not transfer that responsibility 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 ends. The separate licence below applies to code you include in your product.
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. The continuing licence lets you distribute builds containing generated output after your account ends. 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 cancel at any time from the dashboard billing page or by asking support. Cancellation stops the next renewal. The account keeps working until the end of the period you have already paid for, with no refund for the unused part. It then lapses under section 3, including the 7 days of licence validation for your customers. To delete the account rather than leave it lapsed, ask support after reading the rest of this section.
- 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 your product. You must review and test it before shipping, as with any other change in your repository. A plugin run is not a security audit. Its audit command checks source against our published rules and provides no certification. We do not endorse presenting a plugin run as an audit or certification to customers, insurers or prospective buyers of your company. The plugin uses an AI coding agent that edits real files in your repository. Commit your work before running it and read the diff afterwards. Each command that changes files 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.