Data processing agreement

Version
2026-10-19
Effective

This is a previous version. The current version is 2026-11-17, effective 2026-11-17.

Read the current version

This Data Processing Agreement ("DPA") is between Salisan, Inc., a Delaware corporation with its registered address at 2261 Market Street STE 38901, San Francisco, CA 94114, United States ("Salisan", "we", "us"), and the organisation that has accepted our Terms of Service ("Customer", "you"). It forms part of the Terms and sets out how we process personal data on your behalf when we provide the Service.

This version applies to Customers whose organisation's main country is a Member State of the European Union or the European Economic Area. It applies to all our processing of Customer Personal Data. An Account Owner accepts it in the Service together with the Terms. A new organisation accepts it before it enters Patient Data, and an existing Customer has 14 days from the date this version takes effect to accept it. Records in the Service always stay readable; until an Account Owner has accepted, your organisation cannot add or change Patient Data in the Service or use its AI features.

1. Definitions and interpretation

1.1 Terms defined in the Terms. Service, Order, Authorised User, Customer Data, Patient Data and AI Output have the meaning given in the Terms of Service ("Terms"). "Agreement" means the Terms, any Order and this DPA.

1.2 Further definitions.

  • GDPR: Regulation (EU) 2016/679.
  • Data Protection Law: the GDPR and the laws of the European Union and its Member States that supplement it and apply to the processing under this DPA, including the Dutch GDPR Implementation Act (UAVG) and the German Federal Data Protection Act (BDSG).
  • Customer Personal Data: personal data in Customer Data that we process on your behalf to provide the Service.
  • Personal Data Breach: a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Customer Personal Data that we or our Subprocessors process.
  • Subprocessor: a processor that we engage, or that a Subprocessor engages, to process Customer Personal Data.
  • SCCs: the standard contractual clauses annexed to Commission Implementing Decision (EU) 2021/914 of 4 June 2021, completed as set out in Annex 4.
  • Account Owner: a member of your organisation in the Service who holds the owner role.
  • Representative: our representative in the European Union under Article 27 GDPR, named in section 17.

1.3 GDPR terms. Controller, processor, data subject, personal data, processing, special categories of personal data and supervisory authority have the meaning given in the GDPR.

1.4 Interpretation. "Including" means including without limitation. Headings are for convenience only.

2. Scope and roles

2.1 Roles. You are the controller of Customer Personal Data and we are your processor. Where you process Customer Personal Data as a processor for another controller, you confirm that your instructions are authorised by that controller, and we act as your subprocessor.

2.2 Subject matter and details. We process Customer Personal Data to provide the Service under the Agreement. Annex 1 describes the data subjects, the categories of personal data, the nature and purposes of the processing and its duration, for each area of the Service.

2.3 Our own data. We are the controller of personal data we process for our own purposes: accounts and sign-in, billing, support, the security of the Service and the technical and usage data described in section 5.5 of the Terms. Our Privacy Policy describes that processing. This DPA does not apply to it.

2.4 Your responsibilities. You are responsible for the lawfulness of the processing you instruct, including having a lawful basis and, for health data, a condition under Article 9 GDPR; for informing patients and other data subjects; for meeting your record-keeping and professional secrecy obligations; and for not submitting the data that section 7.6 of the Terms prohibits to the AI features.

3. Instructions

3.1 Documented instructions. We process Customer Personal Data only on your documented instructions, including with regard to transfers to a third country, unless European Union or Member State law to which we are subject requires otherwise. In that case we inform you of that legal requirement before processing, unless that law prohibits it on important grounds of public interest. Your instructions are:

  • (a) the Agreement, including this DPA;
  • (b) your and your Authorised Users' use and configuration of the Service, such as creating and changing records, sending emails, forms and letters, using AI features, setting retention options, excluding patients from AI, and starting exports, patient erasure or offboarding; and
  • (c) any other written instruction that you give us and that we agree to, for example by email to privacy@salisan.com.

