Reqursor Development Acceptable Use Policy

1. About this policy

This policy sets the rules for using Reqursor Development, the self-hosted AI development agent made by Reqursor Technologies ("Reqursor", "we", "us"), and the license portal at license.reqursor.com. It is part of the Terms of Service and applies to your business. You must make sure that everyone you give access to, such as team members, contractors and anyone who uses an API token you created, follows it, and you are responsible for their use as for your own.

Reqursor Development runs on your own infrastructure. You decide what it works on and what it can reach, so you are responsible for how it is used. This policy tells you where the limits are.

2. Use it lawfully

You must use Reqursor Development in line with the law that applies to you and to us. You must have the right to give the agent the code, tickets and data you give it, and the right to change the repositories and systems you connect.

Do not use Reqursor Development to:

• infringe someone's intellectual property rights or copy code you are not allowed to copy or reuse
• process personal data without a legal basis or break confidentiality duties you owe to others
• break export control, sanctions or other trade rules

3. Do not use it to cause harm

Do not use Reqursor Development, or ask the agent, to create, change or deploy anything whose purpose is to:

• build or spread malware, ransomware, spyware or other malicious code
• attack, probe, disrupt or gain access to systems, networks or accounts you do not own and have no written permission to test
• steal credentials, defraud people, send spam or run phishing or other deceptive schemes
• track, harass, stalk or discriminate against people, or collect data about people unlawfully
• cause serious physical harm or build weapons

Authorized security work is allowed. Writing tests, hardening your own code, fixing vulnerabilities and testing systems you are permitted to test are normal uses.

4. Protect your systems and your access

You must use the controls the product gives you responsibly:

• Give the agent only the repositories, credentials and network access it needs for the tickets you want done.
• Do not point it at production systems, customer data or secrets it does not need.
• Keep protected branches, protected paths and approval settings switched on where your risk calls for them.
• Run the software on a host you control. Do not run it on shared or public build runners where other people can see your code.
• Do not turn off or work around the protections of the software, such as its secret scan or its git policy, to put other people's data at risk. Running without isolation is your choice under the Terms of Service, and you accept its risks.

You are responsible for the actions of the agent on your systems, as if you had taken them yourself.

5. Tickets, content and model providers

Everything you send to a model provider through Reqursor Development is also governed by that provider's usage policy and terms. Their rules apply on top of this policy. In particular:

• Do not put content in tickets or code that you may not lawfully send to a model provider.
• Do not try to get the model to ignore its provider's safety rules, for example by hiding instructions in tickets, repositories or web content.
• Treat tickets from people outside your team as untrusted. Reqursor Development marks ticket text as external content and logs suspicious instructions, but this is a safeguard, not a guarantee.

The AI Usage Policy explains how the AI is used and where your data goes.

6. Respect the license

Do not:

• share a seat, a login, a password or an API token between people
• exceed the seats, projects and features of your plan
• remove, disable, bypass, patch, forge or replay the license checks, the license token or the daily check, or send false license data
• install the software on more instances than you license
• use our relay or your Reqursor Credits in any other way than through Reqursor Development, resell or share credits, or try to get around the request limits, spending limits or checks of the relay
• sell, rent, lend, sublicense or host the software for others, or use it to run a service for others
• reverse engineer, decompile or disassemble the software, except where the law says this cannot be forbidden

The Terms of Service set out the license terms in full.

7. Do not misuse our services

Do not misuse the license portal, the license server or our websites:

• no automated or excessive requests that harm their availability, including requests to our relay that do not come from Reqursor Development
• no attempts to access another customer's licenses, installs or account
• no testing of our systems for vulnerabilities without our written permission. If you find a vulnerability in Reqursor Development, the license server or the license portal, report it privately to [email protected], do not share the details publicly, and give us reasonable time to fix it. Our security page describes how we handle reports.

8. What happens when the rules are broken

If we think this policy has been broken, we may ask you to explain or to stop. Depending on how serious the breach is, we may also:

• warn you in writing
• suspend your license, or end the agreement, on the grounds the Terms of Service give us
• report the breach to the authorities where the law requires it, or where we have a lawful basis to do so

We act in proportion to the breach, and where we can, we tell you first and give you a chance to remedy it. We act at once only where the Terms of Service allow it, for example where there is a serious risk to others or where the license itself is being circumvented.

When a license is suspended or ends, the software stops starting new work. The software never deletes or changes your data, your repositories or your server, and we do not use remote shutdown or deletion to enforce this policy. You can still read and export your history.

9. Reporting a concern

If you see a breach of this policy, or you have a question about whether something is allowed, contact us:

• Legal: [email protected]
• Support: [email protected]
• Anything else: [email protected]
• Contact form: reqursor.com/contact

To report a security vulnerability, email [email protected] as section 7 describes.

10. Changes to this policy

We may update this policy when our products or the rules change. The latest version is always on this page, and the date and revision number at the top show when it last changed. We tell customers about material changes in advance, as the Terms of Service describe.

11. About us

Reqursor Technologies, Rotterdam, The Netherlands. Chamber of Commerce (KvK) number: 42184274. Dutch law applies to this policy, and the District Court of Rotterdam (Rechtbank Rotterdam) has exclusive jurisdiction, as the Terms of Service state.