Plain-language policy
Privacy, without the fog.
Last updated 22 September 2026 · Two Waters Fitness 3.0 pre-release preview.
Who this policy covers
Two Waters Fitness is developed by TwoWaters. This policy describes the 3.0 pre-release iPhone app and its Apple Watch, WidgetKit and complication companions. Preview features and connected services may not be available in every build.
Account and Apple Health permissions
Sign in with Apple is required in the current preview. Apple provides an app-specific identifier and may provide a name and email address on first authorisation, including a relay address if you choose Hide My Email. These account details are stored in Keychain. Connected community services use an authenticated session.
Apple Health access is a separate choice. With your permission, the app reads selected activity, workout, nutrition, sleep, heart-rate, weight and recovery categories. The Health Access screen explains the supported categories.
Only an explicit log action can write dietary energy, protein, carbohydrate, fat, water or alcoholic beverage count, and only with the corresponding write permission.
Private app storage
Plans, preferences, workout and climbing history, meals, notes and selected personal photos are primarily held in private app storage. Optional wellbeing entries can include injuries, treatment reminders and quit or reduction history. These entries are separate from public climbing contributions.
The optional InfluxDB credential is stored in Keychain. Signing out does not by itself erase all stored records.
Optional private iCloud backup
Private backup is optional. It saves a recovery snapshot of selected app-owned plans, progress, local history, nutrition records, preferences and personal meal, climbing and coaching photos in your private CloudKit database. Some app-owned records can contain sensitive wellbeing information.
The backup excludes Apple Health records, public climbing-directory data, InfluxDB and trainer-service copies, sign-in credentials and membership state. A private backup is not a public climbing submission.
Turning backup off stops future automatic uploads but retains existing snapshots. Use the backup deletion control to remove matching snapshots in the current iCloud account. Backups in another iCloud account cannot be removed from the current account. Automatic backup retention is limited to seven snapshots.
Optional sharing with a personal trainer
If you choose a trainer, select a sharing scope and confirm it, the app can send selected daily training, nutrition, climbing and hangboard summaries to a protected TwoWaters service hosted on Azure. Sync Now initiates the transfer; granting permission alone does not send your full personal journal.
Access is restricted to the chosen trainer relationship. Revoking that relationship removes access and requests deletion of its stored summaries and advice. These records are not published in CloudKit. Availability depends on the preview service.
Shared climbing directory
Approved sites, sections, routes, contributor labels, public comments and updates, licensed images and opted-in leaderboard contributions can be published in the public CloudKit directory. Private attempts, sends, notes, personal photos and Apple Health data are not public directory records.
New submissions and changes go through a protected Azure service. Reports, blocks, moderation decisions and staff audit information remain private service records. The app does not treat a private pending draft as a published contribution.
Public browsing and contribution have different account requirements. Contribution requires the applicable signed-in account and configured services; production publication is not promised by this preview.
Shared images and screening
Only submit a climbing image if you have permission to share it publicly. Selected submission images are decoded, resized and re-encoded to remove source metadata before private staging and review.
Where configured, the service sends the re-encoded public-submission image to OpenAI for automated safety screening. This does not send all personal app photos or Apple Health data. Screening alone does not publish an image; images remain subject to human review, including when screening is unavailable.
Only approved shared content enters the public directory. Use the in-app reporting and blocking controls to raise concerns. These flows depend on the configured preview service.
Support and suggestions
An in-app submission can contain your name, email, message, a technical summary and an optional screenshot that you review. The selected screenshot is re-encoded and attachments are held privately for validation and scanning. Personal logs and Apple Health readings are not automatically attached.
Review the screenshot and text before sending. Remove sensitive readings, identifiers and credentials. A form is not delivered until the app confirms the service accepted it; use jaybirkett@two-waters.co.uk if sending is unavailable.
Optional InfluxDB export
When you enable export, selected supported Apple Health and app records are sent directly to the server, organisation and database you configure. TwoWaters does not operate that database or receive its contents through this export. Its owner controls access, retention and deletion.
Supported app exports can include training, meals, climbing, shopping-list state, wellbeing entries and progression. Some categories are sensitive; choose deliberately and review the destination before enabling them.
Other services and purchases
Precise climbing-location features request location permission where needed. Venue searches may send a venue name to Apple Maps, and optional licensed-image searches may query Wikimedia Commons. Food barcode lookup uses Open Food Facts. These services receive the requests needed for the feature; external links open under the destination website’s policies.
Paid membership is disabled in the current preview. This website offers no paid tier or subscription price. StoreKit purchase integration is preparation for a future offering, not a current sale.
Advertising and tracking
The app contains no advertising, cross-app tracking or third-party analytics SDK. Health and fitness information is not sold or used for advertising, marketing or data brokerage.
Retention, recovery and account deletion
Use the relevant in-app control to remove local records. Removing the app does not remove private iCloud backups, public contributions, trainer-service records or personal-server exports. Manage Apple Health permissions and records in Apple’s Health and Settings apps.
The account-deletion flow requests fresh Apple authorisation and can report pending, partial or completed processing. A submitted request is not proof that server deletion or Apple credential revocation has completed. Full service completion is not verified for this preview; contact jaybirkett@two-waters.co.uk if the flow is unavailable or unresolved.
Private backups have their own deletion control. Delete exports at your InfluxDB server. For shared-directory or privacy requests, provide only enough information to identify the contribution; do not email Health readings or credentials.
Health and contact
Two Waters Fitness is not a medical device. Its fitness, nutrition and recovery information is general support, not diagnosis, treatment or rehabilitation advice.
Privacy and deletion questions: jaybirkett@two-waters.co.uk.