Privacy Statement
O27

Contrôle documentaire

Référence
PUB-04-EN
Version
1.7
Statut
approuvé
Dernière mise à jour
2026-11-16
Commit
1738a79 (signature vérifiée)

Table of Contents

French version: Déclaration de confidentialité. The French version prevails in case of divergence.

Purpose

This statement describes the personal data O27 processes, why it processes it, with whom it is shared, how long it is kept, and the rights you have.

It covers O27's websites, the platform it operates and the products that platform carries, in particular Paraphe (shared inbox), Havre (platform for Belgian out-of-school care operators) and HeyJP (assistant for heating engineers).

Controller

Item Value
Operator O27 SRL
Company number BE 1044.535.392
Registered office Place du Nouveau-Monde 6, 5300 Andenne, Belgium
Data protection contact contact@o27.io

O27 SRL, incorporated on 27 October 2026, has taken over the processing previously carried out by POSTULA CONCEPTIONS SRL (BE 0775.772.346). The organisations using the service have been informed.

No data protection officer is appointed to date. The question is reviewed at each annual review of this statement.

Two distinct roles

O27 acts sometimes as controller, sometimes as processor. The distinction determines your rights and whom to address them to.

Role Data concerned
Controller Website visitors, prospects and contacts, user accounts, access logs
Processor Content entrusted by a customer organisation: messages, attachments, contacts, case records

For data processed as a processor, the controller is the customer organisation: your employer, your care operator, or the entity that opened your access. O27 processes that data only on their instructions and forwards any request to them.

Processing as a controller

Processing Data Legal basis Retention
Website visits IP address, user agent, timestamp, requested resource Legitimate interest (security) As set by the logging policy
User accounts Name, work address, role, authentication factors, identity of the Google or Microsoft account used to sign in Performance of the contract with the organisation Life of the account, then erasure
Access and security logs Account identifier, timestamp, action, IP address Legitimate interest (security), legal obligation As set by the logging policy
Enquiries and correspondence Name, address, content of the exchange Pre-contractual steps, legitimate interest Duration of the relationship, then limited archiving
Error monitoring Technical trace, account identifier, timestamp Legitimate interest (reliability) As set by the logging policy

No decision producing legal effects is taken on the sole basis of automated processing.

Processing as a processor

Where a customer organisation uses the platform, O27 processes on its behalf:

  • the content of messages synchronised from the connected mailbox: headers, bodies, attachments, threads;
  • the contact details contained in those messages: senders, recipients, signatures;
  • the case records entered in the product concerned, including, for Havre, data relating to minors and their legal guardians.

This data is used only to provide the service. It is not used to train models, and is neither sold, transferred, nor used for advertising or profiling.

Connecting a Google or Microsoft account

Paraphe uses your Google or Microsoft account in two distinct ways, both through OAuth 2.0: to sign you in to Paraphe, and to connect the mailbox you designate. You authenticate with your provider; O27 neither receives nor stores your password.

Signing in with Google or Microsoft

Where your organisation has not reserved sign-in to its own identity provider, Paraphe offers to sign you in with your Google or Microsoft account. It then requests identity permissions only:

Provider Scope What it allows Why it is requested
Google openid, email, profile Account identifier, address and whether Google has verified it, name, link to the profile picture, Google Workspace domain where there is one Authenticate you and find your account
Microsoft openid, email, profile Account identifier, address, name, and whether the address's domain is verified by its owner Authenticate you and find your account
Microsoft User.Read Reading the directory profile, of which Paraphe keeps only the identifier, display name, first name, surname, address and principal name Read the account's identifier and address

This data is used only to authenticate you and find your Paraphe account. A sign-in is linked to the account that already holds the same address only if the provider vouches for that address: verified by Google, or on a domain verified by its owner at Microsoft. Once signed in, you may also link, from your account, a Google or Microsoft account whose address differs from yours, and remove it in the same place. In every case, this data is stored with your account, as the link to your Google or Microsoft account, and deleted with it. No access or refresh token from this sign-in is kept: it opens no later access to your account.

