Skip to main content
Legal

Data processing agreement and technical and organisational measures

Version 1.19 · Last updated: 15 November 2026

Law firms, medical practices and businesses need a contract on the processing of personal data on their behalf (Article 28 GDPR) as well as a description of the technical and organisational measures (Article 32 GDPR) in order to use “Simpliant Dictation”. You will find both here in full and as a PDF download.

This data processing agreement applies to all plans. Like the agreement on confidentiality under Section 203 of the German Criminal Code and Section 43e BRAO, it is an annex to the General Terms and Conditions, which you accept with a separate declaration when you start the trial or place an order; no signature is required. Immediately afterwards you receive the contract documents as PDF files by email. A signed counterpart or individual amendments are available on request at support@simpliant.eu. You can find your documents at any time in your account under Contracting party and contracts, where you can also retrieve a copy containing the details of your business.

Download documents

The PDF versions are authoritative in German; this English page is a translation for information purposes.

Contracting parties

This agreement is concluded between the customer – hereinafter the “controller” – and Simpliant Technologies GmbH, Fasanenstraße 12, 10623 Berlin, Germany, registered in the commercial register of Charlottenburg Local Court under HRB 247115 B, VAT ID DE356327395, represented by its Managing Director Steffen Groß – hereinafter the “processor” –; hereinafter individually a “party” and jointly the “parties”.

Controller (customer)

The executed copy inserts the controller’s details: full company name, address, authorised representative, register court and registration number, contact person for data protection and – where appointed – the name and contact details of the data protection officer. These details are optional; without them the copy designates the controller by the billing details or by the customer account.

Processor

Simpliant Technologies GmbH
Fasanenstraße 12, 10623 Berlin, Germany
Managing Director: Steffen Groß
Register court: Charlottenburg Local Court (Amtsgericht Charlottenburg), HRB 247115 B
VAT ID: DE356327395

Point of contact at the processor for instructions, notifications, requests for evidence and any other data protection matters: support@simpliant.eu. No data protection officer has been appointed; there is no obligation to appoint one under Article 37 GDPR for the processing activities covered here.

Preamble

The controller uses the “Simpliant Dictation” software on the basis of the General Terms and Conditions of Simpliant Technologies GmbH for Simpliant Dictation together with the plan agreement (hereinafter the “main contract”). The service converts submitted voice recordings (dictations) into text and linguistically corrects the dictated text where this function is switched on in the controller’s application or triggered by the user (AI correction); the dictation content may contain personal data of third parties. The controller alone decides on the purposes and means of this processing. This constitutes processing on behalf of a controller within the meaning of Article 4(8) and Article 28 GDPR, which this agreement gives effect to.

Simpliant Technologies GmbH is itself the controller for the account, billing, usage and operational data of contracting parties. This agreement does not apply in that respect; the privacy policy for Simpliant Dictation does.

Section 1 Subject matter and duration

(1) The subject matter of the processing is the provision of the transcription service described in the main contract: receiving the voice recordings submitted by the controller, converting them technically into text, the automated linguistic correction of the dictated text where it is switched on in the controller’s application or triggered by the user (AI correction), returning the result to the controller’s application and the ancillary processing required for this (quota management, abuse prevention, operational security).

(2) The agreement begins upon signature, or – where the contract is concluded electronically – upon its incorporation into the main contract, and runs for the term of the main contract. It ends with the main contract without requiring separate termination. Separate termination of this agreement alone is excluded, because the service cannot be provided without processing on behalf of the controller. This does not affect the controller’s right to terminate the main contract extraordinarily for good cause, in particular in the event of serious breaches by the processor of data protection law or of this agreement, and in the case of Section 6(4).

(3) In the event of conflicts, this agreement takes precedence over the main contract on data protection matters. It takes precedence over the annexes unless an annex expressly provides a rule that is more favourable for the data subjects.

Section 2 Nature, purpose and scope of the processing

(1) Nature of the processing: collection, recording, organisation, storage (temporary only, paragraph 3), retrieval, use, transmission to the transcription provider described in Annex 2 for conversion into text and for AI correction, erasure and destruction.

