Effective August 7, 2026.
Lapped is a private, invitation-based fitness league and optional family-care app. Questions and privacy requests may be sent to support@getlapped.app.
Lapped does not request raw HealthKit samples, routes, location, nutrition, workouts, cycle data, or permission to write to Apple Health.
Apple Health is Lapped's only health ingestion boundary. The iPhone performs read-only HealthKit aggregate queries and sends bounded civil-day summaries to authenticated, App-Checked Firebase Functions. Raw samples and HealthKit source or device metadata do not leave the phone.
If you use Fitbit, you may independently enable Google Health's setting that writes supported Fitbit data into Apple Health. Lapped still reads Apple Health; it does not connect to Fitbit or Google Health, receive their credentials, call their APIs, or control their export timing.
Lapped refreshes health data when the app is opened, resumed, or manually refreshed. It does not promise continuous background HealthKit delivery.
We use the minimum data needed to provide authentication, private leagues, goals, leaderboards, challenges, streaks, notifications, account security, optional Sleep League features, and user-directed Care sharing. We do not use health data for advertising, tracking across other companies' apps or websites, credit, insurance, employment, or data brokerage.
Care sharing is optional, directional, revocable, and granted caregiver by caregiver, metric by metric. The only Care metrics are activity, walking/running distance, and optional reconciled sleep duration. A caregiver receives only metrics present in their active grant; server-side filtering prevents access to ungranted fields. A Care relationship does not grant raw access to another person's Firestore health documents.
Lapped's independent Sleep League score and its sharing preference are separate from Care and remain controlled by the member.
Application data is stored in the Lapped Firebase project. Health writes and Care projections are server-controlled. Apple relay/cursor state, work queues, push installations, and other operational collections deny all client access. Access is limited to the account owner, authorized private-league members for league-visible projections, explicitly authorized caregivers for filtered Care responses, and service operators who need access to operate or secure Lapped.
We use authentication, App Check, least-privilege Firestore rules, bounded queries, encryption in transit, deterministic retry/idempotency controls, and retention policies for terminal operational records. No system can guarantee absolute security.
We retain account and product data while your account is active and as needed for security, legal obligations, dispute resolution, and bounded operational retries. Expiring operational receipts are removed through configured retention policies.
You can delete your account in the app. Deletion removes the canonical account, Apple relay state, metrics, league and Care relationships, notifications, installation ownership, and other person-scoped operational records according to the product's deletion workflow. Deletion does not alter data already stored in Apple Health, Fitbit, or Google Health because Lapped does not own those stores or their connection.
Lapped is not directed to children under the minimum age required to consent to online services in their jurisdiction.
We may update this policy as the product or law changes. Material changes will be reflected by updating the effective date and, when appropriate, notifying users in the app or release notes.