Skip to content

Data processing agreement

Version dated November 15, 2026

1. Parties and subject matter

This agreement governs the processing of personal data that Reelease Software, S.L.U. (“the processor” or “Reelease”) carries out on behalf of the customer of the Reelease platform (“the controller”) when providing the service described in the platform terms of use, of which it forms part.

It meets the requirements of Article 28 of Regulation (EU) 2016/679 (GDPR) and Spanish Organic Law 3/2018 (LOPDGDD). If the controller and Reelease sign a specific data processing agreement, that agreement prevails over this text.

2. Duration

The processing lasts as long as the service. When it ends, Reelease keeps the data temporarily for 90 days, solely to return it to the controller or to let it reactivate the service and without processing it for any other purpose, and then deletes it under section 10.

3. Nature and purpose of the processing

Reelease processes personal data exclusively to provide the service: analyze and document the systems the controller connects, publish and run use cases with AI agents under the configuration and approvals the controller defines, keep a run record of each run, provide support and invoice.

The processing includes collection, recording, structuring, storage, retrieval, disclosure to authorized subprocessors and erasure. In live operation, the agent queries what it needs on each run and the controller's databases are not copied. Code the controller 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 does keep the knowledge that is extracted and reviewed (the map of the systems, the catalog, the documents, the summaries and short code citations) and the run record of each run.

4. Types of data and data subjects

The personal data Reelease may process depends on the systems and use cases the controller connects. In general:

  • Element
    Data subjects
    Detail
    The controller's users of the platform; employees, customers, suppliers and other people whose data appears in the systems, documents and tools the controller connects.
  • Element
    Categories of data
    Detail
    Identification and contact data; professional data; content of connected documents, code and systems; messages and files from connected work tools; activity logs and the run record of each run.
  • Element
    Special categories
    Detail
    Not foreseen. Processing special categories of data (Article 9 GDPR) or data relating to criminal convictions and offences (Article 10 GDPR) requires a prior written agreement between the controller and Reelease setting out that processing and its specific safeguards. Without that agreement, the controller will not publish use cases whose purpose is to process them and will inform Reelease if the connected systems contain them.
  • Element
    Account data
    Detail
    Name, email, company, role, language, platform usage and billing: processed by Reelease as controller, under the platform privacy policy.

5. Reelease's obligations as processor

Reelease undertakes to:

  • Process the data only on the controller's documented instructions, which are those resulting from this agreement, the terms of use and the configuration the controller makes in the platform, including with regard to international transfers. If Union or Member State law requires other processing, Reelease will inform the controller beforehand, unless that law prohibits it. If an instruction infringes the law, Reelease will inform the controller immediately.
  • Not use the data for its own purposes or to train AI models, and ensure that its model providers do not do so either.
  • Ensure that persons authorized to process data have committed to confidentiality and received the necessary training.
  • Apply the security measures in section 6 and keep them up to date.
  • Not engage another processor without the controller's authorization, under section 7.
  • Assist the controller so it can respond to data subjects' rights and meet its obligations regarding security, breach notification, impact assessment and prior consultation. If a data subject contacts Reelease directly, Reelease will pass the request on to the controller without delay.
  • Keep a record of the processing activities carried out on behalf of the controller.
  • Make available to the controller the information needed to demonstrate compliance with these obligations and allow the audits in section 11.
  • Delete or return the data when the service ends, under section 10.

6. Security measures

Reelease applies, at a minimum, these technical and organizational measures:

  • Encryption of data in transit and at rest. Integration credentials and each operator's access are stored encrypted (AES-256) and are never sent to the operator's computer. If an agent uses the remote browser, the computer only receives temporary access to that run's session, which gives no access to the account and expires with it, within one hour at most.
  • Services hosted in the European Union (Google Cloud, Madrid region), with per-customer isolation and access control by role and by agent.
  • Agents that start with no capability enabled; only an administrator of the controller enables them. Every action that changes data waits by default for approval by someone other than the person who started the task.
  • Pre-run checks on every run, a digitally signed plan and a run record of each run with its steps, approvals and actions.
  • Activity log of configuration changes, retention periods per system, which the controller can adjust depending on its plan, and legal hold.
  • Vulnerability management, security updates and a responsible disclosure channel published on the security page.
  • Database backups and recovery procedures. Backups are deleted in their ordinary retention cycle, which Reelease will communicate to the controller, and are not used for any other purpose until they are deleted.

