Acceptable Use Policy

Effective Date: September 4, 2026  |  Last Updated: September 4, 2026

This policy says what you may and may not do on Revquix. It forms part of our Terms of Service and is incorporated into them by reference, so breaking a rule here is breaking the Terms.

It applies to everyone: visitors, members, mentors and business clients. Mentors are additionally bound by the Mentor Code of Conduct, and everything published or posted is additionally subject to our Community Guidelines.

1. The general rules

Do not use Revquix to:

• Break the law, or help anyone else break it.
• Post, host or transmit content you do not have the right to use, or that infringes someone else's copyright, trademark, privacy or other rights.
• Harass, threaten, defame or impersonate anyone - including impersonating Revquix, our staff, or a mentor.
• Send spam, chain messages, or unsolicited advertising.
• Upload or distribute malware, or anything designed to damage or gain unauthorised access to a computer system.
• Probe, scan or test the security of the Platform, or try to get at data that is not yours.
• Interfere with the Platform's operation, or with anyone else's use of it.

If you are a security researcher and believe you have found a vulnerability, we would rather hear about it than not: write to [email protected] with the details and give us a reasonable chance to fix it before disclosing it. Testing in good faith, reported responsibly, is not what the bullet above is aimed at.

2. Running code on our infrastructure

The Playground, Projects and the coding problems all execute code you write. That code runs on servers Revquix operates, inside a sandbox, sharing capacity with everyone else using the Platform at that moment. This section is the part of this policy most likely to be new to you, so it is the longest.

2.1 What the sandbox already prevents

Some things are not rules you are asked to follow - they are simply not possible, and we would rather tell you than have you wonder:

• Your program has no network access. The runner is started with networking disabled and sits on an isolated internal network with nothing published to the internet. A program cannot call out, fetch a URL, scan a host, or be used as a proxy. This is a property of how the sandbox is built, not a filter we apply to your code.
• Your program cannot see anyone else's. Each run is isolated, gets a wall-clock and CPU budget measured in seconds, and is capped on memory, processes, open files and output size.
• Nothing persists between runs. The sandbox is not storage. Your files live in your project; the runner starts clean.

2.2 What you must not do

• Mine cryptocurrency, or run proof-of-work, distributed-computing or rented-compute workloads of any kind. The runner exists for learning and for building; it is not a compute service.
• Attempt to escape the sandbox, reach the host, reach our internal network, or read another user's data.
• Deliberately exhaust shared capacity - fork bombs, infinite allocation, or running the maximum permitted jobs continuously in order to degrade the service for other people. Hitting a limit while genuinely learning is fine and expected; that is what limits are for.
• Drive the runner from a script. Runs are for a person at a keyboard. Automating them, or coordinating accounts to multiply an allowance, is a breach.
• Use project storage as a file host. Projects hold the code and assets of a project. They are not a place to park archives, media libraries, backups, or material unrelated to what you are building.
• Run or store anything unlawful, including code whose purpose is to attack a system you do not own.

2.3 Quotas

Runs, saved snippets, project count, file sizes and canvas size are all capped. The current numbers are shown in the product rather than written here, so that what you read is what is actually in force. We may change them, and we may apply a lower limit to an account we believe is abusing the service.

Exceeding a quota is not a breach of this policy - the limit simply stops you until it resets. Deliberately working around one is.

3. What you store and share

Projects, canvases, snippets, uploads and profile media are yours, and the rules in Section 1 apply to all of them. Two additional points:

• Public means public. If you move a project, canvas or snippet to a shared link or to public, anyone holding the link can open it, and a public item can also be found, copied, exported and indexed by search engines. Do not put anything there you would not put on a public web page.
• Do not upload other people's personal data. A resume you were sent, a client database, a spreadsheet of contacts - these belong to the people in them, and Revquix is not the place to process them.

4. Automated access

• Do not scrape, crawl, harvest or bulk-download profiles, mentor listings, articles, documentation or problems, and do not build a database or a competing product out of them.
• Do not use the Platform through anything other than our own interfaces, except where we have given you written permission.
• Do not circumvent, disable or interfere with our bot checks, rate limits, quotas or free-usage allowances - including by creating multiple accounts to obtain more of something than one account is given.

5. AI features

Our AI Policy explains what the AI features do with what you give them. For the purposes of this policy:

• Do not use the AI features to produce content that would breach Section 1 if you wrote it yourself.
• Do not attempt to manipulate a prompt in order to extract our instructions, another user's data, or behaviour we have not offered.
• Do not use generated text to misrepresent your experience or identity to an employer. Our tools are there to help you present what is true about you more clearly, not to invent it - and we do not invent numbers in your bullets.
• Do not resell, redistribute or wrap our AI features as a service of your own.

6. Marketplace conduct

• Keep the transaction on Revquix. Do not ask for, or offer, payment outside the Platform for a service you found here. Messages are automatically screened for payment handles and links for this reason, and it is not only a rule about our fee: a payment taken off-platform leaves the buyer with no refund right and no dispute process.
• Do not use another member's contact details for anything other than the session or order that put you in touch.
• Do not leave, solicit or trade dishonest reviews. See our Community Guidelines.

7. What happens if you break this policy

We aim for the smallest response that fixes the problem. Depending on what happened and whether it looks deliberate, we may:

• Contact you and ask you to stop.
• Remove or unpublish the content in question.
• Reduce a limit, or withdraw access to a single feature, while leaving the rest of your account working.
• Hold, reverse or refuse credits obtained through the conduct - see Credits & Referrals.
• Suspend or close the account.
• Report the matter to the authorities where the law requires it or the conduct warrants it.

For anything short of an immediate safety or security risk, we will normally tell you what happened and why. If you think we got it wrong, reply to us or write to [email protected] and a person will look at it again.

8. Telling us about a problem

To report content or conduct that breaches this policy, email [email protected] with a link and a short description, or open a support request from your dashboard. This is also the route for a grievance under the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021 - our Grievance Officer and the response times we commit to are in Privacy Policy §10.

9. Changes

We may update this policy as the Platform changes. We will revise the “Last Updated” date, and material changes will be notified in-product or by email.