READY FORTOUCHPERFORMANCE LAB

Your records & sharing.

Ready for Touch is a touch rugby training app. Here is how the current version handles your information.

Working out as a guest

You can follow general workouts without an account. Unfinished guest sessions use a temporary recovery copy on this device for up to 24 hours. Optional remembered guest history keeps up to 90 days of records on this device. Save this workout keeps the selected result for account sign-in. That action keeps the result in this device’s browser storage through sign-in, with a seven-day window to save it. Up to ten results can wait there. Each result is removed when saved or discarded; expired copies are removed when the app next accesses them. After signing in, review the destination account and confirm saving. Completed work, skipped parts, timing and any review answers are saved as a general workout. Your coach-sharing settings then apply. Guest music preferences remain temporary.

Your account and training

New email accounts use Supabase to send and verify a sign-in code. Existing accounts keep their current sign-in during the transition; connecting accounts requires verification of both identities. Supabase handles the email address and sign-in session, while training records stay in the app’s database. Your profile, test measurements, programme, workout logs, field sessions, mobility records and any health details you enter are saved against your account in the app’s hosted Cloudflare D1 database. While signed in, a recovery copy of training records and pending edits stays on this device for up to seven days, including any health information you entered. It is scoped to your account. Pending edits retry when the app is open and connected; competing account changes require review. Unfinished field, mobility and gym steps also have a temporary 24-hour recovery copy. Device storage can be cleared by your browser and is not a guaranteed backup. Clear recovery copies from Help & beta feedback in You, or clear this site’s data in your browser. Use a private device for sensitive records. You can download sessions and completed logs for offline use; those files stay on your device.

Social sign-in

When available, you can use Google, Apple or Facebook to sign in or create an account. The provider shares your account identifier, email and permitted basic profile information with Supabase to verify your identity. We do not request access to your contacts, posts, files or fitness data. Your provider password stays with that provider. Social sign-in does not share your training or health records with other players or enable coach access. Use the same sign-in method each time; Apple’s hidden email or a different provider email can create a separate account. We do not merge training histories by matching email addresses. Contact info@readyfortouch.com if you need help finding existing records.

You choose coach access

Your account records are private except for Community content you explicitly share with selected squads or approved connections. Joining the coaching space lets the Ready for Touch coach read your profile and training records, including past records, injury details, check-ins and notes. Period and cycle-tracker entries require a separate sharing choice. Programme adjustments and any health notes you write are part of shared training records, so consider what you include.

Change or withdraw sharing under You. Withdrawal stops future access through the coaching workspace; it cannot recall information already viewed or downloaded. Your recent coach record views are listed in You.

Community, squads and sharing

Community is optional and separate from your private athlete profile. You choose a social display name, username, optional club, bio and photo. Exact-username discovery and profile links are optional. Players approve connection requests. Joining a squad shares the display name and weekly training-day count you consent to, plus squad Touch reactions.

Every workout post has its own audience: only you, selected squads or approved connections. No workout posts automatically. A new squad does not receive your old posts; later squad joiners and later connections cannot see earlier posts unless you deliberately share them again through a new audience selection. Workout cards show only title, date, duration, level, completed work and a modification label. Health notes, cycle entries, test footage and detailed lift loads are excluded. Posts include only the photo and caption you add yourself. You can remove posts, restrict their audience, disable comments, remove connections, mute, block and report content. Former members lose access to squad-only posts. Existing legacy workout-sharing flags do not publish posts into the new feed; review and share those workouts again.

Community profiles, posts, audiences, connections, Touches, comments and in-app notifications are saved in the hosted Cloudflare D1 database. Removing a social post leaves your private training record saved. Removing the source workout makes its post unavailable. Reports go to the Ready for Touch owner’s moderation area; moderation actions and reported-photo views are recorded separately from coaching access. Push notifications, public discovery feeds and direct messages are not enabled.

