Acceptable Use Policy.
Kantrix runs your workloads on hardware you control and connects it to a portal we run. This policy sets out what neither part may be used for, so the platform stays safe for every partner and customer on it.
Who this policy applies to
This Acceptable Use Policy ("Policy") is part of the Terms of Service. It applies to everyone who uses Kantrix: customers, partners, the clients partners serve, and each of their users. Capitalized words have the meanings given in the Terms.
If you are a partner, you are responsible for your clients' use of Kantrix as well as your own. Your agreements with your clients must require them to follow this Policy.
Your own workloads
What you run in virtual machines and containers on your nodes is yours. We don't inspect it, and Kantrix staff cannot open a console or shell on your nodes. You remain responsible for it, and you must not use any part of Kantrix to do the things listed below. That includes cloud nodes, apps from Hub, the cloud witness, and every connection through the control plane.
What you must not do
Break the law or harm others
- Use Kantrix in breach of any law that applies to you, including export control and sanctions, privacy, anti-spam and consumer protection laws.
- Store, run or distribute malware, ransomware or other code built to damage systems or gain unauthorized access. Security research on systems you own, or are authorized to test, in an environment isolated from other people's systems is allowed.
- Attack, scan, probe or disrupt any system you are not authorized to test, or run botnets, command-and-control servers or denial-of-service attacks.
- Send spam, or send or host phishing, fraud or identity theft.
- Store or distribute child sexual abuse material, or content that incites violence against people.
- Infringe or misappropriate anyone's intellectual property, or collect or process personal information without a lawful basis to do so.
Abuse the platform
- Get into, or try to get into, any account, organization, client, site, node or data you have not been given access to.
- Bypass or interfere with the controls that keep customers apart, check roles, count nodes, expire API tokens, verify signed releases or record the activity log.
- Modify node software to defeat its signature checks, or connect modified node software to the control plane.
- Place an unreasonable load on the control plane, including by sending automated requests faster than our documentation allows.
- Scrape the portal or our websites, or create accounts by automated means or with false details.
- Open several free accounts, or split one organization across accounts, to get past Kantrix Community's limits.
- Share a sign-in between people, or give an API token to anyone who isn't entitled to the access it carries.
- Reverse engineer the Services, except where the law allows it despite this restriction, or use them to build a competing product.
- Remove or alter Kantrix's notices of ownership, except where the Services let a partner apply its own brand.
Misuse AI features
- Use the assistant, or any other feature built on an AI model, to create content that breaks this Policy, or try to get around the safeguards we or our model providers put in place.
- Put personal information into the assistant that you have no right to share with us for that purpose.
Misrepresent Kantrix
- Claim to be Kantrix, or make commitments on our behalf.
- Describe Kantrix's security, certifications or service levels in a way our published documents don't support. For example, Kantrix does not yet hold a SOC 2 report; see our Security Policy.
Security research
We welcome good-faith security research. You may test Kantrix for vulnerabilities if you:
- test only accounts, organizations and nodes that you own or have written permission to test;
- stop as soon as you reach anyone else's data, and don't keep, share or change it;
- don't degrade the Services for anyone else: no denial-of-service or load testing, no social engineering of our staff, partners or customers, and no physical attacks;
- report what you find to security@kantrix.io with enough detail to reproduce it, and give us reasonable time to fix it before you tell anyone else.
Research that follows these rules is not a breach of this Policy or of the Terms, and we will not bring a legal claim against you for it.
Reporting misuse
If you believe someone is using Kantrix in breach of this Policy, email abuse@kantrix.io. Tell us what you saw, where and when. For a security vulnerability, use security@kantrix.io instead.
What we may do
We act in proportion to the harm. Depending on how serious the breach is and whether it has happened before, we may:
- ask you to stop, and give you time to put it right;
- remove a user's access or revoke an API token;
- suspend all or part of the Services;
- end your agreement, as the Terms allow;
- report the matter to law enforcement, where we believe someone's safety is at risk or the law requires it.
Where it is lawful and safe, we will tell you before we act and explain why. Any suspension will be limited to what is needed to stop the harm. Where we can, it will cover the portal and API rather than the workloads already running on your nodes.
Changes to this policy
We may update this Policy as Kantrix and the law change. We will give at least 30 days' notice of a material change, by email or in the portal, unless the change is needed sooner for legal or security reasons. The date at the top shows when it last changed.
Contact
Questions about this Policy: legal@kantrix.io.