Signing in with Google or Microsoft connects no mailbox and gives access neither to your mail nor to your calendar. The mail permissions below are requested only when you choose to connect a mailbox. The two stay separate: you may sign in with one account and connect another mailbox, and withdrawing access to a mailbox does not remove sign-in with your account.

Permissions requested

To connect a mailbox, Paraphe requests:

Provider Scope What it allows Why it is requested
Google openid Identifier of the authorising account Bind the connected mailbox to the account that consented
Google email Address of the authorising account Verify that the connected mailbox is the expected one
Google https://www.googleapis.com/auth/gmail.modify Read, compose, send, mark read and move to trash, through the Gmail API Synchronise messages into the shared inbox, send replies from your address, and reflect there what you do in Paraphe
Microsoft openid, email, profile Identifier, address and principal name Bind and verify the connected mailbox
Microsoft offline_access Refresh token Keep synchronising without prompting for authentication on every cycle
Microsoft https://graph.microsoft.com/Mail.ReadWrite Read messages, mark them read and move them to trash, through the Microsoft Graph API Synchronise messages into the shared inbox and reflect there what you do in Paraphe
Microsoft https://graph.microsoft.com/Mail.Send Send a message through the Graph API Send replies from your address

Paraphe reaches both providers through their APIs and no longer uses IMAP or SMTP. That is what allows these narrower permissions: gmail.modify is the smallest Google scope covering what Paraphe does, where the previously requested https://mail.google.com/ also permits the permanent deletion of your mail, which Paraphe never performs. gmail.modify remains a restricted scope and we use it for that purpose alone. The two Microsoft permissions are its Graph equivalents, requested for the same reason and no wider.

All of Paraphe's Microsoft permissions are delegated: Paraphe requests no Application permission. It acts on behalf of the user who connected the mailbox and reaches only what that user can access, which is their own mailbox; shared mailboxes would need Mail.ReadWrite.Shared, which Paraphe does not request. An administrator who consents for the whole organisation spares each user from consenting themselves and allows them to connect their own mailbox: Paraphe still has no access to the mailbox of a user who has not signed in to it. To reserve Paraphe to some users, the administrator turns on "Assignment required" in the properties of the Paraphe enterprise application in Microsoft Entra ID and assigns only those users or a group: an account that is not assigned can no longer sign in to Paraphe, except Global Administrators, whom Microsoft exempts from this rule.

Paraphe never permanently deletes a message. Deleting a mail in Paraphe moves it to your mailbox's trash, where you can retrieve it and where your provider's own retention rules apply. On Google that is also a technical limit: gmail.modify allows every read and write operation except immediate permanent deletion, which is precisely why the broader scope is no longer requested.

What we do with the data so obtained

Synchronised messages are stored in the customer organisation's space, isolated from the others, to power the features visible on screen: shared inbox, search, threads, conversation summaries, assistance in drafting replies.

The content of a message is submitted to a language model for the features that depend on one: at the user's request, or automatically when a message is received or sent, to classify it, prepare a draft reply and summarise the conversation. The model provider used is Mistral AI. Its qualification on three points, actual location of processing, commitment not to reuse data for training and retention of requests on the provider's side, is under way; the result will be recorded in the sub-processor register.

OAuth tokens are encrypted at rest and are exposed by no interface.

Google Limited Use disclosure

O27's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Withdrawing your authorisation

You may at any time:

  1. disconnect the mailbox from within Paraphe, which deletes the stored tokens and stops synchronisation;
  2. revoke access directly at your provider, at myaccount.google.com/permissions for Google, at myapps.microsoft.com or account.live.com/consent/Manage for Microsoft.

Revocation stops synchronisation. Paraphe appears at each provider as a single application, for sign-in and for the mailbox: revoking access there, even only to stop signing in with that account, may also stop synchronising a mailbox connected with the same account. Erasure of messages already synchronised is a matter for the customer organisation, as controller, under the terms of its contract.

