Privacy Policy
Dawdle is built to be private. There are no accounts, analytics, ads, tracking, or developer-operated servers. Dawdle stores your practice data locally. The only way the app prepares information for the developer is when you choose Contact support; nothing is sent unless you affirmatively send the visible email.
The short version
- Dawdle does not automatically collect or transmit your personal data, practice data, or diagnostics.
- Dawdle stores sessions, breath-hold scores, custom breathing patterns, goals, and preferences locally on your device. Depending on your Apple backup settings, ordinary device backups may include this app data.
- If you contact support, Dawdle opens a visible email composer. You can review, edit, remove the diagnostic attachment, or cancel. The developer receives the email and attachment only if you choose Send.
- If you enable it, Dawdle can write mindful minutes to Apple Health. It never reads your health data.
- Purchases are handled entirely by Apple. We never see your payment details.
Data stored on your device
Dawdle keeps local data so the app can work: completed sessions and sessions ended early; breath-hold test scores; optional mood and note entries; custom breathing-pattern names, timing, and settings; selected practice goals; reminder settings; onboarding status; and app preferences such as theme, sounds, haptics, app icon, and subscription state. The active app data is stored locally using Apple's standard on-device storage and protected by your device's security. Dawdle does not sync this data to any server operated by us, and we have no ability to access it. Depending on your Apple device-backup settings, Apple may include app data in a device backup and restore it when you restore or replace a device. Those backups are provided and controlled by Apple under your Apple account and backup settings, not by Dawdle or its developer.
After you authorize Apple Health, a failed Mindful Minutes write may be kept in a protected local retry queue. A queued item contains the session start and end times, duration, and a random local session identifier used to prevent duplicate HealthKit entries. The queue is excluded from device backups, is limited to 256 items and 128 KiB, does not leave your device except when Dawdle asks HealthKit to complete the write, and is removed sooner when the write succeeds or Dawdle detects that write access has been revoked. Dawdle removes queued items older than 30 days the next time the app processes the queue; iOS cannot run that cleanup while Dawdle is never launched.
Dawdle also keeps a small, short-lived operational diagnostic log on your device for reliability events such as a local save, reminder, audio, Apple Health write, or StoreKit operation. It contains only fixed event codes, severity, timestamps, and bounded nonnegative counts — never notes, mood, breath-hold scores, session measurements, reminder times, personal, stable device, session, or transaction identifiers, URLs, free-form error messages, payment details, or HealthKit samples. The local ring is capped at 900 KiB, protected on disk, and excluded from device backups. Dawdle removes diagnostic events older than seven days the next time the app records or prepares diagnostics; iOS cannot run that cleanup while Dawdle is never launched.
Contacting support
When you choose Contact support, Dawdle creates a new random 80-bit request identifier and prepares a redacted JSON diagnostics attachment in memory. The attachment is capped at 950 KiB and contains only the request identifier, a schema version, its generation time, the app version and build, iOS version, hardware model identifier and coarse device category, locale identifier, time-zone identifier, and up to seven days of diagnostic event timestamps, typed event codes, severity, and allowlisted bounded counts. It does not contain your practice, health, purchase, identity, user-entered, or free-form error data.
If Apple Mail is configured, Dawdle places the support address, a short subject containing the app version/build and request identifier, a “What happened?” prompt, and the JSON attachment into Apple's in-app Mail composer. Device and diagnostic context remains in the attachment rather than being repeated in the message. You can review and edit the email, inspect or remove its attachment, or cancel. Dawdle does not send the email or attachment automatically; the developer receives them only if you choose Send. The email service you use processes the message under its own privacy terms.
If the in-app Mail composer is unavailable, or a report cannot be prepared, Dawdle offers an external email link containing only the support address and a prepared subject. That fallback does not add a message body or attach diagnostics. You remain in control of whether to send it.
Support data received by the developer
Dawdle contains no analytics or crash-reporting SDKs, advertising frameworks, or third-party trackers. The app makes no automatic network request to a server operated by the developer. If you choose Send in a support composer, the developer receives the sender name and email address supplied by your mail account, the prepared subject and request identifier, your message and signature, and any diagnostic attachment you leave in the email. This information comes directly from you and from the redacted report that Dawdle prepares on your device.
We use support correspondence only to respond to your request, investigate the problem you reported, maintain the security and reliability of Dawdle, and comply with legal obligations. We do not sell or share it for cross-context behavioural advertising, use it for advertising or marketing, or combine it with advertising profiles. Access is limited to the developer and people or service providers authorized to help operate email and support. Your email provider and ours process the message under their own terms and may process it in countries other than your own.
Where the GDPR applies, the legal basis is taking steps at your request or performing our agreement with you, our legitimate interest in providing support and keeping Dawdle reliable and secure, and compliance with legal obligations where required. Please do not add practice, health, payment, or other sensitive information to your support message.
Where Saudi law applies, we process support correspondence as necessary to respond to your request and provide support, to comply with applicable legal obligations, and, where permitted, to maintain the security and reliability of the app.
Apple Health (HealthKit)
You can optionally connect Dawdle to Apple Health. If you grant permission, Dawdle writes the time from your breathing sessions — including sessions you end early — to Apple Health as Mindful Minutes. This integration is write-only:
- Dawdle never reads any data from Apple Health.
- The developer does not receive HealthKit data or disclose it to third parties, and Dawdle never uses it for advertising, marketing, or data mining. Apple Health is a user-controlled repository; other apps may access entries there only if you separately authorize them.
- You can revoke access at any time in the Health app or in Settings, and you can delete any entries Dawdle has written from within the Health app.
Purchases
Dawdle Pro subscriptions are processed by Apple through the App Store. Your payment information is handled entirely by Apple under Apple's Privacy Policy; we never receive your payment details. To determine whether Pro features are available, Dawdle uses Apple's StoreKit framework to process subscription status and the transaction metadata needed to verify entitlement on your device. We do not operate a purchase backend or maintain our own record of your identity or purchase history.
Notifications
If you enable practice reminders, they are scheduled locally on your device. Dawdle sends no reminder data to us or to a developer-operated notification service, and no push-notification service is used.
Data retention and deletion
You control the data stored by the installed app. Deleting Dawdle deletes its active local app data from that device. A copy may remain in an Apple device backup according to your Apple backup settings and Apple's retention practices; Dawdle and its developer cannot access or delete those backups for you. Mindful Minutes entries previously written to Apple Health remain in the Health app (as is standard for Health data) and can be deleted there at any time.
We retain support emails and attachments until the request and any resulting investigation are resolved, and longer only where required by law or necessary to establish or defend legal claims. When retention ends, we delete them from our active support mailbox. Residual provider backups expire according to the email provider's backup-retention process. You may request earlier deletion by replying to the same thread.
Your rights
Dawdle's developer holds no server-side copy of your practice data. Your installed app holds its local data, and Apple may hold device-backup, HealthKit, and App Store information under your Apple account and settings. Depending on where you live and which law applies, you may have rights to request access to, correction of, deletion of, restriction of, or a portable copy of personal data we hold, and to object to certain processing. You may also have the right to complain to your local data-protection authority. These rights can be subject to legal exceptions.
California residents may also have rights to know the categories and specific pieces of personal information collected, correct or delete it, and receive equal service when exercising privacy rights. During the preceding twelve months, the only categories the developer may have collected are identifiers and contact information (your sender name, email address, and support request identifier), customer-support and email content, and diagnostic or device-context information that you chose to send. The source is you and the report prepared on your device; the purposes and recipient categories are described above. We do not sell personal information or share it for cross-context behavioural advertising.
To exercise an applicable right, email support@continuum.sa with “Privacy request” in the subject. Describe the request and, if it concerns a support report, include its request identifier if available. We may verify the request by replying to the email address associated with the correspondence. You may use an authorized agent where applicable law permits. If we deny a request, we will explain why and describe any available appeal or complaint route.
Beta testing through TestFlight
If you install a beta version through Apple's TestFlight service, Apple automatically provides Continuum with beta usage information and crash reports under the TestFlight Terms. Continuum uses this information only to test, diagnose, and improve the app. TestFlight feedback may also include information and screenshots you choose to submit.
Children's privacy
Dawdle is not directed at children. A person who is under the age of majority where they live should use Dawdle only with the permission and supervision of a parent or legal guardian. Children should not send personal or sensitive information through Contact support. If you are a parent or guardian and believe a child sent us information, please contact us using the privacy-request process above.
Changes to this policy
If we ever change how Dawdle handles data — for example, if a future feature introduces optional syncing — we will update this policy, change the effective date and version above, and clearly surface any material change in the app. The current version is always available at dawdle.continuum.sa/privacy.
Contact
Dawdle is made by Continuum Company ("Continuum"), a company based in Saudi Arabia. Continuum is responsible for support correspondence it receives. For privacy questions or requests, contact support@continuum.sa.