Skip to main content
Legal

Privacy policy

Last updated: 20 November 2026

This privacy policy provides information on the processing of personal data when using the web portal, the associated application programming interface and the desktop applications for Windows and macOS of “Simpliant Dictation”. Processing and data storage take place within the European Union or the European Economic Area. If you use sign-in via Google or Microsoft, processing in the USA by the respective provider cannot be ruled out (Sections 4 and 13).

The contractual language is German. Translations are provided for information only; the German version is authoritative.

1. Controller

The controller within the meaning of the General Data Protection Regulation (GDPR) is:

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
Email: support@simpliant.eu

For data protection matters and the exercise of your rights as a data subject, you can reach us at support@simpliant.eu.

2. Overview of the processing activities

We process personal data only to the extent necessary for the provision of our Service, for its security, or to comply with legal obligations. The following sections describe, for each processing activity, the purpose, legal basis, retention period and recipients.

Who is responsible: With regard to the content of your dictations that you submit for transcription as a business customer (e.g. law firm, medical practice, company), we act as a processor on your behalf; the data processing agreement (DPA) is decisive for this, not this policy. This privacy policy concerns the processing activities for which we are the controller (account, billing, operations, portal, apps).

3. Account and registration

Purpose: Creation and administration of your user account, email verification, sign-in, and evidence of your status as an entrepreneur (Section 14 BGB), as we supply businesses only.
Data: email address, optionally name, password (stored exclusively as a hash), verification status, timestamp of your entrepreneur declaration.
Legal basis: Article 6(1)(b) GDPR (contract/pre-contractual measures); for the evidence of entrepreneur status additionally Article 6(1)(f) GDPR (legitimate interest in documenting the B2B conclusion of contract).
Retention: Until the account is deleted; thereafter deletion without undue delay, unless a statutory retention obligation applies.

Upon a new registration, we generate an internal notification to one of our operational mailboxes. It contains the email address and the name of the new account, the time of your entrepreneur declaration and, for the detection and prevention of abuse during account creation, a truncated IP address (IPv4 without the last octet, IPv6 truncated to the /64 prefix) and the browser and platform family (for example “Chrome on Windows”). Neither the full IP address nor the full user agent is used for this. The legal basis is Article 6(1)(f) GDPR (legitimate interest in abuse-free operation).

Obligation to provide data: providing your email address, choosing a password or signing in via Google or Microsoft, and declaring that you act as an entrepreneur within the meaning of Section 14 BGB, are required for the conclusion and performance of the contract. You are under no statutory obligation to provide this information; without it, however, we cannot create an account or conclude a contract with you. For the trial period and the paid plan, the billing details and a means of payment are additionally required (Section 7). Contracting-party details for the contract documents are optional.

Contracting-party details and evidence of acceptance of the contract

Purpose: conclusion of the contract on the basis of the General Terms and Conditions with their annexes, the confidentiality agreement and the data processing agreement (DPA), evidence that, and in which versions, you accepted them (Article 28(9) GDPR, Section 43e(3) BRAO), and provision of the contract documents, on request with your details of the controller.
Data: the designation of the customer as it stood on acceptance: your optional details of the controller (company, address and country, the authorised representative and their function, the register and registration number, a data protection contact point with name, email address and telephone number, and a data protection officer with name and contact details); absent such details, the company and address from your billing details; otherwise the email address of your account. In addition, the versions of the documents accepted, the occasion of the acceptance (start of the trial, order or acceptance in the customer account), the time and reference number of the acceptance, a snapshot of these details, a checksum of the generated copy and a record of the documents sent (file name, version, checksum, time). We do not collect the IP address or the browser identifier for this purpose.
Legal basis: Article 6(1)(c) GDPR in conjunction with Article 28 GDPR, additionally Article 6(1)(f) GDPR (legitimate interest in being able to evidence the conclusion of the contract).
Retention period: we keep the contracting-party details in your account until you change or remove them, at the longest for as long as the contract runs, so that the copy containing your details can be produced; they are deleted there when the account is deleted. The evidence of acceptance is retained for the term of the contract and thereafter until the statutory retention and limitation periods expire, also after an account deletion, attached to an anonymised account record (Section 16); ten years after the acceptance it is then deleted automatically, together with the copy and the dispatch record.

4. Authentication and session management

Purpose: sign-in and maintenance of your session, securing access to the portal, API and apps.
Data: login credentials (email/password), access/API tokens, session cookie, refresh token, device/session identifiers, activation codes; where two-factor authentication is enabled, additionally the TOTP secret (stored encrypted) and the recovery codes shown to you once.
Legal basis: Article 6(1)(b) GDPR; additionally Article 6(1)(f) GDPR for securing access.

