Acceptable Use Policy. What is fine, and what is not.

01About this policyLink copied

This policy sets the rules for using Reqursor, the AI agent of Reqursor Technologies ("we", "us") that turns tickets into checked code changes and, in early access, changes online stores. It applies whether we host Reqursor for you or you host it yourself, and it covers its dashboards, its APIs, our relay for Reqursor Credits, our license portal (license.reqursor.com) and our websites. It is part of the Terms of Service and applies to your business. By using Reqursor, you agree to this policy for yourself and for every team member you enable.

Reqursor Development and Reqursor Platform are now one product, Reqursor. Some of our other documents and our earlier websites still use the earlier names. In this policy, Reqursor Development means the part of Reqursor that works on your code, and Reqursor Platform means the part that changes online stores, which is in early access, by invitation. A rule that applies to one part only says so.

You must make sure that everyone you give access to follows this policy, such as team members, contractors, agents and anyone who uses an API token you created. You are responsible for their use as for your own.

You decide what Reqursor works on and what it can reach, so you are responsible for how it is used. Because many customers share what we run, how you use it can also affect the security and stability of others. This policy tells you where the limits are.

Where this policy conflicts with the Terms of Service or with a written agreement with us, the Terms or that agreement prevail.

02Use it lawfullyLink copied

You must use Reqursor in line with the law that applies to you and to us, including the laws of the Netherlands and the European Union. You must have the right to give it the code, tickets, content and data you give it, and the right to change the repositories, systems and stores you connect.

Do not use Reqursor to:

• infringe someone's intellectual property or publicity rights, copy code you are not allowed to copy or reuse, or copy another party's brand or identity
• process personal data without a legal basis, or break confidentiality duties you owe to others
• break export control, sanctions or other trade rules
• do anything unlawful, fraudulent or harmful, or anything that could damage, disable, overburden or impair our services or interfere with another customer's use of them

03Do not use it to cause harmLink copied

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

• build or spread malware, viruses, worms, trojans, ransomware, spyware, cryptominers or other malicious or self-propagating code, or host command-and-control, exfiltration or drop sites
• 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, run phishing pages, fraudulent payment forms or deceptive login screens, run carding, or run any other deceptive scheme
• send unsolicited bulk or commercial messages (spam), run mailing lists without valid consent, or support spam that starts elsewhere
• 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.

04Content you must not host or make availableLink copied

For the online store part, in early access, you must not use the stores that run through Reqursor, the store definitions, the instructions you give the AI or any other data you process there to host, store, send, distribute, sell or make available:

• content that is illegal under applicable law, or that promotes, facilitates or incites illegal activity
• content that infringes the rights of others, including copyright, trademark, trade secret, patent or database rights
• goods or services whose sale is illegal, restricted or prohibited where you or your customers are, including illegal drugs, weapons, counterfeit goods and unlicensed regulated products
• content that is defamatory, harassing, threatening or hateful, or that depicts or promotes the exploitation of minors or violence
• content that violates applicable privacy, data protection or consumer protection law

For the part that works on your code, the same idea applies to what you put in tickets, in code and in the repositories you connect: do not put in anything that you may not lawfully hold or send to a model provider.

Your responsibility for what runs

You own your data and you are responsible for everything you run through Reqursor: your code, tickets and repositories and, for the online store part, the content, products, configuration and data of your stores, including everything the AI produced and you confirmed. You must make sure it is lawful, does not infringe the rights of others and follows this policy. For the online store part, we operate the infrastructure and the deployment process. We do not review or endorse store content and do not take responsibility for it. You are responsible for the actions of the agent on your systems, as if you had taken them yourself.

05The AI, model providers and confirming changesLink copied

The AI proposes, and you decide. You are responsible for reviewing what it proposes and for confirming only changes that follow this policy and the law. AI output can need adjusting: for the online store part, placeholder text, stock imagery and first settings are starting points, not final content. For the online store part, nothing takes effect until you confirm it. For the part that works on your code, by default the agent works on its own branch and delivers a draft pull request, and you review the result.

Do not:

• give the AI content that you have no right to use
• use confirmation shortcuts, automation or shared logins to approve changes for someone who has not reviewed them
• try to make the AI ignore its safety rules, or those of its provider, for example by hiding instructions in tickets, repositories, web content, imported pages or other material it reads
• use the AI to produce content or code that breaks this policy

Model provider rules

Everything you send to a model provider through Reqursor is also governed by that provider's usage policy and terms, whether the provider is your own or the one behind Reqursor Credits. Their rules apply on top of this policy.

Treat tickets from people outside your team as untrusted. Reqursor 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.

06Protect your systems and your accessLink copied

You must use the controls that Reqursor gives you responsibly:

• Give the agent only the repositories, credentials and network access it needs for the work 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.
• If you host Reqursor yourself, 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 share your credentials, and do not let anyone use your account who is not a user you have enabled. For the online store part, in early access, do not turn off multi-factor authentication when Reqursor asks you to use it.
• 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.

07Do not get around our controlsLink copied

For the online store part, in early access, each store runs in its own isolated environment, with its own private network and storage, and every change is checked before it goes live. These controls protect you and every other customer. You must respect them and must not try to get around them. In particular, you must not:

• try to bypass, weaken or defeat the isolation between stores or organizations, or access data, stores or resources that belong to another organization
• gain or try to gain unauthorized access to any account, system, network, component or infrastructure, whether by exploiting a vulnerability, by using stolen or shared credentials, or otherwise
• disrupt, degrade or interfere with Reqursor, its checks, its monitoring or the availability of the services for other customers, including through denial-of-service or resource-exhaustion techniques
• get around the confirmation step, the checks that run before a change goes live, or the record of changes, or tamper with how changes are recorded
• bring in configuration, code or extensions meant to escape the isolation of a store, raise privileges, switch off monitoring or hide changes
• collect or scrape data about other customers, their stores or Reqursor without permission
• misrepresent your identity or affiliation, or forge headers or identifiers to hide where content or traffic comes from

Isolation and checks are security controls. Per-store isolation, the confirmation step and the checks before a change goes live protect every customer. Any attempt to defeat them is a serious breach of this policy and can lead to immediate suspension.

08Respect the licenseLink copied

For the part that works on your code, and for Reqursor Credits, 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, 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

For the part that works on your code, do not reverse engineer, decompile or disassemble the software, except where the law says this cannot be forbidden. For the online store part, in early access, do not reverse engineer, benchmark or extract the control plane, the AI services or the deployment logic, or use the services to build a competing platform, beyond what applicable law expressly allows.

These rules apply to you and to anyone you give access to. They do not limit the hosted service that Reqursor itself provides. The Terms of Service and the License Terms set out the license terms in full.

09Use our services fairlyLink copied

Do not misuse the license portal, the license server, our relay, an instance or store that we host for you, or our websites. You must use them fairly and within the limits of your plan, and you must not place an unreasonable or disproportionate load on them or affect other customers. This means:

• no automated or excessive requests that harm availability, including requests to our relay that do not come from Reqursor
• no runaway or abusive AI or deployment activity, no storage or bandwidth abuse, and no cryptocurrency mining or similar workloads
• no attempts to access another customer's licenses, installs, hosted instance, stores or account, and no attempts to reach the servers behind an instance or store that we host for you

If you need more than your plan includes, upgrade your plan. We may apply reasonable technical measures, such as rate limiting, to protect the stability and fairness of our services.

10Reporting a vulnerabilityLink copied

Do not test our systems for vulnerabilities without our written permission. Ask for it at [email protected]. If you find or suspect a vulnerability in Reqursor, the license server, the license portal or the infrastructure behind them, report it privately to the same address, and do not share the details publicly until we have had reasonable time to fix it. In your report, say which part of Reqursor and which page or URL is affected, the steps to reproduce it and the impact you expect.

If you find a problem by chance, stop, do not access, change or delete data that belongs to others, and report it. Never put live passwords or keys in a report. If a credential has leaked, tell us which one and change it first. Testing that we have authorized in writing, and that stays within that permission, is not a breach of this policy.

Our Responsible Disclosure Policy and Security pages say how we handle reports. We acknowledge every report and keep you informed while we investigate. We run no bug bounty or other reward.

11What happens when the rules are brokenLink copied

We may investigate a suspected breach of this policy. If we think it has been broken, we may ask you to explain or to stop. We act in proportion to the nature and severity of the breach, and where we can, and where it does not put others at risk, we tell you first and give you a chance to remedy it. For the online store part, we may act at once and without prior notice where a breach threatens security, integrity, availability or legal compliance, or where the law requires it. For the part that works on your code, 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.

Depending on how serious the breach is, we may:

• warn you in writing
• suspend your license, or suspend or limit access to the accounts, stores or features concerned
• throttle or limit resource use
• for the online store part, remove, disable or isolate the content or the store concerned
• end your account or the agreement, in whole or in part, on the grounds the Terms of Service give us, in cases of serious or repeated breach
• keep evidence, and cooperate with or report to the authorities where the law requires it or where we have a lawful basis to do so

Your data

For the part that works on your code: 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. While a license is suspended, you can still read and export your history. When the agreement ends, the Terms of Service say what happens next: an installation you host yourself keeps its data, and we delete an instance that we host for you.

For the online store part: suspension or ending an account under this policy does not limit any other right or remedy we have under the Terms of Service or the law. The Terms say what happens to your data when an account ends, including how you can export it.

12Reporting a concernLink copied

If you see a breach of this policy, or you are not sure whether something is allowed, contact us. Describe the issue and name the store, install or resource concerned, so that we can find it and look into it. We handle reports in confidence as far as we reasonably can while we look into them.

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

13Changes, governing law and about usLink copied

We may update this policy when Reqursor, the law or our practice changes. The latest version is always on this page, and the revision number and date show when it last changed. We tell customers about material changes in advance, as the Terms of Service describe. For the online store part, if you disagree with a change, you may export your data and cancel before it takes effect.

Dutch law governs this policy, without regard to its conflict-of-laws rules. The District Court of Rotterdam (Rechtbank Rotterdam), the Netherlands, has exclusive jurisdiction over any dispute that arises from or relates to this policy and cannot be settled amicably, unless mandatory law says otherwise.

Reqursor Technologies, Rotterdam, The Netherlands.