Account data
Level Up stores the account details you provide, including name, email address, password hash, date of birth, plan status, onboarding choices, and profile fields you choose to complete.
Closed beta
Level Up is currently in closed beta. Features and policies may change as the service develops, and material updates will be reflected on these pages.
Product activity
We also store training logs, goals, notifications, progression data, and moderation outcomes needed to run the service. Optional product analytics are used only after you consent.
Optional analytics
With your permission, Level Up uses EU-hosted PostHog to understand product use and Google Analytics 4 to understand broad acquisition and signup journeys. Advertising storage, advertising user data, and ad personalization remain disabled.
Analytics use an internal account identifier rather than your email address. We do not send proof files, messages, notes, typed form content, passwords, or full URLs containing private query details. Session replay is disabled for the closed beta. If it is reviewed and explicitly enabled later, sensitive pages and form inputs must remain masked or blocked.
You can accept, reject, or change this optional choice at any time using Cookie settings. Rejecting analytics does not affect the core service.
Referral attribution
When you open an invite link, Level Up stores the referral code in your session until registration. Referral records track attribution and qualification status without exposing referred users' private account details.
Uploaded proof
Proof uploads such as video, image, or PDF evidence are stored so Level Up can review claimed progression, manage disputes, preserve moderation history, and protect the integrity of progression data.
Public and private choices
Profile visibility is controlled from Account settings. Private profiles stay off public profile and leaderboard pages. Approved proof or progression should only appear publicly when the owner has enabled the relevant public surface.
Admin review access
Authorized admins and reviewers may access submitted proof, moderation notes, user reports, and related account context when needed to review progress claims, enforce safety rules, handle abuse, or support the platform.
Payments and billing
If paid plans are enabled, payment processing is handled by an external payment processor such as Stripe. Level Up should store only the billing status, plan metadata, and payment references needed to operate subscriptions or supporter payments, not raw card details.
Account controls
Your settings and deletion path
You can update your account name, email address, public profile details, privacy setting, password, and tagging permissions from Account settings.
You can request deletion of your account from the same page. The delete flow requires your current password and the exact confirmation phrase DELETE NOW.
Deletion removes active account data and owned private files promptly. Unpublished creator Courses are removed; published shared Courses may remain without the creator account identity. Connected billing, scheduled hosted sessions, and Clans with other members must be resolved before deletion so another person's access or records are not removed unexpectedly.
Strava access is revoked when connected. Analytics already sent to providers and transactional messages already delivered follow the provider's retention or manual privacy-request process. Encrypted backups can retain deleted data until the documented backup retention window expires; deleted accounts are not restored into the live service from routine backups.
Do not upload another person's personal data, private footage, or sensitive documents unless you have permission or another lawful basis to do so.
Level Up's closed beta is intended for people aged 18 or over. We do not knowingly permit under-18 accounts during this phase. Parents, guardians, schools, and clubs must not create accounts for children in the closed beta.
Some existing accounts do not have a recorded date of birth, so we cannot claim that every existing user's age has been confirmed. Missing age information alone does not currently trigger automatic suspension or deletion. Suspected underage access requires a safeguarding and privacy review.
Any future access for people under 18 would require updated policies, age-appropriate design, and safeguarding controls before launch. Adult-only eligibility does not remove the need to protect vulnerable adults, community members, or private evidence.
Contact and support
Questions, privacy requests, and support issues
Use the Contact / Support page for beta support requests, moderation questions, payment issues, and privacy-related requests.
Related policies