Submerso privacy policy
Last updated: 17 November 2026
This policy explains how Submerso handles information when you train, make a purchase or contact support. Submerso is a dry breath-hold and breathing training app for people aged 16 and over.
Who is responsible
Ben Gilroy, trading as Craft App Co., is responsible for the personal information described here. Email hello@craftapp.co with privacy questions or requests. Visits to craftapp.co are covered separately by the website privacy notice.
Training records and preferences
Submerso stores breath-hold results, dates, session types, performed timings and training history to run training and show your progress. It also stores settings such as spoken guidance, haptics, reminders and your safety acknowledgement. Reminders use device notifications with your permission.
App history is stored on your device and, when available, synced through a private Apple iCloud database associated with your Apple Account. Local storage remains available when iCloud cannot be used. This is distinct from analytics: training records are not sent as custom analytics event properties. Submerso has no separate user registration or custom account backend. Apple’s own terms and privacy information govern your Apple Account and iCloud service.
Apple Health and Apple Watch
On iPhone and iPad you can choose to save eligible training sessions as Apple Health workouts. Submerso uses recorded session dates and timings for those workouts and can query its app-authored workouts to reconcile exports and avoid duplicates. It does not import your general Health history to build training tables.
When Submerso has permission to save workouts, the iPhone app also runs a temporary workout session during guided training so the session keeps running while your iPhone is locked. That temporary workout is always discarded and is not saved to Health. Before your first guided session, the app explains this and lets you allow workout access or continue without it.
Guided Apple Watch sessions require workout-writing permission. Reading heart rate during a workout and saving the finished workout are optional. Hold tests do not require Health access. Heart-rate samples are not stored in Submerso’s training-history database. The Watch workout uses Apple’s HealthKit services. Apple Health records and app history are separate.
You control Health permissions through Apple’s settings. Turning saving off does not delete existing Health workouts. Deleting Submerso history leaves Health workouts intact, and you can manage those separately in Health. Custom analytics events do not contain heart rate, Health records or Health permissions.
Purchases
Apple processes App Store payments. RevenueCat helps Submerso check purchases, restore access and manage paid access. This involves purchase and subscription information, product identifiers and a pseudonymous app user identifier. Submerso does not ask you to enter payment-card information directly.
RevenueCat’s app user identifier is also used as the Mixpanel identifier, and a Firebase app-instance identifier is supplied to RevenueCat. These links allow subscription and app-usage information to be associated. RevenueCat also sends subscription events, such as trials, renewals, cancellations and revenue, to Mixpanel under the same identifier. Pseudonymous information can still be personal information. It is not anonymous.
Usage analytics and crash reporting
The iPhone and iPad app uses Firebase Analytics and Mixpanel to understand use of screens, training features and purchase flows. Crashlytics receives automatic crash reports and limited, sanitised reports of selected app failures to help diagnose reliability problems. These SDKs are not configured in the Apple Watch app or Live Activity extension.
Analytics and crash reporting are enabled by default on iPhone and iPad. Health permissions do not control this collection. To object to this use or ask us to delete analytics data linked to your app identifier, email hello@craftapp.co.
Custom usage events include screen visits, training type, session outcomes, the planned and completed length of guided sessions, chart-range choices and purchase-flow actions. For CO2 and O2 tables, session length depends on your breath-hold baseline. Your analytics profile also records whether you have Pro, whether the Submerso Apple Watch app is installed and how many Apple Watch sessions have synced to your iPhone. Events record the app language and whether the app is a test build. They exclude individual breath-hold durations, personal bests, heart rate, Health records or permissions, generated intervals, notes, reminder schedules, CloudKit identifiers and record identifiers. Event timestamps can still reveal when interactions happened and allow approximate elapsed-time inference.
SDKs also process identifiers, device and app metadata, automatic events and diagnostic context beyond those custom events. Crash reports can contain stacks and analytics breadcrumbs. Submerso’s own nonfatal reports use fixed messages, source locations and sanitised categories and codes rather than raw records or arbitrary error descriptions.
Mixpanel's automatic mobile events are enabled: first open, app updates, app sessions and their length, and in-app purchases.
To measure Apple Search Ads campaigns, RevenueCat receives Apple's AdServices attribution token, which Apple uses to say whether an install came from one of our Apple Search Ads campaigns. Submerso does not ask for permission to track you and does not collect the advertising identifier (IDFA).
Submerso does not configure advertising-identifier collection or advertising personalisation in Firebase. Mixpanel autocapture and session replay are not enabled, and IP-derived geolocation is disabled. Those configuration choices do not mean the providers receive no identifiers or technical information.
Contacting support
If you email us, we receive your email address, any name you provide, your message and attachments. Google Workspace handles this correspondence. We use it to respond and investigate your request. Emails composed inside Submerso may include device and app details, subscription status and your RevenueCat app user identifier. You can edit the message before sending. Please avoid unnecessary health or other sensitive information.
Why we use information
We use information for these purposes, on these legal bases:
- Providing the app and your history, including iCloud sync, optional Apple Health workouts and reminders: to perform our contract with you.
- Paid access and purchases, through Apple and RevenueCat: to perform our contract with you.
- Answering support requests: to perform our contract with you, or our legitimate interest in helping people who contact us.
- Usage analytics and crash reporting: our legitimate interest in understanding how Submerso is used, fixing faults and improving the app. You can object to this at any time by emailing hello@craftapp.co.
Installing the app, acknowledging training safety information or accepting the terms does not by itself provide consent to analytics.
Providers and international processing
The services involved are Apple (iCloud, Health and App Store), RevenueCat, Google (Firebase Analytics, Crashlytics and Workspace) and Mixpanel. The configured Mixpanel project uses US data residency. Other providers have their own international processing arrangements. These services can process information outside the UK. Their privacy and data processing information describes the arrangements and safeguards that apply to their services.
Provider information: Apple privacy, RevenueCat privacy, Firebase privacy, Mixpanel privacy and Google Workspace data processing terms.
Retention and deletion
App history remains stored when a subscription ends. You can delete app history using the available history controls. iCloud synchronises those deletions when available. Apple Health workouts are managed separately. Uninstalling does not by itself cancel subscriptions or establish that iCloud, Health or provider records have been erased.
Deleting training history does not delete remote analytics or subscription records. These are kept as follows:
- Google Analytics (Firebase) keeps detailed event data for 2 months, and user-level data for 14 months after you last use the app. Aggregated reports are not affected by these limits.
- Mixpanel deletes event data after 2 years.
- Crashlytics keeps crash reports and their identifiers for 90 days.
- RevenueCat keeps purchase and subscription records while we use its service, under its retention policy, so that paid access can be checked and restored.
We keep support correspondence for as long as needed to answer your request, handle related follow-up and meet applicable legal obligations. Email hello@craftapp.co to request deletion of analytics or other personal information linked to your app identifier.
Your rights and younger users
Depending on your circumstances, you may have rights to access, correct or erase personal information, restrict or object to processing, and receive certain information in a portable form. Email hello@craftapp.co to make a request. You may complain to the UK Information Commissioner’s Office or your local data protection authority.
Submerso is intended for users aged 16 and over, including 16–17-year-olds. Their privacy rights apply too. The app does not verify age or collect parental consent. Younger users and their parents or guardians can contact us with questions about personal information and privacy rights.
Changes
We update this policy when the way Submerso handles personal information changes. We communicate material changes as appropriate to their effect.