Retention period: the access tokens of the dictation applications are valid for 15 minutes and are renewed via a refresh token. The web portal session (session cookie and the associated portal token) is valid for a maximum of 30 days and is renewed on every sign-in. The following periods also apply: activation codes for 30 minutes, password reset links for one hour, email confirmation links for 48 hours. Expired entries are removed by a daily clean-up. Upon the end of the contract, sessions are revoked and access to transcription is deactivated.

Protection against automated sign-in attempts: to fend off automated sign-in attempts we evaluate the IP address of the request and temporarily lock the combination of account and IP address after several failed attempts. We delete the log of sign-in attempts (time, account, IP address and browser identifier) after 30 days. The legal basis is Article 6(1)(f) GDPR (legitimate interest in defending customer accounts against attacks).

Sign-in via third-party providers (SSO): As an alternative, you can sign in via Google (Google Ireland Ltd., Gordon House, Barrow Street, Dublin 4, Ireland) or Microsoft (Microsoft Ireland Operations Ltd., One Microsoft Place, South County Business Park, Leopardstown, Dublin 18, Ireland).
Data: upon sign-in, your email address, your name and the identifier of your account with the respective provider are transmitted to us; conversely, the provider learns that you are signing in to Simpliant Dictation.
Legal basis: Article 6(1)(b) GDPR (performance of the user relationship at your instigation).
Third-country reference: processing in the USA by the respective provider cannot be ruled out in this context. Both providers are certified under the EU-US Data Privacy Framework; any transfer is to that extent based on the European Commission’s adequacy decision pursuant to Article 45 GDPR. The respective provider is an independent controller for the processing within your account held with it.
Using sign-in via third-party providers is voluntary; you can register and sign in with an email address and password instead.

5. Protection against automated access (CAPTCHA)

Purpose: protection of registration and sign-in against automated mass requests.
Method: we use ALTCHA, a self-hosted proof-of-work method. It does not integrate any external service and does not set any cookies; no personal profile data is transmitted to third parties.
Legal basis: Article 6(1)(f) GDPR (legitimate interest in preventing abuse).

6. Dictation, audio and transcription data

Purpose: conversion of your voice recordings into text (transcription), linguistic correction of that text where AI correction is switched on and return of the result to your application.

Processing chain

  1. The app (Windows/macOS) records audio or takes over a recording.
  2. The recording is transmitted, TLS-encrypted, to our transcription service. We operate this service ourselves on rented servers in Germany (hosting providers: see Section 12).
  3. The transcription service forwards the recording for conversion into text to our transcription provider, exclusively via that provider’s permanently configured EU endpoint. The use of a non-European endpoint is technically excluded; if configured otherwise, the service does not start operating.
  4. The transcript is returned to your app.

Storage

  • Temporary audio files are deleted immediately after completion or cancellation of the transcription.
  • Realtime audio is processed exclusively in memory; no audio file is stored permanently for this purpose.
  • Transcripts are not stored permanently on the server side and are only returned to your app.
  • For quota and abuse control, the transcription service stores usage metadata (pseudonymous user identifier, minutes consumed, type of use, timestamp, as well as device/session data). This is deleted automatically after 90 days.
  • In the app when a dictation cannot be delivered: If the connection drops while sending, the transcription service responds with an error or the recording is interrupted, the app keeps the recording exclusively in memory, for at most 10 minutes, in order to send it automatically or at your request (“Erneut senden”, send again). The app sends automatically once after a connection drop, as soon as the connection is restored, and up to three times after an error of the transcription service (after a few seconds, after a further 15 and after a further 45 seconds). The macOS application sends an interrupted recording only at your request; the Windows application sends a recording interrupted by screen lock or sleep automatically after unlocking or waking. The Windows application sends a recording whose result the transcription service can no longer provide or which is too large for it only at your request. The most recently recognised text stays in memory for 5 minutes so that you can insert it again with “Letztes Diktat einfügen” (insert last dictation). If another program has the focus in the meantime or the target cannot be determined reliably, the app places the text on the clipboard, marked as confidential, instead of inserting it. Recording and text are deleted on success, on discarding, when the period expires and when the app is closed. On sign-out, both applications delete the last text, and the Windows application also deletes the recording. The macOS application also deletes the last text immediately on a new activation. On sign-out and on a new activation, it keeps a recording that has not yet been sent until its period expires, but no longer sends it automatically: if the same account signs in again, it offers the recording for sending again; if a different account signs in, it deletes it immediately. The Windows application deletes recording and text as soon as signing in via the browser or an activation with a connection code has succeeded. In both applications, screen lock and sleep do not delete anything, nor, on macOS, does the screen saver: a recording in progress ends; the macOS application still converts it into text, the Windows application does so after unlocking or waking. The text and a recording not yet sent remain in memory, at most until the periods stated above expire; these run from creation and continue during the lock. After unlocking or waking, the app sends a waiting recording once more automatically, up to three times after an error of the transcription service; what is sent only at your request is still sent only at your request. Nothing is inserted automatically afterwards; you can retrieve the text with “Letztes Diktat einfügen” (insert last dictation). The app does not create any files for this. The operating system may swap memory to disk, and on Windows hibernation also writes it there; on macOS swapping is always encrypted, on Windows only if drive encryption (such as BitLocker) is enabled.
  • Protection against double counting: So that such a retry is counted against your quota only once, the app sends an identifier of the recording; it is a hash value and contains no content. For this purpose the transcription service stores only hash values of the user identifier, the identifier and the recording as well as the processing status, no recording and no text. The entry expires 30 minutes after the last send attempt. Expired entries (hash values only) are not deleted on a fixed schedule but at the next transmission of a recording with an identifier, from any user, and at the latest when your account is deleted; even then, neither recording nor text is stored. For the live path of engine version 3, which currently runs only as a pilot, the service stores, per request, a hash value of the user identifier and the request identifier for 24 hours, likewise without content. It deletes expired entries at the next session via this path, from any user; when your account is deleted, it removes all of your entries. Independently of this, the identifier serves as the booking reference of the quota reservation; there it forms part of the usage metadata and is deleted together with it after 90 days.

