The parties
This agreement is made between the practice that uses Praxamo, meaning the professional or healthcare organisation for which the practice was created on the platform (the “Practice”), controller of its patients’ data, and Praxamo, which provides the platform (the “Provider”) and is the processor.
- Contact for this agreement and for data protection: privacy@praxamo.it
The agreement implements Article 28(3) GDPR and forms an integral part of the Terms of service. For everything that concerns personal data protection, where the Terms and this agreement say different things, this agreement prevails.
Acceptance and versions
The Practice accepts this agreement when it is created on Praxamo, with a box of its own, separate from the one for the Terms. If the practice was created by the Provider and handed to its owner through an invitation, or existed before this agreement, a user with the owner role accepts it from the console, which shows a notice until someone does.
Every version has a code, shown at the top of this page. For every practice, the platform records the version accepted, the date and time of acceptance and the user who gave it. When the text changes, the new version must be accepted again; until then the version accepted earlier remains in force.
Subject matter and duration
The Provider processes personal data on the Practice’s behalf only to provide the Praxamo service described in the Terms: the practice’s website with its online booking page, the emails to patients (confirmations, reminders, notices of changes and cancellations and, if the Practice sends them, invitations to book), and the console to manage the diary, patients, services, locations, hours and team. The processing is described in detail in Annex I.
The agreement lasts as long as the contract for the use of the service. The obligations of confidentiality, return and deletion keep applying for as long as the Provider holds any of the Practice’s data.
Nature and purpose of the processing
The processing is carried out by electronic means and consists of collecting data (from the booking form on the Practice’s website or from the console), recording, organising, storing, consulting and altering it, sending service communications, backing it up, extracting it at the Practice’s request, and erasing it.
The purposes are only those of the service: managing the Practice’s bookings and diary, sending patients the communications the service provides for or the Practice decides to send, keeping the consents collected, publishing the Practice’s website, and keeping the service secure and running.
The Provider does not use patients’ data for its own purposes: it does not use it for advertising, does not sell it, does not use it to profile anyone and does not use it to train artificial-intelligence models.
Types of data and categories of data subjects
On the Practice’s behalf the Provider processes these types of personal data:
- patients’ identity and contact details: first name, surname, email address, telephone number, date of birth if the Practice records it, preferred language;
- appointments: date, time and length, service, practitioner, location or mode (in person or remote), status, the note the patient writes when booking and the notes the Practice adds;
- consents: the consents the patient gave or refused (for example to reminders), with date and time, the version of the text shown, IP address and browser;
- the communications log: which emails were sent, not sent or suppressed, to which address, when and with what outcome, never the text of the message;
- invitations: the email addresses to which the Practice sent an invitation to book, with date and outcome, and the addresses that asked not to receive further invitations;
- waiting list: people who ask to be told if a place becomes free, with the service and the period they want;
- the content of the Practice’s website: texts, photos, names, titles and contact details of the professionals and staff the Practice publishes.
Special categories of data (Art. 9 GDPR). An appointment with a health professional, such as a psychologist or a dentist, can reveal information about the patient’s health: the service therefore treats every appointment as data concerning health. The platform asks for no diagnosis and no clinical records; if the Practice writes health information in the notes, that too is data concerning health processed on its behalf.
Categories of data subjects: patients, people who book or request an appointment, people on the waiting list, people to whom the Practice sends an invitation, and the Practice’s professionals and staff, for the data the Practice records or publishes about them.
The Practice’s documented instructions
The Provider processes the data only on documented instructions from the Practice, including with regard to transfers to third countries, unless required to do so by European Union or Italian law; in that case it informs the Practice before processing, unless the law prohibits it.
The instructions are this agreement, the Terms of service and the choices the Practice makes when using the service: the configuration of the practice and every operation carried out from the console (for example creating, moving or cancelling an appointment, sending an invitation, publishing the website). Further instructions are given in writing to privacy@praxamo.it; if they require work beyond the service, the Provider may ask for a reasonable fee, agreed in advance.
If it considers that an instruction infringes the GDPR or other data protection rules, the Provider tells the Practice immediately and may suspend carrying it out until the Practice confirms or changes it.
Confidentiality of personnel
The Provider authorises to process the data only the people who need it to provide the service, and only once they have committed themselves to confidentiality or if they are under a statutory obligation of confidentiality. The Provider’s staff do not look at patients’ data, except where strictly necessary to resolve a problem reported by the Practice, for the security of the service or to comply with a legal obligation.
Security of processing
The Provider takes the technical and organisational measures required by Article 32 GDPR, appropriate to the risk of processing that concerns health data. They are described in Annex II. The Provider may update them as technology progresses, provided the level of protection does not decrease.
Sub-processors
The Practice gives the Provider general written authorisation to engage other processors (sub-processors). Those in use are listed in Annex III and, always current, on the Sub-processors page.
The Provider tells the Practice about any addition or replacement of a sub-processor at least 30 days in advance, by email to the users with the practice’s owner role. Within that period the Practice may object on reasonable data protection grounds by writing to privacy@praxamo.it. If no solution is found, the Practice may terminate the contract at no cost before the change takes effect.
The Provider imposes on every sub-processor, by a written contract, the same data protection obligations as in this agreement, in particular sufficient guarantees about security measures, and remains fully liable to the Practice for their performance.
Requests from data subjects
The Provider assists the Practice, by appropriate technical and organisational measures, in responding to requests by which data subjects exercise their rights under Articles 15–22 GDPR.
From the console the Practice can itself view and correct patients’ and appointments’ data. For requests the console does not let it fulfil directly, such as erasing a patient’s data or a copy of their data in a structured format, the Provider carries out the Practice’s written instructions within 10 working days.
If a data subject’s request reaches the Provider, the Provider does not decide on it: it forwards it to the Practice without undue delay, and in any case within 5 working days, and tells the data subject it has done so.
Personal data breaches
When it becomes aware of a personal data breach affecting the Practice’s data, the Provider notifies the Practice without undue delay and, where possible, within 24 hours, so that the Practice can meet the 72-hour deadline for notifying the Garante (Art. 33 GDPR). The notice goes by email to the users with the practice’s owner role.
The notice contains, as far as already known, the information in Article 33(3) GDPR: the nature of the breach, including the categories and approximate number of data subjects and records concerned; the name and contact details of a contact person at the Provider; the likely consequences; and the measures taken or proposed to address it and to mitigate its effects. Information not yet available is provided later, as it is established.
The Provider records every breach, immediately takes the measures to contain it, and assists the Practice in notifying the Garante and, where required, in communicating the breach to data subjects (Art. 34 GDPR).
Impact assessment and prior consultation
The Provider makes available to the Practice the information about the processing and the security measures it needs for its data protection impact assessment (Art. 35 GDPR) and any prior consultation of the Garante (Art. 36 GDPR): in particular the annexes to this agreement and the answers to questions the Practice sends in writing.
Return and deletion of data
When the contract ends, the Practice has 30 days to ask for a copy of its data: the Provider prepares it in a structured, commonly used and machine-readable format (for example CSV) and delivers it within 30 days of the request.
After that period the Provider deletes the Practice’s data from the database, unless European Union or Italian law requires it to be kept. The encrypted backups that still contain it are deleted within the following 35 days, when their retention period expires, and until then they stay encrypted and cannot be accessed by the service.
On request, the Provider confirms the deletion in writing.
Information and audits
The Provider makes available to the Practice all information necessary to demonstrate compliance with the obligations of Article 28 GDPR, and allows for and contributes to audits, including inspections, conducted by the Practice or by an auditor mandated by the Practice and bound by confidentiality.
Audits are agreed in writing with at least 30 days’ notice, normally no more than once a year except after a data breach or at the request of a supervisory authority, and are carried out without compromising the security of the service or the confidentiality of other practices’ data. Each party bears its own costs.
Transfers outside the European Economic Area
The Provider processes and stores the Practice’s data in the European Union and does not transfer it outside the European Economic Area, except in the cases stated for each sub-processor in Annex III, with the safeguards of Chapter V GDPR (an adequacy decision or standard contractual clauses). Any new case is notified to the Practice as a change of sub-processor.
The Practice’s obligations
The Practice, as controller, undertakes to:
- give patients the privacy notice: the platform publishes one on the Practice’s website from the details the Practice enters, and the Practice checks it is correct;
- have a legal basis for every processing it entrusts to the Provider, including the invitations to book sent by email, and collect the consents required;
- enter accurate and relevant data, and not write more health information in the notes than is necessary;
- manage its staff’s access to the console and revoke it when someone leaves the Practice;
- tell the Provider without delay about any suspected breach it becomes aware of.
Liability
Each party is liable for the damage caused by its own processing under Article 82 GDPR. Between the parties, the limitations of liability in the Terms of service apply; they do not apply in cases of wilful misconduct or gross negligence, nor where the law does not allow liability to be limited.
Changes to the agreement
The Provider may update this agreement, for example to reflect a new law or a change of sub-processor. Material changes are notified to the Practice at least 30 days before they take effect and must be accepted with the new version; if the Practice does not accept them, it may terminate at no cost. No change may reduce the guarantees for data subjects required by Article 28 GDPR.
Governing law and jurisdiction
This agreement is governed by Italian law. The competent court is the one stated in the Terms of service. If the Italian and English versions differ, the Italian version prevails.
Annex I: description of the processing
| Item | Description |
|---|---|
| Controller and processor | The Practice is the controller; Praxamo is the processor. |
| Service | The practice’s public website at the address it chose (for example your-name.praxamo.it), with the booking page; emails to patients; the console for the diary, patients, services, locations, hours and team; invitations to book sent by email in the practice’s name. |
| Data subjects | Patients; people who book or request an appointment; people on the waiting list; people the practice invites; the practice’s professionals and staff. |
| Data | Identity and contact details; appointments and notes; consents with their evidence; the communications log; invitations and unsubscriptions; the waiting list; website content. |
| Special categories | Data concerning health, because an appointment with a health professional can reveal it, and whatever the Practice writes in the notes. No clinical record or diagnosis is asked for by the platform. |
| Operations | Collection, recording, organisation, storage, consultation, alteration, sending service emails, backups, extraction on request, erasure. |
| Frequency | Continuous, for the whole term of the contract. |
| Retention | For the term of the contract, as the Practice decides; the communications log up to 12 months; unfinished provisional bookings 1 day after they expire; at the end of the contract, return and deletion as described in “Return and deletion of data”. |
| Location | European Union. Sub-processors and any transfers: Annex III. |
Annex II: technical and organisational measures
The measures the Provider applies today:
- Separation between practices enforced by the database: every table holding a practice’s data is protected by row-level security policies applied in forced mode, and an automated test that tries to read one practice’s data from another blocks every release if it fails.
- Least privilege in the database: the application connects with a role that neither owns the tables nor is an administrator, and with that role the audit log can be neither altered nor deleted.
- Encryption in transit: every page and every request goes over HTTPS (TLS).
- Minimal exposure: from the internet only the HTTPS reverse proxy can be reached; the database and the API accept connections only from the server itself, and the other ports are closed by the network firewall.
- Authentication: passwords stored only as hashes (scrypt), never in clear; two-step verification with TOTP codes available on every account and mandatory for platform administrators; revocable sessions that expire after 12 hours at most.
- Abuse protection: limits on the number of attempts per IP address for sign-in, sign-up, password reset and booking; every request that changes data must carry a header a foreign website cannot add (CSRF protection), on top of the SameSite session cookie.
- Audit log: every operation that changes data is recorded append-only, with who, what, when, outcome, IP address and browser, never the content of the data; the rows are chained by hashes, so any tampering is evident; the log is kept for 24 months.
- No clinical content in emails: communications to patients carry only the appointment’s details, never the Practice’s notes.
- Data minimisation: uploaded photos are re-encoded with their metadata removed, the GPS position included; diagnostics data keeps no IP addresses, link codes or search values.
- Technical logs kept for no longer than 12 months.
- Organisation: access to production systems only for authorised people bound by confidentiality; a written procedure for data breaches, with a breach register and notice to practices without undue delay.
Annex III: authorised sub-processors
The Practice authorises the Provider to engage these sub-processors, which are the ones the platform uses today:
| Provider | What for | What data it sees | Where | Transfers outside the EEA |
|---|---|---|---|---|
| Microsoft Azure (Virtual Machines)Microsoft Ireland Operations Ltd | Hosting of the platform and its database | All data the platform processes, encrypted in transit | European Union | Data stored in the European Union (EU Data Boundary). Exceptional access from the United States covered by the EU-US Data Privacy Framework and standard contractual clauses. |
| BrevoSendinblue SAS (Brevo) | Sending service emails (confirmations, reminders, sign-in) | Email address and message text, which carries no clinical information | European Union (France) | No transfer outside the EEA |
| Azure OpenAIMicrosoft Ireland Operations Ltd | AI-generated background for the practitioner’s photo (only on request) and a check of the address chosen at sign-up | The practitioner’s photo; the practice name, profession and chosen address. Never patient data | European Union | Data stored in the European Union (EU Data Boundary). Exceptional access from the United States covered by the EU-US Data Privacy Framework and standard contractual clauses. |
| Azure Monitor Application InsightsMicrosoft Ireland Operations Ltd | Error and performance diagnostics | Technical request data, without parameter values, tokens or IP addresses | European Union | Data stored in the European Union (EU Data Boundary). Exceptional access from the United States covered by the EU-US Data Privacy Framework and standard contractual clauses. |
The list is kept up to date on the Sub-processors page. Changes follow the procedure in the Sub-processors section.