Skip to content

Platform privacy policy

Version dated November 11, 2026

1. What this policy covers

This policy explains how Reelease Software, S.L.U. (tax ID B70662838, Ronda de Azkue, 1, planta 13, Torre BEC, 48902 Barakaldo (Bizkaia), Spain; “Reelease”) processes the personal data of the people who use the Reelease platform: whoever creates the account, invited people, administrators and operators. For this processing, Reelease is the controller.

It does not cover the data contained in the systems, documents and tools the customer connects to the platform, or the content of run records. Reelease processes that data on behalf of the customer, as processor, under the data processing agreement. The reelease.io website has its own privacy policy.

2. What data is processed

Depending on how you use the platform, Reelease processes this data:

  • Account and profile: first name, last name, email address, company, role, language and the system or organization you belong to.
  • Sign-in: the email address the sign-in link is sent to; if you sign in with GitHub, the profile data GitHub provides (identifier, username, name, email, picture and company) and the access tokens GitHub issues, which are stored encrypted; and if your organization uses its identity provider (SSO), the identifier, email and name that provider sends. Reelease does not receive your GitHub password or your provider password. If you turn on the second factor, its key is stored encrypted and the recovery codes in a form that cannot be read.
  • Invitations: the invited person's email, who invited them, the assigned role and the status of the invitation.
  • Operators: the work account each operator signs in with and the technical data of the operator app needed to connect it securely.
  • Activity: what each person does in the platform (configuration, publications, rule changes, approvals) and the run count for each period.
  • Support: the messages you exchange with Reelease and whatever you include in them.
  • Billing: the organization's tax details, the billing email, the plan purchased and the payment history. Card details are collected and stored by Stripe; Reelease does not see them.
  • Product usage: which screens and features of the platform are used, linked to a pseudonymous identifier.
  • Technical data: IP address, browser and security logs needed to serve the platform and protect it against abuse.

3. Purposes and legal bases

  • Creating and managing the account, enabling sign-in and providing the contracted service. Basis: performance of the contract with the customer (Article 6(1)(b) GDPR). For invited people and operators, who do not sign the contract, the legitimate interest of the customer and of Reelease in their teams using the contracted service (Article 6(1)(f) GDPR).
  • Logging account activity so the customer can audit who did what and when, and for the security of the service. Basis: performance of the contract and the legitimate interest in traceability and security (Articles 6(1)(b) and 6(1)(f) GDPR).
  • Detecting abuse, preventing unauthorized access and resolving incidents. Basis: the legitimate interest in protecting the platform and its customers (Article 6(1)(f) GDPR).
  • Measuring how the platform is used in order to improve it. Basis: the legitimate interest in improving the service (Article 6(1)(f) GDPR).
  • Counting, in aggregate, how many people visit the trial space entry page and request the link, without cookies or anything stored in your browser: the server computes a keyed daily fingerprint from the IP address and the browser, which are not stored; the fingerprint changes every day and cannot be traced back to them. Basis: the legitimate interest in measuring and improving the demo (Article 6(1)(f) GDPR).
  • Providing support. Basis: performance of the contract (Article 6(1)(b) GDPR).
  • Invoicing and collecting payment for paid plans and meeting tax and accounting obligations. Basis: performance of the contract and compliance with legal obligations (Articles 6(1)(b) and 6(1)(c) GDPR).
  • Sending service notices: sign-in links, invitations, quota and pilot-end notices, and changes to the terms or the subprocessors. Basis: performance of the contract (Article 6(1)(b) GDPR).
  • Sending you, as a customer, marketing emails about Reelease: plan reminders and offers similar to what you already use. Basis: legitimate interest and Article 21.2 of the Spanish Information Society Services Act (LSSI). Every email has an unsubscribe link, and you can turn them off in My account → Notifications (“Emails with news and offers”); service notices keep arriving.
  • If, when requesting a trial space, you tick the optional box to receive an email with Reelease news when the trial ends, sending you that single email. Basis: your consent (Article 6(1)(a) GDPR), which you can withdraw with the unsubscribe link in that email or by writing to info@reelease.io. Without the box ticked, you only receive the notices about the trial space itself, such as its expiry.

Reelease does not sell this data, does not send you marketing communications outside the cases above and does not use it to make automated decisions with legal effects on you. Nothing the agent reads during a run is used to train AI models.

4. How long it is kept

  • Account, profile and sign-in: while the account is active. When the service ends, for 90 days so the customer can export its data or reactivate the service; then it is deleted.
  • Invitations: until they are accepted or withdrawn; expired ones are deleted after seven days.
  • Trial follow-up email address: until the email is sent, one day after the trial space expires, or until you unsubscribe; then it is deleted.
  • Activity and security logs: as long as needed for the security and auditing of the service, with the retention periods the customer configures per system and, if there is one, for as long as a legal hold lasts.
  • Product usage: 400 days.
  • Support: while the request is handled and the relationship with the customer lasts; closed requests from people without an account, for at most two years from the last message.
  • Billing: the periods required by tax and commercial law, generally up to six years.

After those periods, the data is deleted, except data that must be kept blocked under a legal obligation and only for as long as that obligation lasts. Backups are deleted in their ordinary retention cycle.

5. Providers

Reelease does not share this data with third parties unless required by law. To provide the platform, it relies on these providers, which process it on its behalf as processors:

  • Google Cloud (Madrid): platform services.
  • Neon (Frankfurt): database.
  • Resend: delivery of sign-in links, invitations and notices.
  • Microsoft: the corporate email service Reelease uses for support.
  • Cloudflare: checking that whoever signs in, signs up or requests a trial space is a person (Turnstile).

In addition, Stripe manages plans and payments: it receives the name and email of each account when it is created, charges subscriptions and issues invoices; for some purposes, such as fraud prevention, it acts as an independent controller under its own privacy policy. If you sign in with GitHub, GitHub processes your account under its own policy.

The list of subprocessors gives the region and transfer mechanism of each provider.

6. International transfers

Reelease services run on Google Cloud, in Madrid, and the database on Neon, in Frankfurt. Some providers, such as email delivery, payments, bot protection and GitHub sign-in, may process data in the United States. In those cases, the transfer relies on the EU-U.S. Data Privacy Framework, where the provider is certified, or on the standard contractual clauses approved by the European Commission.

7. Your rights and how to exercise them

You can exercise your rights of access, rectification, erasure, objection, restriction and portability, and withdraw any consent you have given, by writing to info@reelease.io or to Ronda de Azkue, 1, planta 13, Torre BEC, 48902 Barakaldo (Bizkaia), Spain. Reelease will reply within one month.

If your request concerns data Reelease processes on behalf of the customer, such as the content of run records, Reelease will pass it on to the customer, which decides on that data, and will help it respond.

If you believe your request has not been handled properly, you can lodge a complaint with the Spanish Data Protection Agency (www.aepd.es).

8. Security

Reelease applies technical and organizational measures appropriate to the risk: encryption in transit and at rest, personal accounts, role-based access control and activity logging. The data processing agreement describes them in more detail.

The platform uses technical cookies: the session and sign-in cookies, the language cookie, the one that remembers the state of the menu and the light or dark theme cookie, which it shares with reelease.io. For seven days it also keeps two cookies that remember which page and which campaign you came from when signing up. It uses no third-party analytics.

9. Changes to this policy

Reelease may update this policy. Changes are published on this page with their version date and, if they are substantial, announced in the platform. Questions about this policy 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.