DeizDeiz has different responsibilities.
Deiz determines the processing needed for account creation, subscriptions, security, support and its own billing. For these purposes, Deiz acts as the data controller.
You decide why and how the data is used. Deiz provides the software and acts as a data processor under the DPA (in French).
The patient information page (in French) describes only what happens in Deiz. It does not replace your practice’s own GDPR privacy information.
Three levels of protection coexist.
1. Encryption in the browser
The main identity and care-related fields are encrypted on your device before they are sent: last name, first name, date of birth, address, session notes, questionnaires, waiting-list notes and detailed invoice content.
When an account is created, Deiz enables managed protection by default. The key remains encrypted, but a recovery copy is wrapped using a server key to allow access to be restored after authentication. This mode protects stored data, but it is not strict end-to-end encryption because Deiz retains the technical ability to recover the key.
You can enable personal protection in Settings > Security. Your key is then protected by your master password, passkeys or recovery codes. Your master password is not sent to Deiz. In this mode, Deiz does not have the normal means to decrypt these fields.
2. Encryption at rest, readable by the server
To send a confirmation, reminder, invoice or management link, Deiz must be able to use the patient’s email address and phone number. These copies remain encrypted when stored. Some credentials for connected services, such as Mobupay or SuperPDP, and documents prepared for sending receive the same protection.
3. Technical and financial data
Identifiers, dates and times, statuses, appointment modalities, prices, amounts, currencies, jurisdictions, payment references and technical logs must remain usable by the application. They do not always contain a name, but may enable indirect identification and are still treated as personal data when they relate to a person.
Processing related to your account.
| Purpose | Main data | Legal basis | Retention period or criterion |
|---|---|---|---|
| Create and operate your account | Email, professional identity, profession, settings and login logs | Pre-contractual steps and performance of the contract | While the account is active; active data is then deleted within 30 days of closure. RDS backups are kept for up to 7 days after active deletion. |
| Manage the Pro plan and payments | Stripe or bank transfer identifiers, billing data, amounts and statuses | Performance of the contract and accounting obligations | While the clinician’s account is active. Deiz facilitates export so the clinician can choose their own archiving solution. |
| Support | Messages, contact details, attachments and relevant identifiers | Provision of the service and legitimate interest in responding | Up to 3 years after the last exchange, unless a dispute is ongoing |
| Security and diagnostics | Technical traces, IP address, errors and relevant identifiers | Legitimate interest in securing and diagnosing the service | Up to 12 months for logs controlled by Deiz; the applicable plan’s retention period for Sentry/Grafana |
| Public profile and visibility | Professional name, profession, locations, phone number, public consultation types and availability | Pre-contractual steps and performance of the contract at the practitioner’s request | Until publication or the integration is disabled |
The legal bases and retention periods for patient records are determined by the practitioner acting as controller, not by Deiz.
The account email address and minimum professional information are required to create, secure and operate the service. Without them, Deiz cannot open the account or provide the corresponding features. Deiz does not make decisions producing legal or similarly significant effects on the user solely on the basis of automated processing within the meaning of Article 22 of the GDPR.
What the server processes for your patients.
Identity, date of birth, address, notes, questionnaires, session details, billing information and other fields entered in the record.
Email address and phone number, so the server can send the requested communications.
Appointment dates, times, status and modality, location, price, invoice and payment, currency, jurisdiction, relationship identifiers and delivery logs.
An invoice or document may be made readable for the time needed to send it by email, make it available on the portal or transmit it for electronic invoicing. Any temporary copy is deleted once that operation is complete, or when the workflow’s scheduled expiry is reached if the operation fails.
Your listing in AI assistants.
When you enable your profile’s listing, Deiz makes your public booking information available through its search API and MCP (Model Context Protocol) server without authentication. Deiz performs this processing to provide the visibility service you requested, on the basis of performance of the contract.
MCP responses contain your professional name, profession, profile and booking links, public consultation types, any Mon soutien psy designation declared by the practitioner, their duration and price where provided, currency, consultation locations with known geographical coordinates or video modality, time zone and available slots. Technical identifiers and the calculation date accompany this information. This tool does not provide any patient record, name, contact details or booked appointment.
Recipients are the people, applications and AI assistant providers querying this public service. Those services may process responses under their own rules and from other countries; their privacy policies describe their uses, retention periods and applicable safeguards. Access to public information does not give them access to your practice’s private data.
Disabling listing excludes your profile from new MCP searches without waiting for availability to refresh. The page may remain accessible through its direct link. Disabling listing does not erase responses already received or retained by a third party; requests about those copies must also be directed to that third party.
If you use an assistant to search for an appointment, Deiz receives the criteria sent by that assistant: profession, optional city or geographical point and requested radius, office or video consultation, optional Mon soutien psy filter, dates and pagination parameters, as well as the technical data needed for the request. Do not send names, contact details or medical information. The geographical point is used only as the centre of the requested search; it is not included in the public offers returned and is not sent to a third-party geocoding service by MCP. Booking and entry of contact details continue on Deiz. See the MCP documentation (in French) for details.
Third-party services: who receives what.
Each provider is used for the infrastructure or feature indicated. Integrations marked optional are used only when the corresponding feature is enabled. Processing regions, further subprocessors and transfer safeguards are also governed by each provider’s contracts and policies.
| Service | When | Data involved | Provider information |
|---|---|---|---|
| AWS Infrastructure | Production | HDS-certified hosting in Paris, SES emails, SNS SMS, backups and technical data. An email may contain dates, links and attachments. An SMS contains the number and reminder text. | AWS privacy HDS certification |
| Cloudflare Turnstile Bot protection | Registration, booking and protected public forms | Verification token, IP address and browser technical data. Deiz does not send clinical notes. | Cloudflare privacy |
| Infomaniak kMeet Optional | Video consultation | Opaque room identifier, the label “Consultation”, a generic patient display name or the practitioner’s name, network data and audio/video streams. Deiz does not receive or record audio/video content. | Infomaniak privacy (in French) |
| Google Meet Optional | If you choose Google Meet for video consultations | Google Calendar event and meeting creation request. During the call, Google processes audio/video streams, participation information and technical metadata, including IP address, call dates, times and durations. Call history may be retained depending on the account and Google settings. Deiz stores the meeting link without receiving or recording the conversation. | Google Meet privacy Google privacy policy |
| Zoom Optional | If you connect your Zoom account and use it for video consultations | Practitioner’s Zoom account ID and email, connection permissions, scheduled meeting time and duration, meeting ID and join link. Zoom processes audio/video streams and participation data during the call. See the Zoom integration details. | Zoom privacy statement |
| Google OAuth, Gmail and Calendar Depending on use | Google sign-in, administrative/support emails or enabled synchronization | Practitioner’s Google account, connection permissions and messages sent to a Deiz Gmail inbox. For events and the selected calendar, see the Google Calendar synchronization details. | Google privacy |
| Reserve with Google Optional | Google visibility and booking | Practitioner’s public information, locations, consultation types, prices, links and availability. Feeds do not contain patient records. | Google privacy |
| Stripe Billing and Connect Optional | Pro subscription, EUR payments or saved card | Practitioner’s email and identifiers for the subscription. For a patient: email, amount, currency, invoice reference and technical identifiers. Card and KYC details are entered with Stripe; Deiz stores neither PAN nor CVC. | Stripe privacy |
| Mobupay / Monext Optional, New Caledonia | Advance payment or XPF payment | Amount, opaque reference, purpose, technical URLs, language and expiry. Deiz does not add the patient’s name, email or phone number to the Mobupay request. Card details are entered on the provider’s checkout. | Mobupay website |
| SuperPDP Optional, Pro France | Requested electronic invoicing and e-reporting | For a B2B invoice: the complete Factur-X PDF and the invoice’s legal, tax and accounting data. For B2C: transaction aggregates without patient identity. Payments needed for reporting may also be transmitted. | SuperPDP website |
| Pennylane Optional connection | Invoice transmission and electronic invoicing | The complete Factur-X PDF and the invoice’s legal, tax and accounting data. | Pennylane privacy (in French) Pennylane providers (in French) |
| Sentry and Grafana Cloud Diagnostics | If configured | Errors, traces, metrics, environment and technical identifiers. Deiz aims to limit these flows to diagnostics, but an error may contain a personal reference or a provider’s technical response. | Sentry privacy Grafana privacy |
Connecting to Pennylane
The practitioner enables export for administrative and accounting management. It covers complete billing documents, which may reveal the use of a healthcare professional even when the service is VAT-exempt. Session notes, questionnaires and other record documents are not transmitted by this integration. The practitioner must limit invoice descriptions to the necessary information and inform the people concerned about this recipient; they determine the appropriate legal basis and, where health data is involved, the applicable condition under Article 9 of the GDPR.
Deiz keeps an encrypted copy of the PDF to be exported, Pennylane company and document identifiers, export and payment statuses, and the technical information needed for tracking. Connection tokens are encrypted on the server and deleted on disconnection. Documents and export history remain stored with the invoices in Deiz under the retention rules described in this policy.
Disconnection suspends exchanges, subject to any operation already in progress, and does not erase copies Pennylane has already received. Their retention and requests for access, return or deletion are also governed by the practitioner’s contract with Pennylane. Pennylane’s roles for each type of processing are described in its privacy policy and the data processing agreement attached to its terms. Deiz’s hosting safeguards in Paris do not automatically extend to copies sent to that service.
Public services, such as the French Annuaire Santé directory or French geocoding APIs, may receive the practitioner’s professional identity or address. They do not receive patient records in the identified requests.
Some providers may process data from other countries. Depending on the recipient, safeguards rely on an adequacy decision, the Data Privacy Framework, the European Commission’s standard contractual clauses or another mechanism provided for by the GDPR. A copy or reference to the applicable safeguard can be requested at audren.bdb@gmail.com.
Data used to synchronize Google Calendar.
When you enable synchronization, Deiz uses the connected Google account, selected calendar and chosen synchronization directions. Connection tokens are encrypted at rest. Identifiers and technical information are used to track updates.
If you choose Google Meet in Settings > Calendar, you ask Deiz to create a Google Meet meeting for your video consultations through your Google Calendar connection. The link is added to the event in the selected calendar and stored in Deiz to redirect you and the patient to it. For an existing event without a Meet link, Deiz may add the meeting when the video link is opened. Events needed for Google Meet may be created even if general appointment export is disabled. Deiz does not add the patient as a Google guest or enable conversation recording.
From Google to Deiz, events are imported as unavailable time. Deiz stores their title, start and end dates and times, and Google identifier. Event status allows deletions to be taken into account.
From Deiz to Google, appointments are created, updated or deleted in the selected calendar. Deiz sends the times, time zone, a title based on the consultation type or the title entered for a professional engagement, an indication of modality where applicable, and technical identifiers. The description contains a link to the patient’s care record in Deiz, accessible after authentication.
Data used for your Zoom video consultations.
Connecting to Zoom is optional and authorized by the practitioner from their Deiz account. Deiz uses the Zoom account ID and email address to associate it with the correct practitioner, along with the permissions needed to create a meeting and retrieve its access links. This data is used to operate the requested integration as part of the Deiz service.
When the Deiz link for an appointment using Zoom is first opened, Deiz requests creation of a meeting with the date, time, planned duration and generic title “Consultation”. This request does not contain the patient’s name, email or phone number, clinical reason, session notes or questionnaire answers. The waiting room is enabled and Deiz does not enable automatic recording.
Deiz stores the Zoom account ID and email, access and refresh tokens encrypted on the server, and the ID and join link for each meeting created, associated with the appointment. This allows the same meeting to be joined without creating a new one each time the link is opened. The host-only link is retrieved for the authenticated practitioner; it is not stored in the database or shared with the patient.
Connection data is retained while the integration is linked to the Deiz account. Meeting associations are retained while the corresponding appointments and integration exist. When disconnection from Settings > Integrations succeeds, Deiz revokes Zoom authorization and deletes connection data, tokens and meeting associations from its active database. Deleting the Deiz account also deletes this data; backup copies expire according to the period specified in this policy. Revocation directly in Zoom is detected when a token is refreshed or the API denies access, and does not trigger immediate deletion of all local data. You can disconnect the integration in Deiz or request deletion using the contact in the Your rights section.
Disconnection does not delete meetings already created in your Zoom account. Likewise, editing or deleting an appointment in Deiz does not automatically update or delete a meeting already created in Zoom. You can manage those meetings directly in Zoom.
During the call, Zoom processes audio/video streams, display names entered by participants, participation information and technical data such as IP addresses. Deiz does not receive or record the content of Zoom conversations. Zoom’s retention of this data and any recordings depend on the account, features used and Zoom settings. Deiz’s hosting safeguards in Paris do not extend to Zoom: processing locations, international transfers and the exercise of rights with Zoom are described in its privacy statement. The practitioner informs patients about the use of this service for video consultations.
Your rights and who to contact.
For your Deiz account data, you can request access, rectification, erasure, restriction, objection or portability where the corresponding right applies. You can also lodge a complaint with the CNIL.
For patient records for which you are the controller, Deiz provides tools to view, edit, delete and export data, and assists you within the service’s technical limits.
Cookies and external resources.
Deiz does not integrate advertising tools or marketing profiling into its interfaces. Strictly necessary cookies or local storage are used for sessions, security and preferences.
Some interfaces load resources directly from providers, such as Stripe.js, the Mobupay SDK, Turnstile, fonts or external libraries. The provider then receives at least the usual technical data associated with a web request, such as the IP address, browser and referrer.