Legal

Reqursor Development Sub-processors

Last updated: October 10, 2026 · Reqursor Technologies · Rev 1.1

All legal documents

In plain language

  • This page lists the providers that handle customer data for us when we host Reqursor Development for you and when your license runs on Reqursor Credits.
  • Anthropic provides the AI models behind Reqursor Credits.
  • Where we host your instance, Hetzner stores it, and the traffic to it passes through the network of Cloudflare.
  • If you self-host with your own key, your model provider is yours, not ours.
  • We tell you at least 30 days before we add or replace a sub-processor, and you can object.
  • The Data Processing Agreement refers to this page.

1. About this page

This page lists the sub-processors of Reqursor Technologies ("Reqursor", "we", "us") for Reqursor Development. A sub-processor is a provider that we engage to process customer personal data for you, under our Data Processing Agreement. With a self-hosted license and your own key, Reqursor Development runs on your own server and your model requests go straight to your own provider, so the providers in section 2 that handle model requests do not receive them. Where we host Reqursor Development for you with Reqursor Credits, your model requests pass through our relay, and the providers in section 2 process them and the data in your instance.

2. Sub-processors for customer personal data

These providers process the content of your model requests when your license runs on Reqursor Credits, and the data in an instance that we host for you.

Anthropic

  • What it does: provides the AI models behind Reqursor Credits. Our relay forwards each model request to Anthropic with our own account, and Anthropic returns the answer.
  • Data: the content of your model requests, which can hold your code, ticket text and any personal data in them, and the answers. Anthropic may keep requests and answers for a limited time under its terms.
  • Entity: Anthropic Ireland, Limited, Ireland, which contracts with customers in the European Economic Area, Switzerland and the United Kingdom.
  • Where: Anthropic decides where it processes data under its commercial terms. This can include places outside the European Economic Area. The safeguard for that transfer is the standard contractual clauses in Anthropic's data processing addendum, which its commercial terms incorporate.
  • Terms: Anthropic's commercial terms with us apply. Under them, Anthropic states that it does not train its models on data from its API customers. We do not have a zero-retention agreement with Anthropic.

Hosting provider for our relay

  • What it does: hosts the servers on which our relay runs.
  • Data: your model requests pass through its servers in transit, and the relay's logs and usage records are stored there for a short time. The relay does not store requests or answers.
  • Provider: Hetzner Online GmbH, Gunzenhausen, Germany
  • Where: a Hetzner data center in [Germany (Falkenstein or Nuremberg) or Finland (Helsinki), to be confirmed]. Under its data processing agreement with us, Hetzner processes the data only within the European Union.

Hosting provider for the instances that we host

  • What it does: hosts the servers on which an instance that we host for you runs.
  • Data: everything in your instance: your tickets, run history, audit log and encrypted secrets, and the copies of your repositories that the agent works on.
  • Provider: Hetzner Online GmbH, Gunzenhausen, Germany
  • Where: a Hetzner data center in [Germany (Falkenstein or Nuremberg) or Finland (Helsinki), to be confirmed]. Under its data processing agreement with us, Hetzner processes the data only within the European Union.

Cloudflare

  • What it does: provides the network in front of the instances that we host. The traffic to and from the web address of your instance passes through it.
  • Data: what is sent to the web address of your instance and what it answers, which can hold ticket text, code and any personal data in them, and the IP address of each person who uses the instance. Cloudflare decrypts this traffic on its network and encrypts it again before it reaches our server.
  • Entity: Cloudflare, Inc., United States.
  • Where: Cloudflare processes traffic on its network of geographically distributed data centers, which can be outside the European Economic Area. The safeguard for that transfer is the standard contractual clauses in Cloudflare's data processing addendum, and Cloudflare states that it complies with the EU-US Data Privacy Framework.

Hosting provider for our license server and mail server

  • What it does: hosts the servers on which our license server, its database and our mail server run. The mail server receives the support material that you email us.
  • Data: support material that contains customer personal data, in our mail server. It also hosts the license, billing and usage records that we keep as the controller.
  • Provider: Hetzner Online GmbH, Gunzenhausen, Germany
  • Where: a Hetzner data center in [Germany (Falkenstein or Nuremberg) or Finland (Helsinki), to be confirmed]. Under its data processing agreement with us, Hetzner processes the data only within the European Union.

3. Other providers that handle data for us

We use these providers to run licenses and billing. For license, billing and contact data we are the controller, as our Privacy Policy describes, and for that data they are not sub-processors under the Data Processing Agreement. We list them so that you can see everyone who handles your data.

  • Stripe, which processes payments, invoices and customer portal sessions for licenses and credit top-ups, as our processor and, for its own legal and fraud-prevention duties, as an independent controller. We never receive your card details.
  • Our hosting provider and our mail server, listed above, which also handle license, billing and contact data for us.

4. Providers that are yours, not ours

With a self-hosted license and your own key, your prompts go from your server straight to your provider, and we do not receive them. You choose that provider, and your agreement with it applies. This covers Anthropic, Amazon Bedrock, Google Vertex AI and Microsoft Foundry and, as a beta, Moonshot AI. Read section 6 of the AI Usage Policy before you use Moonshot AI. We do not offer Moonshot AI through Reqursor Credits, so it is not our sub-processor. The same goes for your git remote and the integrations you connect, such as your tracker, email or Slack. You choose them, and your agreement with them applies.

5. Changes to this list

We tell you at least 30 days before we add or replace a sub-processor, by email to the contacts on your license and by updating this page. The date and revision number at the top show when the list last changed. You can object to a change on reasonable data protection grounds within 30 days, as the Data Processing Agreement describes.

6. Contact

For questions about our sub-processors, or to object to a change, contact us:

Reqursor Technologies, Rotterdam, The Netherlands. Chamber of Commerce (KvK) number: 42184274.

Data Protection Contact

[email protected] · Reqursor Technologies, Rotterdam, The Netherlands