Skip to content

Platform terms of use

Version dated November 15, 2026

1. Scope and acceptance

These terms govern the use of the Reelease platform (“the platform”), a cloud service provided by Reelease Software, S.L.U., tax ID B70662838, registered at Ronda de Azkue, 1, planta 13, Torre BEC, 48902 Barakaldo (Bizkaia), Spain (“Reelease”). The platform lets an organization (“the customer”) understand its systems, publish use cases and run them with AI agents under its control.

By creating an account or using the platform, the person doing so declares that they act on behalf of a customer with authority to bind it, and accepts these terms and the data processing agreement. If the customer does not agree, it must not use the platform.

Use of the reelease.io website is governed by its own website terms of use. If a customer has a signed contract with Reelease, that contract prevails over these terms where they conflict.

2. Sign-up and account

Sign-up is done with a GitHub account, with a sign-in link sent by email or, if the customer's organization sets it up, with its identity provider. Profile details must be accurate and belong to a real person with a work email address.

Each account is personal. Whoever uses it is responsible for what is done with it and must protect access to it: not sharing the sign-in link, signing out on shared computers and notifying Reelease promptly of any suspected unauthorized use.

The customer may invite more people according to its plan. Invited people are bound by these terms and the customer is responsible for their use of the platform.

3. Plans and limits

The platform is offered in four plans: Free, Pilot, Pro and Enterprise. Each plan sets usage limits, such as the number of systems, agents and people, knowledge storage and the runs included per month. The current limits of each plan are shown in the platform when it is chosen and in the billing section.

The Free plan does not expire and is for trying the platform with one system, one agent and one person, with a small number of runs per month and without invitations or document export. Reelease may adjust these limits with prior notice in the platform.

The Pro plan is purchased monthly or yearly and includes a number of runs per month shown in the platform. It also includes help with kickoff and connecting the customer's systems and a named contact, with the scope that section 4 sets for that help. Prices and payment terms for paid plans are shown in the platform at the time of purchase and are governed by section 6.

The Enterprise plan is subject to a separate contract, which prevails over these terms, and may include dedicated deployments in the customer's cloud or on its premises, custom limits and specific support terms.

The trial space (“Explore it live”) is a temporary environment with sample data for one sector. It expires after 72 hours and is deleted with everything in it. It does not allow file uploads or connecting real systems and must not be used with personal or confidential data. These terms apply to it where relevant.

4. Pilot of up to three months

The Pilot plan is a paid trial period of up to three calendar months from activation. The customer chooses how to pay when subscribing. Monthly: the customer may cancel it at the end of any paid month from the Stripe customer portal, with no commitment for the remaining months. As a single payment for all three months, with the discount stated at purchase: if the customer cancels before the end, the service continues until that date and the amount is not refunded, and if the customer moves to Pro, Stripe takes the unused part off the first Pro invoice. Either way it ends automatically at the end of the three months, with no tacit renewal.

The Pilot plan includes hands-on help from Reelease: a kickoff session to define the success goal, help with configuration and connecting the customer's systems, a named contact, support for incidents and questions, and a results review at the end. This is help for the customer, who remains the one configuring and connecting its systems. Building custom connectors and integration work that Reelease carries out on request are governed by a separate services order. The Pilot plan runs on the Reelease service, with no dedicated deployments.

The Pilot's first deliverable is the system map and its documentation, in the first week: Reelease delivers it within five working days (Monday to Friday, excluding national public holidays in Spain) of the customer connecting or uploading the code for the scope agreed at the kickoff session, within the limits of its plan, published on the plans and pricing page. It counts as delivered when the analysis of that scope has finished and the customer has, in the platform, the navigable system map with the sources of each element and its generated documentation, exportable as PDF or Word. If the scope changes, the period starts again once the code for the new scope is connected or uploaded. The platform shows the customer the target date and status of this deliverable.

Before the pilot ends, the platform gives notice and offers an upgrade to Pro or Enterprise. If neither is chosen, or if the customer cancels earlier, the account returns to the Free plan and its limits apply: the other people on the account become read-only and no systems or agents can be created above those limits.

Pilot data and run records are kept for 90 days after the pilot ends, so the customer can export them or reactivate the service. After that period, Reelease may delete them, except what it must keep blocked under a legal obligation.

5. Runs and usage