Processing by the transcription provider

Processing takes place via the provider’s permanently configured EU endpoint; the provider has confirmed that requests to this endpoint, including realtime transcription, are processed in the EU. For our organisation, zero data retention since 16 October 2026 is in place at the transcription provider. The provider does not retain recordings, transcripts or correction texts beyond the time required to generate the response and does not use them to train or 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 our transcription service. The assurance covers the content. The provider’s terms and its data processing addendum apply to its technical billing and security metadata.

AI correction

AI correction is switched on by default in the Windows and macOS applications and can be switched off in the settings at any time. The applications have a German interface; their labels are quoted here in German with an English translation. In the Windows application, AI correction is found in the “KI-Korrektur” (AI correction) section; in the macOS application, it is under “Einstellungen → Allgemein” (Settings → General). If it is switched on or you use it in the app, the app transmits the dictated text, TLS-encrypted, to our transcription service. The service forwards the text via the same permanently configured EU endpoint to the same provider that also performs the transcription, and returns the corrected text to your app. The information above on processing by the provider applies accordingly. Our transcription service does not store the texts; it only logs technical information without content (time, provider, model used, device class, response time and size of the request). In the macOS application, by contrast, the text levels “Wortgetreu” (verbatim), “Bereinigt” (cleaned up) and “Geglättet” (smoothed) and the “Gesprochene Satzzeichen umsetzen” (convert spoken punctuation) function work entirely on your device; no text is transmitted to us or to the transcription provider for them. If AI correction is switched on, however, the macOS application also transmits the text as described above.

Dictionary

You can add your own terms in the application’s “Wörterbuch” (dictionary) (for example technical terms, personal names or place names) and store misspellings for each term, which the application replaces with your spelling after transcription. With the default setting “Nur auf diesem Gerät ersetzen” (replace on this device only), the dictionary stays on your device and is only applied locally after transcription; it is not transmitted to us. Only if you expressly choose “An die Spracherkennung mitsenden” (send to speech recognition) in the dictionary does the application transmit your terms as a recognition aid together with the recording to our transcription service and from there to the transcription provider; if you also use “KI-Korrektur” (AI correction) in the Windows or macOS application, they are also sent there together with the text to be corrected (see “AI correction”). Only the term in your spelling is transmitted, not the stored misspellings, and in total no more than roughly the first 100 words. Terms beyond that or terms that are not suitable as a recognition aid (for example because of special characters or their length) are replaced by the application on your device only. Your organisation can set an IT policy so that the dictionary is only applied on the device and not sent. If you choose to send it, do not store any information in the dictionary that should not be transmitted.

Legal basis: Article 6(1)(b) GDPR (provision of the service commissioned by you, including AI correction). Insofar as you, as a business customer, submit dictation content relating to third parties, we process this as a processor on the basis of the DPA.

7. Subscription and payment processing

Purpose: administration of your plan, the trial period and the usage quotas, as well as processing of payment.
Data: selected plan, subscription/payment status, trial status, usage minutes, payment references. We do not process or store complete payment-instrument/card data – these are collected exclusively by our payment service provider.
Recipient: Mollie B.V., Amsterdam, Netherlands (EU).
Legal basis: Article 6(1)(b) GDPR (contract); for the statutory retention of invoice/accounting data, Article 6(1)(c) GDPR.
Retention period: we retain documents relevant to billing in accordance with the statutory periods: invoices and other accounting vouchers for eight years (Section 147(1) no. 4 and (3) of the German Fiscal Code (AO), Section 257(1) no. 4 and (4) of the German Commercial Code (HGB), Section 14b(1) of the German VAT Act (UStG)); books, records and annual financial statements for ten years (Section 147(1) no. 1 and (3) AO, Section 257(1) no. 1 and (4) HGB). Each period begins at the end of the calendar year in which the document was created (Section 147(4) AO, Section 257(5) HGB).