(2) The purpose of the processing is exclusively (a) the automated conversion of the submitted voice recordings into text and the return of the transcript to the controller’s application, (b) the automated linguistic correction of the dictated text (spelling, punctuation, grammar and wording) where it is switched on in the controller’s application or triggered by the user, and the return of the corrected text to the application (AI correction), and (c) the directly related quota management, abuse prevention and assurance of proper operation. AI correction is switched on by default in the application and can be switched off by the user at any time; while it is switched off, no AI correction takes place unless the user triggers it in the individual case.

(3) Depth of processing: Dictation content is processed only temporarily. Depending on the operating mode chosen, the recordings are transmitted while they are being made or after they have been completed. They are held only for the duration of the transcription and are then deleted without undue delay, including in the event of an error or abort. Transcripts are not stored permanently at the processor but returned to the controller’s application. Texts submitted for AI correction are held only for the duration of the correction; the corrected text is returned to the controller’s application and is not stored at the processor. Dictionary terms sent along (Section 2(6)(d)) are processed only together with the respective recording and are not stored at the processor. Annex 2 applies to retention at the sub-processor.

(4) No purposes of its own: The processor processes dictation content exclusively to perform this agreement. The content is not analysed, used for the processor’s own purposes, used for product improvement or used to train artificial intelligence models. For the processor’s organisation, zero data retention has been active at the transcription provider used since 16 October 2026; that provider does not retain the transmitted inputs and outputs beyond the time required to generate the response and uses them neither to train nor to improve its models (Annex 2).

(5) The place of processing of dictation content is member states of the European Union or states party to the Agreement on the European Economic Area. Details are set out in Annex 2, section B; Section 6(6) applies to third-country transfers.

(6) Categories of personal data processed on behalf of the controller:

  • a) The content of the voice recordings (dictations), of the transcripts generated from them and of the texts submitted for AI correction and the corrected texts; the controller alone determines their composition. They may contain in particular names, addresses, contact details, dates of birth, file references, descriptions of facts and the content of contracts and correspondence.
  • b) The voice and speech characteristics of the dictating persons and of any other persons captured in the audio.
  • c) Technical accompanying data of the transmission relating to the dictation content: the time and length of the recording, the time and size of an AI correction, the operating mode chosen, a pseudonymous user identifier and device and session data of the devices used.
  • d) Terms that the user creates in the application’s “Wörterbuch” (dictionary terms; the application has a German interface) and whose transmission as a recognition aid the user expressly switches on in the application; without this setting they remain on the device and are not transmitted. They may contain in particular names, companies and technical terms.

(7) Special categories of personal data under Article 9 GDPR and data subject to professional secrecy under Section 203 of the German Criminal Code may be contained in dictation content. Section 10 applies in this respect.

(8) Categories of data subjects: clients, patients and other principals of the controller; employees and corporate officers of the controller, in particular the dictating persons; parties to contracts, proceedings and correspondence and other third parties named or described in the dictation content.

(9) The controller can limit the scope of the data transmitted at any time; the processor has no influence on the selection of content.

Section 3 Rights and obligations of the controller

(1) The controller is solely responsible for assessing the lawfulness of the processing and for safeguarding the rights of data subjects (Article 24 GDPR). In particular, it ensures that there is a valid legal basis for transmitting the dictation content and that it is entitled to involve a processor.

(2) Right to issue instructions: The processor processes the personal data exclusively on documented instructions from the controller. The description of services under Sections 1 and 2 and the settings and transmissions made by the controller in the course of use constitute the initial instruction.

(3) Form of instructions: The controller issues supplementary or divergent instructions in text form to support@simpliant.eu; oral instructions must be confirmed in text form without undue delay. Instructions may be amended, supplemented or replaced at any time. The processor documents the instructions and their implementation.

(4) The controller’s persons authorised to issue instructions are named upon conclusion of the contract. Absent a separate designation, the authorised representative and the data protection contact named at the outset are deemed authorised to issue instructions; if these are not named either, the holder of the customer account is deemed the contact person and authorised to issue instructions. On the processor’s side, instructions are received by the management at support@simpliant.eu.

(5) Obligations in operation: The controller manages user accounts and device activations on its own responsibility, keeps access credentials and activation codes confidential and withdraws them without undue delay when a person leaves. It informs the processor without undue delay of any errors, irregularities or suspected unauthorised access identified, documents the instructions it has issued and assesses on its own responsibility whether the measures in Annex 1 are appropriate to the risk of the data it transmits.