3.2 Service statistics. You instruct us to produce aggregated statistics on the use of the Service, to operate and improve it (section 5.4(a) of the Terms). We compute one operational figure per practice per month, such as counts, rates and durations of appointments, visits, forms, requests and tasks. We do not use clinical values, free text or patient or staff identifiers. Demonstration organisations and patients who are excluded from analytics are left out. We store and show only medians and quartiles across at least 10 practices, never a figure for an individual practice, and only Salisan's platform administrators can see them. We do not use service statistics to identify a practice, an Authorised User or a patient.

3.3 Help articles. You instruct us to turn resolved support requests into help articles for all customers after removing personal data (section 5.4(b) of the Terms). An administrator decides which resolved request may be used. The draft is written without personal data, a person reviews it, and an automated check for patient data must clear it before it is published. Published articles contain no personal data.

3.4 No other purposes. We do not process Customer Personal Data for any purpose of our own other than the instructed uses in sections 3.2 and 3.3. In particular, we do not sell Customer Personal Data, use it for advertising or marketing, use it to train AI models, or try to re-identify data from which personal data has been removed.

3.5 Unlawful instructions. We tell you without undue delay if, in our opinion, an instruction infringes Data Protection Law. We may suspend that instruction until you confirm or change it. We do not provide legal advice.

3.6 New instructions. If a new instruction would require a change to the Service or would cost us more than a minor effort, we may decline it or offer to carry it out for a fee that we agree in advance. If we decline an instruction that you need in order to comply with Data Protection Law, you may terminate the affected part of the Service under section 7.5.

4. Confidentiality and professional secrecy

4.1 Personnel. We give access to Customer Personal Data only to personnel who need it for the purposes in section 3 and who are bound by a written obligation of confidentiality that continues after their engagement ends. We train them in data protection at least once a year.

4.2 Professional secrecy. We treat Patient Data as subject to your professional secrecy, such as the medical professional secrecy under Article 7:457 of the Dutch Civil Code and Article 88 of the Dutch Individual Healthcare Professions Act (Wet BIG), and the obligations of German healthcare professionals.

4.3 Section 203 of the German Criminal Code. Where you or your Authorised Users are bound by professional secrecy under section 203 of the German Criminal Code (StGB):

  • (a) we and our personnel act as persons contributing to your professional activity (sonstige mitwirkende Personen) under section 203(3), second sentence, StGB, and we treat Patient Data as secrets within the meaning of section 203 StGB;
  • (b) we undertake to keep those secrets, and we are aware that a contributing person who discloses them without authorisation commits a criminal offence under section 203(4), first sentence, StGB;
  • (c) we take note of those secrets only to the extent necessary to provide the Service;
  • (d) we have bound our personnel to secrecy in text form, with notice of the criminal consequences of a breach;
  • (e) we engage a further contributing person, including a Subprocessor, only if it is bound to secrecy in the same way and passes the same obligation on to anyone it engages (section 203(4), second sentence, no. 2, StGB); and
  • (f) these obligations continue after the Agreement ends.

4.4 Disclosure to authorities. If a public authority asks us to disclose Customer Personal Data, we refer it to you where we may. We disclose Customer Personal Data only where European Union or Member State law requires it, we inform you beforehand unless that law prohibits it, and we disclose no more than the law requires. Where a right to refuse disclosure applies to us as a contributing person, for example under section 53a of the German Code of Criminal Procedure (StPO), we invoke it unless you release us from it. Clause 15 of the SCCs also applies.

5. Salisan personnel access

5.1 Who. Our personnel with access to the systems that hold Customer Personal Data are, at the date of this DPA, one person: our founder, who holds the roles of Chief Executive Officer, Security Officer and Engineering Lead. We will update this section by notice under section 15 if this changes.

5.2 When. Our personnel access Customer Personal Data only when that is needed to provide support that you request, to operate, maintain or secure the Service, to investigate or resolve an incident, or where European Union or Member State law requires it, and only the minimum necessary for that task.

