LP PERFORMANCE · TRAIN WITH PURPOSE
Your privacy
Who looks after your data
Lee Perry, trading as LPPerformance (sole trader), is responsible for your personal data. Contact Tgg.Personaltraining@gmail.com or write to LPPerformance, 973 Kingsbury Road, Erdington, Birmingham, West Midlands, B24 9QB, United Kingdom. Updated 31 October 2026 to describe Community sharing, challenges, strength records and web payments, alongside the existing coaching, device storage and recovery arrangements.
Adults only
LP Performance is for adults aged 18 and over. New applicants must confirm they are 18 or older. This is a self-declaration, not independent age verification.
What we use and why
We use your account, contact and invitation details to provide the coaching service you request (contract). We use necessary security and support information to keep the service safe and resolve problems (legitimate interests). We use coaching goals, workout history, check-ins, pain, sleep, energy, weight, food information and shared notes to personalise and review your coaching. Where this reveals health information, we ask for your explicit consent (UK GDPR Articles 6(1)(a) and 9(2)(a)). We do not sell client data or make solely automated decisions with legal or similarly significant effects.
Phone platform
The phone app reports whether you use Android or iOS when you sign in. This lets your assigned coach see the last reported platform beside your name when helping with the app. This platform report does not include your phone serial number or a list of installed apps. Browser use does not replace your last reported phone platform. Optional phone notifications use a separate app-installation identifier, described below.
Signup device details
When you create an account in a version supporting signup device details, we suggest a broad device platform, such as Android, iPhone, iPad, Windows, Mac or Linux. You can correct that selection before signing up. We save the selected platform, whether you used the app or a browser, and whether you corrected it, to help your coach support account setup. Where signup notifies your assigned coach, the existing notification includes this device description alongside your name and email. These signup details do not include a saved raw browser user-agent, exact phone model, phone serial number or list of installed apps, and are not used to decide account or membership access. A browser's signup platform is separate from your last reported phone platform and the notification installation identifier described below.
Group-training interest list
With your agreement, we collect your name and email and record your choice so Lee can contact you about joining a group with other people. Requests are kept for group matching while needed. The list is private; your contact details are not shared with potential group members without your agreement. Supabase receives and stores the request; Resend may notify Lee by email. To limit abuse, the service stores a keyed hash of the network address supplied to it. Service providers may retain normal security logs. Please do not include health information. You can withdraw your interest or ask to be removed by emailing Tgg.Personaltraining@gmail.com.
Optional phone notifications
In versions supporting phone notifications, you can turn them on in Account and grant your phone's notification permission. We use an Expo push token, a random app-installation identifier and its server-side hash, your account/session link, app identifier, notification preference and, where available, platform and installed build number to send and open the correct coaching alerts. The installation secret is kept in secure device storage and sent to our service for registration and status checks; the registration table stores its hash. Checking your notification settings when you sign in or return to the app also sends this identifier, even while notifications are off. A delivery token is registered when notifications are enabled with permission. The installation identifier is not a phone serial number or advertising identifier. These records are private transport and access-control information, not a directory other clients can browse.
Notification providers and choices
For delivery, Expo receives the destination push token and notification content, then passes the notification to Google Firebase Cloud Messaging on Android or Apple Push Notification service on iOS. Providers may process delivery and technical information outside the UK under their own service arrangements. LP does not use notification identifiers for advertising or cross-app tracking. Turn off phone notifications in Account or change your phone's notification settings. A successful in-app switch-off clears the active delivery token; turning them off cannot recall a notification already queued or displayed. Registration expiry prevents later eligible sends until renewed; it does not itself erase the registration record. Records linked to a deleted account or deleted sign-in session are removed by the database relationship. Other necessary records follow the retention and deletion rules below. Automatic delivery and available notification types depend on the released version and service configuration.
Your health-data choice
Before using personalised coaching in the app, you can explicitly agree to LPPerformance collecting, storing and using the health-related information you choose to provide for planning and reviewing your coaching. The choice starts unchecked. You can withdraw it in More > Account at any time. Withdrawal stops new coaching entries and updates; it does not undo processing already carried out lawfully. Existing records remain available for access or deletion requests while we review any lawful retention reason. If you decline or withdraw, contact Lee about coaching options that do not require this app to process health information. Never include health details in an invitation or before consent.
Who can see it
Your private account and coaching records are available to you and your assigned coach. Community and group sharing choices are described below. Supabase provides authentication, database and private media storage; the project database is in London. Resend delivers account emails using the configured Ireland sending region. OpenAI Sites hosts the public app and receives ordinary web request information. Cloudflare runs connected bookings and the optional AI service described below. Expo and, according to your phone platform, Google Firebase Cloud Messaging or Apple Push Notification service process optional phone notification delivery. Stripe processes enabled web checkout and payment receipts. Support email uses Gmail. Provider support and subprocessors may process information outside the UK; ask us for details of the applicable arrangements.
Profile and avatar choices
You may add a small profile picture and starting age, height and weight. Your profile picture is private to your account; starting measurements are available to you and, with health-data consent, your assigned coach. Where supported, you can crop and zoom your chosen profile photo on the device before saving it to your account. Your 3D avatar choices, optional avatar portrait, chosen expression and touch preferences are saved on your device. If you explicitly share an avatar portrait in Community, that shared copy is also stored with your Community profile. Avatar portraits are pictures rendered from your chosen 3D model; we do not scan your face or match your identity from a photo. Versions supporting saved-meal account sync keep your saved meals privately in your account and cache a copy on your device, including changes waiting to sync. Older versions keep bookmarked meals on that device only. Saved-meal sync requires your health-data choice; withdrawing pauses access and new changes while existing records remain subject to the retention and deletion rules below. Avatar customisation does not use a paid AI service or estimate your health.
Community and private groups
Community is optional. Your chosen display name, posts and replies are visible to people who can access that discussion or group and to your coach. Private bug reports are visible to you and your coach. Directory listing, avatar portrait and achievement sharing have separate choices that start off; turning them on can show the selected profile details to other eligible Community members. Your private workouts, food logs, check-ins and health measurements are not automatically posted. Coaches can moderate contributions and review reports; report and moderation records help manage safety and support. Turning profile sharing off does not erase earlier contributions or copies already seen or saved by others. Avoid posting confidential health information or another person’s details. Contact Lee about correction or removal.
Challenges and strength records
When you choose to use Challenges, we keep your enrolment, submissions, coach reviews and earned progression in your coaching account. Any submitted photo evidence uses its private-photo access controls. Community displays of your achievements depend on your separate sharing choice. Strength records you choose to enter keep separate 1, 3 and 5 repetition histories; they do not require you to perform a maximum-effort test. These private coaching records use the health-information choice and retention arrangements described in this notice.
Web payments and receipts
Where web checkout is enabled, Stripe receives the payment and billing details you enter into its secure checkout. LP uses account and purchase references, agreed prices, payment or subscription status, access or session-credit allocations, and refund or cancellation records to provide the purchased service and handle support. Full card numbers and security codes are entered into Stripe checkout rather than LP’s coaching forms. Payment receipts are sent through Stripe when enabled. Account deletion is separate from cancelling an active renewal, and necessary payment records may be retained for applicable legal obligations or claims under the retention rules below.
Optional session bookings
PT Sessions runs the connected booking service on Cloudflare. When you open Bookings, it verifies your LP sign-in and assigned coach, then uses an explicitly approved link to your booking record. The service receives booking details and account identifiers, rather than your workout, meal or health records. Your coach can connect Google Calendar for session availability and confirmed appointments. Linking a coach or client record requires approval; it is not done automatically from an email address.
Optional AI chat
AI chat is optional. Before sending your first question in a session, you are shown a separate choice to start chat and share the conversation with Cloudflare. Declining does not prevent ordinary coaching features. We use the text you choose to send to answer your question; recent questions and replies may be included for context. Do not include confidential health details, passwords, payment details or information about other people. Your workout and meal plans, bookings, photos and private coaching messages are not automatically fetched or attached to chat. AI replies can be wrong and do not replace your coach or a qualified clinician.
AI access checks and information sent
The Cloudflare service receives your question, limited recent conversation and your sign-in token. It verifies that token with Supabase and reads your account identifier and coach/client role to check access and apply request limits. The AI model receives conversation text and whether you are a coach or client, not your sign-in token or an automatically attached account name, email or identifier. Any personal information you type into chat is still part of the conversation sent for processing. Some questions about using LP Performance receive a labelled app guide from the same service without invoking the AI model. We do not use chat for advertising, cross-app tracking or automated changes to your records.
Chat history and provider handling
Visible chat history is held in app memory for the current signed-in session, not saved as a transcript in Supabase. Clear removes the local conversation; closing the window only hides it and does not clear it. Ending the app session or signing out clears the in-memory chat. Clearing or closing cannot recall a request already sent. Our AI service does not deliberately log prompts, replies or sign-in tokens and has no chat archive. Cloudflare and Supabase may retain ordinary service, account-access and security diagnostics under their provider policies; this notice does not promise that every provider keeps zero records. Cloudflare states that Workers AI customer content is not used for model training or service improvement without explicit consent; we have not enabled such use. Cloudflare may process requests outside the UK. Provider information: https://developers.cloudflare.com/workers-ai/platform/data-usage/.
How long we keep it
We keep active coaching records while providing coaching and for up to 12 months after coaching ends, allowing continuity if you return. We review unused accounts and invitations after 30 days and remove them when no onboarding purpose remains. General support correspondence and minimal privacy-request completion records are kept for up to 12 months after resolution. We review retention monthly. Valid deletion requests can shorten these periods. Only specific records needed for a legal obligation or an actual legal claim are retained as an exception, with a documented reason and necessary period; this is not a blanket exception for all coaching data.
Device storage and copies
The web app stores sign-in state in the current browser tab, unfinished workouts and saved-meal copies on your device. Versions supporting meal sync also keep waiting meal changes there until they are acknowledged or reviewed. Versions supporting draft recovery keep unfinished check-in answers, food descriptions, meal compositions and saved-food or saved-meal builders on the device, tied to your account and consent choice and, where applicable, the particular form, period or record version. Food diary requests waiting for a confirmed save are also kept for retry. Resuming a draft does not submit answers, add food eaten or save a bank item. These are necessary for account access, offline use and draft recovery. Signing out does not erase every unfinished draft, waiting request or saved-meal copy; clear this site's stored data on shared devices. You control copies or exports you save. Encrypted computer backups are taken after substantial completed and checked batches of changes, when the designated computer is available; there is no daily computer-backup schedule. Recovery archives are retained until explicitly reviewed and removed; automatic 14-day pruning is not enabled. Provider-managed backups, where enabled, follow the provider’s configured retention. Database restoration and private-media recovery have been tested, but a separate off-device recovery copy has not yet been verified. If information remains in a backup pending expiry, it must stay outside routine use and erasure must be reapplied before restored data is used.
Your rights and requests
You can ask for access, correction, erasure, restriction or portability where applicable, object to processing based on legitimate interests, or withdraw consent. Contact Tgg.Personaltraining@gmail.com; we verify identity proportionately without requesting passwords. We respond without undue delay and within one calendar month. If a lawful extension or exception applies, we explain it within the initial month. You can complain to the Information Commissioner's Office at ico.org.uk/make-a-complaint/.
Changes
We will update this notice when the service changes. A material change to health-data purposes requires a new consent choice; accepting account terms or an age declaration alone is not health-data consent.