Sharing drafts, including a selected photo, may be kept in this device’s IndexedDB storage for up to seven days and are recovered when you reopen the composer. Expired drafts are removed when accessed. They never publish automatically. Sign out or clear site storage on shared devices. Guests can create and export images without an account; posting requires sign-in and an explicit publishing action. Exported images are created on the device and can be downloaded or sent to another app. Copies exported elsewhere cannot be recalled by Ready for Touch.

Coach workspace

The coach can add private coaching notes, tags, athlete status and follow-up dates for athletes who share their records. These are saved in the hosted database and are available only to the coach. The coach can also propose a lighter session or recovery day with a reason. You review and accept it before it changes your programme; the accepted adjustment stays with that date. Private notes alone do not change training. Withdrawing sharing stops access to these coaching records through the dashboard.

Mobile sign-in

The native app stores its sign-in session using iOS Keychain or Android Keystore-backed storage. The website stores its sign-in session in this browser. Training records are retrieved from the same account database. Clips are processed on the device; they are not automatically backed up.

Trackers and imported workouts

Activity files are parsed on your device. We save only selected summaries: source, title, sport, start time, date, duration, distance or average heart rate where supplied, any effort you enter and a link to a saved workout if you choose one. GPS routes and raw files are not uploaded. Imported copies are stored in your account database and follow your coach-sharing choice. Counted workouts contribute to your training-day count shared with squads you join; their details are not posted to the squad feed.

The native mobile app can request read access to workouts in Apple Health or Health Connect. Only the workouts you review and confirm are uploaded. No background health sync, health-data advertising, or sleep, medical, menstrual, route or write permissions are requested. Revoke access in your phone’s health settings. Revoking permission does not delete imported copies: remove those in Trackers or use Delete all records in You.

When enabled, a direct Strava connection uses OAuth. We store access and refresh tokens encrypted in the app database, and fetch up to 30 recent activities only when you request them. These API activities are displayed privately to you, not saved as training records, shared with coaches or squads, exported, or used for programme decisions. The on-screen list clears when the app is hidden or after five minutes. Disconnecting revokes provider access and deletes connection credentials; if revocation fails, the app reports the failure and you can retry or revoke access in Strava settings. Temporary connection requests expire after ten minutes and are removed on subsequent connection requests. File imports are separate copies you explicitly choose to retain.

Photos and video

Camera clips and uploaded videos used for tests are processed in the browser and are not uploaded to the coach or stored in the account database. Save any clip you want to keep to your device before closing it. Saved test records contain the measurements and review metadata, not the footage. Test videos are not stored across devices. Community profile and workout photos that you explicitly upload are stored separately in Cloudflare R2. Photos are resized and location metadata is removed. Access is checked against the profile or post’s permissions. Unused uploads become eligible for cleanup after 24 hours and are removed on the owner’s next upload; account deletion removes their stored photos.

Export and deletion

Use the record export and data controls in You to download or remove your training records. Cycle-tracker entries can also be removed independently in the tracker. Removing training records does not delete your sign-in account, coach access history, private coaching notes or coaching-sharing settings. Use Delete my account in Account, help & privacy to request account-level deletion without sending an email. We aim to process requests within seven days; pending requests can be cancelled. Account deletion also removes the sign-in identity, training, coaching notes, shared content and memberships, and closes squads you own. It cannot remove copies already downloaded by you or others. Provider backup retention is separate from active account storage.

Other services

Opening music services or exercise videos takes you to those services or loads their content. Their account and privacy settings apply. Ready for Touch does not receive your music-service password.

Beta feedback and service operations

When you open your account we record your verified email, display name, first visit and last visit. The owner can see profile-completion status and saved-workout counts to support the service, without gaining access to private training or health details. Support reports include the text you submit, category, screen and web/app type. No footage, test results or health entries are attached automatically. Reports appear in the owner’s support queue and your report history.

Planning squad sessions

Squad members can arrange field sessions and see the chosen session, meeting time and place, and the display names of people who mark themselves as going. No location tracking is used. Attendance does not mark a workout complete. Leaving a squad removes your attendance and the meetups you organised there.

Questions?

Email info@readyfortouch.com.