5.3 How. Infrastructure access goes through single sign-on with multi-factor authentication and short-lived credentials, without long-lived access keys. Database work runs as short-lived tasks that are logged. AWS records administrative actions in an audit trail, and every access to patient data in the Service writes an audit record.

5.4 No access through platform roles. The Service's platform administration roles give no access to your patient data. Our personnel cannot sign in as one of your Authorised Users: impersonation is disabled in the Service. Platform administrators must use two-factor authentication.

6. Security

6.1 Measures. We implement the technical and organisational measures in Annex 2 to ensure a level of security appropriate to the risk, as required by Article 32 GDPR, taking into account the special categories of personal data in Patient Data.

6.2 Changes. We may update the measures as technology and risks develop, provided that the update does not reduce the overall level of protection of Customer Personal Data.

6.3 Your measures. You are responsible for the security measures within your control, such as managing your Authorised Users and their roles, requiring two-factor authentication where appropriate, and protecting the devices and networks your Authorised Users use.

7. Subprocessors

7.1 Authorisation. You give us general written authorisation to engage Subprocessors. The Subprocessors at the date of this DPA are listed in Annex 3. The current list is published at salisan.com/legal/subprocessors.

7.2 Full chain. The list names every Subprocessor, including the Subprocessors that our Subprocessors engage to process Customer Personal Data, with its legal name, registered country, service, the Customer Personal Data it receives, its processing location and the transfer safeguard. We keep the address and a contact point of each Subprocessor up to date and give them to you on request without undue delay, together with other information that you reasonably need to verify the chain, such as the relevant data protection terms with commercial terms removed.

7.3 Contracts. We engage a Subprocessor only under a written contract that imposes on it data protection obligations that are no less protective than those in this DPA, in particular sufficient guarantees to implement appropriate technical and organisational measures (Article 28(4) GDPR). We remain responsible to you for the performance of each Subprocessor's obligations as for our own.

7.4 Changes. We notify you at least 30 days before we add or replace a Subprocessor, by email to your Account Owners and by updating the published list. A new Subprocessor receives no Customer Personal Data before the notice period ends.

7.5 Objection. You may object to a change on reasonable data protection grounds by writing to privacy@salisan.com within the notice period. We will discuss your objection in good faith and, where we reasonably can, propose a solution, such as not using the new Subprocessor for your Customer Personal Data. If we cannot resolve your objection, you may terminate the affected part of the Service, or the Agreement, by written notice with effect before the change applies to you. We refund prepaid fees for the period after termination.

8. International transfers

8.1 Location. We host and process Customer Personal Data in the European Union: in Amazon Web Services' eu-central-1 region (Frankfurt, Germany), with backups in the same region, and AI processing on the EU routes listed in Annex 3. We do not replicate Customer Personal Data to another region.

8.2 Transfer to Salisan. Salisan, Inc. is established in the United States, so your disclosure of Customer Personal Data to us is a transfer to a third country. For that transfer, the SCCs are incorporated into this DPA by reference: Module Two (controller to processor) where you are a controller, and Module Three (processor to processor) where you are a processor. You are the data exporter and we are the data importer. The clause selections and annexes of the SCCs are completed as set out in Annex 4.

8.3 Our position under Article 3(2) GDPR. We have no establishment in the European Union. The GDPR applies to our processing under Article 3(2) GDPR, and we have designated the Representative. The European Commission has said that the 2021 SCCs are not designed for importers whose processing is already subject to the GDPR, and has announced separate clauses for that case. Until such clauses are adopted and incorporated under section 8.5, we use the SCCs as the safeguard for this transfer, and we comply with the GDPR directly as a processor.

8.4 Onward transfers. We transfer Customer Personal Data to a Subprocessor outside the European Economic Area only on the basis of an adequacy decision or other appropriate safeguards under Chapter V GDPR, and in compliance with Clause 8.7 and Clause 9 of the SCCs.

8.5 Replacement. If the European Commission adopts standard contractual clauses that cover transfers to importers subject to Article 3(2) GDPR, or replaces the SCCs, we may incorporate the new clauses by notice to you. They apply from the date stated in the notice, provided that they do not reduce the protection of Customer Personal Data.

