01Who we are and who these terms are for
These terms are an agreement between you and Reqursor Technologies ("Reqursor", "we", "us"), a company based in Rotterdam, The Netherlands.
"You" means the business that starts a trial, buys a license, gets access by invitation or otherwise uses Reqursor. The person who accepts these terms for it confirms that they have the authority to do so. By starting a trial, activating or buying a license, accepting an invitation, or installing or using Reqursor, you confirm that you act for a business and that you have the authority to accept these terms for it. Reqursor is not offered to consumers.
Reqursor is an AI agent that turns tickets into checked code changes. Technical teams hand it tickets, and anyone else can describe a change in its AI chat and confirm the draft ticket it writes. We host Reqursor for you with Reqursor Credits, or you host it yourself with your own key. The online store part of Reqursor changes online stores that we run for you. It is in early access, by invitation. Licenses are managed in Reqursor Licensing, our license portal at license.reqursor.com.
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 these terms, 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. These terms cover all of Reqursor, Reqursor Credits and Reqursor Licensing. Where a rule applies to only one part, the sentence says which.
02The documents that apply
The following documents together make up the agreement between you and us:
- these terms
- the Refund, Cancellation and Credits Policy
- the Data Processing Agreement and the sub-processor list, where they apply
- the Acceptable Use Policy
- the AI Usage Policy
- your order, which names your plan, term and fees, and any special terms we agreed with you in writing
If you and we sign a separate Software License Agreement, its terms come first where they conflict with these terms. Otherwise your order comes first, then these terms, then the other documents in the list above. The Data Processing Agreement prevails over every other document in this list, including a Software License Agreement and your order, on the processing of personal data on your behalf. The Privacy Policy explains how we handle personal data and does not change these terms. Your own purchasing or general terms do not apply, even if you refer to them in a purchase order.
03What Reqursor is
Reqursor has a part that works on your code and a part that works on online stores. Your order states what you get.
- The part that works on your code. It prepares changes to your code with AI models. Tickets become checked code changes, and a person who is not technical can describe a change in the AI chat and confirm the draft ticket. The next section explains how it is licensed and run.
- The online store part, in early access, by invitation. It builds, moves and runs online stores for you. You describe a store in plain words, the AI proposes it, and every change is checked before it goes live. Today it starts with a conversation and a demo that we show you in person. The service includes AI store generation from natural language, AI-powered migration of existing stores, monitoring and operations, a deterministic execution engine, per-store isolation and a conversational AI interface for store management.
We keep improving Reqursor, and the documentation describes what each part does.
04The software and your license
Subject to these terms and to payment of the fees, we grant you a non-exclusive, non-transferable, non-sublicensable license, for the term of your plan, to use Reqursor for your own internal business operations, within the limits of your plan. For the part that works on your code, that means use on one installation (an "instance"). For the online store part, it means use of the service for the stores that your order names.
For the part that works on your code, we offer Reqursor in two ways. Your order states which one applies to your license, and a license is one or the other.
- Hosted with Reqursor Credits. We host and operate the instance for you (the "hosted service"), so you have nothing to install. AI usage is paid with Reqursor Credits, as the section on Reqursor Credits describes, and you need no model provider account or API key. Where we have switched it on for your instance, a person can instead run the tickets they start on their own personal Claude account, as the AI Usage Policy describes.
- Self-hosted with your own key. You install and run the instance on your own server and connect your own model provider account, for example your own Anthropic API key. The plan price is then a platform-only fee, as the section on plans, fees and payment describes, and your model provider bills you directly for AI usage.
On the Solo, Starter and Team plans you choose between the two at checkout. For an Enterprise license we agree it with you in your order, and an offline license file is available only with your own key. We change an existing license from one way to the other on request. Changing a hosted license means moving to an installation on your own server, which we arrange with you: contact us at [email protected].
For the online store part, in early access, we run the stores for you on our infrastructure. Access is by invitation.
Reqursor is licensed, not sold. We keep all rights in the software and its documentation. If you self-host, the software is delivered as compiled software, and you may make the copies needed to install it and to make backups of your instance.
Your plan sets the number of developer seats, the number of projects and the features you can use. Updates, support and new releases are available while your license is valid and until the update date stated in your license token. A release published after that date does not start new work on your instance.
05Accounts, seats and roles
You must provide accurate information when you create an account. You are responsible for keeping your credentials secure and for all activity under your account. You must enable multi-factor authentication when asked to. Tell us at once if you suspect unauthorized access.
Seats and roles in the part that works on your code
A developer seat is for one named person with the Owner, Admin or Developer role: anyone who can write tickets or control runs. You may not share logins, passwords or API tokens between people. You may reassign a seat when a person leaves your business or permanently changes role, but not to rotate one seat among several people.
Viewers have read-only access and do not take a seat. Deactivated users, the agent and API tokens do not count as seats. A project is one connected git repository. Archiving a project frees its place in your project limit, and its history stays readable.
Where your plan sells them, you can add extra seats and projects during your term at the prices of your plan. Additions are prorated to the end of the current billing period. Reductions take effect at the next renewal, and we refuse them while you use more seats or projects than the reduced total allows.
Organizations and team members in the online store part
For the online store part, in early access, an organization (a "tenant") is the main billing and isolation unit. Organization admins can invite team members, assign the roles Admin, Operator and Viewer, and manage billing. Each role has its own permissions, which the Team Management section of your dashboard lists.
06The 14-day trial
For the part that works on your code, the self-serve way to try Reqursor is Start with credits. You buy an amount of Reqursor Credits as a one-off purchase, and we issue a starter license that runs for 14 days. It runs on Reqursor Credits only, so you need no model provider account or API key. It includes the integrations of the Team plan, limited to 3 seats and 3 projects. In these terms and in the documents listed above, "trial" means this starter license or an evaluation that we arrange with you.
The credits you buy with Start with credits are purchased credits under the section on Reqursor Credits. When the 14 days end, or earlier if the credits are used up, the software starts no new work until you choose a plan, and you keep access to your history and exports. There is no self-serve trial of a self-hosted installation with your own key. If you want to evaluate self-hosting, contact us and we arrange an evaluation with you in writing. We may refuse a starter license or an evaluation where there are signs of abuse, and we provide both as is, without a support target and without the warranty in these terms.
The online store part, in early access, has no self-serve trial. It starts with a conversation and a demo.
07Plans, fees and payment
The fees for each plan, seat, project and store are on the pricing page and in your order. Prices are in euros and exclude VAT. Annual plans are invoiced in advance for the year and monthly plans monthly in advance. Payments run through Stripe, and you manage invoices, payment methods and cancellation in the Stripe customer portal. We never receive your card details.
How fees are counted. For the part that works on your code, fees are per plan, with seats and projects as the plan states. For the online store part, in early access, billing is per store per month according to the plan tier in your order.
The two ways to run the part that works on your code. Hosted with Reqursor Credits costs more than self-hosted, because it includes the hosting, the credits and the inference relay. Hosted with Reqursor Credits, the plan price includes the hosted service and the credits that your plan states. Self-hosted with your own key, it is a platform-only fee: it covers the software, and it includes no AI usage and no credits, because your model provider bills you for AI usage.
Taxes. We calculate VAT (BTW) from your billing details. Customers in the Netherlands pay 21% Dutch VAT. Business customers in another EU member state with a valid VAT number are invoiced without VAT under the reverse charge. Other customers are invoiced as the VAT rules require. You are responsible for any other taxes on your side, and you must give us accurate billing details, including your business name and VAT number.
Payment terms. Subscriptions are charged through Stripe when they are due. A failed payment through Stripe is retried automatically. An invoice we send you directly is payable within the term stated on it, which is 30 days unless your order says otherwise. If you pay late, we may charge the statutory commercial interest and the reasonable costs of collection under Dutch law.
Renewal. A subscription renews automatically for the same period until you cancel it.
Plan changes. For the part that works on your code, upgrades and extra seats or projects take effect at once and are charged pro rata for the rest of the billing period. Downgrades and removed extras take effect at the next renewal, without a refund for the period already paid. For the online store part, in early access, upgrades take effect at once with prorated charges, and downgrades take effect at once with prorated credits.
Price changes. For the part that works on your code, we may change our list prices from a renewal, and we will tell you in writing at least 30 days before that renewal. Any price lock in your order stays in force for the period it states. For the online store part, in early access, we may change prices with 30 days' notice.
Onboarding fee. If your order includes a one-time onboarding fee, the Refund, Cancellation and Credits Policy says when it is refundable. Where your order says the fee is credited against your first annual invoice, we credit it as stated.
Special offers. Offers such as founding-customer terms apply only where your order says so, on the conditions stated in it.
08Reqursor Credits
Reqursor Credits pay us for AI model usage in the part that works on your code. They apply to a license that runs on credits: a license for the hosted service, or a starter license under the 14-day trial. On such a license your model requests go through our relay to the model provider, and you need no model provider account. The exception is a ticket that a person runs on their own Claude account, where we have switched that on for the instance. It uses no credits and does not go through our relay, as the AI Usage Policy describes. A self-hosted license with your own key includes no credits and cannot use them, and neither can an installation that runs on an offline license file. With your own key, model requests go straight from your server to your provider and never through our relay, with one exception: Reqursor Intelligence, the assistant panel. If an Owner or Admin of a self-hosted installation chooses our monthly allowance for it, the assistant's questions, with the ticket, run and project details it read to answer, go through our relay to Anthropic. We pay for them, up to a monthly allowance. They use no credits and nothing is charged. If they choose your own key, the questions go straight to your provider.
- Included credits. Where your plan includes credits, we grant them each month, once the invoice for that period is paid. Included credits expire at the end of the period they were granted for and do not roll over.
- Top-ups. You can buy more credits as a one-off purchase in the license portal. We add them to your balance once the payment is confirmed. We never top up your balance automatically. A top-up is final: once you have bought credits, the purchase is not refundable, except for a billing error or a double charge or where mandatory law requires it. Purchased credits do not expire. If you cancel, they stay on your balance, and you can use them again when you have a paid license that can use credits.
- Order of use. The software uses included credits first, then promotional credits, those that expire soonest first, then purchased credits. Promotional credits expire on the date we state when we grant them.
- How credits are used. Each model request uses credits, depending on the model and on the amount of text it handles. The usage of a run is rounded up to a whole credit. The rates and the price of credits are shown in the product and in the license portal, and you can see your balance and usage there.
- Running out. When your balance is used up, the software pauses the tickets that depend on credits, and they continue once credits are available again. Your balance can go below zero after a late usage report, a refund, a payment dispute or a change of billing period. While it is below zero, the software starts no new work on credits, and we set the shortfall against the credits you receive or buy next. We send an email notice when your balance runs low and when a run is paused for lack of credits, normally once per period.
- Limits. You can set spending limits per ticket, day and month. We also apply protective limits, such as spending limits for your account and for the service as a whole, and limits on the number of requests, and we may pause the use of credits where we see signs of abuse or an unpaid or disputed payment.
- Models and rates. We choose which models are available through credits and may add or remove models. We may change the rates and the price of credits with at least 30 days' notice. A change never reduces the number of credits you already hold, and it does not apply to a run that has already started.
- No cash value. Credits are not money, are not interest-bearing and have no cash value. You cannot transfer them or use them outside Reqursor, and purchased credits are not refundable, as the Refund, Cancellation and Credits Policy says.
- Your data. When you use credits, your prompts pass through our relay on their way to the model provider. The AI Usage Policy and the Privacy Policy explain what that means for your data.
09Cancellation and refunds
You can cancel your subscription at any time in the Stripe customer portal, through the license portal or by email to [email protected]. For the part that works on your code, cancellation takes effect at the end of the billing period you have already paid for, and your license stays usable until then. The Refund, Cancellation and Credits Policy says what we refund and when. Outside that policy, fees you have paid are not refunded, except where mandatory law requires it.
For the online store part, in early access, you can also delete your account, as the section on suspension and termination describes.
10License checks and what happens when a license lapses
The part that works on your code checks your license before it starts work. The check uses a signed license token bound to your instance, which is renewed by a daily check with our license server at license.reqursor.com. The check contains only the license metadata listed in the Privacy Policy, never your code, tickets or prompts. The software also asks the license server about once a day for the signed list of releases your license covers, which an administrator can turn off in the settings. That request carries only the license token. Enterprise customers who self-host with their own key can use an offline license file instead, which sends nothing.
If your installation cannot reach the license server, it keeps working. It shows a warning after 7 days without a successful check, and a license token stays valid for 30 days after the last successful check. Moving your installation to new hardware does not lock it out: a changed hardware fingerprint is noted and never a reason to refuse a license.
When a license is expired, revoked, does not verify or does not cover the installed release, or the installation has been modified, the software starts no new work and adds no projects. It never deletes or changes your data, your repositories or your server. If you self-host, you can always read your history, export your data and take backups. If we host the instance, you can read your history and export your data for as long as we host it, and the section on suspension and termination says what happens to it when the agreement ends. We do not use remote shutdown of your server, data deletion or any other destructive measure to enforce a license.
11Your responsibilities
If you self-host, you provide and run the hardware, operating system, network and backups of your installation, and you follow the documentation. You keep the installation's master key safe: without it, stored credentials cannot be recovered from a backup. If we host the instance, we provide and run its server, operating system and network, and you export the data that you want to keep outside it.
You are responsible for:
- your model provider account, if you use one, its costs and its terms
- your use of Reqursor Credits and the people who can spend them
- the credentials you enter and who you give access to
- the tickets, instructions and configuration you give the software
- if you self-host, keeping the software and its host updated and secured
- your choice of checks, protected branches and approval settings
- for the online store part, in early access, the content of your stores and the decisions you make about their configuration
- for the online store part, regular backups of your store business data, such as orders, products and customers, which we recommend
Some self-hosted deployments give the agent no isolation from the host, for example on Windows or in process-only mode. The documentation explains which setup gives which protection. If you self-host, you decide where and how to run the software, and you accept the risks of that choice.
12AI output and your review
For the part that works on your code, Reqursor prepares changes to your code with AI models. It commits a change only when your configured checks pass and its review finds evidence for the ticket's criteria, and you can require approval before any change is committed. The checks reduce risk, but they do not remove it.
For the online store part, in early access, the AI proposes store definitions such as design tokens, page layouts and configurations from your plain-words input. Every proposal is shown to you for review, and nothing is applied to a production store until you confirm it. Placeholder text, stock imagery and first configurations are starting points, not final content. Once you confirm a store definition and it is committed to Git, execution is designed to be deterministic: the same inputs give the same deployment, each store is isolated from the others, and every change is auditable and can be rolled back to a prior committed state.
You remain responsible for reviewing, testing, deploying and using the changes, and for how you configure the software. We do not guarantee that a change is correct, secure, complete, free of third-party rights or fit for a particular purpose. AI output can contain errors, including plausible code that is wrong. We do not guarantee specific deployment times or AI output quality. The AI Usage Policy explains how the AI is used and where your data goes.
13Acceptable use
You and the people you give access to must follow the Acceptable Use Policy and the terms of your model provider, and must use the software in accordance with applicable law. In short, you may not use Reqursor for illegal purposes, try to reach another organization's data or stores, get around isolation or security controls, host malware or carry out attacks, exploit a vulnerability instead of reporting it through our Responsible Disclosure Policy, or exceed your plan limits without upgrading.
14Your data and our access
If you self-host, the software runs on your installation, and your code, tickets, run history, audit log and encrypted secrets are stored there. Your code and ticket text leave it only for the model provider you configured (or Anthropic, if a person signs in with their own Claude account), your git remote and the integrations you connect, as the AI Usage Policy explains. The one exception is the assistant: if an Owner or Admin chooses our monthly allowance for Reqursor Intelligence, its questions, with the ticket, run and project details it read to answer, go through our relay to Anthropic. The installation also contacts our license server, as the section on license checks describes. We have no access to your installation or the data in it unless you send data to us, for example in a support request or a diagnostics bundle. Please read a diagnostics bundle before you send it.
If we host the instance, it runs on servers that we operate. Your tickets, run history, audit log and encrypted secrets, and the copies of your repositories that the agent works on, are stored there, and your model requests go through our relay to the model provider, as the AI Usage Policy explains. We use the data in a hosted instance only to provide the hosted service and support to you.
For the online store part, in early access, each organization's stores run in their own isolated containers. We use your store configuration data only to provide the service. Your store business data, such as orders, products and customers, lives in your store's own volumes and is not accessed or read by us, except while we move an existing store to Reqursor for you, and then only with your explicit consent, read-only and for as long as the move takes.
Our Privacy Policy describes the personal data we process to run licenses, billing, credits, support and the license portal. Where we process personal data on your behalf, for example in prompts that pass through our relay, in an instance that we host for you or in the stores that we run for you, we act as your processor. Our Data Processing Agreement covers this processing and applies automatically, and our sub-processor list names the providers involved. For the usage, license and billing data described in the Privacy Policy, we are the controller.
15Intellectual property
We and our licensors keep all rights in the software, its documentation and our names and logos. Open-source components are licensed under their own terms, which are listed in the NOTICE file shipped with the software, and nothing in these terms limits the rights those terms give you.
You keep all rights in your code, tickets, configuration, store definitions, design tokens, page content, business data (orders, products, customers) and other data ("your data"). We claim no rights in the code changes the software produces for you. Rights in AI-generated output are not settled everywhere, and your model provider's terms may also apply to it. We do not promise that you will hold rights in AI output or that it does not resemble third-party material.
If you send us feedback, you give us the right to use it to improve our products without payment or obligation. We do not name you as a customer or publish your feedback without your approval, unless your order says otherwise.
16Restrictions on the software
You may not, and may not allow anyone to:
- remove, disable, bypass or patch the license checks, the license token, the daily check or the plan limits
- forge, alter or replay a license token or a license check, or send false license data
- share a license key or install the software on more instances than you license
- copy, sell, rent, lend, sublicense or distribute the software, or offer it to others as a hosted service
- use our relay or your credits in any other way than through Reqursor, or resell or share them
- modify the software or remove its proprietary notices
- reverse engineer, decompile or disassemble the software, except to the extent that mandatory law allows it despite this restriction
These restrictions apply to you and to anyone you give access to. They do not limit the hosted service that we ourselves provide.
Nothing in this section limits the rights you have by mandatory law, including articles 45j to 45m of the Dutch Copyright Act (Auteurswet).
Breaking this section is a material breach, and we may suspend your license at once.
17Support, updates and availability
We give support during your term at the level of your plan, by email to [email protected] and during Dutch business hours. The first-response targets for each plan are published on our pricing and documentation pages. They are targets, not guarantees, and they do not give rise to service credits unless an enterprise order says so. Support does not cover your own code, checks and repositories, your model provider, or your hardware, operating system and network.
A self-hosted installation runs on your own infrastructure, so we do not host it and we do not give an availability guarantee for it. Where we host the instance for you, we run the hosted service with reasonable care, and we give an availability guarantee for it only if your order states one. We run the license server and our relay with reasonable care, and the software keeps working while the license server is unreachable, as the section on license checks explains. Model access through credits depends on our model providers, and we do not guarantee that it is available at all times.
For the online store part, in early access, we aim for 99.5% availability of the control plane, the dashboard and the AI services. This is a target, not a guarantee. Running stores continue to operate independently of that availability. If the AI provider is unavailable, AI features degrade, and stores and monitoring continue.
We may develop the software further. We will not remove a material feature of your plan during your term without offering an equivalent or a pro rata refund of the prepaid fees for the rest of the term.
18Warranty
For the part that works on your code, during your paid term we warrant that the software will materially perform as the documentation describes. If it does not, we will, at our choice, correct the defect within a reasonable time or give you a workaround. If neither is possible, you may end the affected subscription and receive a pro rata refund of the prepaid fees for the rest of the term. This is your only remedy for a breach of this warranty.
The warranty does not cover defects caused by your hardware, operating system, network, model provider, repositories, checks or configuration, by use against the documentation, or by modification. Apart from this warranty, and as far as the law allows, we provide the software without any warranty, express or implied, including of merchantability or fitness for a particular purpose, and without a warranty that AI output is correct.
19Liability
The part that works on your code. To the extent the law allows, our total liability under or in connection with these terms is limited, for all events that have the same cause or that occur in the same contract year together, to the greater of (a) the fees you paid us in the 12 months before the first of those events, including what you paid for credits, and (b) EUR 1,000. A contract year runs from the date you accepted these terms, and each following 12 months.
The online store part, in early access. To the extent the law allows, our total liability for the online store part is limited to the fees you paid for it in the 12 months before the claim.
For the part that works on your code, we are not liable for damage other than direct damage. Direct damage means only the reasonable costs of establishing the cause and extent of the damage, the reasonable costs of making our defective performance conform to the agreement, and the reasonable costs of preventing or limiting damage. In particular we are not liable for lost profit, lost savings, business interruption, damage from code changes you deployed, or damage from the acts, output or charges of a model provider or other third party. We are not liable for loss of data that you could have prevented with the backups the documentation describes.
For the online store part, we are also not liable for AI-generated content that you reviewed and confirmed, for business losses that result from your store configuration decisions, for data loss in your store business data (we recommend regular backups), or for outages of third-party services such as payment gateways and hosting providers.
None of this limits liability that cannot be limited by law, including liability for damage caused by our intent or deliberate recklessness (opzet of bewuste roekeloosheid) or that of our management. You must notify us of a claim in writing within a reasonable time after you become aware of the damage.
20Confidentiality
Each of us keeps the other's confidential information confidential and uses it only to perform this agreement. The software's compiled code, its non-public documentation and your order are our confidential information. Your data is yours.
21Suspension and termination
We may suspend your license, after written notice where practical, if an invoice stays unpaid 30 days after a reminder, or at once if you break the restrictions on the software. For the online store part, in early access, we may also suspend your account after notice if payment keeps failing. We may suspend at once if you seriously break the Acceptable Use Policy and there is a serious risk to others. A suspension of the part that works on your code has the same effect as an expired license, and it ends when the cause is resolved.
Either of us may end the agreement by written notice if the other breaches it materially and does not remedy the breach within 30 days after a written notice describing it. We may end it at once if you break the restrictions on the software, and, to the extent the law allows, either of us may end it if the other is declared bankrupt or granted a suspension of payments. For the online store part, in early access, we may also end your account for a violation of these terms, persistent non-payment, illegal use or security threats to Reqursor. We give notice, except in cases of imminent security risk.
When the agreement ends, your license ends and the software starts no new work. If you self-host, the section on license checks continues to apply: the software deletes nothing, you can still read and export your history, and you remove the software from your servers yourself. If we host the instance, that section applies until the agreement ends. Export the data that you want to keep before then, because after the agreement ends we delete the instance and the data in it or, at your choice, return that data, as the Data Processing Agreement says. That deletion ends the hosted service. It is not a measure to enforce a license. If we end the agreement for a reason other than your breach or your insolvency, we refund the prepaid fees for the period after the end date, as the Refund, Cancellation and Credits Policy says.
For the online store part, in early access, you can delete your account in the Data and Compliance section of your dashboard. That starts a grace period of 7 days. During the grace period, your stores keep serving traffic but team access is revoked. After 7 days, your stores go offline. All data is permanently purged within 30 days after the grace period ends, except the records we must keep by law. Export what you want to keep before you delete your account.
Sections that by their nature survive the end of the agreement, including those on intellectual property, restrictions on the software, liability, confidentiality and governing law, keep applying.
22Changes to these terms
We may update these terms for a valid reason, such as a change in the law, in the software or in our services. We will tell you about material changes by email, in the license portal or in your dashboard at least 30 days before they take effect. If a change materially disadvantages you and you do not agree, you may end the agreement by written notice before the change takes effect, and we will refund the prepaid fees for the period after the end date. For the online store part, you may also export your data and cancel before the change takes effect. If you keep using the software after the notice period, you accept the change. A change to these terms does not change the fees, plan limits or term stated in an order that is already running, unless you agree or the law requires it. The date and revision number at the top show when these terms last changed.
23Governing law and disputes
These terms, and any dispute arising from or in connection with them, including non-contractual obligations, are governed by Dutch law. The United Nations Convention on Contracts for the International Sale of Goods (CISG) does not apply. Any dispute is submitted exclusively to the District Court of Rotterdam (Rechtbank Rotterdam), The Netherlands.
24General and contact
These terms are the whole agreement on their subject and replace earlier agreements and statements about it, including the earlier terms of service for Reqursor Development and for Reqursor Platform. Changes to an order must be in writing, and an electronic acceptance counts as writing. You may not assign the agreement without our written consent, and we may assign it to a successor of our business. Neither of us is liable for a failure caused by circumstances beyond its reasonable control, including outages of model providers, hosting providers, payment providers or the internet. If a provision is invalid, the rest stays in force. These terms are in English.
For legal questions and notices, contact us:
- Legal: [email protected]
- Support and billing questions: [email protected]
- Privacy: [email protected]
- Anything else: [email protected]
- Contact form: reqursor.com/contact
- Reqursor Technologies, Rotterdam, The Netherlands
All our documents are on the legal overview. The Security document describes how we protect Reqursor, and the GDPR and Data Hosting document explains where data is hosted.