← All legal documents

Acceptable Use Policy

Last updated 2026-09-13 · Version 2026-09-13.1

Effective date: 13 September 2026 Provider: Kanabe Aron Persoană Fizică Autorizată Address: 692, Sânsimion, Harghita 537285, Romania Tax identification code (CIF): 42879844 Trade Register No.: F19/359/2020 VAT identification number: RO42972799 Email: [email protected]

This Acceptable Use Policy forms part of our Terms of Service. It applies to everything you run on our infrastructure, on both free and paid plans.

Why this policy exists. When you submit a solution, we build and execute your code on our servers. That is an unusual amount of trust to extend, and it only works if everyone uses it for what it is meant for: solving coding challenges. This policy draws the line.

This policy covers code that runs on our infrastructure. Our command-line tool runs on your machine and carries different risks — those are covered separately in the CLI Runner Terms and Risk Disclosure.

1. What the platform is for

Writing, building, testing, and evaluating solutions to the coding challenges we publish. Anything meaningfully outside that purpose is likely a breach of this policy, whether or not it appears below.

2. Prohibited — security and isolation

The following will result in immediate termination without refund, and may be reported to the authorities.

  • Attempting to escape, break out of, bypass, or probe the execution sandbox, or otherwise interfere with the isolation of code execution.
  • Attempting to reach our internal infrastructure from inside a submission — including the container registry, the queue and cache, the Kubernetes API, cloud metadata endpoints, or any internal network address.
  • Accessing, attacking, or attempting to access other users' data, accounts, or submissions.
  • Attempting to obtain credentials, tokens, signing secrets, or environment variables belonging to us or to other users.
  • Uploading, running, or distributing malware, viruses, ransomware, or other malicious code.
  • Security testing, penetration testing, vulnerability scanning, or red-teaming of the Service without our prior written permission. Request permission at [email protected] before you begin.
  • Interfering with, disrupting, or degrading the Service or anyone else's use of it.

Reporting a vulnerability is welcome and is not a breach of this policy — provided you stop at the point of discovery, do not access other users' data, do not exfiltrate or destroy anything, and tell us promptly at [email protected]. We will not pursue you for a good-faith report made on those terms.

3. Prohibited — abuse of compute resources

We give every user a share of finite, paid-for compute. Do not take more than your share.

  • Cryptocurrency mining, distributed computing, or any workload whose purpose is to consume compute rather than solve a challenge.
  • Running persistent or long-running services — servers, daemons, bots, schedulers — beyond what a challenge requires. Submissions are for building and testing, and are terminated when they exceed their time limit.
  • Using a submission container as a proxy, VPN, tunnel, relay, scraper, or exit node, or to send traffic to third parties.
  • Sending spam, bulk email, or unsolicited messages of any kind.
  • Denial-of-service attacks, flooding, or load generation against us or anyone else.
  • Deliberately triggering excessive resource consumption — fork bombs, unbounded memory allocation, filling disk — whether to disrupt the Service or to see what happens.
  • Circumventing usage limits: creating multiple accounts, sharing accounts, automating signups, abusing invitations or free trials, or otherwise obtaining more submissions than your plan allows.
  • Automating or scripting the Service in ways not offered through our API or CLI tool, including scraping challenges or test cases.

4. Prohibited — content and conduct

  • Uploading illegal content, or content infringing intellectual-property, privacy, or other rights.
  • Submitting code you do not have the rights to submit — including proprietary or confidential code belonging to an employer or client.
  • Uploading personal data about other people.
  • Using free-text fields — display name, submission notes, cancellation feedback — for abusive, harassing, hateful, or unlawful content.
  • Impersonating another person or misrepresenting your affiliation.
  • Reselling, sublicensing, or commercially exploiting the Service or its compute resources.
  • Reverse-engineering, decompiling, or attempting to extract source code or non-public components of the Service, except where that restriction is prohibited by law.
  • Republishing or redistributing our challenges or test cases.
  • Any unlawful, fraudulent, or deliberately harmful use.

This list is illustrative, not exhaustive. Conduct that clearly falls outside the purpose in Section 1 can breach this policy even if it is not listed.

5. Technical limits

These limits are enforced automatically. Working within them is not a breach; deliberately engineering around them is.

  • Monthly submission quota — set by your plan and shown on your profile. Submissions are refused once it is exhausted.
  • Execution time limits — submissions that exceed their deadline are terminated.
  • Memory limits — submissions exceeding them are terminated.
  • Concurrency limits — how many submissions run at once is capped per tier; paid submissions are prioritised.
  • Upload limits — submissions must be valid archives within the size limit.

We may change these limits at any time, and may apply temporary restrictions to protect the Service.

6. Your own machine

Our CLI tool executes build and test definitions that we supply on your computer, including running Docker containers. You are responsible for the machine you run it on and for deciding whether to trust what it executes. See the CLI Runner Terms and Risk Disclosure before installing it.

7. What happens if you breach this policy

We respond proportionately to what we find. Depending on severity we may:

  1. Warn you and ask you to stop;
  2. Restrict or freeze your quota, or throttle your submissions;
  3. Suspend your account pending investigation;
  4. Terminate your account and delete all associated data;
  5. Report unlawful activity to the relevant authorities.

For Section 2 breaches — security and isolation — we will normally go straight to step 4 or 5, with no warning.

As set out in the Terms of Service, termination for breach is without refund, and this applies to paid accounts. We are not obliged to warn you first, though we generally will where the risk is low and the breach looks accidental.

If you believe we acted in error, email [email protected] and we will review it.

8. Reporting abuse

To report abuse, illegal content, or an infringement of your rights, email [email protected] with enough detail to identify the content or account. We investigate every report we can act on.

9. Changes

We may update this policy as the Service changes or new forms of abuse appear. The version and date at the top of this page reflect the current version, and material changes are notified as described in the Terms of Service.