8.6 Transfer assessment. On request, we give you the information that you reasonably need to document your assessment under Clause 14 of the SCCs, including the measures in Annex 2.

9. Assistance

9.1 Data subject requests. The Service lets you respond to data subject requests yourself: you can export a patient's record, correct entries while keeping their history, restrict processing, exclude a patient from AI features, export the access history of a record and erase a patient. If we receive a request from a data subject about Customer Personal Data, we forward it to you within 2 business days and do not respond to it ourselves, except to tell the data subject that we have forwarded it. Where the Service does not let you respond, we assist you with appropriate technical and organisational measures, insofar as this is possible.

9.2 DPIAs and prior consultation. We assist you with data protection impact assessments and prior consultations with supervisory authorities (Articles 35 and 36 GDPR), taking into account the nature of the processing and the information available to us. This includes Annexes 1 to 3, a description of how the AI features process data, and answers to reasonable questions.

9.3 Other obligations. We assist you in ensuring compliance with your obligations under Articles 32 to 36 GDPR, as set out in sections 6, 9.2 and 10, and we cooperate with a supervisory authority on request.

9.4 Costs. Assistance under this section is free of charge where it relies on the features of the Service, the information in this DPA, or a reasonable effort. For assistance that requires significant effort, or that is needed because of your own breach, we may charge our reasonable costs, which we agree with you in advance.

10. Personal Data Breaches

10.1 Notice. We notify you of a Personal Data Breach without undue delay, and in any case within 48 hours after we become aware of it, by email to your Account Owners and to any further contact you give us for this purpose.

10.2 Content. The notice includes, as far as we know at the time:

  • (a) the nature of the Personal Data Breach, including where possible the categories and approximate number of data subjects and of personal data records concerned;
  • (b) the name and contact details of our contact point (privacy@salisan.com);
  • (c) the likely consequences of the Personal Data Breach; and
  • (d) the measures we have taken or propose to take to address it, including measures to mitigate its possible adverse effects.

If we cannot provide all information at once, we provide it in phases without undue further delay. During a serious breach, we update you at least daily until it is contained.

10.3 Response. We take reasonable steps to contain and investigate the Personal Data Breach and to mitigate its effects, and we keep a record of it. We assist you in notifying the supervisory authority and data subjects. You decide whether to notify them. We do not notify supervisory authorities or data subjects about a Personal Data Breach of Customer Personal Data ourselves, unless the law requires us to.

10.4 No admission. Our notice of a Personal Data Breach is not an acknowledgement of fault or liability.

11. Deletion and return

11.1 During the Agreement. You can export Customer Data at any time while your account is open, in a structured, commonly used and machine-readable format (section 5.6 of the Terms). Export files expire after 7 days. You can erase individual patients with the Service's erasure tools, subject to the legal retention periods that the Service applies for your country.

11.2 At the end. After the Agreement ends, your workspace remains readable and exportable until an Account Owner closes the account by confirming its deletion in the Service, and for 30 days after that, or longer where Schedule 1 of the Terms applies. Your export is how we return Customer Personal Data to you. During those 30 days the workspace is read-only, and any Account Owner can cancel the closure.

11.3 Deletion. At the end of that period we delete Customer Personal Data from the Service, verify that none remains, and send your Account Owners a deletion certificate. Copies in backups and superseded file versions expire within 35 days after deletion. If a backup is restored within that time, every deletion is applied again before the Service resumes. On request, we confirm the deletion in writing.

11.4 What we keep. We keep only:

  • (a) the access audit records that the Service keeps for your country's logging obligations in its write-once archive, which hold keyed references, the action, the outcome and the time, never names or health details, until their retention period in Annex 1 ends;
  • (b) data that European Union or Member State law requires us to keep, or that we need to establish, exercise or defend legal claims, for that purpose only.

