Legal
Licence terms (EULA)
Version 1.1, effective 5 October 2026.
1. About these licence terms
These licence terms govern your use of the Pro editions of PIM Manager and SecurityInsight, including Pro trials. The licensor is 2linkIT ApS, Strandvejen 21A, 6000 Kolding, Denmark, VAT DK39208032 (“Invardia”, “we”, “us”). Invardia is a brand of 2linkIT ApS. “You” means the company named in the order or licence file.
These terms apply together with our Terms of sale and, where we handle personal data on your behalf, our Data processing agreement. By installing, activating or using Pro, you accept these terms on behalf of your company.
“Software” means the Pro edition of the product, its updates, scripts, templates and documentation that we provide to you. “Tenant” means a Microsoft Entra ID tenant, identified by its tenant id.
2. Community and Pro
The Community editions are free and published on GitHub under their own licences: SecurityInsight Community (from version 3.0) under the PolyForm Shield 1.0.0 licence, and PIM Manager Community under its own Open Core licence. These licence terms do not govern Community. Community is governed only by the licence in its GitHub repository.
The Pro editions are paid, licensed per Microsoft tenant, and governed by these terms. PIM Manager is also available as Pro MSP, for service providers that manage their customers’ tenants.
3. Licence grant
For the term of your subscription and subject to payment, we grant you a non-exclusive, non-transferable, non-sublicensable right to install and use the Software:
- only in the Microsoft tenants named in your licence file;
- for your internal business purposes; and
- for Pro MSP: also to manage the tenants of your own customers that are named in your licence file, as part of services you provide to them. You are responsible for having your customers’ authority to do so and for your customers’ compliance with these terms.
You may make the copies you reasonably need to install, run, test and back up the Software within those tenants. All rights not expressly granted are reserved by us.
A trial licence gives the same rights for the trial period stated in the trial licence file, for evaluation only.
4. The licence file and tenant binding
Pro is activated by a signed licence file. The licence file names the product, edition, term and the tenant id(s) it covers.
- The product checks the licence file offline, inside your environment. It does not need to contact us to start.
- A licence file works only in the tenants it names. A licence file that names no tenant is not valid.
- You must not copy or use a licence file in any tenant it does not name, alter a licence file, or share it with anyone outside your company (or, for Pro MSP, outside the customers it covers).
If you need to move a licence to another tenant, contact us as described in the Terms of sale.
5. Restrictions
You must not:
- reverse engineer, decompile or disassemble the Software, except to the extent the law expressly permits this despite this restriction;
- circumvent, disable or interfere with the licence check, the signature verification of licence files or updates, or any other technical protection;
- sell, rent, lend, redistribute, publish or sublicense the Software, or offer it as a hosted service to third parties (other than Pro MSP use as permitted in section 3);
- remove or alter copyright notices or licence information; or
- use the Software in breach of applicable law, including sanctions and export control rules.
6. Your environment and your responsibilities
The Software runs in your own environment. You install it into your own Microsoft Azure subscription and tenant (for example in Azure Container Apps or on a virtual machine), and it runs under your control with your own identities. We do not host the Software and, in normal operation, we do not receive or process your security, directory or vulnerability data.
You are responsible for:
- Azure costs: Microsoft bills you directly for the Azure resources the Software uses.
- Identities and permissions: the managed identity (preferred) or service principal with certificate that the Software uses, and the permissions you grant it. Grant only the permissions the documentation describes for the features you use.
- Data: you are the controller of all data the Software processes in your environment, and you decide what it collects, how long it is kept and who can see it.
- Backups and security of your environment, including access to the Software’s resources, storage and secrets.
- Testing and decisions: PIM Manager can change privileged access in your tenants, and SecurityInsight produces risk scores and findings. Test changes before you roll them out broadly and check results before you act on them.
7. Remote support access
Pro support is provided through tickets in the customer portal and by email. If you want hands-on help, you can give us access to your environment in a way you own and control:
- You create the app registration. You create an “Invardia Support” app registration in your own tenant, using the script we publish. You own it.
- You decide the permissions. You choose the level: Troubleshoot (read-only) or Setup (broader, for deployments). You can restrict it further, for example with a Conditional Access policy that allows sign-in only from our published support IP address.
- You store a short-lived secret with us. You enter a client secret in the customer portal. It is stored encrypted in our Azure Key Vault, is never shown again and is never stored in a database. The secret lifetime is 90 days by default, or 1 day for a one-off setup.
- Renewal needs your approval. Before the secret expires we send you up to three reminder emails. If you do not approve renewal, the secret is not renewed and our access ends.
- You can withdraw access at any time by disabling or deleting the app registration in your tenant, removing its secret, or removing the registration in the customer portal.
We connect only when you have asked for help, only to the environment you named, and only from our support host. Every change to your environment registration is emailed to you. While we work in your environment we act as your processor under the Data processing agreement, and we access only what is needed for the support case. More detail is on our remote access page.
8. Updates
Pro updates are delivered through our update platform. Each update is signed, and the Software verifies the signature before it is applied. You control when updates roll out in your environment. We release updates in rings (0 development, 1 internal test, 2 design partners, 3 broad availability); pre-release versions you choose to install before broad availability are provided as they are, for testing.
We are not obliged to release any particular feature. Which versions we support is described in the documentation; to receive support you may need to install a recent update. Community updates are published on GitHub.
9. Telemetry and licence requests
Licence requests. The Software can request and renew its licence from us automatically. It then sends only its tenant id, product version and an install id (and, for renewal checks, its current licence file). We approve new tenants manually; renewals are approved automatically when a valid licence already exists.
Status telemetry. Pro installs send identified status reports to us: product, version, edition, update ring, job outcomes, error class, error text (with secrets redacted) and counts as numbers. They are tied to your environment through an install key. We use them for product health, release quality and proactive support.
Telemetry never contains your security findings, directory objects, user lists or credentials. Known secret patterns are redacted before storage. We keep error text for 90 days and report rows for 13 months.
Opt-out. You can switch telemetry off at any time in the product settings. The Software then sends one final “opt-out” notice so that we know the silence is intentional, and nothing more after that. Licence requests are not telemetry and continue if you use automatic licence renewal; you can instead install licence files manually.
Community installs send telemetry anonymously (a random install id; no tenant, host name, user or error text), on by default with opt-out. This is governed by the Community licence and documentation.
10. Intellectual property
The Software and all intellectual property rights in it belong to 2linkIT ApS or its licensors. You receive only the rights in section 3. Your data remains yours. If you send us suggestions or feedback, we may use them freely without obligation to you.
The Software may include open-source components that are licensed under their own licences, which are listed in the Software or its documentation. Those licences apply to those components.
11. Warranty
We warrant that, during your paid subscription, the Software will perform materially as described in its documentation when installed and used as documented. If it does not, tell us, and we will at our option correct the defect, provide a workaround or, if we cannot do so within a reasonable time, let you terminate the affected licence and refund the prepaid fees for the remaining full months. This is your only remedy for a defect.
Beyond this warranty, the Software is provided “as is”. We do not warrant that it is error-free, that it will run without interruption, that it will detect every risk or vulnerability, or that it meets requirements not stated in the documentation. Trials and pre-release versions are provided as they are, without any warranty, to the extent the law allows.
12. Intellectual property claims
If a third party claims that your use of the Software as permitted by these terms infringes its intellectual property rights, we will handle the claim at our cost, provided you notify us promptly, let us control the defence and cooperate reasonably. We may modify or replace the Software so that it no longer infringes, obtain a right for you to continue, or terminate the licence and refund the prepaid fees for the remaining full months. This does not apply to claims caused by your modifications, combinations with other products, or use in breach of these terms.
13. Liability
The limitations of liability in section 12 of the Terms of sale apply to these licence terms. In short: no liability for indirect or consequential loss, and total liability capped at the fees paid in the 12 months before the claim, except where the law does not allow liability to be limited.
14. Term and what happens at the end
The licence runs for the term in your order or licence file, and ends when the subscription ends or the agreement is terminated.
When the licence ends:
- the Pro features keep working for a 30-day grace period after the licence ends and then stop;
- you stop receiving Pro updates and support;
- your data stays in your environment, under your control. We do not hold it and cannot delete it. You decide whether to keep, export or delete it, or to remove the Software and its Azure resources; and
- you should delete or disable the “Invardia Support” app registration if you have not already done so. We purge your support secrets from our Key Vault when the registration is removed or the agreement ends.
Sections 5, 10, 13 and 16 continue to apply after the licence ends.
15. Sanctions and export control
You and we will comply with applicable sanctions and export control laws. You must not use, export or make the Software available in breach of those laws, including to persons, entities or countries subject to sanctions. We may refuse orders, licence requests or support where providing them would breach such laws.
16. Governing law and disputes
These terms are governed by Danish law, excluding its choice-of-law rules. Disputes are settled by the Danish courts, with the District Court in Kolding as the court of first instance.
17. Contact
- Support: support@invardia.com
- Sales and licensing: sales@invardia.com
- General: info@invardia.com