Two Waters Fitness

Support and readiness

Help for the current build.

Two Waters Fitness 1.0.1 · build 2 · pre-release.

01

Contact support

Email jaybirkett@two-waters.co.uk with a short description, the screen involved and the steps that led to the issue.

Do not send Health readings, private photos, Apple identifiers, API tokens or local server addresses.

02

Sign in with Apple

The current build requires Sign in with Apple. Health access is separate: signing in never grants Health permission.

If Apple sign-in state becomes invalid, use the account controls in the app or contact support. The current build can remove its local Apple sign-in association.

03

Apple Health access

Open More → Apple Health Access to request or review supported categories. Missing permissions or measurements remain blank rather than being filled with sample values.

Meal, water and alcohol values are written only after an explicit log action and only when the matching write permission is authorised.

04

CloudKit climbing

The shared climbing directory is pre-release. It is designed to use public CloudKit records for walls, sections, routes, licensed images, moderation reports and opted-in leaderboard ascents.

CloudKit Production activation, final user blocking and moderation operations must be completed before public release. Personal Health data is never stored in the shared directory.

05

StoreKit membership

StoreKit 2 support is prepared for monthly and annual Full memberships, purchase restoration and Apple subscription management.

Products, pricing, Sandbox proof and Free/Full enforcement are not yet release-ready. There is currently nothing to purchase through this website.

06

Optional InfluxDB

More → Sync Settings contains the optional user-configured InfluxDB connection. The token is protected in Keychain and the export travels directly to the server the user configures.

Twowaters does not operate or receive that database. The user or server owner controls access, retention and deletion.

07

Data and account deletion

Local records can be removed through available in-app controls or by deleting the app. Apple Health permissions and records are managed through Apple’s Health and Settings apps. InfluxDB exports must be removed from that server.

A complete in-app “delete account” flow, Apple token revocation and public-contribution anonymisation or deletion are still release gates. For a public directory deletion request, email support.

08

In-app forms

Support, Report and Suggestion forms exist in the app and exclude Health readings, photos, personal logs, private server addresses and API tokens.

Delivery requires the support submission service to be configured. Until then, the app retains the form and reports that it was not sent; use the support email above.

Release evidence

What “pre-release” means here

The source contains iPhone, WidgetKit, Apple Watch and complication targets. This website does not claim verified Xcode compilation, signing, device installation, TestFlight availability, StoreKit Sandbox success, CloudKit Production deployment or App Review acceptance.