We continue to protect what we keep under this DPA and process it for no other purpose. Separately, as controller under our Privacy Policy, we keep a record of the offboarding and of the acceptance of the Agreement, including the name and email address of the person who accepted it, for the period in Annex 1.

12. Information and audits

12.1 Information. We make available to you the information necessary to demonstrate compliance with Article 28 GDPR and this DPA. This includes this DPA and its Annexes, summaries of our security policies, answers to a reasonable security questionnaire once a year, and any independent audit reports or certifications that we hold at the time.

12.2 Audits. If that information is not sufficient to demonstrate compliance, if a supervisory authority requires it, or after a Personal Data Breach, you may audit our compliance with this DPA, including by inspection. An audit:

  • (a) is announced in writing at least 30 days in advance, or with as much notice as the circumstances allow after a Personal Data Breach or at a supervisory authority's request, together with a proposed scope;
  • (b) is carried out by you or by an independent auditor bound by confidentiality who is not our competitor, remotely or at our premises during business hours, and in a way that does not disrupt the Service or give access to other customers' data;
  • (c) takes place no more than once in any 12 months, unless it follows a Personal Data Breach or a supervisory authority's request; and
  • (d) relies on our Subprocessors' independent audit reports for their facilities, such as AWS's data centres, which do not admit customer audits.

12.3 Costs. Each party bears its own costs of an audit. If the audit shows that we materially breached this DPA, we bear our own costs and reimburse your reasonable costs of the audit, and we remedy the breach without undue delay.

12.4 Supervisory authorities. Nothing in this section limits the powers of a supervisory authority, or the audit rights in Clause 8.9 of the SCCs, which we fulfil in the way set out in this section.

13. Liability

13.1 Terms apply. Each party's liability arising out of or in connection with this DPA is subject to section 16 of the Terms, including its cap, exclusions and exceptions.

13.2 Data subjects and the law. Section 13.1 does not limit either party's liability to data subjects under Article 82 GDPR or under Clause 12 of the SCCs, or any liability that cannot be limited under applicable law.

13.3 Fines. Each party bears any administrative fine imposed on it under Article 83 GDPR for its own infringements.

14. Order of precedence

In case of conflict on a data protection matter, the following order applies: the SCCs, this DPA, then the rest of the Agreement. This is consistent with section 19.2 of the Terms.

15. Changes

We may change this DPA as set out in section 18 of the Terms, with at least 30 days' notice of a material change. A change will not reduce the protection of Customer Personal Data without your agreement. We may also change this DPA with shorter notice where Data Protection Law, a supervisory authority or the European Commission requires a change, and we will tell you why.

16. Term, governing law and jurisdiction

16.1 Term. This DPA applies for as long as we process Customer Personal Data, even after the Agreement ends. Sections 4, 10, 11 and 13 survive for as long as we keep any Customer Personal Data.

16.2 Governing law and jurisdiction. This DPA is governed by the laws of the Netherlands. The competent court in Amsterdam, the Netherlands, has exclusive jurisdiction. The SCCs are governed by the law and subject to the courts set out in Annex 4, and data subjects keep their rights under Clause 18(c) of the SCCs.

17. Notices and contact

17.1 Notices. We send notices under this DPA to your Account Owners' email addresses or through the Service. You send notices and questions about this DPA to privacy@salisan.com.

17.2 Representative. Our representative in the European Union under Article 27 GDPR is Mohammed Al-Azzani, Nieuwstraat 157A, 6461 KB Kerkrade, the Netherlands, privacy@salisan.com.

17.3 Data protection officer. We have not designated a data protection officer. Our privacy contact is privacy@salisan.com. If we designate one, we will publish the contact details and update this section.

17.4 Language. This DPA is written in English. Translations are for convenience only; the English version prevails.

Annex 1: Description of the processing

A. Parties

PartyDetails
Data exporterThe Customer, as identified in the Service. Role: controller, or processor on behalf of another controller. Contact: the Account Owners. Activities: use of the Service for its healthcare practice.
Data importerSalisan, Inc., 2261 Market Street STE 38901, San Francisco, CA 94114, United States. Role: processor, or subprocessor where the Customer is a processor. Contact: privacy@salisan.com. Representative: as in section 17.2. Activities: providing the Service.

