Privacy Policy

Last updated: October 2026

The short version: ampulse needs no account and keeps your physiology on your phone. There are no analytics, ads or third-party tracking SDKs, and no server of ours holds your data. Sensors connect to the phone directly over Bluetooth.

Controller

Perihela LLC, 30 N Gould St, Ste N, Sheridan, WY 82801, United States
support@ampulse.fit

Local recording and optional connections

• Nights and days. Sleep results, beat-to-beat intervals, heart rate, breathing, skin temperature, steps and calories are read from your Polar band over Bluetooth and stored as files on your iPhone — the raw data and ampulse's reading of it, side by side. Deleting the app deletes them — see Delete your data.
• Training sessions. Recordings from chest straps, running pods and gym machines are computed and stored on the device only.
• Heart rate to gym equipment. Off by default. If you turn on “Send heart rate to gym equipment”, your iPhone advertises your current pulse as a standard Bluetooth heart-rate sensor, so a treadmill or bike you pair can show it. While the setting is on, a device in Bluetooth range that connects receives that pulse value and nothing else. Turn the setting off to stop it.
• Location. For outdoor runs, GPS traces are recorded on the device to measure pace and distance, and stay in the session files on your phone. One exception, named plainly: at the start of an outdoor run ampulse sends a single position — the first good GPS fix — to Apple's WeatherKit to read air temperature and humidity, which the heat-adjusted pace needs. One request per run, no Ampulse identifier attached, nothing stored on our side. Legal basis: performance of the contract (Art. 6(1)(b) GDPR). Denying location access, or training indoors, means no position is ever sent.
• Exports you start. Apple Health and Strava are off until you turn them on. Enabling Health writes your nights (sleep, resting heart rate, heart rate variability as SDNN and, from iOS 27, RMSSD, breathing rate and the beat-to-beat series) and your sessions as workouts with heart rate, power and distance to your Health store under Apple's rules. If you connect Strava, an ampulse.fit function exchanges the temporary authorization code and later refresh tokens with Strava; it does not store them. Access and refresh tokens are kept in your iPhone Keychain, and session files upload directly from your iPhone to Strava only when you share them or enable automatic publishing. Strava processes those copies under Strava's privacy policy. FIT and CSV exports go wherever you share them.
• Apple Health import. With your permission, ampulse reads these types from Apple Health: sleep analysis, resting heart rate, respiratory rate, heart rate variability (SDNN, and RMSSD from iOS 27) and sleeping wrist temperature. Imported records are stored on your iPhone, excluded from iCloud backup, and never included in the automatic folder mirror — they leave the device only in an export you start by hand. Turning off import removes the imported nights; it does not delete the source records in Apple Health.
• Connected folder and AI. If you link an export folder, ampulse keeps a copy of your record there automatically. A folder in iCloud Drive or another sync service is handled by that provider. The optional MCP connector reads the folder on your computer and returns requested records to your assistant. A cloud assistant receives those tool results under its own privacy policy. This path does not pass through an ampulse health-data server.
• Firmware. Checking for and downloading Polar firmware requires access to Polar’s firmware service. Local recording and storage do not require uploading your recordings to that service.
• Voice and audio. Coaching cues are bundled audio, played on the device.

Retention and deletion

Everything lives as files in the app's storage for as long as you keep it. Deleting a night removes its recording and its summary; deleting a session removes its file, and for a session imported from the band also its verbatim archive. Deleting the app removes its local recording files. Copies outside the app need to be managed separately.

One small record deliberately survives a session deletion, and it is worth naming: for a session imported from the band, ampulse keeps the band's own internal path for that recording — a string such as /U/0/20260826/E/… — in a local list of what has been imported. It carries no measurement and no personal data; its only job is to stop the next sync from importing the recording you just deleted all over again, because the original stays on the band until you sync or reset it. That list is a plain file on your device and goes when the app goes.

Copies in connected folders, cloud storage, Apple Health, Strava or assistant conversations are managed separately under those services’ policies. Deleting ampulse or removing its connector does not erase those copies. Review the linked folder and any services you shared with when deleting your record.

Purchases

Subscriptions are processed by Apple through your Apple ID. We receive no payment details and no identity data — only Apple's anonymous confirmation that an entitlement exists. Apple's processing is governed by Apple's privacy policy.

Support email

If you write to us, we process your email address and the content of your message to answer you (Art. 6(1)(b) and (f) GDPR). If you choose to attach diagnostics from the app, we also receive the app and iOS version, iPhone model, language, time zone, phone battery and thermal state, whether Bluetooth, notifications, Apple Health, Strava and the AI folder are on, Polar Loop pairing, firmware and battery, the app log from the current launch, the Polar Loop sync log and any crash and hang reports. No heart-rate, HRV, sleep, session, location or account data is included. Support mails are deleted once the matter is resolved, unless statutory retention duties apply.

This website

ampulse's website and the narrow Strava authorization function are hosted by Vercel Inc. The hosting infrastructure processes technical access data (such as IP address, time of request and user agent) to deliver and secure them (Art. 6(1)(b) and (f) GDPR). During Strava connection and token renewal, the function also handles the temporary authorization code or refresh token only long enough to send it to Strava; ampulse does not log or store that payload. No workout, sensor or health file passes through this function. We set no cookies and run no analytics on this site. See Vercel's privacy policy.

Your rights

Under the GDPR you have the rights to access, rectification, erasure, restriction, data portability and objection (Arts. 15–21), and the right to lodge a complaint with a supervisory authority. We do not hold your app’s health recordings on our servers. For personal data we do process, such as support correspondence, contact the address above. Data you share with other providers is also subject to their policies.

Health data, plainly

ampulse reads heart, sleep and movement data because measuring them is the product. That data is processed on your device for you, and for nothing else: it trains no models, feeds no advertising, and reaches us in no form.

Changes

If this policy changes, the new version appears on this page with an updated date.