Privacy Policy for dun

Last updated: October 1, 2026

This Privacy Policy explains how Manuel Fessen ("we", "us", or "our") processes information when you use the dun iPhone app, its keyboard extension, and its Live Activity.

dun processes dictation audio on your device. The app also uses external services for product analytics, diagnostics, subscriptions, advertising attribution, and feedback. These services receive the information described below. You do not need to create a dun account, but the services use persistent, pseudonymous identifiers. This information is not necessarily anonymous merely because it does not include your name or email address.

1. On-Device Speech Processing

• Dictation audio is transcribed on your iPhone using downloaded speech models.
• Optional writing-style polish uses Apple's on-device Foundation Models when supported and available.
• Translation uses Apple's Translation framework and may require downloading language models.
• We do not upload your voice for cloud transcription or use your speech to train models.
• We do not sell your voice or transcripts.
• Personal dictionary entries are used locally to improve recognition and text correction.

The analytics and subscription services described below receive usage and transaction information; they do not perform speech recognition for dun.

2. Microphone and Background Readiness

dun requires microphone permission to record a dictation. During a dictation, audio samples are collected for local transcription. Pausing stops the collection of samples until you resume.

The microphone can remain active between dictations so that you can start the next dictation from the keyboard without reopening the main app. Once setup is complete and dictation is available, opening dun can also start this readiness session. While the engine is idle or dictation is paused, incoming audio buffers are discarded rather than saved for transcription.

Stopping or cancelling a dictation ends the collection of dictation audio; it does not necessarily end the readiness session. The orange iOS microphone indicator can therefore remain visible even when no dictation is being saved.

You can choose when the idle session ends in dun's settings. The default automatic setting leaves its lifetime to iOS without a fixed dun timer. Timed settings end it after the chosen idle period; the immediate setting releases it after the current dictation and processing cycle finishes. You can also end the readiness session using the Live Activity's power control. iOS can interrupt or terminate the session independently.

3. Full Access for the Keyboard

iOS requires Allow Full Access so the keyboard can use dun's shared App Group container to coordinate with the main app and receive dictation results. The shared container includes settings, dictation status, text handoffs, and diagnostic events.

Full Access does not cause dun to upload your voice for transcription or capture other apps' screens for writing-style personalization.

4. Data Stored on Your Device

dun stores settings, downloaded models, personal dictionary entries, dictation results, subscription status, and diagnostic information on your device. Some of this information is shared between the app and its extensions through the App Group container.

Completed transcripts are saved locally by default, with a maximum of 500 entries. In the transcript history settings, you can keep transcripts without a time limit, keep them for 1, 7, or 30 days, or turn off regular history. Expired entries are removed when dun next runs or accesses the history; deletion is not guaranteed to happen while the app is inactive.

Interruption recovery is an exception: text recovered from an interrupted recording is saved and marked even when regular history is turned off, so you can retrieve a result that was not inserted into another app. You can delete these entries from the history as well.

You can delete saved transcripts inside dun. Removing the app removes its local app data. Deleting history or removing dun does not remove text already inserted into other apps, Apple's purchase records, or information previously transmitted to the services below. Device backups are managed through your iOS and Apple account settings.

5. Product Analytics, Diagnostics, and Session Replays

We use PostHog to understand how dun is used, find failures, and improve setup and app navigation. The integration is configured to send information to PostHog's EU endpoint.

When the main app runs, it can send:

• A persistent installation identifier and session identifiers.
• App launches, screen visits, taps, repeated taps, onboarding progress, and feature usage.
• Dictation duration, word counts, selected models, languages, writing styles, and failure categories.
• Device model, memory information, iOS and app versions, language and region settings, time zone, App Store storefront country, and technical network state.
• Diagnostic log entries from the main app and extensions, including timestamps, state changes, model preparation information, errors, and performance measurements.

Further information: PostHog Privacy Policy.

6. Purchases, Subscriptions, and Advertising Attribution

Apple processes App Store payments. We use RevenueCat to verify purchases, restore them, and determine whether paid features are available. RevenueCat processes a pseudonymous customer identifier, purchase and receipt or transaction information, subscription and entitlement status, and technical app and device information. We do not receive your full payment card details from Apple.

RevenueCat's Apple AdServices integration is enabled. It sends an attribution token to RevenueCat so that available Apple Ads campaign information can be associated with an installation and its purchases. This helps us measure whether advertising leads to subscriptions.