(6) Additional costs: Instructions that go beyond the contractually agreed service and cause the processor considerable additional effort may be remunerated on a time and materials basis, subject to prior notice and agreement. Instructions serving to fulfil the processor’s statutory obligations are excluded from this.

Section 4 Obligations of the processor

(1) Binding effect of instructions (Article 28(3)(a) GDPR): The processor processes the data only on the controller’s instructions, unless Union or Member State law requires it to process; in that case it communicates the legal requirements before processing, unless that law prohibits such communication on important grounds of public interest. If it considers an instruction to infringe data protection provisions, it informs the controller without undue delay and may suspend execution until the instruction is confirmed or amended.

(2) Confidentiality (Article 28(3)(b), Article 29 and Article 32(4) GDPR): It only deploys persons who have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality. The commitment is made in text form, continues to apply beyond the end of the activity and expressly includes the prohibition on processing personal data outside the scope of the instructions. Those bound are informed of the data protection requirements applicable to them.

(3) Further obligations under Article 28(3) GDPR: Section 5 applies to the technical and organisational measures (point (c)), Section 6 to sub-processors (point (d)), Section 7 to assistance with data subject rights (point (e)), Sections 7 and 8 to assistance under Articles 32 to 36 GDPR (point (f)), Section 11 to deletion and return (point (g)) and Section 9 to evidence and audits (point (h)).

(4) It maintains a record of all categories of processing activities carried out on behalf of the controller (Article 30(2) GDPR) and makes it available to the supervisory authority on request. It cooperates with the supervisory authority in the performance of its tasks (Article 31 GDPR).

(5) It rectifies, erases or restricts the processing of the data processed on behalf of the controller only on the controller’s instructions. If a data subject contacts it directly, it forwards the request to the controller without undue delay.

(6) Requests from authorities: If the processor receives an order from an authority or a court to disclose the data processed on behalf of the controller, it informs the controller without undue delay insofar as this is legally permissible and refers the requesting body to the controller’s responsibility. It discloses data only to the extent that it is legally obliged to do so.

(7) It informs the controller without undue delay if a data protection officer is appointed in the future.

Section 5 Technical and organisational measures

(1) The processor implements the technical and organisational measures under Article 32 GDPR described in Annex 1 and maintains them for the term of the agreement.

(2) It is entitled to adapt the measures to technical progress and to the further development of the service, provided that the agreed level of protection is not reduced. It documents material changes and makes them available to the controller on request.

Section 6 Sub-processors

(1) General authorisation: By concluding this agreement, the controller grants its general written authorisation under Article 28(2), first sentence, GDPR for the use of the sub-processors described in Annex 2 by service, registered office and place of processing. The companies concerned are set out in the list under Annex 2 section D.

(2) Passing on of obligations: The processor imposes on each sub-processor by contract the same data protection obligations as apply between the parties (Article 28(4) GDPR), in particular sufficient guarantees of appropriate technical and organisational measures; where a sub-processor fails to fulfil them, the processor remains liable to the controller for their performance. The engagement of further sub-processors by a sub-processor already named is permitted only subject to the continued application of these obligations; the processor monitors their sub-processor lists.

(3) Changes: If the processor intends to engage or replace a sub-processor, it notifies the controller in advance in text form, stating the name, registered office, service, place of processing and the categories of data concerned. The controller may object to the change in text form within 30 days of receiving the notification, on important data protection grounds (Article 28(2), second sentence, GDPR). If it does not object in time, the change is deemed authorised; the processor points this out separately in the notification.

(4) Consequences of an objection: Following a timely and substantiated objection, the parties endeavour to find an amicable solution. If none is reached within 30 days, the controller has a right of extraordinary termination in respect of the affected service and, insofar as the service cannot reasonably be used without it, of the main contract, with effect from the date of the planned changeover; fees paid in advance are refunded pro rata.

(5) Not sub-processing are ancillary services supporting the business activities where access to the data processed on behalf of the controller is neither necessary nor intended (for example telecommunications, postal and transport services, cleaning, maintenance without data access). The processor also ensures appropriate confidentiality and security precautions in this respect.

(6) Third-country transfers: A sub-processor processing outside the EU or EEA is used only if the requirements of Articles 44 et seq. GDPR are met, in particular on the basis of an adequacy decision under Article 45 GDPR or EU standard contractual clauses together with a documented transfer impact assessment. This also applies to further service providers engaged by a sub-processor (Annex 2, section B).

