← All policies

Privacy and data

Health Data and Connected Services

Apple Health permissions, scoring data, server uploads and disconnecting.

Published · Version 0.6 · Effective 23 October 2026 · Commpair (Pty) Ltd

What Apple Health access means

ASTA requests read access to steps, workouts, walking/running distance, cycling distance, swimming distance and sleep. The reviewed iPhone Health connection requests no write access to Apple Health. The iPhone app asks for Health access only after you choose a Health feature and approve its disclosure and selected data types. Dashboard readings cover the current day, while sleep processing can include the preceding day to capture an overnight session. Event scoring reads the applicable event or daily activity window. It does not request heart-rate samples or workout routes.

Apple lets you choose access by data type. A missing result may reflect permissions, a source that has not synced, no matching records or a connection problem. ASTA cannot infer that you refused access merely because no records were returned.

What leaves your phone

For eligible events, steps can be uploaded as time-bounded totals. Saved workouts can be uploaded with a record identifier, activity type, start/end times, distance, source app/device information and evidence used to reject manual records. Pools use daily totals and may use sleep duration and start/end times.

This information is linked to your ASTA account on the server to verify activity, avoid duplicates, calculate progress and determine results, including for the free test-credit beta. Health-derived progress and results may be shown in event views. Pool members can see each other’s status, goal completion and non-sleep current totals; detailed wallet-Pool reports are limited to the viewer’s own player in the reviewed response. Read Privacy Policy before enabling sync or joining an event.

Eligible activity sources

Running, cycling and swimming require a completed recorded workout with suitable distance evidence. Everyday movement is not a substitute for a saved workout. Manually entered workouts do not qualify.

A third-party app must write a compatible workout and distance to Apple Health, and the record must pass ASTA’s source and validation checks. Data appearing in Apple Health is not a guarantee that every Garmin, Strava or other record is supported.

Where offered, a direct connected-service or companion-device integration has its own supported activities and authorisation. Avoid submitting the same activity through multiple routes; duplicate or overlapping records require verification.

Sync timing and background activity

With syncing enabled, ASTA may receive Health changes and attempt background uploads. Device settings, connectivity and iOS scheduling can delay delivery. Check the displayed sync status; a notification does not extend a deadline.

Competition activity must occur within its activity period. The current app provides a seven-minute final upload window after the Competition ends; this permits delayed receipt, not extra exercise. Pool day handling follows the separate Pool rules.

Disconnect and withdraw permissions

Before connecting Health, ASTA explains the selected data types, uploads and participant audience. Your versioned sharing choice is recorded on the server. In Settings, disconnect Apple Health to withdraw sharing consent and stop automatic uploads. You can also change ASTA’s individual read permissions in Apple Health. Removing device permission does not remove information already uploaded to ASTA or records in the source service.

Use the data-rights and account-deletion controls for previously uploaded account information. Disconnect Strava using its connection control. ASTA stops importing, erases its active stored credentials and queues provider revocation with retries if Strava is unavailable. Tokens awaiting revocation remain encrypted until the grant is revoked. Previously imported activity is handled through the data-rights and deletion process. Revoking access can stop future activity from counting.

Turning off Health sharing stops future consent-gated uploads; it does not erase previously uploaded activity or results. Use account deletion or contact help@astafitness.com about existing information. ASTA does not delete records from Apple Health.

Limits on health-data use

Health information must not be sold, used for advertising or shared for unrelated purposes. ASTA’s beta does not use Health data for advertising tracking, marketing notifications or sponsor access. Apple’s HealthKit rules apply in addition to privacy law.

Free test credits have no cash or redemption value. Event participation can still share Health-derived progress and results with the event’s audience, as disclosed before Health sharing is enabled. These disclosures do not establish Apple approval or make every possible use of Health data permissible.