B. Data subjects

Patients; their relatives and contact persons; referrers, general practitioners and other healthcare professionals named in records; the Customer's Authorised Users and invitees; and authors of support requests.

C. Categories of personal data

  • Patient demographics and administration: name, date of birth, gender, marital status, language, interpreter need, date of death, contact details, addresses, insurance details and national identifiers (such as the BSN or KVNR, masked in the interface).
  • Special categories (Article 9 GDPR), health data: conditions, allergies, risk assessments, medications and orders, visits, notes and reports with their version history, vital signs, care plans, forms and responses, letters, tasks, documents and files, consultation recordings and transcripts.
  • Communications: appointments, emails, letters, form and request links, reminders and their delivery records.
  • Contact persons and professionals: name, relationship or organisation, contact details and professional identifiers.
  • Authorised Users: membership, role, teams, invitations, preferences and the access audit trail.
  • AI inputs and outputs: prompts, conversation history, tool results, attached files, document pages and consultation audio, and the AI Output produced from them.

The Service may contain data about patients under 18 in its non-AI features. Section 7.6 of the Terms prohibits submitting such data to AI features.

D. Safeguards for special categories

The measures in Annex 2, in particular: encryption in transit and at rest; access limited by organisation, role and care relationship and checked on the server on every request; an audit record for every read, search, change, export and deletion of patient data; confidentiality and professional secrecy under section 4; masking of national identifiers; minimisation of the data sent to AI providers; and automatic exclusion of patients under 18 and of patients you exclude from AI features.

E. Frequency

Continuous, for as long as you use the Service.

F. Nature and purposes, per area of the Service

AreaProcessingPurpose
Patient recordsStoring, displaying, editing and searching records with their version history; files and documents; the practice's own analytics (Insights).Keeping the medical and administrative record of your practice.
Scheduling and communicationAppointments and calendars; emails, letters, forms, measurement requests, reminders and digests to patients; notifications to Authorised Users.Organising care and communicating with patients and colleagues.
AI featuresThe Agent's chat and actions, document writing, reading uploaded documents (OCR), transcription of consultations, chat memory and titles, template translation and a sandbox for data queries. The Agent asks an Authorised User to confirm before it sends an email or form or changes an appointment.Drafting and organising documentation for review by your Authorised Users.
Members and audit trailAccess control, attribution of changes, and the access log that practices must keep (NEN 7513 in the Netherlands; section 309 SGB V applied by analogy in Germany).Securing access and answering patients' questions about who accessed their record.
Export, erasure and offboardingPatient and organisation exports; patient erasure with restriction, grace period and country minimums; offboarding, confirmed by an Account Owner, with export, a 30-day grace period and deletion.Data portability, erasure and the end of the Agreement.
Instructed usesService statistics (section 3.2) and help articles (section 3.3).Operating and improving the Service.
Support and operationsHandling support requests that you make, and maintaining and securing the Service (section 5).Providing and securing the Service.

G. Duration and retention

We process Customer Personal Data for the term of the Agreement and until it is deleted under section 11. Within that term:

  • Medical record content is kept as long as you decide. When you erase a patient, the Service applies your country's legal minimum: in the Netherlands 20 years from the last change, with destruction on the patient's request; in Germany 10 years after treatment.
  • Consultation recordings are kept with the record by default. You can choose deletion 30 days after the transcript is saved, or once the transcript is final (at most 72 hours). Audio of failed transcriptions is deleted after 72 hours.
  • Agent chats are deleted 90 days after the last activity, or after the period you choose (30 to 365 days).
  • Administrative patient emails are deleted 18 months after sending. Clinical emails and letters are kept with the record. Notifications are deleted after 90 days.
  • Access audit records are kept for at least 5 years for the Netherlands and 3 years for Germany.
  • Exports expire after 7 days. Backups and superseded file versions expire after 35 days.
  • Offboarding and acceptance records are kept for 5 years after offboarding.
  • AI providers keep requests only to detect abuse, for at most 30 days.