(7) Shorter periods of sub-processors: If a sub-processor announces the use of further subcontractors of its own with a shorter period than paragraph 3 grants the controller, the processor notifies the controller in text form without undue delay as soon as it becomes aware of this itself, but in any event before the change takes effect. The controller may object to the change within 30 days of receiving this notification on important data protection grounds; if no amicable solution is reached, it may, by way of derogation from paragraph 4, terminate the main contract without notice. Fees paid in advance are refunded on a pro rata basis.

Section 7 Assistance to the controller

(1) Data subject rights: The processor assists the controller by appropriate technical and organisational measures in responding to requests from data subjects under Chapter III GDPR, in particular regarding access, rectification, erasure, restriction of processing, data portability and objection (Articles 15 to 18, 20 and 21 GDPR).

(2) It does not itself answer requests from data subjects concerning the data processed on behalf of the controller. If a data subject contacts it directly, it forwards the request to the controller without undue delay and at the latest within three working days and points out the controller’s responsibility. It implements instructions to assist with a data subject request without undue delay, as a rule within seven working days of receipt, insofar as this is technically possible and involves reasonable effort.

(3) Technical starting position: Since dictation content is processed only temporarily and transcripts are not stored permanently (Section 2(3)), the processor as a rule holds no content data processed on behalf of the controller to which a request for access, rectification or erasure could relate. In such cases, assistance is limited to confirming this fact and providing information on the usage metadata held.

(4) Security, impact assessment, consultation: It assists the controller with the obligations under Article 32 GDPR and with a data protection impact assessment and any prior consultation of the supervisory authority (Articles 35 and 36 GDPR) by providing, on request, Annex 1 and information on processing operations, data flows, sub-processors and security measures.

(5) Remuneration: For assistance that goes beyond the statutory obligations or is attributable to a circumstance within the controller’s sphere, the processor may, subject to prior notice, charge reasonable remuneration on a time and materials basis.

Section 8 Personal data breaches

(1) The processor notifies the controller of any personal data breach within the meaning of Article 4(12) GDPR of which it becomes aware and which concerns the data processed on behalf of the controller, without undue delay and at the latest within 24 hours of becoming aware of it, in text form to the controller’s data protection contact person named at the outset.

(2) The notification contains, where available, a description of the nature of the breach including the categories and approximate number of data subjects and records concerned, the time at which it was identified, the name and contact details of the point of contact providing information, a description of the likely consequences and of the measures taken or proposed to address the breach and to mitigate its possible adverse effects. Where not all information is available at once, the notification is made without undue delay with the information available and is supplemented in stages.

(3) The processor takes the necessary measures to secure the data and mitigate possible adverse consequences without undue delay and documents the incident and the measures. It assists the controller with its obligations under Articles 33 and 34 GDPR; it does not itself notify the supervisory authority or communicate with data subjects, as the controller decides on this.

Section 9 Evidence and audit rights

(1) The processor makes available to the controller all information necessary to demonstrate compliance with the obligations laid down in Article 28 GDPR (Article 28(3)(h) GDPR).

(2) Standard evidence: Evidence is provided primarily by submitting suitable documentation – the current versions of Annexes 1 and 2, answers to a written questionnaire (self-disclosure) and any certificates, attestations or audit reports from independent bodies, including those of the sub-processors. The processor answers such requests within 30 days of receipt. The controller may request this evidence once per calendar year and on an ad hoc basis where there is cause.

(3) On-site audit: If the evidence under paragraph 2 is not sufficient, the controller is entitled to satisfy itself of compliance with this agreement by means of an on-site inspection, either itself or through a third party. The following applies:

  • a) notice in text form with a period of at least 14 days; where there is specific cause, in particular following a personal data breach or at the request of a supervisory authority, without undue delay and without any notice period;
  • b) carried out during normal business hours, without avoidable disruption to operations, once per calendar year and beyond that where there is cause, by the controller itself or by an auditor appointed by it who is bound to secrecy and who must not be a competitor of the processor;
  • c) safeguarding the processor’s trade and business secrets and the confidentiality of other customers’ data; the auditor is not granted access to personal data of third parties.

(4) Audits at sub-processors are carried out indirectly through the processor. It forwards substantiated audit requests and makes available the evidence, certificates and audit reports it receives from the sub-processors.

