Privacy policy

This policy describes the personal data processed by this website and by the hosted service Releo Cloud. An instance of Releo that you host yourself sends nothing to the Publisher: its operator is solely responsible for it.

1. Who is responsible

• Controller: WYATT GROUP (see the legal notice), for account management, billing, the security of the Service and this website.
• Processor: for the data your organization entrusts to the Service (invited members, builds, testers, devices), the Publisher acts on behalf of your organization, under the data processing agreement.

2. Data processed

Data	Source	Details
Account	you	Name, email address, hashed password (never stored in clear), preferred language, role in the organization. With single sign-on, the identifier provided by your identity provider.
Sessions	your browser	Session cookie, IP address and browser (user agent) of each session.
Store and tool credentials	you	App Store Connect API keys (.p8, Key ID, Issuer ID), distribution certificates, Google Play service account JSON keys, read-only git tokens, LLM provider keys, Android keystores. Encrypted at rest (AES-256-GCM) and never returned by the API.
Builds	you, your CI	.ipa / .aab binaries, version and build numbers, commit, release notes, history of uploads and promotions, uploader.
iOS testers	your testers	UDID, name, model and iOS version of the iPhone registered on a public page, to create an ad hoc profile.
Audit log	the Service	Action, actor, date and IP address (sign-ins, changes, downloads).
Billing	you, Stripe	Organization, plan, number of seats, subscription status. Card data is processed by Stripe and never goes through our servers.
Emails	the Service	Address and content of transactional emails (confirmation, password reset, invitations).
Website	your browser	Technical logs of the web server (IP address, requested page, date), for security.

3. Purposes and legal bases

• Providing the Service (accounts, upload and promotion of builds, public pages, release notes): performance of the contract.
• Billing subscriptions and bookkeeping: performance of the contract and legal obligation.
• Securing the Service (sessions, audit log, rate limiting, server logs): legitimate interest.
• Sending transactional emails: performance of the contract.

No data is used for advertising, sold, or used to train a model.

4. Recipients and subprocessors

The data is available to the Publisher and, depending on their roles, to the members of your organization. Subprocessors of the Publisher:

Subprocessor	Purpose	Location
OVH SAS	Hosting of the application, its database and the uploaded builds	France
Stripe Payments Europe, Ltd.	Payment of subscriptions and invoicing	Ireland (transfers to the United States under the EU-US Data Privacy Framework)
Resend, Inc.	Transactional emails (confirmation, password reset, invitations)	United States

On the instructions of your organization, the Service also sends data to services that you choose and configure with your own accounts:

• Apple (App Store Connect, TestFlight) and Google (Google Play): binaries, release notes, test devices;
• your git provider (GitHub, GitLab…): reading commits;
• your LLM provider (any OpenAI-compatible provider, for example OpenRouter): commit messages and release notes, to write or translate the notes. Nothing is sent to an LLM if your organization does not configure one.

These services act under their own terms, accepted by your organization.

5. Transfers outside the European Union

The data of the Service is hosted in the country shown for the hosting provider in the table above. A transfer outside the EU (Stripe, or a provider you choose) relies on an adequacy decision, such as the EU-US Data Privacy Framework, or on the standard contractual clauses of the European Commission.

6. Retention

• Account and content: as long as the account exists. After the deletion of the account or organization, erased within 30 days, then gone from the backups as they rotate (14 days).
• Binaries: only the most recent ones of each app and platform are kept; older ones are deleted automatically. Build metadata stays as long as the app exists.
• Sessions: until sign-out or expiry (30 days).
• Audit log: as long as the organization exists (the history shown depends on the plan).
• Invoices: 10 years (bookkeeping obligation).
• Web server logs: 12 months at most.

7. Security

Encrypted connections (HTTPS), hashed passwords, secrets encrypted at rest with AES-256-GCM, temporary credential files readable only by the process that calls the stores and deleted right away, roles per organization and per app, scoped API keys, audit log, regular database backups.

8. Cookies and local storage

• This website sets no cookie and contains no tracker nor audience measurement tool. If you pick a theme in the documentation, the choice is saved in your browser’s local storage.
• The Releo Cloud app sets a single cookie, the session cookie, strictly necessary to sign in. It keeps your language, theme and display preferences in local storage.

These are exempt from consent, so there is no cookie banner.

9. Your rights

You have the rights of access, rectification, erasure, restriction, objection and portability of your data. Write to contact@releo.app. For the data that an organization entrusted to the Service (for example as an invited member or a tester), contact that organization first; the Publisher will help it answer.

You can lodge a complaint with the French data protection authority, the CNIL, or with the authority of your country.

10. Changes

This policy may change with the Service. A significant change is announced by email to account holders.