1. Information We Collect
1.1 Account Information
When you create an account using Sign in with Apple or Sign in with Google, we receive and store:
- Display name — your name as provided by Apple or Google
- Email address — your email address (if you use Apple's private relay, we receive the relay address only)
- Authentication identifier — a unique identifier assigned by Firebase Authentication
We do not have access to your Apple ID password, Google password, or payment method details.
1.2 Fitness Profile Data
During onboarding and through the Settings screen, you may provide:
- Biological sex
- Body weight
- Training goal (e.g., hypertrophy, strength, general fitness)
- Training experience level
- Training background
- Number of training days per week
- Rest period preference
- Available gym equipment
- Preferred weight unit (kg or lbs)
- Barbell and dumbbell increment preferences
- Maximum dumbbell, dumbbell pair, and barbell weights
This data is stored locally on your device and synced to our cloud servers for AI-powered features. It is used to generate personalized workout programs.
1.3 Workout Data
When you log workouts, we collect:
- Workout date and duration
- Exercises performed
- Sets, repetitions, and weights used
- Workout completion status
- Personal records (PRs) detected during workouts
- AI coaching feedback and weight suggestions attached to completed sessions
1.4 Subscription Information
If you subscribe to Liftplanr Premium, we store:
- Subscription product identifier (monthly or yearly)
- Subscription expiration date
- Store transaction identifier (Apple App Store on iOS, Google Play on Android)
- Subscription environment (production or sandbox)
All payment processing is handled entirely by the app store on your platform — Apple through the App Store on iOS, or Google through Google Play on Android. We do not collect or have access to your credit card number, billing address, or other payment details. We use RevenueCat as our subscription-management provider; it validates your purchase with the relevant app store and reports your subscription status back to us (see Sections 5 and 11).
Coach (trainer) subscriptions are billed separately through Stripe — see Section 1.11.
1.5 Health & Fitness Data (Apple Health & Health Connect)
The App can optionally integrate with your device's health platform — Apple Health (HealthKit) on iPhone and Apple Watch, or Health Connect on Android. These integrations are off by default and are enabled only from the Settings screen.
Apple Health (iOS). If you enable the Apple Health integration, the App may read and write the following HealthKit data:
- Body weight — read from Apple Health to keep your profile up to date
- Workouts — written to Apple Health so your completed strength-training sessions appear in the Health app and contribute to your Activity rings
- Heart rate — read during Apple Watch workouts to display your current heart rate on the Watch and record it with the workout session
- Active calories — collected during Apple Watch workouts and saved with the workout session
Health Connect (Android). If you enable the Health Connect integration, the App may read and write the following Health Connect data:
- Body weight — read from Health Connect to keep your fitness profile up to date
- Workout sessions — completed strength-training sessions are written to Health Connect so they appear in your other health and fitness apps
- Active calories — an estimated active-energy figure for each completed session is written to Health Connect
The Android app does not read heart rate, as Liftplanr does not yet have a Wear OS companion app.
Health-platform data is accessed only with your explicit permission, granted through the operating system's standard authorization prompt. You can revoke access at any time:
- iOS — Settings > Privacy & Security > Health > Liftplanr on your iPhone or Apple Watch
- Android — open the Health Connect settings, then App permissions > Liftplanr
Important: Workout, heart rate, and active-calorie data written to your health platform stays on your device and in your personal health account, managed by Apple or Google. This data is not sent to our servers. Body weight read from your health platform is used to update your fitness profile, which syncs to our servers for AI features (see Section 3). We do not share health-platform data with third parties, with a coach you link to, or with our AI provider beyond the body weight already in your profile, and we never use it for advertising.
1.6 Exercise Videos
The App may download exercise demonstration videos to your device for offline viewing. These videos are static content fetched from our servers and do not contain or transmit any personal data. You can disable video caching in Settings > App Settings.
1.7 Push Notifications
If you enable notifications, the App may send push notifications for:
- Workout reminders — scheduled reminders to train
- Rest timer alerts — notifications when your rest period between sets is complete
- Weekly summaries — a weekly training summary
- Coach activity — if you have linked a coach, notifications when they publish a new program or reply to you
You can control each notification type individually in the App's settings. Reminders, rest alerts and weekly summaries are generated locally on your device using your operating system's local notification framework and send nothing to our servers. Coach notifications are sent from our backend through Firebase Cloud Messaging and carry only the identifiers needed to open the right screen.
1.8 Website Analytics (Website Only)
When you visit our website, we may use Firebase Analytics (Google Analytics) to understand how visitors use the site — for example, which pages are viewed and for how long. We only enable analytics after you accept our cookie banner. If you decline, no analytics data is collected. Analytics data is aggregated and does not identify you personally.
1.9 App Analytics and Crash Reporting
The App uses Firebase Analytics and Firebase Crashlytics on both iOS and Android. Both are linked to your Firebase account identifier, which means the events and crash reports we receive are associated with your account rather than being anonymous. We describe this plainly because it is what the App does today.
What Firebase Analytics records:
- Which onboarding step you reached, and whether you finished onboarding
- Whether an AI action was tapped and whether it succeeded (program generation, optimize, exercise swap, coach chat)
- Paywall impressions, trial starts, and subscription events
- Workout started / workout completed counts
- Screen views and standard app-lifecycle events collected by the Firebase SDK (app open, first open, session start), plus the device model, OS version, app version, language and coarse country the SDK derives from the request
What Firebase Crashlytics records:
- Crash and non-fatal error stack traces, device model, OS version, app version, and the account identifier of the session that crashed
What neither of them ever receives: your workout content (exercises, sets, reps, weights), your body weight, your reported injuries, your messages to the coach, or anything you type. Events are counters and identifiers — "a workout was completed", never which workout.
- Legal basis: Art. 6(1)(f) GDPR — our legitimate interest in understanding whether the App works and in fixing the crashes it produces. We have balanced this against your interests: the data is limited to product interaction and stability, is never used for advertising or profiling, is never sold, and is never combined with data from other services.
- Your choices: you can object at any time under Art. 21 GDPR by emailing support@liftplanr.app, and we will disable analytics and crash reporting for your account. An in-app switch to turn both off is being added in a forthcoming release.
- Analytics and crash data are deleted along with everything else when you delete your account.
1.10 Ask Otso (coach chat)
Ask Otso is the App's in-app chat with our AI coach. It runs only when you open it and send something.
What is sent to our backend, and on to our AI provider, when you send a message:
- Up to the last 8 messages of the current conversation, each capped at 500 characters — yours and the coach's
- Today's session context: the workout day, the exercises in it, your planned and logged sets, your rest timings, and how far into the session you are
- Your fitness profile and equipment (the same data Section 3 describes)
- Your active injuries, and — if you tap "something hurts" — the body part you select
- Your first name, if you provided one at sign-in
What is stored on our servers: the reply is written to a short-lived idempotency record that expires after one hour, so that a retry from a flaky connection returns the same answer instead of charging you a second turn. That record is the only server-side persistence of a chat turn. We do not keep a chat history on our servers; the conversation you see lives on your device.
Other facts about Ask Otso:
- Usage is capped at 40 turns per day per account
- Chat content is never used to train AI models (see Section 11)
- Chat content is never shared with a coach you have linked (see Section 1.11)
- Do not type anything into the coach you would not want processed by an AI service — it is a training assistant, not a confidential channel, and it is not a medical service (see our Health & Fitness Disclaimer)
Legal basis: Art. 6(1)(b) GDPR — performance of the service you asked for; Art. 9(2)(a) — your explicit consent for the health-related parts (injuries, body weight) you choose to include.
1.11 Liftplanr Coach (a linked human coach)
Liftplanr Coach lets a real personal trainer program for you. Nothing here happens unless you accept an invite from a coach, and you can end it at any time.
What your linked coach can see about you:
- Your name
- Your body weight
- Your training goal and experience level
- Your available equipment
- Your active injuries
- Your workout sessions — date, exercises, sets, repetitions and weights
- Your weekly check-ins — the adherence, energy and sleep scores and any notes you write
- Comments you leave on a workout
What your linked coach can never see:
- Your email address
- Your Ask Otso conversations
- Your Apple Health or Health Connect data
- Your payment or subscription details
Ending the link. You can unlink from your coach at any time in the App, and your coach can unlink you from their side. Access to your data ends at unlink, immediately. If your coach's subscription lapses, the same applies. A 7-day grace period after an unlink keeps your own access to the App open while you decide what to do next — it does not extend your former coach's access to your data.
If you are the coach. When you sign up as a trainer we additionally process your business contact details and your Stripe customer and subscription identifiers so we can bill you. Payment card details go directly to Stripe and are never seen by us. The videos and images you upload for your clients are stored as described in Section 4.5. Your obligations toward your clients' data are set out in our Terms of Service.
Legal basis: Art. 6(1)(b) GDPR — performance of the coaching service you asked for; Art. 9(2)(a) — your explicit consent to share health-related data (body weight, injuries, check-in notes) with a coach, which you give by accepting the link; Art. 6(1)(b) and 6(1)(c) for a trainer's own billing and bookkeeping data.
1.12 Apple Search Ads Attribution (iOS)
If you install the iOS app after seeing an ad in the App Store, Apple's AdServices framework gives the App a short-lived attribution token. The App forwards that token to RevenueCat, which exchanges it with Apple to learn which campaign the install came from, so we can tell whether our advertising is worth the money.
- The token is not an advertising identifier. We do not collect the IDFA, and the App shows no App Tracking Transparency prompt, because we do not track you across apps or websites owned by other companies.
- What comes back is campaign-level attribution — which campaign, ad group and keyword produced the install — not anything about you personally.
- This runs on iOS only. There is no equivalent on Android or the website.
- Legal basis: Art. 6(1)(f) GDPR — our legitimate interest in measuring our own marketing. You may object under Art. 21 by contacting us.
1.13 Information We Do NOT Collect
- We do not collect your precise location
- We do not access your contacts, photos, or camera (the coach portal's media upload reads only the file you pick)
- We do not share Apple Health or Health Connect data with third parties, with a linked coach, or use it for advertising. Body weight read from your health platform may be synced to our servers as part of your fitness profile (see Section 1.5)
- We do not use device advertising identifiers, and the iOS app shows no App Tracking Transparency prompt (see Section 1.12)
- We do not serve advertisements
- We do not sell your data, and we have never done so
2. How We Use Your Information and Legal Basis
We use the information we collect for the following purposes. Under GDPR, we are required to identify a legal basis for each processing activity:
| Purpose | Data Used | Legal Basis (GDPR) |
|---|---|---|
| Account authentication | Email, display name, authentication identifier | Art. 6(1)(b) — contract performance |
| AI workout program generation | Fitness profile (goal, experience, equipment, sex, body weight), workout history | Art. 6(1)(b) — contract performance; Art. 9(2)(a) — explicit consent for health data |
| AI weight suggestions | Fitness profile, recent exercise performance | Art. 6(1)(b) — contract performance; Art. 9(2)(a) — explicit consent for health data |
| AI session feedback | Fitness profile, first name, completed workout data | Art. 6(1)(b) — contract performance; Art. 9(2)(a) — explicit consent for health data |
| AI injury exercise modifications | Fitness profile, reported injuries | Art. 6(1)(a) — consent; Art. 9(2)(a) — explicit consent for health data |
| Ask Otso coach chat | Up to 8 recent messages (≤500 characters each), today's session context, active injuries, first name | Art. 6(1)(b) — contract performance; Art. 9(2)(a) — explicit consent for health data |
| Sharing your training data with a coach you linked | Name, body weight, goal and experience, equipment, active injuries, sessions, check-ins, workout comments | Art. 6(1)(b) — contract performance; Art. 9(2)(a) — explicit consent for health data |
| Coach subscription billing (trainers only) | Business contact details, Stripe customer and subscription identifiers | Art. 6(1)(b) — contract performance; Art. 6(1)(c) — legal obligation (bookkeeping) |
| Apple Health / Health Connect sync | Body weight (read), heart rate and active calories, workout summaries (write) — with your permission | Art. 6(1)(a) — consent; Art. 9(2)(a) — explicit consent |
| Cloud backup and sync | Workout sessions, programs | Art. 6(1)(b) — contract performance |
| Subscription management | Transaction ID, product ID, expiration date | Art. 6(1)(b) — contract performance |
| Rate limiting | Daily count of AI feature usage (no personal data) | Art. 6(1)(f) — legitimate interest (service stability) |
| Crash reporting | Crash logs, device model, OS version, account identifier | Art. 6(1)(f) — legitimate interest (service stability) |
| App analytics | Product-interaction events (onboarding steps, AI taps, paywall, workouts) linked to your account identifier — no workout content, injuries or chat text | Art. 6(1)(f) — legitimate interest (product improvement) |
| Website analytics | Page views, session duration (website only, with your consent) | Art. 6(1)(a) — consent |
| Transactional lifecycle email | Email address, first name, account timestamps, trial/purchase state | Art. 6(1)(f) — legitimate interest (servicing the account you created); soft opt-in under ePrivacy Art. 13(2) |
| App Store install attribution (iOS) | Apple AdServices attribution token, campaign-level attribution | Art. 6(1)(f) — legitimate interest (marketing measurement) |
Note on health data: Body weight, biological sex (in a fitness context), injury reports, check-in notes and anything health-related you type into the coach chat may constitute data concerning health under GDPR Article 9. We process this data based on your explicit consent, which you provide when you use the App's AI features or accept a coach link. You can use the App's core features (workout logging, tracking) without consenting to AI data processing, and you never have to link a coach.
2.1 Lifecycle emails
We send a small, fixed set of one-off emails about the account you created. We do not run a newsletter and we do not send recurring marketing. There are exactly four:
| When it sends | Sent at most | |
|---|---|---|
| Your plan is ready | After you sign up and generate your first program but have not yet started a trial or subscription | Once per account |
| Your AI coach is on pause | After a trial or subscription has ended | Once per account |
| No big commitment needed | After you opened the store's purchase sheet and cancelled without buying | Once per account |
| How is training going? (review request) | Around day 10 after you started paying | Once per account |
- What they contain: your first name (if you provided one at sign-in), the reason you received it, a link to open the App, our postal identity, and a one-tap unsubscribe link.
- One-tap unsubscribe stops all of them. Unsubscribing from any one of these emails opts you out of the entire pipeline — we will not email you again from it. You can also email support@liftplanr.app.
- Who sends them: we use Resend as our email delivery provider. Resend processes your email address and the message content on servers in the United States (see Sections 5 and 10).
- Legal basis: Art. 6(1)(f) GDPR — our legitimate interest in servicing an account you deliberately created, together with the soft opt-in path in the ePrivacy Directive Art. 13(2): the emails concern the same service you signed up for, and every one carries a clear, free opt-out.
- Apple Sign-In private relay: if you signed up using "Hide My Email," we send to the relay address Apple provides — we never receive your real email, and Apple forwards the message to you.
- Support replies, receipts and security notices are not part of this pipeline and are not covered by the unsubscribe link; they are sent only in response to something you did.
3. AI-Powered Features
Liftplanr uses a third-party AI service to power its AI features, including program generation, program optimization, weight suggestions, session feedback, and the Ask Otso coach chat. See Section 11 for the specific service used.
What data is sent to our AI provider
When you use an AI feature, the following fitness data only is sent to our AI provider's servers:
- Training preferences (goal, experience level, days per week)
- Body metrics (biological sex, body weight)
- Available equipment
- Workout history (exercises, weights, and repetitions)
- Reported injuries (body part and severity), when using exercise modification features
- The text you type into the Ask Otso coach chat — up to the last 8 messages of the conversation, each capped at 500 characters
- The body part you select when you tell the coach that something hurts
What data is NOT sent to our AI provider
- Your email address
- Your device identifiers
- Your Firebase user ID
- Your IP address (not forwarded in request payloads)
Your first name may be included in AI requests to personalize coaching feedback and session reviews. No other personally identifiable information is sent.
All AI requests are processed through our backend servers (hosted in the EU) — the App does not communicate directly with the AI provider. However, the AI service may process requests on servers located in the United States or other regions outside the EU. Only the fitness data listed above is included in these requests. AI-generated responses are returned to you and are not stored on our servers, with one narrow exception: an Ask Otso reply is held in an idempotency record that expires after one hour, so a retried request does not produce a second answer (see Section 1.10).
Data sent to our AI provider is not used to train AI models. See Section 11 for our AI provider's terms of service.
4. Data Storage and Security
4.1 Local Storage
Your fitness profile and workout data are stored locally on your device in an SQLite database — Apple's SwiftData framework on iOS, the Room persistence library on Android.
We want to be precise about encryption: the App does not apply its own encryption layer to that local database. It relies on the operating system's file-level encryption — iOS Data Protection on iPhone and Apple Watch, and Android's file-based encryption — which protects the file while the device is locked and is tied to your device passcode or biometric lock (Face ID, Touch ID, or Android biometric unlock). On a device with no passcode set, that protection is correspondingly weaker. Set a passcode.
4.2 Cloud Storage
Account information, workout sessions, and programs are synced to Google Cloud Firestore, hosted in the EU (europe-west1, Belgium) region. Data is:
- Encrypted in transit using TLS 1.2+
- Encrypted at rest using Google's default encryption
- Protected by Firebase Security Rules that restrict access to authenticated users only — each user can only access their own data, and a linked coach can read only the client data listed in Section 1.11
4.3 Backend Infrastructure
Our backend runs on Google Cloud Functions in the EU (europe-west1) region. All API requests require a valid Firebase Authentication token. We do not maintain separate logs containing personal data.
4.4 Android Backup
The Android app is excluded from Android backup. Your local workout database is not copied into Google's Auto Backup or Device-to-Device transfer, so a copy of your training data never lands in a Google Drive backup we cannot see or delete. Your data reaches a new device the way it is meant to — by signing in and syncing from our servers.
4.5 Coach Media Storage
Videos and images that a coach uploads for their clients are stored in Google Cloud Storage (Firebase Storage) in the EU. Storage Security Rules deny all direct access to that bucket. The only way a file goes in is a short-lived signed upload URL our backend mints for one declared file, and the only way it comes out is a tokened download URL — an unguessable per-file token issued when the upload is finalized. A coach's library is not browsable by other coaches, by other clients, or by anyone with the bucket name.
5. Data Sharing
We do not sell, rent, or trade your personal information to third parties.
We share data only with the following service providers, strictly for the purposes of operating the App:
| Provider | Purpose | Data Shared |
|---|---|---|
| Google Firebase (Authentication) | Account sign-in and management | Email, display name, auth ID |
| Google Firebase (Firestore) | Cloud storage and sync | Workout data, programs, subscription status |
| Google Cloud Storage (Firebase Storage) | Coach media hosting (EU) | Videos and images a coach uploads for clients |
| Third-party AI service (see Section 11) | AI workout generation, coaching, and the Ask Otso chat | Fitness profile, workout history, chat text, first name (no email or user ID) |
| Apple App Store / Google Play | Consumer subscription payment processing | Handled by the app store — we receive transaction identifiers only |
| RevenueCat | Subscription management infrastructure; Apple Search Ads attribution exchange | App user identifier (your Firebase user ID), purchase receipts, subscription status, iOS AdServices attribution token |
| Stripe | Coach (trainer) subscription billing | Trainer's email and billing details, Stripe customer and subscription identifiers. Card details go to Stripe directly and are never seen by us |
| Resend | Transactional lifecycle email delivery | Email address, first name, message content |
| Apple AdServices (iOS only) | App Store install attribution | Short-lived attribution token — no advertising identifier (see Section 1.12) |
| Apple Health / Health Connect | Health data sync (with permission) | Body weight (read — synced to profile on our servers), heart rate and active calories (stay on device), workout summaries (write — stay on device) |
| Firebase Analytics | App and website usage analytics | Product-interaction events linked to your account identifier (app); page views with your consent (website) |
| Firebase Crashlytics | Crash reporting and stability | Crash logs, device model, OS version, account identifier |
We also share your training data with a coach you have personally linked — a human being, not a service provider — strictly as described in Section 1.11.
We do not share data with advertising networks, data brokers, or any other third parties.
6. Data Retention
- Active accounts: Your data is retained for as long as your account is active.
- Deleted accounts: When you delete your account, all data is permanently removed from our servers and your device immediately (see Section 8). We do not retain any personal data after account deletion — there is no grace period or soft-delete window. Cloud Function execution logs (which do not contain personal data) are retained for 30 days per Google Cloud's default log retention policy.
- AI processing: Data sent to our AI provider for AI features is processed in real time. AI-generated coaching feedback and weight suggestions are stored with your workout session data so they can be displayed in your workout history and synced across devices. The raw prompts sent to our AI provider are not stored on our servers.
- Ask Otso: a reply is held for one hour in an idempotency record and then expires. Nothing else about a chat turn is kept server-side.
- Coach media: a trainer's uploaded videos and images are deleted from Storage when that trainer's account is deleted.
- Billing records: where Finnish accounting law requires us to retain invoice and transaction records (typically six years), we retain those records for that period even after an account is deleted.
7. Your Rights and Choices
Under GDPR and applicable data protection laws, you have the following rights regarding your personal data:
7.1 Access and Portability
All of your workout data and profile information is visible within the App at any time. You also have the right to receive your personal data in a structured, commonly used, machine-readable format (GDPR Article 20).
Self-service export is on the web portal, and only there. Neither the iOS app nor the Android app has an export button — whichever one you use, this is the route:
- Sign in at liftplanr.app/account with the same Apple or Google account you use in the App, and choose Export my data. Your data downloads as a JSON file.
If you would rather not use the portal, email support@liftplanr.app from the address on your account and we will send you the same JSON within 30 days, as GDPR Article 12(3) requires.
7.2 Correction
You can update your fitness profile at any time through Settings > Edit Profile in the App. You have the right to have inaccurate personal data corrected (GDPR Article 16).
7.3 Deletion
You can permanently delete your account and all associated data at any time through Settings > Delete Account in the App, or from liftplanr.app/delete-account. This action:
- Deletes your Firebase Authentication account
- Deletes all data from Cloud Firestore (profile, sessions, programs, usage records, check-ins, comments)
- Unlinks you from a coach, if you had one, and removes you from their roster
- Deletes a trainer's uploaded media from Storage
- Deletes all local data from your device (the local SwiftData or Room database, cached preferences)
- Is irreversible — deleted data cannot be recovered
Note: If you have an active subscription, deleting your account does not automatically cancel your subscription. You must cancel your subscription separately — on iOS through Settings > Subscriptions on your iPhone or the App Store, on Android through Google Play > Payments & subscriptions, and for a Coach subscription through the Stripe billing portal at Coach > Billing.
7.4 Restriction of Processing
You have the right to request that we restrict the processing of your personal data in certain circumstances (GDPR Article 18), for example, if you contest the accuracy of the data or object to our processing.
7.5 Right to Object
You have the right to object to processing based on legitimate interest (GDPR Article 21). Where we process data on that basis — app analytics, crash reporting, rate limiting, lifecycle emails, and iOS install attribution — you may object by contacting us at support@liftplanr.app, and for the emails by using the one-tap unsubscribe link in any of them.
7.6 Withdrawal of Consent
Where processing is based on your consent (AI features, Ask Otso, sharing with a linked coach, Apple Health, website analytics), you may withdraw consent at any time without affecting the lawfulness of processing carried out before withdrawal. You can stop using AI features at any time. You can unlink your coach at any time, which ends their access immediately. You can revoke Apple Health or Health Connect access in your device's settings. You can reject analytics cookies on the website.
7.7 Sign Out
You can sign out at any time through Settings > Sign Out. Signing out clears your authentication state but preserves your local data on the device.
7.8 Right to Lodge a Complaint
If you believe we have not handled your personal data properly, you have the right to lodge a complaint with a data protection supervisory authority. In Finland, this is:
Office of the Data Protection Ombudsman (Tietosuojavaltuutetun toimisto) Lintulahdenkuja 4, 00530 Helsinki, Finland Email: tietosuoja@tietosuoja.fi Website: https://tietosuoja.fi
If you reside in another EU/EEA country, you may also contact your local supervisory authority.
7.9 Automated Decision-Making
The App uses AI to generate workout programs, weight suggestions, session feedback, coach chat replies, and exercise modification suggestions based on your fitness profile and workout history. These are automated processes — no human reviews the AI output before it is shown to you. The AI does not make decisions that produce legal effects or similarly significant effects concerning you. You are always free to disregard AI suggestions and make your own choices about your workout. If you have concerns about an AI-generated recommendation, contact us at support@liftplanr.app.
8. Account Deletion Details
When you choose to delete your account, the following data is permanently deleted:
From our servers (Google Cloud Firestore):
- User profile document (name, email, subscription status)
- All workout session records
- All saved workout programs
- All AI usage counters
- Check-ins, workout comments, and coach-link records
From Firebase Authentication:
- Your authentication account and credentials
From Google Cloud Storage:
- If you were a coach, every video and image in your media library
From your device:
- The local database (SwiftData on iOS, Room on Android) — all profiles, programs, sessions, exercises
- All cached preferences and onboarding flags
- AI suggestion cache
9. Children's Privacy
You must be at least 16 years of age to use the App (see our Terms of Service). We do not knowingly collect personal information from anyone under 16. If we become aware that a person under 16 has provided us with personal information, we will take steps to delete that information promptly. Liftplanr Coach is for trainers aged 18 or over.
10. International Data Transfers
Your data is processed and stored in the European Union (Belgium). If you are located outside of the EU, your data will be transferred to and processed in the EU.
Some of our processors operate in the United States:
| Processor | What is transferred | Safeguard |
|---|---|---|
| Google (Gemini API) | Fitness data, chat text, first name (see Section 3) | EU-US Data Privacy Framework (Google is certified) and Google's Data Processing Addendum |
| RevenueCat | App user identifier, purchase receipts, subscription status, iOS attribution token | Standard Contractual Clauses |
| Stripe | Trainer billing details and identifiers | EU-US Data Privacy Framework and/or Standard Contractual Clauses |
| Resend | Email address, first name, message content | Standard Contractual Clauses |
We rely on the EU-US Data Privacy Framework, Google Cloud's Data Processing Addendum, and Standard Contractual Clauses for the lawful transfer and protection of your data. We have entered into data processing agreements with our service providers in accordance with GDPR Article 28. You may request a copy of the relevant safeguards by contacting us at support@liftplanr.app.
11. Third-Party Services
The App uses the following third-party services:
- Firebase Authentication — Google Privacy Policy
- Firebase Analytics — Google Privacy Policy (product-interaction events linked to your account identifier)
- Cloud Firestore — Google Cloud Terms
- Google Cloud Storage / Firebase Storage — Google Cloud Terms (coach media)
- Google Gemini API (AI features and Ask Otso) — Gemini API Terms
- Firebase Crashlytics — Google Privacy Policy (crash logs linked to your account identifier)
- Firebase Cloud Messaging — Google Privacy Policy (coach push notifications)
- RevenueCat (subscription management, install attribution exchange) — RevenueCat Privacy Policy
- Stripe (Coach subscription billing) — Stripe Privacy Policy
- Resend (transactional email delivery) — Resend Privacy Policy
- Apple AdServices (iOS only, App Store install attribution) — Apple Privacy Policy
- Apple App Store (iOS) / Google Play Billing (Android) — consumer subscription payment processing
- Apple HealthKit (iOS only) — Apple Privacy Policy (on-device only, with your permission)
- Health Connect by Android (Android only) — Google Privacy Policy (on-device only, with your permission)
- Sign in with Apple (iOS only) — Apple Privacy Policy
- Google Sign-In — Google Privacy Policy
We encourage you to review the privacy policies of these third-party services.
12. Changes to This Privacy Policy
What changed in this version (September 8, 2026): we now describe app analytics and crash reporting as linked to your account identifier rather than anonymous (Section 1.9); added the Ask Otso coach chat (Section 1.10), Liftplanr Coach data sharing with a human coach (Section 1.11), and Apple Search Ads attribution (Section 1.12); corrected Section 4.1 to say the local database relies on operating-system file encryption, not an app-level encryption layer; documented the Android backup exclusion (4.4) and coach media storage (4.5); replaced the single re-engagement email with the four lifecycle emails (2.1); and added Stripe, Resend, Google Cloud Storage and Apple AdServices to the processor and transfer lists.
We may update this Privacy Policy from time to time. If we make material changes, we will notify you by updating the "Last Updated" date at the top of this policy. We encourage you to review this Privacy Policy periodically.
13. Contact Us
If you have any questions, concerns, or requests regarding this Privacy Policy or your personal data, please contact us at:
Parcloud Oy Business ID (Y-tunnus): 3154332-3 Finland Email: support@liftplanr.app
Apple App Privacy
The following data types are collected by the App, as declared on the App Store:
| Category | Data type | Purpose | Linked to identity |
|---|---|---|---|
| Contact Info | Name | App Functionality | Yes |
| Contact Info | Email Address | App Functionality | Yes |
| Health & Fitness | Health (body weight, heart rate) | App Functionality | Yes |
| Health & Fitness | Fitness (workouts, active calories) | App Functionality | Yes |
| User Content | Other User Content (coach chat messages, weekly check-ins, workout comments, coach-uploaded media) | App Functionality | Yes |
| Identifiers | User ID | App Functionality | Yes |
| Purchases | Purchase History | App Functionality | Yes |
| Usage Data | Product Interaction | Analytics | Yes |
| Diagnostics | Crash Data | App Functionality | Yes |
All data is used for App Functionality and our own analytics only. No data is used for tracking, and the App collects no advertising identifier.
Google Play Data Safety
The following summarizes the data the Android app collects, as declared in the Google Play Data safety section:
| Data type | Collected | Shared | Purpose |
|---|---|---|---|
| Name | Yes | No | App functionality; account management |
| Email address | Yes | No | App functionality; account management |
| Health info (body weight) | Yes | No | App functionality |
| Fitness info (workouts, active calories) | Yes | No | App functionality |
| User content (coach chat messages, check-ins, workout comments) | Yes | No | App functionality |
| User IDs | Yes | No | App functionality |
| Purchase history | Yes | No | App functionality |
| App interactions | Yes | No | Analytics |
| Crash logs | Yes | No | App functionality (diagnostics) |
All collected data is encrypted in transit. We do not sell your data, and we do not share data with third parties for advertising. You can request that all of your data be deleted at any time from Settings > Delete Account in the App. The service providers listed in Section 5 process data only to operate the App.
Health Disclaimer
Liftplanr is a fitness tool and is not a substitute for professional medical advice. Please review our Health & Fitness Disclaimer for important information about using the App for exercise.
Summary
| Question | Answer |
|---|---|
| Do you sell my data? | No, never. |
| Do you show ads? | No. |
| Do you track me? | Not across other companies' apps or websites — no advertising identifier, no ATT prompt. Inside Liftplanr we do record product-interaction events and crash reports linked to your account, to see what works and what breaks. Website analytics only with your consent. |
| What AI sees my data? | Google Gemini — your fitness data, workout history, first name and whatever you type into Ask Otso. Never your email or user ID, and never used to train models. See Section 11. |
| Can my coach read my chats? | No. A linked coach sees your training, check-ins and comments — never your Ask Otso conversations, your email, or your health-app data. |
| Do you access health data? | Only with your permission, via Apple Health (iOS) or Health Connect (Android). Heart rate and calories stay on your device. Body weight syncs to our servers for AI features. |
| Where is my data stored? | On your device + EU (Belgium) cloud servers. AI, payments and email processors may process in the US under DPF or SCCs. |
| Can I delete everything? | Yes, instantly, from Settings > Delete Account. |