Protection against repeated trial periods: the free trial period requires a credit card to be deposited. For this purpose, Mollie charges a one-off verification amount of €0.01 to the card, which we then refund automatically, and sets up a payment mandate for subsequent debits. To prevent the same card from being used for several trial periods, we receive a card fingerprint from Mollie, i.e. an identifier of the card generated by Mollie, not the card number. From this value we create a hash value (HMAC) using a secret key and, for this purpose, store exclusively this pseudonymous card identifier, without any link to your customer account.
Purpose: prevention of repeated trial periods.
Data: pseudonymous card identifier (HMAC hash value of the card fingerprint) and time of storage.
Legal basis: Article 6(1)(f) GDPR. Our legitimate interest lies in protecting the free trial period against repeated use with the same card.
Retention period: 24 months; the card identifier is then deleted.

8. Sending of emails and contacting us

Purpose: sending of transactional emails (email address confirmation, activation, password reset, billing-related notices).
Recipient: Brevo (Sendinblue SAS), Paris, France (EU); sender address noreply@simpliant.eu. Open and click measurement is set to anonymised collection in our mail provider’s account; it is not attributed to individual recipients. Brevo technically routes links in our emails via its own addresses; any evaluation is anonymised.
Data: email address, name, content of the respective transactional email including any attachments, in particular the contract documents (contract overview, GTC, confidentiality agreement and DPA), which contain the designation of the customer (company, address and, where given, the authorised representative) and which we send you automatically after acceptance and again when you request them in the portal.
Legal basis: Article 6(1)(b) GDPR.
Retention period: email confirmation links are valid for 48 hours; otherwise only for as long as necessary for delivery and traceability.

Contact form

Purpose: receiving and answering your enquiry submitted through the contact form on our website.
Data: name, email address, type of organisation and your message; optionally also the organisation and the number of workplaces as well as whether a professional secrecy obligation (Section 203 of the German Criminal Code) is affected. To fend off automated bulk enquiries we additionally store a truncated IP address (IPv4 without the last octet, IPv6 truncated to the /64 prefix). We do not store a browser identifier.
Legal basis: Article 6(1)(b) GDPR where your enquiry is aimed at a contract; otherwise Article 6(1)(f) GDPR (legitimate interest in answering enquiries and in fending off automated bulk enquiries).
Retention period: six months from receipt; a daily clean-up removes older enquiries automatically. The email correspondence arising from your enquiry is kept for as long as is necessary to handle it and to document how it was handled.
Please note: do not enter any client, patient or other confidential third-party data in the free-text field.

Diagnostic data for support

Purpose: handling your support request and fixing errors in the desktop applications.
Procedure: the applications create a diagnostics file only when you yourself choose “Diagnose exportieren…” (Export diagnostics; macOS: “Help” menu, Windows: notification area or Settings → Support). Beforehand you see what the file contains. You then decide: with “Diagnose an Simpliant senden – wird nach 90 Tagen gelöscht” (Send diagnostics to Simpliant – deleted after 90 days) the application transmits the file in encrypted form to our server and assigns it to your account; you receive a reference number. With “Nur als Datei speichern” (Save as file only) the file stays on your device and does not reach us. The applications do not provide for sending it by email.
Data: technical information, namely app and system version, settings without credentials, logs of the last seven days and the history of the dictation key (when it was pressed and released and how the application responded, without other keys and without text). The application never sends memory dumps (crash reports of the operating system). They can only be included in a file that you store on your device with “Nur als Datei speichern” (Save as file only). Dictation content, entries in your dictionary, credentials, email addresses and user names from file paths are not included; window titles appear only as their length and as a check value that cannot be reversed. In your account we additionally store the reference number, time, platform, app version, size and checksum of the file.
Recipients: only the persons responsible for support at our company, via the admin area. The file is kept in the non-public storage of our production server at our data centre operator in Germany (Section 12); it is neither opened nor unpacked on the server.
Legal basis: Article 6(1)(b) GDPR (support under the contract), supplemented by Article 6(1)(f) GDPR (our legitimate interest in detecting and fixing errors in the applications).
Retention period: we delete the diagnostics no later than 90 days after receipt. A daily clean-up removes older files automatically, and immediately when your account is deleted. The case details (reference number, time, platform, app version, size and checksum) may remain in database backups for up to 7 days afterwards (Section 10); the diagnostics file itself is not backed up.
Voluntary provision: sending the file is voluntary. Without a diagnostics file we may only be able to trace an error to a limited extent.

9. Downloads and automatic software updates

Purpose: provision of signed installation files and automatic updates of the desktop apps.
Data: when downloading or retrieving automatic updates, your IP address is processed for technical reasons; in addition, the time and the requested version may be logged.
Legal basis: Article 6(1)(b) GDPR (provision of the service) and Article 6(1)(f) GDPR (security and currency of the software).
Retention period: short-term technical logs with automatic rotation; no permanent storage.