Recipients

Data is disclosed only to the providers necessary to operate the service, bound by a processing agreement under Article 28 GDPR, except for the push notifications described below.

Provider Role Location
Hetzner Compute, storage, network, object storage Germany
OVH Storage of backup archives, encrypted European Union
Model providers Inference on content, for the features that depend on it See the register

The sub-processor register is kept up to date and provided to customers on request. Any addition or replacement is notified to them before it goes into service.

Your own mail or identity provider is not an O27 sub-processor: the mailbox and the account stay with them, under their contract with you.

Push notifications. If you turn on notifications for an O27 app or site, they reach you through the service of your phone or browser. For the apps, O27 uses Apple (Apple Push Notification service, iPhone and Safari) and Google (Firebase Cloud Messaging, Android). Google acts as a processor; Apple offers no processing agreement for this service and applies its developer terms. For a site's notifications, the service is your browser vendor's (Google, Apple, Microsoft or Mozilla), chosen by the browser and not by O27. These services receive an identifier for your device, and the time and size of each notification. A notification carries no data from your organisation: no message subject or sender, no customer's or person's name; only a generic label. The content appears once the app is open.

Data may also be disclosed to an authority where a legal obligation requires it.

Transfers outside the European Union

The main infrastructure and backups are hosted in the European Union. This does not guarantee that all processing and provider access remain within the Union. Processing locations, subprocessors and any applicable transfer safeguards are specified in the register supplied to customers before the relevant service is used. Model providers are listed there with the state of their qualification.

Apple's and Google's push notification services process your device identifier outside the European Union, in particular in the United States, with no option to keep it in the Union. For Google, the transfer relies on the EU-US Data Privacy Framework and, failing that, on standard contractual clauses. For Apple, the mechanism is stated in the register supplied to customers; no notification goes through Apple before it is established.

Slack and Linear support internal coordination and task tracking. Customer content is not permitted there; bug reports use test data or fully redacted screenshots. Staff account data remains processed by these providers under their applicable agreements.

Retention and erasure

Data Retention
Synchronised messages and attachments While the mailbox is connected, then as set by the customer contract
OAuth tokens Until the mailbox is disconnected or access revoked at the provider
Notification device identifier Until notifications are turned off, you sign out, or the service reports the identifier is no longer valid
User accounts Life of the account, then erasure
Access and security logs As set by the logging policy
Backup archives Encrypted, purged at the end of their retention cycle

At the end of the contractual relationship, the customer organisation's space is purged, backups included once their cycle expires.

Security

Encryption in transit on every access, backup archives and operating secrets encrypted at rest, named accounts, multi-factor authentication, separate spaces per customer organisation, access logging, backups whose restoration is exercised.

The full description is provided to customers and prospects on request, at the contact address above. Vulnerabilities are reported to that same address.

Cookies

O27's public websites are static and set no cookies.

The application sets only the cookies necessary for it to work: authenticated session, cross-site request forgery protection and, if you choose to trust your device, a cookie that spares you the second factor for fourteen days. No advertising cookies, no third-party analytics trackers.

Your rights

Under the conditions of Articles 15 to 22 GDPR you have the right of access, rectification, erasure, restriction, objection and portability, and the right to withdraw consent at any time without affecting the lawfulness of processing carried out beforehand.

  • For processing where O27 is the controller, address your request to the contact above. It is answered within one month, extendable by two months where the request is complex.
  • For data processed as a processor, address the customer organisation. A request received by O27 is forwarded to them without delay.

You may lodge a complaint with the Belgian Data Protection Authority, Rue de la Presse 35, 1000 Brussels, dataprotectionauthority.be.

Changes to this statement

Any substantial change is communicated to customer organisations before it takes effect. The date of last update and the corresponding commit appear in the document control block of this page.