Privacy Policy

This policy describes what personal data the Ryse application, operated by The Wellness People SRL (Rue Faider 79, 1050 Bruxelles, Belgique), collects, how it uses that data, who it shares it with, how it protects it and how long it keeps it. It covers the rysepro.com website, the Ryse application and the booking pages published by the professionals who use it. All processing complies with the General Data Protection Regulation (GDPR) and Belgian law.

This is a translation of the French version, which is the reference document in case of discrepancy: rysepro.com/confidentialite.

1. Data controller

The Wellness People is the controller for the data of the professionals using Ryse and of the visitors of rysepro.com. For the data a professional records about their own clients, the professional is the controller and Ryse acts as a processor, using that data only to provide the service.

For any question, access request or deletion request, contact us at [email protected].

2. Data we collect

Account and contact data: last name, first name, email address, phone number, occupation, and any information you provide when signing up or requesting access.
Service usage data: the information about your activity (clients, appointments, services) that you enter into Ryse to run your business.
Technical data: connection data, IP address, timestamps and technical logs needed to operate, troubleshoot and secure the service.
Analytics data: pages viewed and actions performed in the application, to understand usage and fix defects.
Data received from Google APIs: only if you enable calendar synchronisation yourself (section 4).

Online payments, where applicable, are handled by our payment provider: card numbers are entered directly with that provider and are never processed or stored by Ryse.

3. Sensitive data

Some of the data above requires stronger protection. We treat it as sensitive data and apply the measures described in section 6:

data received from your Google account (calendar), which the Google API Services User Data Policy classifies as sensitive;
authentication credentials and secrets: passwords, OAuth access and refresh tokens;
appointment data, including the titles of the events imported from your Google Calendar, which may reveal information about a person's private life and, depending on the service, about their wellbeing.

Ryse does not request or knowingly collect health data, banking data, political, religious or trade-union opinions, or data about sexual orientation or ethnic origin. Please do not enter such data in the free text fields of the application.

4. Google Calendar synchronisation

Calendar synchronisation is optional: it only starts if you connect your Google account yourself from Ryse, through the Google consent screen.

4.1 What Google data we access