Download counts: Every ten minutes, we automatically count from the access log how often an installation file was delivered per operating system, separately for downloads in the browser and automatic updates. We use the IP address only transiently in memory to combine repeated requests for the same file within such a ten-minute window. It is neither stored nor passed on for this purpose. Only the count per operating system is sent to our Plausible instance.

Record in your customer account: when you download the application from the signed-in area, we record that event in your customer account.
Data: your user account, the operating system you chose (Windows or macOS), the version number of the file provided and the time of the download. We deliberately record no IP address, no browser or device information and no location data. Downloads without signing in are not recorded, and we do not create pseudonyms or recognition identifiers for this purpose. A further download (for example on a second device) is recorded as a separate event.
Purpose and legal basis: customer care and support (which version you use, whether the installation reached you) and evidence that we provided the software we owe you; the legal basis is Art. 6(1)(b) GDPR, additionally Art. 6(1)(f) GDPR.
Retention: until your account is deleted; the records are deleted in full together with the account. They form part of the information provided under Art. 15 GDPR and are contained in a data export of your account that we provide on request (see Section 16). They are not transferred to third parties.

10. Server logs, error monitoring and operational security

Purpose: ensuring operation, stability and security, error analysis, abuse prevention.
Data: technically necessary log data (e.g. time, requested resource, status code, error messages; on an incident basis, IP address and user agent).
Legal basis: Article 6(1)(f) GDPR (legitimate interest in secure operation).
Retention period: the logs of the individual services rotate by size (at most five files of 20 MB each per service) and are continuously overwritten in the process. The access log of the upstream reverse proxy, whose entries contain IP addresses, is rotated daily and deleted after 7 days. Only connection and security data are logged; no log contains dictation content or transcripts, because these are not stored permanently on the server side.
Backups: a backup of the database and of the object storage is created on the production server every day and before every change to the production environment; these snapshots are stored encrypted and deleted automatically after 7 days. In addition, we back up the systems in encrypted form to a backup archive on separate infrastructure: database snapshots of Simpliant Dictation are selected for deletion there after 5 days and removed after 7 days at the latest; encrypted emergency copies of these database snapshots at geographically separate locations in Germany are deleted after 7 days at the latest. Backups of the system configuration and of the operational logs are retained according to a staggered rule: seven daily, four weekly and six monthly snapshots. Because the access log of the reverse proxy is part of these operational logs, IP addresses may be contained in these backups for up to six months; the backups serve solely to restore operations after an outage and are not analysed for any other purpose. The daily transfer of the encrypted backups to one of the separate backup destinations is carried out by a server of the hosting provider in Finland (EU); no backup snapshots are stored there, only encrypted administrative data of the backups (directory and index data) are cached there. With the keys also held there, file names and the directory structure of the backups can be decrypted, but not file contents. None of these backups contain dictation content.

Error monitoring

Purpose: detection and remedying of technical faults in the portal, the interface and the apps.
Data: error message and technical stack trace, the address called up, browser and operating system details, time. Dictation content, credentials and entries in form fields are not transmitted; we do not transmit your IP address. The same applies to the reports your browser makes about content we have blocked (violations of our content security policy).
Desktop applications: The applications for Windows and macOS transmit error reports only with your consent. The option “Fehlerberichte senden” (send error reports) is switched off by default; the application shows it during setup with a short explanation, not pre-selected. You can select it there or switch it on and off in the application's settings at any time. It does not send any reports before setup is completed. As long as the option is switched on, the application transmits a technical report to dictation-api.simpliant.eu in the event of a crash, an unexpected program error or a dictation key that does not respond as expected; from there it is passed on to our own error monitoring. The report contains the type and code of the error, the affected location in the program, the version of the application and of the operating system, the processor type and, where applicable, the history of the dictation key (when it was pressed and released and how the application responded). It does not contain dictations, texts, the wording of error messages, clipboard contents, window titles, names of files and folders outside the application, user or computer names, or any account or device identifier; memory dumps are not transmitted. Your IP address is processed when the connection is established and is not stored with the report; it appears only in the access log of our server (see server logs above). The legal basis is your consent: where the application reads information on your device for this purpose (version of the application and of the operating system, processor type, history of the dictation key), this is based on Section 25(1) TDDDG; the further processing is based on Article 6(1)(a) GDPR. Consent is voluntary. You can withdraw it at any time with effect for the future by switching off “Fehlerberichte senden” (send error reports) in the application's settings; this does not affect the lawfulness of processing carried out before the withdrawal (Article 7(3) GDPR). The application then no longer sends reports; reports already transmitted are deleted after the period stated below.
Recipients: none. We operate the error monitoring ourselves on rented servers in Germany (Section 12); reports from your browser are received at our own address and forwarded from there to our own error monitoring. No transfer to third parties takes place.
Legal basis: Article 6(1)(f) GDPR (legitimate interest in fault-free and secure operation); for error reports from the desktop applications, Section 25(1) TDDDG and Article 6(1)(a) GDPR (consent, see above).
Retention period: error reports are deleted automatically after 30 days at the latest.