The unit of usage is the run: the governed execution of a use case or a goal, with all its steps and the agents' internal actions. Calls to AI models, queries to systems and intermediate steps within a run are not counted separately. The rules are:

  • Reservation: when a run is admitted, the platform reserves one unit of the period's quota. On the Free and Pilot plans, if the quota is used up, it does not admit new runs and says so; the Pro plan does not stop (section 6) and on Enterprise the contract applies.
  • When it counts: the run counts when it is picked up to start working, even if it later fails or stops.
  • When it does not count: if it ends without anyone picking it up, because it is cancelled, blocked or expires, the reservation is released and no quota is used.
  • Waits and repeats: waiting for approval, resuming after an approval, retries and replans of the same run do not count again.
  • Period: quotas renew every calendar month, in UTC. Whatever is not used in a month does not carry over to the next.
  • AI cap per run: each run has a cap on AI model usage. If it reaches the cap, the platform stops serving its model calls and the run ends as failed, with the reason in its run record. Nothing extra is charged.
  • AI usage for the period: the Free and Pilot plans also include a monthly allowance of AI model usage; if it is used up, the platform does not admit new runs until the next period and says so. The Pro plan does not stop for this reason.
  • Notices: the platform sends an email when 80% and 100% of the month's runs are reached: always to whoever pays for the plan and, on Free and Pilot, also to the system's administrators. Usage for the period is shown in Plans and billing.

A run that ends as completed has gone through the steps of its plan; that does not mean a business result has been achieved. Measuring and billing verified results only applies if agreed in an Enterprise contract, which sets the acceptance criteria, the evidence, how duplicates and corrections are handled and how discrepancies are resolved.

6. Subscription, payments and prices

Paid plans are purchased and paid for through Stripe. The Pro plan renews automatically at the end of each period, monthly or yearly, until the customer cancels it. Plan changes and cancellation are made from the Stripe customer portal; if a change applies mid-period, the amount is prorated as Stripe calculates it.

Pro plan overages: the Pro plan does not stop when the runs included in the month are exceeded. Additional runs are billed per run, at the price published in the platform, from the date Reelease announces with prior notice; runs before that date are not charged. The month's overage is shown in Plans and billing.

Prices are shown excluding taxes. Applicable taxes, such as VAT, are charged as required by law: Stripe calculates them at checkout from the customer's billing address and tax ID or VAT number, and they are shown separately on the invoice.

Reelease may change plan prices with at least thirty days' notice in the platform or by email. The new price applies from the first renewal after that period; if the customer does not accept it, it may cancel before it applies.

If a payment fails, Reelease may limit the account to the Free plan until it is settled.

7. Acceptable use

The customer and its users agree to use the platform lawfully and in accordance with these terms. In particular, they must not:

  • Connect systems, accounts or data to which the customer has no right of access or sufficient authorization.
  • Use the agents for unlawful activities, to harm third parties or to bypass security controls, whether the customer's own or others'.
  • Attempt to access other customers' accounts, systems or data, or interfere with the operation of the platform.
  • Reverse engineer, copy or resell the platform, except as mandatorily allowed by law.
  • Upload content that infringes intellectual property rights, trade secrets or data protection law.
  • Use the platform to make automated decisions with legal effects on people without the human oversight required by applicable law.

Reelease may suspend a user's or an account's access when it detects use that breaches this section or puts the platform or other customers at risk, notifying the customer as soon as possible.

8. Customer responsibilities

The platform works on the customer's systems and under its control. The customer is therefore responsible for:

  • Its systems: deciding which systems are connected, through which API or Client Bridge, and making sure it has the right to do so. In live operation, the customer's systems are queried at run time and its databases are not copied. Code the customer provides for analysis, uploaded as a file or read with read-only access from the code hosting services it connects (for example GitHub, Azure Repos, GitLab or Bitbucket), is processed in a temporary workspace and, if uploaded as a ZIP, is kept for at most 8 days and deleted sooner if that source is removed. Reelease keeps the knowledge that is extracted and reviewed (the map, the catalog, the documents, the summaries and short code citations) and the run record of each run.
  • Its credentials: integration keys and each operator's access belong to the customer. Reelease stores them encrypted, but the customer is responsible for their validity, their scope and for revoking them when appropriate.
  • Its operators: designating who can use each agent and, where the operator application is used, installing it only on computers managed by the customer and keeping them up to date.
  • Approvals: defining in each agent which capabilities are enabled, which actions wait for a person and who approves. By default, every action that changes data waits for approval by someone other than the person who started the task.
  • Knowledge and results: reviewing the map of its systems, the documents and the use cases before publishing them or acting on them. AI models can produce inaccurate or incomplete results, which is why the platform puts them through review and approval by the customer's people. What is not published is never run.
  • Compliance: using the platform in accordance with the regulation that applies to it, including data protection, sector rules and artificial intelligence law.

9. Personal data