We also use Adapty in observer mode for subscription and revenue analytics. It receives verified StoreKit transaction reports, the RevenueCat customer identifier, and technical information collected by its SDK. RevenueCat remains responsible for granting access to paid features; Adapty's integration measures purchases and subscription activity.

The PostHog installation identifier is shared with RevenueCat and Adapty to associate subscription events with app usage. These identifiers link records between the services even though dun does not require a sign-in account.

Further information: RevenueCat Privacy Policy, RevenueCat Apple Ads integration, and Adapty End-Users Privacy Policy.

7. Feedback and Support

If you use dun's feedback board, FeedbackThread receives your submitted feedback, feature requests, and votes, together with the app version and a pseudonymous identifier based on your RevenueCat customer identifier. Where subscription status is available, dun also passes a free, trial, or paying customer tier to help prioritize feedback. Submissions may appear on the feedback board after moderation.

Please avoid including confidential dictations or unnecessary personal information in feedback. If you contact us by email, we receive your email address and whatever information you include in your message so that we can handle your request.

Further information: FeedbackThread Privacy Policy.

8. Network Connections and External Providers

In addition to the services described above, dun can use the network to download speech and dictionary models, download Apple's translation resources, retrieve paywalls and subscription status, and load remote feature settings. Model downloads can use Apple's hosting infrastructure or model repositories such as Hugging Face, depending on the model. Opening support, policy, or App Store links also connects to the relevant website or service.

Providers handling these connections receive the IP address and technical request information needed to deliver the service. Network activity for analytics and subscriptions is separate from local speech recognition: local transcription does not imply that the entire app makes no network connections.

Our providers may process information outside the European Economic Area, including through their infrastructure and subprocessors. PostHog's EU endpoint does not mean that every service used by dun operates exclusively in the EU. The linked provider policies describe their processing arrangements. If you need details about transfers relating to your records, contact us using the details in section 13.

9. Purposes and Legal Bases

We process the information described in this policy to:

• Provide local dictation, text correction, translation, and the keyboard handoff. Legal basis: performance of the contract to provide the app functions you request.
• Manage and restore purchases and access to paid features. Legal basis: performance of the contract and compliance with legal obligations for purchase verification and accounting.
• Diagnose technical failures and improve app usability and reliability. Legal basis: our legitimate interests in maintaining a secure and functional app. You may object as described in section 11.
• Measure product usage, subscription performance, and Apple Ads campaign results, including Adapty subscription analytics and RevenueCat attribution. Legal basis: our legitimate interests in understanding effectiveness of the app and advertising. Attribution uses only campaign information Apple makes available. You may object as described in section 11.
• Handle feedback, support requests, and data protection requests. Legal basis: taking steps at your request and our legitimate interests in handling correspondence; for email contact, your consent implied by contacting us.

These integrations start when the main app launches. The current app version does not include a separate in-app analytics or replay opt-out switch and does not gate these integrations behind a separate consent screen. Objecting does not affect the lawfulness of processing before the objection.

10. Retention and Deletion

Local transcript retention follows section 4. Downloaded models and settings remain until you remove them or delete the app. Local diagnostic files are size-limited; diagnostic entries awaiting upload can remain locally until delivery or log rotation.

Information sent to PostHog, RevenueCat, Adapty, and FeedbackThread is stored separately from the app. Retention depends on the configured service periods and the purpose of the record, including purchase verification, diagnostics, and handling feedback. Removing the app does not automatically send a deletion request to these providers. Contact us for the retention periods currently applicable to your records.

Contact us if you want information about records associated with your installation or want to request their deletion. Applicable legal obligations may require some records to be retained. Erasing dun's records does not erase records Apple holds under its own policies.

11. Your Data Protection Rights

Where the GDPR or similar laws apply, you may have rights to access your personal data, correct it, request its erasure, restrict processing, obtain data portability, and object to processing based on legitimate interests. If processing is based on consent, you may withdraw that consent for the future. These rights are subject to the conditions and exceptions in the applicable law.

You can exercise your rights by contacting us at the email address in section 13. We may need limited information to verify your request and locate the relevant records, because dun does not require a named user account. You do not need to send us voice recordings or the contents of your dictations to make a request.

You also have the right to lodge a complaint with a data protection supervisory authority, including the authority where you live or work.

12. Changes to This Policy

We will update this policy when dun's data handling changes. The date at the top identifies the latest revision.

13. Controller and Contact

The controller responsible for dun's processing of personal data is:

Manuel Fessen
c/o Secato GmbH
Ungelsheimer Weg 7
40472 Düsseldorf
Germany

Email: support@meetdun.com