H. Subprocessors

As listed in Annex 3, for the processing and duration described there.

Annex 2: Technical and organisational measures

1. Location and backups. Customer Personal Data and its backups are stored in AWS eu-central-1 (Frankfurt). An automated infrastructure test blocks replication to another region. Database point-in-time recovery and daily file backups are kept for 35 days in the same region. A restore is tested at least once a year, including that erasures are applied again.

2. Encryption. TLS 1.2 or higher on every public endpoint and for connections to the database and cache, with certificate verification. AES-256 encryption at rest: the database and its backups with AWS-managed keys in AWS Key Management Service, files with Amazon S3-managed keys, and the audit archive and log data with customer-managed keys in AWS Key Management Service. Passwords are hashed with scrypt, sign-in tokens are encrypted, and public link tokens are stored only as SHA-256 hashes. Database credentials rotate automatically. Our laptops use full-disk encryption.

3. Access control in the Service. Every request is checked on the server for the organisation and for access to the patient, including requests by AI tools and background jobs. You manage your members, roles, custom roles, teams and care-team scope. Platform administration roles give no access to patient data, and impersonation is disabled.

4. Authentication. Email verification, a check against known breached passwords, rate limits, two-factor authentication with authenticator apps, passkeys and enterprise single sign-on. You can require two-factor authentication for your members. Platform administrators must use two-factor authentication. Public links for patients expire.

5. Access to infrastructure. Only the personnel named in section 5 have access, through AWS IAM Identity Center with multi-factor authentication and no long-lived access keys. Access is granted on least privilege and reviewed every quarter. Customer Personal Data is never stored on laptops or phones, and production data is never used outside production: development and testing use synthetic data only.

6. Logging and audit. Every read, search, change, export and deletion of patient data writes an audit record in the same database transaction; if the record cannot be written, the action fails. A copy, protected by a keyed integrity code (HMAC), goes to a write-once archive (S3 Object Lock in compliance mode). AWS CloudTrail records administrative activity for 365 days, and Amazon GuardDuty and security alarms alert on unusual activity. Logs are reviewed under our logging policy.

7. Minimisation and log hygiene. Application logs are redacted against an allow-list of fields and kept for 30 days. AI traces carry no inputs or outputs. Audit records use keyed references, not names. National identifiers are masked in the interface. Operational alerts carry only fixed text and opaque identifiers. Exports contain allow-listed fields only. Emails to patients are sent without open or click tracking.

8. AI controls. AI requests go only through Requesty's EU router to the approved EU model routes in Annex 3, with provider-side storage disabled where the provider allows it. AI tools receive an age instead of a date of birth, and no address, contact details or national identifiers. In conversations with the Agent and the other assistants, a pattern filter removes supported identifiers from text before each model call; it does not redact documents, images or audio sent for document writing, document reading or transcription. Patients under 18 and patients you exclude are excluded from AI features, including document processing and transcription. Web research sends only a de-identified question and is blocked if an identifier is detected. Our providers' terms exclude training on Customer Personal Data and limit their retention to at most 30 days, for abuse monitoring.

9. Retention and deletion. A daily automated job applies the retention schedule and skips data under legal hold. Patient erasure deletes every stored version of the patient's data and files and is verified. Restoring a backup applies every erasure again before the Service resumes. Superseded file versions and backups expire within 35 days.

10. Availability and resilience. Managed AWS services with a network spread over two availability zones of the region, infrastructure defined as code, deletion protection on the production database, monitored health alarms, and a documented backup, continuity and recovery plan.

11. Secure development. Every change is reviewed and passes automated tests, including tests that every API route declares its access level, before it is deployed through the deployment pipeline. Code is checked with static analysis, and dependencies and container images are scanned for known vulnerabilities.