The controller may request at any time a more detailed description of these measures for its risk assessment.

7. Subprocessors

The controller gives Reelease general authorization to engage the subprocessors on the list published on the website, which states for each one the service, purpose, region and transfer mechanism.

Reelease will notify the controller by email or in the platform at least thirty days before adding or replacing a subprocessor. The controller may object on reasonable and justified grounds within that period; if no alternative is possible, it may terminate the agreement without penalty.

Reelease imposes on each subprocessor, by contract, data protection obligations equivalent to those in this agreement and remains liable to the controller for their performance.

Tools the controller connects with its own accounts (for example its corporate email, the code hosting services it connects, such as GitHub, Azure Repos, GitLab or Bitbucket, or its messaging workspace) are not Reelease's subprocessors: they are the controller's providers.

8. Notification of personal data breaches

If Reelease becomes aware of a personal data breach affecting data it processes on behalf of the controller, it will notify the controller without undue delay, with a first alert within 24 hours of becoming aware of it at the latest and with updates as more becomes known, so that the controller can comply with Article 33 GDPR. The notification is sent to the email address of the account administrators.

The notification will include, as far as known, the nature of the breach, the categories and approximate number of data subjects and records affected, the likely consequences, the measures taken or proposed and a point of contact. If all the information cannot be given at once, it will be provided in phases.

Reelease will cooperate with the controller in the investigation and in notifying the supervisory authority and the data subjects where required.

9. International transfers

Reelease's services, its database and the AI models run in the European Union. Some subprocessors, such as email delivery or payments, may process data in the United States.

In those cases, the transfer relies on an adequacy decision of the European Commission (including the EU-U.S. Data Privacy Framework, where the provider is certified) or on the standard contractual clauses approved by the European Commission, with supplementary measures where appropriate. The specific mechanism for each provider is stated in the list of subprocessors.

The controller decides where information is processed by AI models: it uses the models of the provider on the list, which run in the European Union, can use a private model on its own infrastructure or, with the Enterprise plan, contract a dedicated deployment in its own cloud or on its premises. Email delivery, payments and sign-in process account data, and their region is shown in the list of subprocessors.

10. Deletion or return at the end of the service

For 90 days after the service ends, Reelease keeps the data temporarily so it can be returned: the controller can export its documents and run records from the platform or ask Reelease to deliver them in a commonly used format.

After that period, or earlier if the controller asks, Reelease deletes the personal data and existing copies, including those held by subprocessors. Data contained in backups is deleted in their ordinary retention cycle, which Reelease will communicate to the controller, and is not used for any other purpose until it is deleted.

That temporary retention is different from blocking: Reelease only keeps blocked the data it must retain under a legal obligation, for as long as that obligation requires and available exclusively to the competent authorities and courts.

11. Audits

The controller may verify compliance with this agreement once a year, or when an authority requires it or a security breach has occurred, through the documentation Reelease provides (description of measures, answers to questionnaires and third-party reports where they exist) and, if that is not sufficient, through an audit of Reelease's premises or systems, with at least thirty days' notice, during business hours and with a reasonable scope, without accessing other customers' data.

The cost of the audit is borne by the controller, unless it reveals a material breach by Reelease.

12. Controller's obligations

The controller undertakes to:

  • Have a legal basis to process the personal data it connects to the platform and to entrust its processing to Reelease, and inform data subjects where required.
  • Connect only systems and tools to which it has a right of access, and configure agents, capabilities and approvals in proportion to the risk of each use case.
  • Carry out a data protection impact assessment when the law requires it. Reelease will assist by providing the information about the platform that the controller needs.
  • Respond to data subjects' rights and authorities' enquiries, with Reelease's assistance.
  • Keep the people with access to the platform up to date and revoke access that is no longer appropriate.

13. Liability and governing law

If Reelease breaches this agreement or processes the data for purposes other than those stated, it will be considered controller for that processing, without prejudice to what the law provides.

This agreement is governed by Spanish law. The parties submit to the courts of Bilbao, unless a mandatory rule establishes another jurisdiction, as under the platform terms of use. Questions about this agreement 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.