11. Cookies and local storage

We use exclusively technically necessary cookies and local storage (Local Storage / Session Storage) that are required for sign-in, session management, storing your language selection and the plan selection you have initiated – in particular the session cookie. This processing is permissible without consent pursuant to Section 25(2) no. 2 TDDDG, as it is strictly necessary in order to provide the service expressly requested by you.

In addition, we store your language selection in a cookie (NEXT_LOCALE) so that the page appears in the language you have chosen. It contains only the language identifier (“de” or “en”) and no information about you personally. Its lifetime is one year; you can delete it in your browser at any time. This cookie, too, is permissible without consent pursuant to Section 25(2) no. 2 TDDDG, because it is required for the presentation of the page that you have requested.

We do not use any marketing or tracking cookies. The reach measurement described below sets no cookies, uses neither local storage nor session storage and does not store any information on your device.

Reach measurement with Plausible Analytics

Purpose: Statistical analysis of the use of this website in order to tailor content and offering to actual demand and to improve technical delivery. For this we use Plausible Analytics. We operate Plausible ourselves at analytics.simpliant.eu, on a server rented from a data centre operator in Germany (EU). The operator processes the data as our processor pursuant to Article 28 GDPR on the basis of the data processing agreement concluded with it (see Section 12). We do not pass the data collected on to any third party.

How the measurement works: We do not embed any script from Plausible or any other provider but use our own measurement code. It sets no cookies, uses neither local storage nor session storage and neither stores nor accesses any information on your device that would require consent under Section 25(1) TDDDG. It only checks whether your browser transmits the “Do Not Track” setting; if it does, no measurement takes place at all. No personal data is stored and no cross-device or cross-site user profiles are created. In particular, your IP address is not stored: the Plausible server processes it transiently only, in order to derive, together with your browser identifier, a daily rotating, non-reversible hash that allows repeat requests on the same day to be counted as a single visit. This makes it impossible for us to attribute the data to an identified person.

Data collected: page requested (address without parameters; one-time identifiers, for example from password reset or email confirmation links, are removed by the measurement code before sending), referrer (only the domain of the referring website), device type, browser, operating system and country of origin based on a local lookup table, without any query to a third party. In addition, we count clicks on download links and on links leading to other websites (in each case only the target address without parameters), as well as the completion of individual steps: a click on a plan button, the start of typing in the registration form, completed registration, confirmed email address, the start of a payment process, the start of the trial period, completed purchase, the download of an installation file and the opening of the overview in the customer area; in addition, requests for pages that do not exist (error 404). With these events we transmit technical information only, without any reference to your account: the language version of the page, the short identifier of the plan concerned, the type of payment process, the operating system of an installation file, the path requested in the case of an error 404 and, for a completed purchase, the net invoice amount of the plan. All reporting is aggregated; individual visitors cannot be identified from it.

Campaign parameters: If you reach our website via an advertising or referral link that we have tagged, that link carries parameters naming the channel (utm_source, utm_medium, utm_campaign, utm_content, utm_term, ref), for example “search engine” or “trade portal”. We count these values together with the page view and, where they are available, together with a completed registration and a completed purchase, in order to see through which channels our offering is found. We transmit only the channel designations contained in the link, in normalised form; no identifier, no number and no other information relating to you is created in the process, and we still do not transmit the full address together with its parameters. So that the information is retained across several page views, we hold it solely in the memory of the loaded page: we set no cookie for this and use neither local storage nor session storage. There is therefore no access to your terminal equipment within the meaning of Section 25(1) TDDDG, so that the question of consent does not arise. If you reload the page, open a new tab or return to us from another website, the information is irretrievably lost.
Legal basis: Article 6(1)(f) GDPR. Our legitimate interest lies in being able to assess the effectiveness of the channels we use; no profiling takes place and the information is not stored beyond the session. If your browser transmits “Do Not Track”, this collection does not take place either; in all other respects the right to object under Article 21(1) GDPR applies (see Section 16).

Retention period: We delete the measurement data 14 months after it was recorded.

Legal basis: Article 6(1)(f) GDPR. Our legitimate interest lies in being able to understand the use of our website statistically in order to improve content, offering and technical delivery. We have balanced this against your interests: the measurement takes place without cookies, without profiling, without storing your IP address and without disclosure to third parties, so your rights and freedoms are affected only slightly; no overriding interests worthy of protection are apparent. We operate Plausible ourselves; the only party involved is our hosting provider, acting as processor (Article 28 GDPR), which provides the server in Germany. There is no transfer to a third country. You may object to this processing pursuant to Article 21(1) GDPR (see Section 16); in addition, no measurement takes place if your browser transmits “Do Not Track”, and measurement can be prevented with a content blocker.