(5) Costs: The processor provides the evidence under paragraph 2 free of charge. It may claim reasonable compensation for on-site audits under paragraph 3; this does not apply where the audit reveals a breach of this agreement or of data protection law, or where it is carried out at the request of a supervisory authority.

(6) The supervisory authorities’ powers of investigation and audit under Article 58 GDPR remain unaffected. The processor informs the controller without undue delay of supervisory measures concerning the data processed on the controller’s behalf.

Section 10 Professional secrecy and special categories of personal data

(1) Dictations by law firms, medical practices and comparable bodies may be subject to professional secrecy under Section 203 of the German Criminal Code. Involving the processor as an “other cooperating person” within the meaning of Section 203(3) and (4) of that Code requires that the cooperating persons are bound to secrecy and that disclosure is necessary in order to make use of the service.

(2) The processor binds the persons involved in providing the service to secrecy (Section 4(2)) and informs them that unauthorised disclosure is a criminal offence under Section 203(4) of the German Criminal Code. Annex 2, section C applies to the sub-processors under Annex 2. The processor does not inspect dictation content on its own initiative; it does so only where this is necessary to perform the contract or the controller has instructed it. If it is required by an official or court decision to disclose data, it hands the data over, where possible, without inspecting them itself and informs the controller beforehand where permitted. If questioned as a cooperating person, it objects by reference to Section 53a of the Code of Criminal Procedure (StPO) and informs the controller, who decides on exercising the right of silence. The duties of secrecy continue to apply after this agreement ends. For all plans, the parties additionally conclude the agreement on confidentiality under Section 203(3), (4) of the German Criminal Code and Section 43e of the Federal Lawyers’ Act (BRAO) (“confidentiality agreement”) as a further annex to the main contract; on matters of professional secrecy it takes precedence over this agreement.

(3) Scope of the obligation: The confidentiality obligation under paragraph 2 applies on all plans and to all persons bound by professional secrecy. This agreement does not contain any further assurance that the processor fully meets the requirements for service providers under Section 203(3), (4) of the German Criminal Code and the professional codes; whether the involvement, including the sub-processors under Annex 2, meets the requirements of professional law is assessed by the controller (paragraph 4). The processor provides a signed counterpart of the confidentiality agreement on request.

(4) The controller is responsible for ensuring that it is entitled to involve a processor for the content concerned and that the necessary legal bases, professional requirements and commitments are in place.

Section 11 Deletion and return after the end of the assignment

(1) After the end of the provision of processing services, the processor deletes all personal data processed on behalf of the controller or returns it at the controller’s choice, unless there is an obligation to store the data under Union or Member State law (Article 28(3)(g) GDPR). The controller communicates its choice in text form no later than 30 days after the end of the contract; if it makes no choice, the data is deleted.

(2) Since dictation content and transcripts are already not stored permanently during ongoing operation (Section 2(3)), a return of content data is as a rule not applicable; the transcripts are held exclusively within the controller’s sphere.

(3) Periods for the remaining data:

  • a) When the contract ends, access to the service is deactivated and existing sessions and device activations are withdrawn.
  • b) The usage data kept for quota and abuse control (pseudonymous user identifier, duration used, operating mode, timestamp, device and session data) is deleted automatically no later than 90 days after it was collected; it therefore expires no later than 90 days after the last use.
  • c) Backups of the Simpliant Dictation database and object storage are created in encrypted form and deleted automatically no later than 7 days after they were created; this also applies to their encrypted copies on separate systems. Backups of the system configuration and of the operational logs are kept in encrypted form according to a staggered rule (seven daily, four weekly and six monthly snapshots), i.e. for up to six months; they contain no dictation content, but do contain IP addresses from the access logs. Targeted deletion of individual records within a backup set is not technically possible; until deletion the data remains blocked exclusively for restoration purposes.
  • d) Technical log data is held only briefly and overwritten automatically.

(4) Statutory retention: Insofar as statutory retention obligations preclude deletion – in particular for billing-relevant documents under Section 147 of the German Fiscal Code and Section 257 of the German Commercial Code – the processing is restricted instead and the data is deleted once the period has expired; this data concerns the processor’s own controllership (preamble) and contains no dictation content. It may retain documentation evidencing processing in accordance with the assignment and with data protection law beyond the end of the contract, in line with the applicable retention periods.

(5) The processor confirms the deletion to the controller in text form on request.

Section 12 Liability

