Acceptable Use Policy

IntelliJ.ONLINE builds and runs code on shared servers. This policy keeps the Service safe, fair and available for everyone. It is part of the Terms of Service and applies to your account, Your Content, your Programs and everything you send through the Service, including support tickets.

1. 2.1.1

   writing, building, running, testing and debugging your own software;

2. 2.1.2

   learning, teaching, coursework, experiments, interviews and professional work;

3. 2.1.3

   downloading open-source dependencies through Maven or Gradle from public package repositories;

4. 2.1.4

   testing the security of your own account and projects, within the rules of the Security Policy.

Do not:

1. 3.1.1

   try to escape, disable, probe or weaken the isolated environment, or read anything outside your own project and caches;

2. 3.1.2

   access or try to access other users' accounts, projects, sessions or data, or the Service's own files, keys, database or administration area;

3. 3.1.3

   attack, exploit, overload or disrupt the Service, its addresses, its providers or its infrastructure;

4. 3.1.4

   reverse engineer, replay, forge or automate the Service's encrypted requests, or get around rate limits, cooldowns or origin checks;

5. 3.1.5

   pass off blocked JVM options, environment variables, agents or native libraries to change how Programs are isolated.

Programs have no internet access, and build tools may reach only public package repositories — the well-known ones and those declared in your build files.

Do not:

1. 4.2.1

   try to reach the internet, the host machine, private networks or other projects from a Program;

2. 4.2.2

   use build tools or the package proxy for anything other than downloading build dependencies, for example to tunnel traffic, fetch unrelated content or send data out;

3. 4.2.3

   scan, attack, flood or stress any system, or test systems you are not authorised to test.

Do not:

1. 5.1.1

   run or attempt to run servers, web applications, APIs, open ports, proxies, VPNs, relays, bots or anything that waits for incoming connections;

2. 5.1.2

   use the Service as file storage, a content-delivery network, a download mirror or a place to host or share files with others;

3. 5.1.3

   mine cryptocurrency, run fork bombs, or start workloads designed to consume CPU, memory, storage or output rather than to build or test your software;

4. 5.1.4

   fill storage, create files or projects in bulk, or split work across accounts to get around limits.

Do not:

1. 6.1.1

   create more than one account, create accounts in bulk or by automated means, or create a new account after a block or closure;

2. 6.1.2

   share, sell, rent or transfer accounts, or use someone else's account;

3. 6.1.3

   use bots, scripts or other automated means to operate the Service instead of its user interface;

4. 6.1.4

   impersonate another person, IntelliJ.ONLINE, our staff or a "Support Agent", or JetBrains or any other company.

Do not create, upload, store, run or send:

1. 7.1.1

   malware, ransomware, spyware, exploit kits, credential stealers or tools whose main purpose is unauthorised access;

2. 7.1.2

   phishing material, including pages or code that imitate the sign-in of another service, and anything designed to collect other people's credentials;

3. 7.1.3

   spam, fraud, scams or deceptive content;

4. 7.1.4

   material that infringes copyright, trademarks or other rights, including pirated software, cracks and key generators;

5. 7.1.5

   personal data of other people without a lawful basis, or secrets that are not yours;

6. 7.1.6

   content that is illegal, harassing, threatening, hateful, or that sexualises or exploits minors.

Use tickets only for genuine questions, reports and suggestions. Do not send spam, abusive or threatening messages, malicious attachments or deliberately false reports, and do not open tickets to flood or test the support system.

Do not use the Service in breach of applicable law, sanctions or export-control rules, or for anyone who is not allowed to receive it.

The isolated environment blocks many prohibited actions automatically and records them in a sandbox log. Administrators may review these records and the related projects, as described in the Terms of Service.

Depending on how serious a case is, we may, immediately and without prior notice:

1. 10.2.1

   stop a Program or build, or refuse to start it;

2. 10.2.2

   remove or disable content, clear build output or close tickets;

3. 10.2.3

   limit features, storage or runs for the account;

4. 10.2.4

   block the account — a blocked account sees a notice and cannot use the Service;

5. 10.2.5

   close the account and delete its data;

6. 10.2.6

   report illegal activity to the competent authorities and cooperate with lawful requests.

We decide whether a use breaks this policy. Enforcement does not limit any other rights we have under the Agreement. If you believe an action was a mistake, tell us through Contact Support.

Report abuse, suspected phishing in our name or content that breaks this policy through Contact Support. Include what you saw, where and when.