Table of Contents

    Privacy Policy for the dictop app

    Last updated: 2026-09-27

    Dictop is a dictation app made by Actondon UG (haftungsbeschränkt). This policy describes the Dictop apps for iOS and macOS and the iOS keyboard. The website policy below is separate.

    1. Processing choices

    Dictop lets you choose an on-device or cloud model for speech-to-text. On-device speech models and Apple Intelligence processing, where available and selected, process the applicable audio or text on your device. They do not send that content to Dictop’s service for that processing.

    If you select a cloud speech model, Dictop sends the recorded audio and the selected speech settings needed to complete that request to Dictop’s speech service and the selected provider. If you select a cloud AI rewrite model, Dictop sends the transcript and the configured rewrite prompts needed to produce that rewrite. The relevant provider’s terms and privacy policy apply to its processing. Dictop does not use dictation audio or transcript content for advertising or tracking.

    Cloud request completion is not exactly-once: if the app is terminated after a provider may have accepted a request but before completion is saved, a deliberate retry can send the request again and may consume credits again.

    2. Local recording, transcripts, and keyboard use

    The Dictop app, not the custom keyboard extension, requests microphone access and records audio. The keyboard does not receive microphone access, including when Full Access is enabled.

    To dictate from other apps, you explicitly start a keyboard session in Dictop. The microphone stays active for that session, for up to one hour or until you stop it. Between dictated segments, idle audio is discarded. A recorded segment is retained locally only while it is needed to transcribe, retry, or recover that segment, then is removed on success, insertion or discard, expiry, or the app’s applicable recovery cleanup. A pending insertion result is removed after acknowledgement or its expiry. If you enable saved history, finished text is stored locally as a Dictop note; if you disable history, successful keyboard dictation can still be inserted without creating that history entry.

    Dictop uses an App Group only for the bounded keyboard protocol and minimal lifecycle state needed to coordinate the containing app, keyboard, and Live Activity. Control records contain identifiers, state, timestamps, and display-only meter levels. They do not contain raw audio, typed document context, transcript text, prompts, credentials, or provider responses. Transcript-bearing results, processing journals, delivery markers, and temporary audio use stronger device file protection.

    The keyboard cannot open Dictop by itself. When account, credit, model, permission, or recovery attention is needed, it asks you to open Dictop manually.

    3. Full Access and microphone permission

    Full Access is an iOS keyboard setting. It lets the keyboard write to Dictop’s shared App Group and use the coordination required for cross-app insertion. It does not grant microphone permission. Microphone permission is requested and used by the Dictop app separately. You can turn either setting off in iOS Settings.

    4. Live Activity and Firebase telemetry

    During an active keyboard session, Dictop shows a Live Activity and iOS shows the microphone privacy indicator. The Live Activity contains session status and a Stop action, not transcript, prompt, audio, or waveform content.

    The main Dictop app uses Google Firebase services to understand product use, operate essential configuration, and diagnose reliability and performance. The keyboard, widgets, and share extension do not use Firebase. This telemetry is separate from the dictation and cloud-processing content described above: Dictop does not intentionally include dictation audio, transcript text, prompts, credentials, provider responses, or document context in Firebase telemetry. Privacy-safe local OSLog events likewise use closed operational stages and categories, not that content.

    The enabled services are Google Analytics for Firebase, Crashlytics, Remote Config, and Firebase Installations on iOS and macOS. Firebase Performance Monitoring is enabled on iOS only; its macOS client is inactive. Firebase Sessions and Google Data Transport are operational components pulled in by these services. Firebase describes Sessions as always collecting limited app-quality and session metadata, including app/bundle, operating-system, SDK-version, network-connection, and background-time information; it describes Google Data Transport as always collecting limited SDK transport metadata, such as log-cache size and dropped-event counts. Firebase A/B Testing is a transitive component of Remote Config. The current app code recognizes only the typed onboarding_flow_variant=control and allowlisted cloud_credit_default_sku values and contains no experiment behavior. The current release Remote Config template has exactly those two parameters, with no conditions, personalization, or experiments.

    What this telemetry includes and why

    5. Telemetry choices

    In shipping builds, Usage Analytics and Crash Diagnostics are initially enabled. They are separate switches in the app’s Settings; turning one off does not turn the other off.

    6. Retention and deletion boundaries

    Dictop removes bounded keyboard artifacts when their protocol or retry lifetime ends and during launch/foreground cleanup. It does not delete a newer job while resolving an older one, and it defers Complete-protected cleanup until the device is unlocked.

    For Firebase data, published retention information is as follows:

    These periods do not override legal retention obligations, data already aggregated, or data retained under a separate service or backup process. The app cannot guarantee deletion after an operating- system uninstall, backup restore, or a stale App Group container that iOS preserves across an install boundary. On the next launch it validates and removes stale protocol artifacts it can access. To remove local Dictop history, use the app’s history controls. For cloud-provider data, contact Dictop or use the applicable provider’s privacy process, as appropriate to the service relationship.

    7. Account and purchases

    Sign in with Apple and in-app purchases are handled through Apple and the services needed to provide the selected cloud credits. Dictop stores authentication material in the device Keychain. Payment card details are handled by Apple, not by Dictop.

    When you delete your Dictop account, we remove or anonymize your account data. We keep accounting, purchase, and invoice records in anonymized form for checks and balances and any applicable legal retention requirements. If you sign in again, you can recover your purchases. Account deletion does not change the separate Firebase, cloud-provider, local-device, backup, and legal-retention boundaries described in this policy.

    8. Service providers and international transfers

    Google/Firebase provides the Firebase services described above for Dictop. Google Analytics for Firebase is governed by separate Google Analytics Terms and Google data practices for partner sites and apps. The other Firebase services are governed by the applicable Firebase terms, including Firebase’s privacy and security information and, where applicable, Data Processing and Security Terms. Google’s role, including whether it acts as a processor or service provider, and the transfer safeguards that apply depend on the service, data, and applicable agreement.

    Firebase may process data in countries where Google or its subprocessors operate, including outside the EEA, United Kingdom, or Switzerland. The applicable Firebase and Google terms describe data-transfer solutions, including Standard Contractual Clauses where applicable; the current subprocessor list identifies Firebase subprocessors and their locations and activities. These arrangements do not replace any rights or protections that apply to you under applicable law.

    9. App Store privacy details

    Apple shows a privacy label for App Store versions of Dictop. The label applies to a particular released version and should be read together with this policy. It should distinguish on-device processing from off-device collection or processing, including cloud-provider and Firebase collection.

    10. Your requests, changes, and contact

    Depending on applicable law, you may ask to access, correct, delete, restrict, object to, or receive a portable copy of personal data that Dictop controls. To make a privacy request or ask a question, email info@actondon.com or use actondon.com/contact. Please identify the Dictop account or device context needed to locate the request, but do not send credentials, dictation audio, transcripts, or other sensitive content by email unless we specifically and securely ask for it.

    We may need to verify your identity and request enough information to locate relevant records. We will assess and respond to requests as applicable under law and our role for the data; some records may remain in aggregated form, in backups while their retention cycle completes, or where retention is required by law. Requests concerning a cloud provider may also need to be directed through that provider or handled with Dictop where Dictop is the contracting party.

    We may update this policy as Dictop changes. Firebase or Analytics settings may change only after the policy and the applicable App Store privacy label have been reviewed as appropriate for that release. The current version is published on this page.

    Privacy Policy for dictop.com

    Last updated: 2024-03-28

    Welcome to dictop.com (the “Website”), operated by Actondon UG (haftungsbeschränkt) (“us”, “we”, or “our”). Your privacy is important to us, and this Privacy Policy explains how we collect, use, and protect information related to your interaction with our Website. This policy applies only to information collected through the Website and not to information collected offline or via other channels.

    1. Information Collection and Use

    We do not collect any personal information from visitors to our Website. As such, there is no personal information to use or disclose.

    2. Cookies and Tracking Technologies

    Our Website does not use cookies or any form of tracking technologies. Hence, visitors’ information or behaviors on the site are not monitored or tracked.

    3. Information Sharing and Disclosure

    Since we do not collect personal information, there is no sharing or disclosure of personal data to third parties.

    4. Data Security

    Even though we do not collect personal information, we strive to use commercially acceptable means to protect our Website and maintain the integrity of our online presence.

    5. Children’s Privacy

    Our Website is not directed at children under the age of 13, and we do not knowingly collect information from children under this age. The app and Website are designed for a general audience and do not require an age limit for usage.

    6. Changes to This Privacy Policy

    We reserve the right to update or change our Privacy Policy at any time. You are advised to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are effective when they are posted on this page. Since we do not collect personal information, we will not notify users of changes. Users are encouraged to check this page regularly for any updates to the privacy policy.

    7. Contact Us

    If you have any questions or suggestions about our Privacy Policy, do not hesitate to contact us. You can find our contact information on our Website and inside the app.