Privacy at LIFT

LIFT is a general-wellness and exercise-planning tool for adults 18 and older. It provides educational workout guidance generated by versioned rules informed by published exercise research. LIFT does not provide medical advice, diagnosis, treatment, rehabilitation, medical clearance, or emergency monitoring, and it cannot determine whether exercise is safe or appropriate for you. If you have a medical condition, injury, are pregnant or postpartum, or have symptoms or concerns, consult an appropriately qualified healthcare professional before exercising. Stop exercising and contact local emergency services for chest pain or pressure, fainting, severe or unusual shortness of breath, new confusion, or another possible emergency. Plans and load estimates are estimates; results and injury prevention are not guaranteed.

This notice describes data handled by the LIFT pilot website and installable PWA. The LIFT pilot team operates the service. Authenticated participants can submit privacy questions or requests through in-app Support.

Configured legal-operator, postal-address, and public privacy-contact details appear at the bottom of this page only when supplied through production configuration. Their absence keeps broad public launch blocked.

The current adult-eligibility acknowledgement is lift-adult-eligibility-2026.07.13. LIFT stores the accepted policy version and timestamp rather than asking for a birth date in that acknowledgement.

LIFT handles account identifiers such as user ID and email, eligibility and policy acknowledgements, display name, units, appearance and notification settings, and account permissions. It also handles profile and Training Passport answers such as goals, experience, confidence, schedule, available equipment, training locations, movement preferences and avoidances, and optional height, weight, gender, or limitation information you submit.

Some profile and training data may qualify as consumer-health or sensitive personal data because it can reveal body measurements, limitations, symptoms, goals, fatigue, readiness, or exercise behavior. Do not submit diagnoses, full medical histories, body photos, precise location, contacts, or unrelated sensitive information.

LIFT handles saved workouts, active and completed workout sessions, exercises, sets, repetitions, loads, duration, distance, RPE or RIR, rest timing, workout feedback, substitutions, generated or curated Training Plans, enrollment, progress, metrics, and body-weight entries.

Workout records remain private unless you intentionally use a social publishing feature. A published post, reaction, or like is visible according to that feature's audience. Private notes, profile answers, body measurements, and support reports are not made social merely because a workout is published.

LIFT handles support and bug reports, replies, attachments or context you submit, and operational records needed to respond. Staff access is limited by assigned permissions but is not the same as no human access.

Operational telemetry can include an account user ID, event name, timestamp, feature step, route or source context, request status, latency, and sanitized failure code. Unless an event has been irreversibly aggregated, LIFT describes this as account-linked telemetry—not anonymous or de-identified data.

LIFT uses data to authenticate accounts; provide workout logging and recovery; generate, display, and progress plans; estimate future sets; show history and metrics; operate selected social features; answer support requests; prevent abuse; diagnose failures; and maintain service security.

Custom plan generation is deterministic and does not send plan inputs to an external generative-AI model. LIFT may use genuinely aggregated statistics for product operations, reliability, and pilot evaluation.

LIFT does not sell consumer-health data, use it for targeted or cross-context behavioral advertising, or provide it to train a general-purpose or external AI model.

Operational service providers may process data under LIFT's direction to provide authentication, hosting, databases, security, communications, or support. Internal account-linked operational analytics are not described as anonymous and are limited to operating and improving the pilot.

Data may be disclosed to service providers acting for LIFT, to people you intentionally share social content with, to protect users or the service, to investigate abuse, or when required by a valid legal process. LIFT does not promise that private data is inaccessible to every authorized processor, operator, or legal recipient.

Before public release, the operator must complete and publish a current processor inventory and state-specific consumer-health consent and authorization flows where applicable.

The current application architecture uses Supabase for account authentication, authentication email delivery, database storage, and related backend services. The repository is configured for Netlify application hosting; when the pilot is deployed there, Netlify processes network and request data needed to deliver the website and server routes.

If you enable web push notifications, LIFT stores the browser-issued subscription endpoint and sends notification payloads through the browser or operating-system push service identified by that endpoint. Email and push delivery can therefore involve the infrastructure providers configured by Supabase, the browser, or the operating system.

Provider roles, subprocessors, hosting regions, contracts, and production configuration can change. A verified, current production processor list and any legally required category or specific-recipient disclosures remain public-launch blockers.

Supabase/Postgres is the source of truth after successful sync. LIFT may use local browser storage to protect active workout drafts, optimistic set state, and queued completion recovery while your device is offline or refreshing.

Local storage may also retain account-scoped custom-plan drafts, interface preferences, timers, support or bug drafts, and install state. It remains on that browser until the app clears it, you clear site data, or the feature expires it. Shared-device users should use browser and operating-system protections.

If you choose Use location this session for the circadian appearance filter, the browser supplies coordinates to calculate local sunrise and sunset in memory. LIFT does not send those coordinates to its server or retain them in browser storage; they are cleared on reload or when the page closes. The app removes coordinates saved by older pilot builds.

Account records are generally retained while the pilot account is active and as needed for recovery, security, abuse prevention, support, legal obligations, and database backups. Completed workouts and plan history are preserved when a generated plan is archived. Exact production retention periods remain a public-launch legal and operational blocker.

LIFT uses authenticated routes, database access policies, least-privilege staff permissions, and conservative service-worker caching. No internet service or storage system can guarantee absolute security. LIFT will evaluate suspected unauthorized disclosures under applicable breach-notification requirements.

You can edit profile details, body-weight entries, notification settings, Training Passport answers, and workout history through the app surfaces that manage those records.

You may request access, correction, export, or deletion through authenticated in-app Support. LIFT may verify the request, retain records when legally or operationally required, and explain any limitation. Some requests are manual during the pilot; self-service account deletion and a formal appeal workflow remain public-launch requirements.

LIFT is restricted to adults 18 and older and is not intended to collect children's data. If you believe an ineligible account or another person's data was submitted, contact Support with only the minimum information needed to investigate.

Material changes receive a new effective date or policy version and may require a fresh acknowledgement. This pilot notice does not replace the state-specific notices, consents, authorizations, or appeal procedures that qualified counsel may require before broad public launch.