When the platform processes personal data for which the customer is the controller, Reelease acts as processor under the data processing agreement, which forms part of these terms. The list of subprocessors is published on the website and updated with prior notice.

Personal data of the platform's users (name, email, company, activity in the platform, support and billing) is processed by Reelease as controller to provide the service, bill for it, provide support and meet its legal obligations, as detailed in the platform privacy policy.

Nothing the agent reads to carry out a task is used to train AI models, either by Reelease or by the model providers the platform uses.

10. Intellectual property

The platform, its software, design, documentation and trademarks belong to Reelease or its licensors. These terms grant the customer a non-exclusive, non-transferable right of use limited to the duration of the service and to its plan.

The customer's systems, code, documentation, data and the results the platform generates from them (the map of its systems, the documents, the use cases and the run records) belong to the customer. Reelease processes them only to provide the service.

Reelease may use aggregated, anonymous technical data about how the platform operates to improve it, without identifying the customer or its systems.

11. Availability and support

Reelease provides the service diligently and strives to keep it continuously available, but does not guarantee any specific level of availability unless agreed in an Enterprise contract. Maintenance downtime is announced in advance when possible.

Support is provided by email, Monday to Friday, 9:00 to 18:00 Madrid time, excluding Spanish national holidays. During those hours, Reelease aims to give a first response within these times: on the Pilot plan, 4 business hours for urgent requests, meaning anything that stops the pilot, and 1 business day for everything else; on the Pro plan, under 1 hour for any request. The Free plan has no committed time and on Enterprise the contract applies. These are first response targets, not resolution times, and they give no right to service credits or penalties. A contractual service level (SLA) exists only in an Enterprise contract.

The platform evolves. Reelease may add, change or withdraw features, giving reasonable notice when a change substantially affects the customer's use.

12. Confidentiality

Each party will treat as confidential the other party's non-public information that it accesses in connection with the service, use it only to perform the service and not disclose it to third parties, except to its staff and providers bound by equivalent obligations, or when required by law.

This obligation lasts for the duration of the service and for five years after it ends.

13. Limitation of liability

Agents act on the customer's systems according to the configuration, capabilities and approvals the customer defines. Reelease is not liable for actions approved or pre-authorized by the customer, nor for the effects of the instructions its users give to the agents.

Reelease is not liable for indirect damage, loss of profits or loss of data that the customer did not export when the platform allowed it. In any case, Reelease's total liability to the customer is limited to the amount paid by the customer in the twelve months before the event giving rise to it.

These limitations do not apply in cases of willful misconduct or gross negligence, or where the law does not allow liability to be limited.

14. Suspension and termination

The customer may cancel its plan at any time from Plans and billing, which opens the Stripe customer portal, and may ask for its account to be closed by writing to info@reelease.io. Cancellation of a paid plan takes effect at the end of the paid period; amounts for periods already started are not refunded, unless the law provides otherwise.

Reelease may suspend or terminate the service if the customer seriously breaches these terms and does not remedy the breach within fifteen days of being notified, if it stops paying or if an authority requires it.

When the service ends, the customer has 90 days to retrieve its documents and run records: by exporting them from the platform or by asking Reelease to hand them over. After that, Reelease deletes the customer's data in accordance with the data processing agreement, except what it must keep blocked under a legal obligation.

15. Changes to these terms

Reelease may update these terms. Changes are published on this page with their version date and announced in the platform at least thirty days in advance when they are substantial. Continuing to use the platform after they take effect means accepting them; if the customer does not accept them, it may cancel before they take effect.

16. General provisions

Force majeure: neither party is liable for a failure or delay caused by events beyond its reasonable control, for as long as they last.

Assignment: the customer may not assign its position under these terms without Reelease’s prior written consent. Reelease may assign it to a company in its group or to whoever acquires its business, giving notice to the customer and keeping the same obligations.

Severability: if a clause is held invalid or unenforceable, the rest remain in force.

Notices: Reelease contacts the customer in the platform or at the account admins’ email address; the customer contacts Reelease at info@reelease.io.

Entire agreement: these terms, the data processing agreement and, where they exist, the signed Enterprise agreement or services order set out everything agreed between the parties about the platform.

17. Governing law and jurisdiction

These terms are governed by Spanish law. For any dispute, the parties submit to the courts of Bilbao, unless a mandatory rule establishes another jurisdiction.

Questions about these terms can be sent to info@reelease.io.

You choose the cookies

We use technical storage to remember your choice and, only if you accept, analytics cookies (Google Analytics) to understand how the site is used. You can change your choice at any time. Learn more in our cookie policy.