This translation is for information only. Only the German version is legally binding: Read the German version.
How to conclude the DPA
- By registering you confirm the DPA. It applies automatically as soon as you use Ora professionally, you do not have to fill in anything.
- Download the PDF and keep it with your records, for example for your documentation under § 62a StBerG.
- You can get a copy signed by us on request via the contact form.
Sub-processors
- Soniox Inc. (USA)Speech recognition in Fast mode and evaluation of the meeting recording, EU region only for audio and transcripts
- Mistral AI SAS (France)AI text refinement, fallback for speech recognition, EU endpoint only
- Vercel Inc. (USA)Ora service and account area, data center in Frankfurt am Main
- Supabase Pte. Ltd. (Singapore)Account database, sign-in and file storage (including meeting recordings until evaluation), data center in Frankfurt am Main
- Sendinblue SAS / Brevo (France)Sending sign-in links and notification emails
- Cloudflare, Inc. (USA)Turnstile, protection against automated requests
Version 2.1 · As of: 17 November 2026
Agreement on the processing of personal data on behalf of a controller pursuant to Art. 28 GDPR with a confidentiality undertaking pursuant to § 62a StBerG and § 203 StGB
between
the Customer, the holder of an Ora account who uses Ora for professional or business purposes, hereinafter the "Controller",
and
Gianmarco Colaiacolo, sole proprietor, trading as "Ora", Roman-Herzog-Str. 26, 81248 München, Germany, e-mail support@ora-ai.de, hereinafter the "Processor".
1. Subject Matter, Conclusion and Term
(1) The subject matter is the processing of personal data by the Processor on behalf of the Controller when using Ora (Mac app "Ora", Ora service api.ora-ai.de) for professional or business purposes.
(2) The agreement is concluded in text form (Art. 28 (9) GDPR, § 62a (3) StBerG). It becomes part of the terms of use upon registration, at which the Controller confirms having taken note of it, and applies as soon as and to the extent that the Controller uses Ora for professional or business purposes. The Processor stores the time and version of the confirmation on the account and, on request, provides a signed copy.
(3) The agreement applies for the duration of the terms of use and ends with their termination or the deletion of the account.
2. Nature and Purpose of the Processing, Types of Data, Data Subjects
(1) Nature and purpose: The Processor receives audio and text via the Ora service, forwards them for speech recognition and AI processing (refining, summarising, answering questions and further functions chosen by the Controller) to the sub-processors listed in Annex 1, and returns the result to the app. At the Controller's request, it also stores encrypted content for synchronisation between the Controller's devices.
(2) Types of data: Content of dictations and meetings:
- Audio (Fast mode; continuously for meetings and, after the end, as the whole recording of both tracks; the sub-processor distinguishes the speakers within the connection or across the whole recording, the Processor does not transmit voice samples and does not create voice profiles),
- text, the template instruction, matching custom terms, up to 100 terms as context for speech recognition (for meetings up to 300 terms from own terms and basic vocabulary, the field of the profile and up to 30 display names of participants, unless the Controller switches this off),
- for functions that the Controller chooses: text around the cursor and selection, window and screen text and names derived from it, text to be revised with an instruction (Refine), the transcript of a meeting or excerpts from several meetings with questions (Chat), summary for a follow-up, display names of speakers, an excerpt for detecting the end of a meeting, individual words for the word check,
- for synchronisation: encrypted content and metadata (area, size, times, identifiers).
The content may contain personal data of any kind, including special categories under Art. 9 GDPR and information subject to professional secrecy.
(3) Data subjects: the Controller, its employees, persons named in dictations (for example clients, customers, patients, business partners) and participants of transcribed meetings, including their voice.
(4) Storage: The Ora service is designed to only pass content through and to process it in working memory while the request is running, and not to store it permanently. The exception is synchronisation: there it stores the content encrypted by the Controller on its devices as ciphertext; the service is designed so that the Processor cannot read it. The app keeps audio for the evaluation of a meeting in Fast mode encrypted on the Controller's device, at most 24 hours after the end of the meeting, and sends it after the meeting to the private file storage of the Ora service (Annex 1). There and at the sub-processor for speech recognition it remains only until deletion after the result, at the latest 24 hours after the evaluation starts. The Ora service is designed to use the recording only for forwarding. Sub-processors process content on its behalf under Annex 1; their storage is governed by the contracts concluded with them.
(5) Not covered are the account, device and counter data for which the Processor is itself the controller (see the Privacy Policy), and data that is processed only on the Controller's device and does not reach the Processor.
3. Instructions
(1) The Processor processes the data only on documented instructions from the Controller, including with regard to transfers to third countries, unless it is required to process by Union law or the law of a Member State; in that case it informs the Controller beforehand, unless the law prohibits this.
(2) The instructions result from this agreement and the settings in the app (in particular Fast or Local mode, AI refinement, meeting transcription, optional functions and synchronisation). The Controller issues further instructions in text form to support@ora-ai.de.
(3) If the Processor considers an instruction to violate data protection law, it points this out without undue delay.
4. Confidentiality and Secrecy
(1) The Processor ensures that the persons authorised to process are committed to confidentiality or are subject to an appropriate statutory obligation of secrecy.
(2) If the Controller is subject to a professional obligation of secrecy, in particular under § 203 StGB or § 57 (1) StBerG, the following also applies:
- The Processor is obliged to maintain secrecy about all third-party secrets that become known to it in the course of providing the service.
- It obtains knowledge of third-party secrets only to the extent the service requires and uses them for no other purpose.
- It has been informed that, as a person assisting under § 203 (4) StGB, it may be liable to prosecution if it discloses a third-party secret without authorisation.
- It obliges further persons and sub-processors to maintain secrecy and points out to them the criminal liability under § 203 (4) StGB, to the extent this is legally required and contractually possible (§ 62a (3) StBerG). Towards sub-processors, it otherwise imposes the obligations under No. 6 (3) by contract.
(3) Whether the use of the sub-processors listed in Annex 1 meets the Controller's professional-law requirements, in particular § 62a (4) StBerG for services provided abroad, is for the Controller to assess. The Processor provides the information in the Annexes for this purpose.
5. Security of Processing
The Processor takes the technical and organisational measures set out in Annex 2 (Art. 32 GDPR) and may adapt them provided the level of protection is not reduced.
6. Sub-processors
(1) The Controller grants general authorisation to engage sub-processors. Those engaged at the time of conclusion of the agreement are listed in Annex 1.
(2) The Processor informs the Controller at least 30 days in advance, by e-mail to the address stored in the account or in the app, of any intended addition or replacement. Within this period, the Controller may object to the change in text form for an important data protection reason. In that case, it may end its professional or business use and delete its account.
(3) The Processor imposes on each sub-processor by contract essentially the same data protection obligations as in this agreement. If a sub-processor fails to meet its obligations, the Processor is liable to the Controller for their fulfilment in accordance with No. 12.
7. Third Countries
(1) The Processor has set up the services so that content is processed in data centres in the European Union (Annex 1).
(2) If sub-processors are established outside the EU or access from there is possible, the transfer takes place only under the conditions of Art. 44 et seq. GDPR, on the basis of the Standard Contractual Clauses of the European Commission (Art. 46 (2) (c) GDPR) and, where the provider is certified under the EU-US Data Privacy Framework, the adequacy decision (Art. 45 GDPR).
8. Assistance to the Controller
(1) The Processor assists the Controller with appropriate technical and organisational measures in handling requests from data subjects (Art. 12 to 22 GDPR). Because it does not store content permanently, it can generally not provide any information about it; for the evaluation of meeting recordings it keeps a job log without content (Annex 2), from which it provides information on request. If a data subject contacts it, it forwards the request without undue delay.
(2) It assists the Controller with the obligations under Art. 32 to 36 GDPR (security, notification of breaches, data protection impact assessment, prior consultation), to the extent the nature of the processing and the information available to it allow.
9. Notification of Breaches
The Processor notifies the Controller of a personal data breach affecting its data without undue delay, at the latest within 48 hours after becoming aware of it, by e-mail to the address stored in the account, with the information under Art. 33 (3) GDPR to the extent available; it supplies missing information later.
10. Evidence and Audits
On request, the Processor provides the Controller with the information necessary to demonstrate compliance with the obligations under Art. 28 GDPR and enables audits, including inspections, by the Controller or an auditor mandated by it who is bound to secrecy. They must be announced with reasonable notice, as a rule at least 14 days, take place during normal business hours without disproportionate disruption to operations, and are carried out primarily by written information and documents.
11. Deletion and Return
(1) Content is not stored permanently (No. 2 (4)); after processing has ended it therefore generally need not be returned or deleted. For synchronisation, the Processor deletes the cloud data at the Controller's initiative ("Delete cloud data") and upon termination of the agreement or deletion of the account. The export in the app serves as return. Recordings of meetings are deleted by the Processor in the file storage and at the sub-processor immediately after the result, on errors, at the Controller's initiative ("Discard", "Delete", signing out the device) and with the deletion of the account, otherwise by a continuous cleanup at the latest 24 hours after the evaluation starts.
(2) The Processor deletes the data mentioned in No. 2 (5) in accordance with the periods in the Privacy Policy, and immediately upon deletion of the account. Data that is only on the Controller's device is deleted by the Controller itself in the app or by uninstalling. Statutory retention obligations remain unaffected.
12. Liability and Final Provisions
(1) Art. 82 GDPR applies towards data subjects. As between the parties, the liability provisions of the terms of use apply.
(2) In case of conflict, this agreement prevails on data protection matters.
(3) The Processor announces changes to this agreement in text form at least 30 days before they take effect; Section 12 of the terms of use applies accordingly.
(4) German law applies. If the Controller is a merchant, a legal entity under public law or a special fund under public law, the place of jurisdiction is München.
Annex 1: Sub-processors
The basis for third-country links is No. 7 (2). The sub-processors process the data on behalf of and on the instructions of the Processor.
Sub-processor | Service | Registered office | Place of processing | Data |
|---|---|---|---|---|
Soniox Inc., 1045 Helm Lane, Foster City, CA 94404 | Speech recognition in Fast mode (dictations, meetings, distinguishing speakers), evaluation of the whole meeting recording as a job | USA | EU region; according to the provider, sub-contractors Amazon Web Services, Google Cloud, Oracle Cloud (EU regions) and Cloudflare | Audio, language, up to 100 terms as context (for meetings up to 300 terms and display names of participants); for the meeting recording file or retrieval address, transcript and context until deletion by the Processor, at most 24 hours after the evaluation starts |
Mistral AI SAS | AI refinement, summary, questions about meetings, Refine, further chosen AI functions, fallback for speech recognition | France | EU, EU endpoint | Text, instructions, matching terms, chosen context, audio in the fallback case |
Vercel Inc. | Operation of the Ora service and the account area | USA | Frankfurt am Main | Content in transit (for the meeting evaluation the recording as a stream, not stored), technical connection data |
Supabase Pte. Ltd. | Account database, sign-in, file storage (app updates, synchronisation, meeting recordings until evaluation) | Singapore | Frankfurt am Main | Account, device and counter data; for synchronisation, encrypted content and metadata; meeting recordings for at most 24 hours and job log without content |
Sendinblue SAS (Brevo) | Sending of sign-in links and notification e-mails | France | EU | E-mail address |
Cloudflare, Inc. | Turnstile, protection against automated requests | USA | global network | IP address, browser details |
Annex 2: Technical and Organisational Measures (Art. 32 GDPR)
Area | Measure |
|---|---|
Content | The Ora service is designed to process audio and text of dictations and meetings only in working memory while the request is running, and not to store them in databases, files, logs or error reports. Exceptions: synchronisation and the recording of a meeting in Fast mode until it has been evaluated (No. 2 (4)). |
Transmission | Connections between the app, the Ora service, the account area and sub-processors run over HTTPS or WSS with TLS 1.2 or higher; the account area sends security headers (including Strict-Transport-Security). |
Location | The Ora service and the account area run in the Frankfurt am Main region, the database and file storage in Frankfurt am Main; Mistral and Soniox are addressed via their EU endpoints, Soniox processes meeting recordings in the EU region. |
Data minimisation | Only the content necessary for the request goes to sub-processors. The following are intended not to be transmitted: e-mail address, account, device or installation identifier, IP address, headers of the app, text of text blocks, basic vocabulary (except as context for meetings, No. 2 (2)), notes and titles. For the meeting evaluation the sub-processor receives only a random job identifier as an identifier, never the meeting identifier. Names from the screen go along at most as individual terms. No device or computer names are stored. |
Access protection | Only signed-in devices can use the Ora service. The device token is random, is kept in the device's Keychain (not synchronised) and at the service only as a SHA-256 hash. The app signs in via the browser with a verifier (PKCE) and a one-time code, of which only hash values are stored. |
Keys | The access key to the AI services is held as a server secret by the Ora service and not in the app. |
Access control | Users can read only their own account record (application and Row Level Security in the database). Changes to account, device and counter data are made only by the server. Evaluation jobs for meeting recordings are bound to the account and device of the first creation; foreign identifiers receive the same answer "not found". |
Input control | Requests are checked on the server side; only permitted models, fields and sizes are accepted. |
Abuse protection | Requests are limited per device, account, e-mail address, IP address and installation, including for referral codes. The counters contain only fingerprints (HMAC) and are deleted after 2 hours at most. Sign-in and the contact form are protected by Cloudflare Turnstile. |
Logging | Operating logs contain, per request, the time, type, result code, duration, length or audio duration and a non-traceable short device identifier, without content, tokens and IP addresses (as intended); retention 14 days, no disclosure to external logging services. For the meeting evaluation the Processor keeps a job log as proof of deletion (random job identifier, times, audio duration, deletion result per object, never audio, text, context or addresses), removed 30 days after deletion. |
Deletion periods | Sign-in requests: expiry after 10 minutes, deletion at the latest 2 hours later; dictation receipts 2 hours; meeting recordings in the file storage and at the sub-processor immediately after the result, at the latest 24 hours after the evaluation starts; job log 30 days after deletion; minute counter of the evaluation 48 hours; abuse counters 2 hours at most; referral assignments without a granted month 90 days; word counter current and four previous weeks; meeting counter 8 weeks; device sign-ins upon sign-out, replacement or after 60 days without a signal; unconfirmed registrations 24 hours; account immediately upon deletion, after 23 months without activity with notice 30 days beforehand. |
Data on the device | The app stores dictionary, history, meetings, notes, text blocks and collected words on the Controller's device in encrypted form (key in the Keychain), with file permissions for the user only and without Time Machine backup. History and meetings are deleted after the chosen period (history never, 24 hours, 7 or 30 days; meetings 1, 7 or 30 days). Optional functions are off until the Controller chooses them. Audio is not stored on the hard drive, except the recording of a meeting in Fast mode: encrypted (key in the keychain of this device, not synchronised), until it has been evaluated and at most 24 hours after the end of the meeting. |
Synchronisation | Content is end-to-end encrypted on the Controller's devices, the key is not held by the Processor. Only the ciphertext and metadata are at the service. Deletion by the Controller or with the account. |
Administrative access | Only the Processor itself has access to hosting, database, configuration and the operator dashboard. The dashboard shows account, licence, device and counter data, not content; changes are logged with time, account and action (13 months). |
Availability | If refinement fails or the service is unreachable, the app can insert the recognised text unedited; in Fast mode, the Ora service can switch to a further service if the recognition service fails, and the app can recognise locally if there is no connection, provided the speech model is loaded. Requests to sub-processors are aborted after a fixed time limit. |