Your Google identity (account identifier and email address, through the openid and email scopes): to know which account the connection belongs to and to avoid duplicates.
Your calendars (scope https://www.googleapis.com/auth/calendar): the list of your calendars, so that you can choose which ones to read and which ones to write to, then the events marked “busy” in the calendars you selected. Of those events, we only store what is described in 4.2.

4.2 How we use that data

Writing to the calendars you designate: appointments and unavailabilities created in Ryse are written to the Google calendar(s) you pick in your settings — your primary calendar by default. You can change that selection at any time; unticking a calendar removes from it what Ryse had written there.
Reading busy times: from the calendars you select, Ryse only keeps, for an event marked “busy”, its date, start time, end time and title in order to block the matching slot in your Ryse schedule.
Event title: the title is imported and displayed in your Ryse schedule so that you can recognise your own commitments. It is visible to you only, inside your account: it never appears on your booking pages nor to your clients, who only see that a slot is unavailable, without knowing why.
Never stored, under any circumstances: the description, location, attendees, attachments and video-conference links of your events are never stored, displayed or transmitted.
Read only: your existing Google events cannot be edited or deleted from Ryse. Ryse only creates, updates and deletes the events it created itself.
Exclusive purpose: this access is used solely to provide the calendar synchronisation you enabled. It is never used for advertising, profiling, or training artificial intelligence models.

4.3 Who this data is shared with

Nobody. Data received from Google APIs is never sold, rented, assigned or transferred to third parties, data brokers, advertisers, analytics tools or providers of artificial intelligence models. It is only accessible to you, within your account, and to our hosting provider, which stores the database without accessing it. It could only be disclosed to a competent authority where the law requires it.

4.4 How we protect it

Encryption in transit: all exchanges with Google and with the application use HTTPS (TLS 1.2 or higher).
Encryption of tokens at rest: your OAuth refresh token is encrypted with AES-256-GCM before being stored. The encryption key is held outside the database, in the protected server configuration: a copy of the database alone cannot reveal the tokens.
No secrets in logs: tokens are never displayed in the interface, written to technical logs, or sent to our analytics tools.
Per-account isolation: every request is authenticated and checked, and can only reach the data of the signed-in account. Imported calendar titles are not exposed by any public page or by any interface available to your clients.
Data minimisation: we only request the scopes required by the feature, and we only store the calendar content described in 4.2.

4.5 Retention, deletion and revocation

Imported busy slots and events created by Ryse are kept only for as long as the Google connection remains active.
When you disconnect your Google account from Ryse, we close the notification channels, remove from your Google calendars the events Ryse had written there — and only those — then immediately delete the encrypted token and the imported slots from our databases. They also disappear from backups within 30 days at most.
You can also revoke Ryse's access at any time from your Google account security settings, or ask us to delete this data by email at [email protected] (handled within 30 days at most).

4.6 Limited Use

Ryse's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In particular, Ryse does not use or transfer data received from Google APIs for targeted or personalised advertising, does not sell it to third parties or data brokers, does not use it to train or improve generalised artificial intelligence models, and does not use it for credit or lending decisions. No human reads this data, except with your explicit and specific consent to resolve an incident, for security purposes, or where required by law.

5. Legal bases and purposes

Performance of the service (contract): managing your account and providing Ryse's features.
Consent: Google Calendar synchronisation, marketing communications and waiting-list sign-up.
Legitimate interest: security, fraud prevention and improvement of the service.
Legal obligation: retention of certain data where the law requires it.

6. Security: how we protect your data

We implement technical and organisational measures appropriate to the risk, reinforced for the sensitive data listed in section 3.

6.1 Technical measures

Encryption in transit: the website, the application and the API are only reachable over HTTPS (TLS 1.2 or higher), with automatically renewed certificates. No cleartext access is offered.
Encryption of secrets at rest: Google OAuth tokens are encrypted with AES-256-GCM using a dedicated key stored outside the database. The encryption is authenticated: any tampering with the stored content is detected.
Passwords: they are never stored in cleartext or in any reversible form. They are hashed with Argon2, the currently recommended password hashing function. Nobody on our side can read them.
Application access control: authentication with a signed token, session expiry, and a check on every request that the requested data belongs to the signed-in account (strict isolation between professionals).
Hosting: servers located in the European Union (Frankfurt, Germany), with DigitalOcean, LLC. The database is not exposed to the public internet and is only reachable from the application.
Logs and internal tools: technical logs contain no passwords and no tokens. Session recordings used to troubleshoot a bug systematically mask the content of input fields.
Backups: backups are kept within the European Union and subject to the same access restrictions as production data.
Updates: servers and software dependencies are kept up to date, and security patches are applied without undue delay.

6.2 Organisational measures

Least privilege: access to production data is limited to the people who need it to operate the service, through named accounts protected by strong authentication.
We do not read your data: we only access the content of your account at your request (support), in the event of a security incident, or where the law requires it.
Confidentiality: everyone with access to the data is bound by a confidentiality obligation.
Vetted processors: our providers are selected for their security guarantees and bound by a data processing agreement compliant with article 28 of the GDPR.
Privacy by design: every change involving sensitive data is designed according to the principles of data minimisation and protection by default.

6.3 In the event of a data breach

In the event of a personal data breach likely to create a risk to your rights, we notify the competent data protection authority within 72 hours of becoming aware of it and, where the risk is high, we inform you directly and without undue delay, stating the data concerned and the measures taken.

No system is infallible: if you notice a vulnerability or suspicious behaviour, write to us at [email protected]; we handle such reports as a priority.

7. Processors and recipients

We rely on providers that process data on our behalf, in compliance with the GDPR and under a data processing agreement:

DigitalOcean, LLC: hosting of the servers and of the database (European Union, Frankfurt, Germany);
Brevo: sending emails and managing contacts;
Stripe: processing online payments, where the professional enables them;
PostHog: product analytics and technical troubleshooting of the application. Input fields are masked and no data received from Google APIs is sent to it;
Google: calendar synchronisation, only when you enable it.

We do not sell your personal data and do not share it with any other third party. It may be disclosed to a competent authority where the law requires it.

8. Transfers outside the European Union

Our hosting servers and our backups are located in the European Union. Some providers (Google, Stripe, PostHog) may process data outside the EU; those transfers are covered by appropriate safeguards, in particular the European Commission's standard contractual clauses and, where applicable, the EU / US Data Privacy Framework.

9. Retention periods

Account and activity data: kept for as long as your account is active, then deleted within 30 days of its closure, unless the law requires longer retention (accounting records, for instance).
Data received from Google APIs: deleted as soon as you disconnect your Google account (section 4.5).
Technical logs: 12 months at most.
Waiting-list contacts: until they unsubscribe.

10. Deleting your data

At any time, you can:

disconnect your Google account from the Ryse settings: the token and the imported slots are deleted immediately;
request the deletion of your account and its data by writing to [email protected] from the email address of your account. We acknowledge receipt within 72 hours and complete the deletion within 30 days at most, backups included, except for data the law requires us to keep. We confirm the deletion by email.

11. Your rights

Under the GDPR, you have the right to access, rectify, erase, restrict, object to and port your data, as well as the right to withdraw your consent at any time. To exercise these rights, write to us at [email protected]; we answer within one month. You may also lodge a complaint with the Belgian Data Protection Authority (autoriteprotectiondonnees.be) or with the data protection authority of your country of residence.

12. Cookies

Ryse only uses the cookies strictly necessary to operate the service and maintain your session, plus one analytics cookie used to understand how the service is used. No advertising cookie is set.

13. Minors

Ryse is a professional tool. It is not directed at minors under 16 and does not knowingly collect their data. Should such data reach us, we would delete it upon notice.

14. Changes

We may update this policy. In the event of a substantial change, we will inform you by an appropriate means before it takes effect. The date of the latest update appears at the top of this page.