Last updated: October 12, 2026
HeadPause is built to be one of the most privacy-preserving apps on the App Store. There is no GMX3C server behind the app, no user account, no advertising identifier, and no microphone access. Head motion from your AirPods is read on your iPhone and used to guide and score your practice. Your practice history is stored on your device, and there is an optional HealthKit Mindful Minutes write that you can turn on or off in Settings.
The only network activity is Apple's purchase verification for the one-time Pro unlock, handled by the App Store. This does not transmit your practice data to us.
With your permission, HeadPause reads head-motion samples from motion-capable AirPods through Apple's CMHeadphoneMotionManager API. This is the single system permission the app requests for sensing, shown to you as "HeadPause reads AirPods head motion to measure stillness and posture during guided head exercises."
The app uses these signals many times per second:
They are used on your iPhone to guide the session and to compute form score, steadiness, angle accuracy, calm score, and horizon-hold percent. Nothing is sent off your device.
Practice history and settings. Session summaries (such as duration, scores, completion, personal bests, streaks, and which free guided runs you have used) and your preferences are stored on your iPhone inside the app's storage. They are not uploaded anywhere by HeadPause.
Session log files. The app you install from the App Store or TestFlight does not write a raw per-session log at all. Only a developer build run from Xcode can write one, for troubleshooting: events with timestamps and, for Balance routines, the head-motion samples listed above, kept in the app's own local storage and cleared each time it launches. HeadPause does not use iCloud for this or for anything else, so no HeadPause folder can appear in the Files app, and GMX3C never receives it.
There is no iCloud sync setting in HeadPause, and your practice history is not synced between devices by the app.
HeadPause plays voice cues and ambient soundscapes through your headphones or speaker during sessions, but it never records audio. The app does not request microphone permission. If iOS ever prompts you for microphone access from HeadPause, that is a bug and you can contact us immediately.
HeadPause supports a single, optional HealthKit interaction: Mindful Minutes. The toggle lives in Settings, Health & privacy and is off by default. When you turn it on, iOS shows the standard HealthKit sharing prompt. If you grant Mindful Minutes write access, each completed Still session writes its duration to Apple Health when the session ends. HeadPause never reads anything from HealthKit, never writes any other type, and writes nothing while the toggle is off.
Head motion from AirPods is the only physiological signal HeadPause processes, and it is never written to HealthKit.
Session reminders, streak alerts, and the weekly summary are optional, controlled by separate toggles in Settings, and scheduled locally by iOS on your device. HeadPause does not use a push notification server.
The Pro unlock is a one-time purchase handled entirely by Apple through the App Store. HeadPause checks your entitlement with StoreKit. GMX3C does not receive your payment details or Apple ID. If you use Family Sharing, Apple handles who in your family group has access.
HeadPause uses Apple's MetricKit, not a third-party SDK. If you have chosen to share analytics with app developers in iOS Settings, iOS may hand HeadPause crash and performance reports. HeadPause stores them in a file on your device. It does not upload them.
Deleting HeadPause from your iPhone removes its on-device history, settings, and any local developer log files. To remove HealthKit data HeadPause wrote, use the Health app.
HeadPause is intended for adults. It is not directed at children under 13 and does not knowingly collect information from them.
If this policy changes, the updated version will appear on this page with a revised "Last updated" date. Material changes that expand data collection will require a clear in-app notice before they take effect.
Questions, concerns, or data requests? Reach the GMX3C team directly.
Contact GMX3Ccontact@gmx3c.com