(1) The liability of the parties towards each other is additionally governed by the provisions of the main contract, in particular its liability provisions.

(2) Article 82 GDPR applies in relation to data subjects and supervisory authorities. Where one party has paid compensation to a data subject, it may claim back from the other party that part corresponding to that party’s share of responsibility for the damage (Article 82(5) GDPR).

(3) Indemnification: The controller indemnifies the processor against third-party claims and, to the extent legally permissible, against fines resulting from its failure to comply with its obligations under this agreement or under the GDPR – in particular where there was no valid legal basis for transmitting the dictation content or where an unlawful instruction was issued. This does not apply insofar as the processor is itself at fault. If the indemnification against fines is invalid, the indemnification against third-party claims remains unaffected.

(4) Limitations of liability do not apply in cases of intent and gross negligence, injury to life, body or health, or mandatory statutory liability.

Section 13 Final provisions

(1) Text form: Amendments and additions to this agreement and its annexes must be made in text form; this also applies to any waiver of this formal requirement. An email to the contact addresses named in this agreement is sufficient.

(2) Updating the annexes: The processor may update Annex 1 and Annex 2 in accordance with Section 5(2) and Section 6 respectively. It makes the current version available to the controller; it notifies the controller of material changes in text form.

(3) Right of retention: The right of retention under Section 273 of the German Civil Code in respect of the data processed on behalf of the controller and the associated data carriers is excluded.

(4) Applicable law and place of jurisdiction: The law of the Federal Republic of Germany applies, excluding the UN Convention on Contracts for the International Sale of Goods. The exclusive place of jurisdiction is Berlin, insofar as the controller is a merchant, a legal person under public law or a special fund under public law. Mandatory provisions of the GDPR and of the German Federal Data Protection Act take precedence over the provisions of this agreement.

(5) Severability: Should individual provisions of this agreement be or become invalid or unenforceable, the validity of the remaining provisions remains unaffected. The parties will replace the invalid provision with a valid one that comes as close as possible to its economic and data protection purpose. The same applies to gaps in the provisions.

(6) Amendments to this agreement: The processor may amend this agreement with effect for the future insofar as this is necessary for an objective reason, in particular because of a change in the law or in case law, because of requirements of public authorities or because of a further development of the service, and the agreed level of protection is not thereby reduced. It notifies the amendment in text form at least six weeks before it takes effect, highlights the amended provisions separately and points out the consequences under sentence 3 separately. If the controller does not object in text form before the amendment takes effect, the amended version is deemed agreed; if it objects, the previous version continues to apply, and both parties may terminate the main contract with effect from the planned date of the amendment. Amendments that lower the level of protection for the data processed on behalf of the controller require the controller’s express consent. Section 6(3) and (4) applies to sub-processors and paragraph 2 to the annexes.

Conclusion of the contract

The agreement is concluded electronically: when starting the trial, with every order or when a free access is activated in the customer account, the controller accepts, with one declaration, the General Terms and Conditions including their annexes, which comprise this agreement and the confidentiality agreement. The documented acceptance and the confirmation in text form with the contract documents replace a handwritten signature; Article 28(9) GDPR expressly permits the electronic format.

Signed-in customers find their contract documents in their account under Contracting party and contracts, where they can also have them sent again by email and retrieve a copy containing the details of their own business. A signed counterpart is available on request at support@simpliant.eu.

Annex 1 – Technical and organisational measures (Article 32 GDPR)

This annex describes the technical and organisational measures taken by the processor under Article 32 GDPR, grouped by protection objective and category of measure. Details of the technical implementation are trade and business secrets and are not disclosed. The measures are updated without falling below the agreed level of protection (Section 5(2) of the agreement).

1. Confidentiality (Article 32(1)(b) GDPR)

Physical access control

  • The processor maintains no server or data centre rooms of its own; processing takes place in the data centres of the sub-processors described in Annex 2. The physical access measures are the responsibility of their operators and are covered by the contracts concluded with them under Article 28 GDPR; their evidence is passed on upon request (Section 9(4) of the agreement).
  • Data carriers containing personal data from this assignment are neither shipped nor kept outside those data centres.

System access control

  • Access to the systems only after authentication. Administrative access is additionally restricted to a separate, non-publicly reachable management network and tied to a personally assigned cryptographic credential; logging in there with a password alone is not possible.
  • Protection against unauthorised login attempts through automatic blocking and limitation of access frequency; password rules are enforced.
  • Sessions and access authorisations are limited in time and can be withdrawn individually at any time.