Server-side metrics: In addition, we count the following events on our servers: a confirmed trial, a confirmed purchase, a renewal and a plan change (each with the short name of the plan, the type of event and the net amount in whole euros), the cancellation of the subscription or of the trial (with the short name of the plan), the sign-in of the first device of an account, the first dictation of an account (only the type of application, no content, no duration) and a completed account deletion. To our self-hosted Plausible instance we transmit only the name of the event and these details. We do not transmit your account identifier, email address or IP address, nor any content. Internally, we create a pseudonymous check value for each event using a server key. It prevents the same event from being counted twice and can only be linked to an account with this key. We do not set any cookies for this and do not access your device. The “Do Not Track” setting only concerns measurement in the browser and does not apply to these counts, as they have no connection to your browser. Retention period: We delete the check values together with the associated details, and the counts in Plausible, 14 months after they were recorded. Legal basis: Article 6(1)(f) GDPR. Our legitimate interest lies in being able to evaluate the use and business development of our offering.

12. Recipients and processors

To provide our Service, we use the following service providers, with whom agreements pursuant to Article 28 GDPR are in place. The processing carried out by these service providers takes place within the EU/EEA (Section 13).

RecipientPurposeLocationLegal basis
Data centre operator with registered office in GermanyHosting/server operation (production server, database, transcription gateway, analytics server)Germany (EU); transfer of encrypted backups via a server in Finland (EU)Article 6(1)(f) / Article 28
Provider of speech recognition models with registered office in the EUSpeech-to-text transcription and AI correction via EU endpoint, without storage of the content (zero data retention)EU (via the EU endpoint)Article 6(1)(b) / Article 28
Mollie B.V.Payment processingNetherlands (EU)Article 6(1)(b)
Sendinblue SAS (Brevo)Sending of transactional emailsFrance (EU)Article 6(1)(b)

We operate the automated abuse protection (ALTCHA) and the reach measurement (Plausible Analytics) ourselves on rented servers in Germany. In this respect, the data centre operator acts as our processor in its capacity as hosting provider (see table); no other service providers are involved. Disclosure to other third parties only takes place where legally required or for the purpose of legal action. On request to support@simpliant.eu, we will provide the names and addresses of the service providers described by category in the first two rows.

13. Transfer to third countries

The processing carried out by us and by the service providers listed in Section 12 takes place within the EU/EEA. The only exception is if you use sign-in via Google or Microsoft (see Section 4): in that case, processing in the USA by the respective provider cannot be ruled out. Both providers are certified under the EU-US Data Privacy Framework; any transfer is to that extent based on the European Commission’s adequacy decision pursuant to Article 45 GDPR.

14. Legal bases at a glance

  • Article 6(1)(b) GDPR (contract/pre-contractual): registration, authentication, transcription including AI correction, subscription/payment, transactional emails, downloads/updates, diagnostics files for support.
  • Article 6(1)(f) GDPR (legitimate interest): operational security, abuse prevention, logging, CAPTCHA, error monitoring, reach measurement, troubleshooting based on diagnostics files.
  • Article 6(1)(c) GDPR (legal obligation): retention under commercial and tax law; evidence of the data processing agreement (Article 28 GDPR).
  • Article 6(1)(a) GDPR (consent): only insofar as we ask you separately for consent, for example for error reports from the desktop applications (Section 10); revocable at any time (Article 7(3) GDPR).

15. Retention periods at a glance

We store personal data only for as long as is necessary for the respective purposes or as required by statutory retention obligations.