12. Physical security. Customer Personal Data is held in AWS data centres, whose physical and environmental controls AWS has independently audited, for example under ISO/IEC 27001 and SOC 2. We have no own data centres or servers.

13. Organisation. Approved information security and privacy policies aligned with ISO/IEC 27001, reviewed every year; a named Security Officer; confidentiality obligations for everyone with access; yearly data protection training; due diligence and a data processing agreement before any supplier receives personal data; and an incident response procedure, tested once a year, that notifies affected practices within 48 hours.

14. Subprocessors. Each Subprocessor is bound by a written contract under section 7.3 and gives its own technical and organisational measures, which we review before engaging it and at least once a year.

Annex 3: Subprocessors

SubprocessorServiceCustomer Personal Data receivedProcessing locationTransfer safeguard
Amazon Web Services, Inc., United StatesHosting: compute, database, file storage, cache, key management, email (Amazon SES), translation (Amazon Translate), query sandbox, logging and backupsAll Customer Personal DataAWS eu-central-1 (Frankfurt, Germany)EU-US Data Privacy Framework (Amazon.com, Inc. certification) and the SCCs in the AWS GDPR Data Processing Addendum
REQUESTY LTD, England and Wales (company no. 15165717)AI gateway: routes requests from the AI features to the model providers belowPrompts, conversation history, tool results, files, document pages and consultation audioRequesty's EU router in Frankfurt, GermanyEU adequacy decision for the United Kingdom; processing in the EU
Microsoft (Azure OpenAI), engaged by RequestyLarge language model for the Agent, document writing, document reading (OCR) and drafting help articlesAs Requesty, apart from consultation audioAzure Sweden Central, inside Microsoft's EU Data BoundaryProcessing in the EU; Microsoft's SCCs and EU-US Data Privacy Framework certification for any transfer outside the EU
Mistral AI, France (registered in Paris under number 952 418 325), engaged by RequestySpeech-to-text transcription of consultations (Voxtral)Consultation audioEuropean UnionEU company processing in the EU; the SCCs in Mistral AI's data processing addendum for any onward transfer

Note on Google Gemini. Web research sends only a de-identified research question to Google Gemini through Requesty, after a check that blocks the request if it detects an identifier. Google therefore receives no Customer Personal Data and is not a Subprocessor. The same question may be sent to public literature databases, which are not Subprocessors either.

Annex 4: Standard Contractual Clauses

  1. Modules. Module Two applies where the Customer is a controller; Module Three applies where the Customer is a processor.
  2. Parties. The Customer is the data exporter and Salisan, Inc. is the data importer, as described in Annex 1, Part A. Acceptance of this DPA in the Service counts as signature of the SCCs.
  3. Clause 7 (docking clause). Applies.
  4. Clause 9(a) (subprocessors). Option 2, general written authorisation. The data importer informs the data exporter of intended changes at least 30 days in advance, as set out in section 7.
  5. Clause 11(a) (redress). The optional wording on an independent dispute resolution body does not apply.
  6. Clause 13(a) (supervision). Where the Customer is established in a Member State, the supervisory authority competent for the Customer, such as the Autoriteit Persoonsgegevens for a Customer in the Netherlands or the competent German supervisory authority for a Customer in Germany. Where the Customer is not established in the European Union but has a representative under Article 27 GDPR, the supervisory authority of the Member State in which that representative is established.
  7. Clause 17 (governing law). Option 1: the law of the Netherlands.
  8. Clause 18(b) (forum). The courts of the Netherlands.
  9. Annex I of the SCCs. Part A (list of parties) and Part B (description of transfer) are set out in Annex 1 of this DPA. Part C (competent supervisory authority) is as in item 6.
  10. Annex II of the SCCs. Annex 2 of this DPA.
  11. Annex III of the SCCs. Annex 3 of this DPA.
  12. Clause 8.9 (audits) is fulfilled as set out in section 12, and Clause 8.6(c) (breach notification) as set out in section 10.
  13. Clause 8.5 and 16(d) (deletion). Certification of deletion under the SCCs is given as set out in section 11.3.