Data access control

  • Role-based authorisation concept; authorisations are granted only to the extent required for the task. The group of persons with administrative access is limited to the necessary minimum and documented; authorisations are withdrawn without undue delay when a person leaves or changes role.
  • Logging of administrative access and security-relevant events.
  • Access secrets are held separately from the application and with restricted access; storing them in the source code is ruled out and checked automatically.

Separation control

  • Tenant separation at application level: access is technically restricted to the data of the authorised user in each case; access to other customers’ data is not provided for via the interfaces.
  • Separation of production, preview and development environments; no production dictation content is used for development and testing.
  • Functional separation of the processing areas (application, data storage, processing of the dictations) in isolated execution environments with separate internal networks.

Pseudonymisation

  • In the transcription area, users are identified exclusively by a pseudonymous identifier; real names and email addresses are not held there, and the identifier is mapped to the account separately from this.

2. Integrity (Article 32(1)(b) GDPR)

Transfer control

  • Encrypted transmission, including for transfers to sub-processors (section 4); unencrypted connections are rejected.
  • The transcription service is technically fixed to the provider’s regional EU endpoint; this applies equally to conversion into text and to AI correction. If the endpoint is configured otherwise, the service does not start operating. According to the provider’s confirmation, processing via this endpoint takes place in the EU (Annex 2, section B). This technical endpoint binding does not guarantee a regional storage location for all of the provider’s account, billing and operational metadata. Outbound connections are limited to a documented, narrow set of destinations.
  • Dictation content is held only for the duration of the processing and is then deleted without undue delay, including in the event of an error or abort; transcripts are not stored permanently but returned to the controller’s application. Texts submitted for AI correction are processed at the processor only for the duration of the correction and are not stored there; retention at the sub-processor is governed by Annex 2 of the agreement.

Input control and traceability

  • Logging of access to the processing systems; the content of dictations, transcripts and texts submitted for AI correction is not logged and secrets are redacted in logs.
  • Changes to the production environment are introduced exclusively through a versioned, documented change procedure with author, reviewer and timestamp; every state is tied to a specific change. Incoming data is checked and limited before processing.

3. Availability and resilience (Article 32(1)(b) and (c) GDPR)

  • Regular, automated backups of the account and subscription portal are stored encrypted on a system separate from the production environment. For short-term recovery, local backups are additionally kept on the production system, daily and before every change to the production environment; they are accessible to administrators only, are stored encrypted (Section 4) and are deleted after 7 days. On the separate system, database snapshots are deleted after 7 days at the latest; backups of the system configuration and of the operational logs are kept according to a staggered rule for up to six months. The backup runs are logged.
  • Documented restoration and rollback procedure; restorability is tested.
  • Monitoring of availability and operating status by a procedure independent of the production environment, with alerting via a separate notification channel. Error monitoring is operated under the processor’s own responsibility and receives no personal data.
  • Automatic restart of the services after disruptions; protection against overload by limiting access frequency, concurrent processing and data volume. Security-relevant updates are installed promptly.

4. Encryption (Article 32(1)(a) GDPR)

  • Encrypted transmission in line with the state of the art for all externally reachable connections and for sending messages to contracting parties. The local backups under Section 3 are encrypted asymmetrically; the key required for decryption is not kept on the production system but stored separately from it. The backups on the separate system are likewise stored encrypted.
  • Passwords, access and activation credentials are stored exclusively in a form that cannot be reversed, in line with the state of the art, and plaintext values are not retained. Cryptographically secure random values are used to generate them.

5. Procedure for regular testing, assessment and evaluation (Article 32(1)(d) GDPR)

  • Every change to the production environment passes through an automated review procedure before it is adopted, covering security-relevant requirements and the effectiveness of the deletion routines; the origin and integrity of the software components used are traceable.
  • The deletion runs state the number of records deleted per category and can therefore be verified.
  • The record of processing activities, the privacy policy, the data processing agreement and this annex are maintained and updated when changes occur.
  • Employees and cooperating persons are bound to confidentiality and informed of the data protection requirements applicable to them. Point of contact for data protection matters, requests for evidence and notifications: support@simpliant.eu.