CategoryRetention period
Audio (temporary / realtime)Immediate deletion after processing or cancellation; realtime only in memory
TranscriptsNot stored permanently on the server side; returned to your app
Recording and last text in the app when a dictation cannot be delivered (for example after a connection drop, a service error, an interruption, a screen lock or sleep)Only in the app’s memory: recording at most 10 minutes, last text 5 minutes, each from creation, including during a lock or sleep; deleted earlier on success, on discarding and when the app is closed, and on sign-out and on a new activation as described in Section 6
Identifier against double counting (hash values only, no content)expires 30 minutes after the last send attempt; deleted at the next transmission with an identifier, at the latest with the account; live path version 3 (pilot): 24 hours, deleted at the next session via this path, at the latest with the account; as the booking reference of the quota reservation 90 days (like usage metadata)
Inputs and outputs at the transcription providerNo retention beyond generation of the response (zero data retention since 16 October 2026, see Section 6)
Usage/quota metadata (individual events)90 days, then automatic deletion
Monthly total of usage minutes per account (billing basis)for the term of the contract, thereafter as a billing record for 8 years (Section 147(3) AO, Section 257(4) HGB)
Access tokens of the dictation applications15 minutes
Web portal session (session cookie and portal token)maximum 30 days; renewed on every sign-in
Activation codes30 minutes
Password reset links1 hour
Email confirmation links48 hours
Contact enquiries from the contact form6 months from receipt, then automatic deletion
Diagnostics files you send us from an application90 days from receipt, then automatic deletion; immediately upon account deletion
Log of administrative access in the admin area24 months, then automatic deletion
Technical logsservice logs: size-based rotation (at most 5 × 20 MB per service); access log of the reverse proxy (with IP addresses): 7 days
Log of sign-in attempts (time, account, IP address, browser identifier)30 days, then automatic deletion
Error reports (error monitoring)30 days, then automatic deletion
Backups of Simpliant Dictationlocal snapshots (encrypted) 7 days; in the encrypted backup archive (a system of our own in Germany) database snapshots 5 days, at most 7 days; emergency copies (Germany) at most 7 days; system backups including the operational logs seven daily, four weekly and six monthly snapshots (up to 6 months)
Invoices and accounting vouchers8 years (Section 147(3) AO, Section 257(4) HGB, Section 14b(1) UStG)
Books, records and annual financial statements10 years (Section 147(3) AO, Section 257(4) HGB)
Pseudonymous card identifier (protection against repeated trial periods)24 months, then deleted
Evidence of acceptance of the contract (versions, time, reference number, designation of the customer, record of documents sent)for the term of the contract, thereafter until the statutory retention and limitation periods expire; after an account deletion, automatic deletion ten years after the acceptance
Account datauntil deletion of the account

16. Your rights

Under the GDPR, you have the following rights:

  • Access (Article 15 GDPR)
  • Rectification (Article 16 GDPR)
  • Erasure (Article 17 GDPR)
  • Restriction of processing (Article 18 GDPR)
  • Data portability (Article 20 GDPR)
  • Objection to processing based on Article 6(1)(f) GDPR (Article 21 GDPR)
  • Withdrawal of consent granted, with effect for the future (Article 7(3) GDPR)

You can exercise two of these rights directly in your customer account. In the signed-in area under My account you will find the data export, which provides all data stored about your account as a JSON file for download (Articles 15 and 20 GDPR), as well as account deletion (Article 17 GDPR). For security reasons, deletion requires re-authentication (your password, or, if you sign in via Google or Microsoft, signing in with that provider again) and the entry of a confirmation phrase.

Once confirmed, the deletion is carried out without any further waiting period: any running subscription is terminated with the payment service provider; your transcription and usage data, device, download and sign-in data as well as your contracting-party details are deleted; issued activation codes and device activations are deactivated; and your user account is anonymised. The process is irreversible. Excluded from it is data subject to a statutory retention obligation (in particular invoicing and payment data) and the record of concluded data processing agreements (Article 17(3)(b) and (e) GDPR); these remain attached to an anonymised account record and are deleted once the retention periods expire. At the payment service provider, the details required for processing and for statutory retention remain in place according to its own periods. In the backups the deletion follows on: backup snapshots created before the deletion still contain your data until they expire according to the periods set out in Section 10; we do not restore them in order to bring back deleted data.

For all other rights, and if you would rather not use the two functions described above yourself, a message to support@simpliant.eu is sufficient; we will then handle your request via that address.

Right to object

You have the right to object at any time, on grounds relating to your particular situation, to processing that we base on Article 6(1)(f) GDPR (Article 21(1) GDPR). This concerns operational security and logging, abuse prevention including CAPTCHA and protection against repeated trial periods, error monitoring and reach measurement. An informal objection to support@simpliant.eu is sufficient. We will then no longer process the data concerned, unless we can demonstrate compelling legitimate grounds which override your interests, rights and freedoms, or the processing serves to establish, exercise or defend legal claims. We do not carry out direct marketing.

17. Right to lodge a complaint with a supervisory authority

Without prejudice to any other legal remedies, you have the right to lodge a complaint with a data protection supervisory authority. The supervisory authority competent for us is:

Berlin Commissioner for Data Protection and Freedom of Information
Alt-Moabit 59–61, 10555 Berlin
Telephone: 030 13889-0 · Email: mailbox@datenschutz-berlin.de

18. Data security

We take appropriate technical and organisational measures to protect your data against unauthorised access, loss or manipulation. Transmission is encrypted (TLS). We operate our services ourselves on servers in the EU rented from the hosting provider listed in Section 12; encrypted backups are additionally kept on a system of our own in Germany and as emergency copies at separate locations in Germany. Transcription is fixed to the provider’s EU endpoint; if configured otherwise, the service does not start operating. Passwords are stored exclusively as a hash.

19. No automated decision-making in individual cases

Solely automated decision-making, including profiling, with legal effect pursuant to Article 22 GDPR does not take place. Transcription is a pure text conversion without any assessment of your person.

20. Amendments to this privacy policy

We adapt this privacy policy as soon as changes to our processing or to the legal situation make this necessary. The version published on this page at the given time applies.

Privacy policy – Simpliant Dictation