6. Control of processing on behalf of the controller (Article 28 GDPR)

  • Sub-processors are selected according to the locations and transfer mechanisms set out in Annex 2 (EU/EEA, Annex 2, section B); contracts under Article 28 GDPR exist with all of them. Annex 2 describes them by service, registered office and place of processing; the controller receives the list with names and addresses on request (Annex 2, section D). Changes are notified in advance in text form (Section 6 of the agreement).
  • The further service providers used by the sub-processors are monitored.
  • The controller’s instructions are documented and their implementation is tracked.

7. Data minimisation and data protection by default (Article 25 GDPR)

  • The function for permanently storing recordings and transcripts is not active in production (section 2).
  • Usage data is kept pseudonymously and deleted automatically once the periods set out in Section 11 of the agreement have expired; expired access and activation credentials are removed in the same run.
  • Only strictly necessary cookies and local storage are used. Audience measurement takes place without any third-party integration, without cookies, without cross-device recognition and without profiling; marketing and advertising networks are not used. Payment and card details are not collected by the processor.

8. Procedure in the event of a personal data breach

  • Breaches affecting the data processed on behalf of the controller are notified to the controller in text form without undue delay and at the latest within 24 hours of becoming aware of them (Section 8 of the agreement).
  • The incident, the immediate measures taken and the course of events are documented; the processor assists the controller with its obligations under Articles 33 and 34 GDPR.

Annex 2 – List of sub-processors

Status: 15 November 2026.

A. Sub-processors in connection with dictation content

  • No. 1 – Data centre operator with registered office and server location in Germany. Service: provision and operation of the computing and storage infrastructure on which the transcription service runs (hosting, storage). Place of processing: Germany (EU). Transfer mechanism: none required.
  • No. 2 – Provider of speech recognition and language models with registered office in the EU. Service: conversion of the submitted voice recordings into text and linguistic correction of submitted texts (AI correction), without storage of the content at the provider (zero data retention, see below). Place of processing: EU/EEA. Transfer mechanism: none required (section B).

In respect of No. 2 the processor gives the following assurance: for its organisation, zero data retention since 16 October 2026 is in place at the provider; the provider has confirmed this in text form. The provider does not retain the transmitted inputs and outputs — recordings, transcripts and correction texts — beyond the time required to generate the response and uses them neither to train nor to improve its models. This applies to the transcription of submitted recordings, realtime transcription and AI correction; the provider has confirmed this in text form for the interfaces used by the transcription service. The assurance covers the content; the provider’s terms and its data processing addendum apply to its technical billing and security metadata.

B. Place of processing and third-country transfers

Processing of dictation content takes place in member states of the European Union or in states party to the Agreement on the European Economic Area. Sub-processor No. 2 has confirmed in text form that requests to the EU endpoint permanently configured in the transcription service, including realtime transcription, are processed in the EU.

Further service providers engaged by a sub-processor are subject to Section 6(2) and (6); the processor monitors their lists (Section 6(2) and (7)). If an own sub-processor with a connection to a third country is engaged in the future, this will only occur in accordance with the procedure under Section 6 and on the basis of a permissible transfer mechanism under Articles 44 et seq. GDPR.

Service providers which the processor uses in its own area of controllership for account and billing data (preamble) are not covered by this agreement; they are named in the privacy policy for Simpliant Dictation.

C. Confidentiality at the sub-processors

The processor is entitled to use the sub-processors described in section A and listed in the list under section D to perform this agreement. They are bound to confidentiality under their data processing agreement with the processor (Article 28 GDPR); this obligation also extends to the persons involved in the processing at their end (Article 28(3), second sentence, point (b) GDPR). At the provider of the speech recognition model (section A No. 2), the content is not stored beyond the time required to generate the response (zero data retention, section A). Whether this involvement meets the requirements for further cooperating persons under Section 203(4), second sentence, No. 2 of the German Criminal Code and Section 43e(3) BRAO is assessed by the controller (Section 10(3) and (4)).

D. List of sub-processors engaged

The processor keeps the names and addresses of the sub-processors described in section A in an up-to-date list. The list forms part of this annex. The processor makes it available to the controller in text form at any time on request; a request to the contact point in the header of the agreement suffices. The list changes only in accordance with the procedure under Section 6(3) and (4); the notice states name, registered office, service, place of processing and affected data categories, and the controller’s right to object remains unaffected.

DPA & TOMs – Simpliant Dictation