Privacy Policy for LIFFT
Last updated: October 2026
1. Overview
LIFFT is designed to be a minimalist, distraction-free training app.
It is built local-first: by default, your workouts, templates, and settings live on your device.
Some features go beyond your device when you choose to use them. Android billing also creates an anonymous profile automatically, as described in Section 3. Optional connected features include:
- Connecting with a coach or partner. When you pair with a coach, or share a live workout or a workout link, a small amount of data passes through our backend server (Supabase) to make the connection. See Sections 5.2 and 5.3.
- Exporting to Google Sheets. If you connect Google, your workouts are written to a spreadsheet in your own Google Drive. See Section 5.1.
- iCloud Backup. If you turn it on, a copy of your data is stored in your personal iCloud account. See Section 6.
- Android Backup. On Android, if you turn backup on or choose Back Up Now, LIFFT stores LIFFT backup files in its hidden application-data folder in your own Google Drive. See Sections 5.1 and 6.
- In-App Purchases. On Apple devices, purchases are processed directly through Apple’s StoreKit and App Store systems. On Android, purchases are processed by Google Play, and RevenueCat helps LIFFT manage access to purchased features. See Section 3.
- Answering how you heard about LIFFT. If you choose Send Answer, your answer is sent through Supabase to our team in Slack. See Section 5.6.
- Sending feedback. When you submit Send Feedback, your message and any image, reply email or diagnostics you choose to include are sent through Supabase to our team in Slack. See Section 5.5.
- Applying to LIFFT Spotter. Spotter is our research panel for working Trainers, and it lives on our website rather than in the app. If you fill in the form at lifft.app/spotter, the answers and contact details you enter are sent to us. Nothing sends them unless you submit that form. See Section 5.4.
We use optional discovery answers to understand where people hear about LIFFT. We do not run advertising or behavioral analytics, and we do not use attribution software or track you across apps or websites. On Android, RevenueCat provides purchase and subscription reporting only for billing and access to paid features. Where data does leave your device, we explain below what is sent, where it goes, how long it is kept, and how to delete it.
2. Information We Collect
Data that stays on your device by default
Unless you use one of the connected features below, this stays only on your device:
- Health and fitness data: logged workouts, including exercises, sets, reps, weights, notes, dates, and durations
- Templates and folders you create
- App settings, themes, fonts, and units
- Your local profile (name, username, optional email, optional photo)
Data you provide that may be shared when you use connected features
- Your name / first name — written into your Google Sheet and, when you pair with a coach, passed through our backend so your coach can identify you.
- Coach profile details (if you set up a coach profile): name, optional email address, optional phone number, Instagram, website, bio, certifications, and a profile photo. When you invite a client, these fields—including email and phone when present—are sent through Supabase and shown to the client you invite. LIFFT does not use phone numbers for automated SMS delivery or phone-number-based pairing. The invited client may choose to open Messages, Phone, or Mail from the profile card.
- Workout and fitness data — written to your Google Sheet if connected; included in optional backup if enabled; and uploaded to our backend when you share a workout or history or use a live paired session.
- Discovery answers: the source you select or type, a random report identifier and submission timing. No workout data, reply email, diagnostics or image is included. See Section 5.6.
- Feedback details: your category and message, an image if attached, an optional reply email, and diagnostics if enabled. Reports also include a random report identifier and submission timing. See Section 5.5.
- Spotter application details (only if you apply at lifft.app/spotter): your name, your email address, your Instagram handle if you give one, how many clients you currently train, optionally how long you have been training, and your written answers about how you deliver workouts and what you still handle over text. Your three consent choices are stored alongside them. Spotter never asks for health, medical, injury or body data. See Section 5.4.
- Backup data — depending on the features you use, an optional backup may include workouts, templates and folders, a local profile and profile photo, saved friends’ names, usernames, status information and avatars, custom exercises and favorites, app settings and customizations, coach or client and Google Sheets metadata, and functional identifiers. Apple backups include a device name and identifier. Android backups include a random installation identifier.
Data collected automatically
- On Apple devices, LIFFT registers with Apple for remote notifications used by CloudKit synchronization. The app receives the device token locally but does not send it to LIFFT’s servers.
- On Android, RevenueCat creates an anonymous App User ID and processes Google Play purchase history so LIFFT can determine which purchases and subscriptions are active. RevenueCat also provides purchase and subscription reporting. LIFFT does not send RevenueCat your profile email or phone number.
- When you use backend sharing, coach connections, or LIFFT LIVE, LIFFT and Supabase use random installation- or coach-scoped identifiers to route and secure those features. These are functional identifiers, not advertising identifiers.
- If you enable iCloud Backup, your device identifier and device name are stored inside your own private iCloud backup records.
We do not collect GPS or precise device location. On Android, RevenueCat derives and retains a country from SDK requests as described in Section 3; this is approximate location in our Google Play disclosures. We do not collect advertising identifiers, including Apple’s IDFA or the Android advertising ID, and we do not use data for advertising or cross-app tracking.
3. In-App Purchases
LIFFT uses Apple’s secure In-App Purchase system.
We do not receive or store your payment information — all transactions are handled by Apple.
For details on how Apple processes purchase data, visit: https://www.apple.com/legal/privacy/
LIFFT offers optional paid features through Apple’s In-App Purchase system, including LIFFT+ subscriptions billed monthly or annually and one-time color-pack purchases. LIFFT Custom and LIFFT+ Lifetime are not offered for new purchases in iOS version 1.2.0. Eligible new Monthly subscribers may receive a free trial; Annual has no introductory free trial. On Apple devices, StoreKit supplies verified transaction and entitlement information needed to determine which paid features are active. LIFFT does not receive your complete payment or billing details.
On Android, purchases are processed by Google Play. LIFFT uses RevenueCat as a billing service provider to manage access to purchased features. RevenueCat processes an anonymous App User ID and Google Play purchase history, including product, transaction, subscription, and entitlement status. Google Play processes your payment method; neither LIFFT nor RevenueCat receives your complete card or bank-account details.
RevenueCat is used for Android purchases. The current Apple app verifies its purchases directly through StoreKit.
Android 1.0 billing data
LIFFT Android 1.0 requires no LIFFT account and offers one-time colors rather than LIFFT Plus subscriptions. When the RevenueCat SDK connects, it creates an anonymous billing profile, including for installations that have not purchased anything. RevenueCat retains an anonymous App User ID and linked aliases, device locale and currency, first- and last-connection timestamps, and app, platform and SDK version information. After a purchase, it also retains store transaction references, purchase history and the entitlement state used to provide purchased features. RevenueCat provides purchase reporting; we do not use advertising identifiers or cross-app tracking.
RevenueCat uses the IP address of SDK API requests to estimate a country. It drops the raw IP after deriving that country and retains the last-seen country on the billing profile. This is separate from Google Play transaction country and device locale. This processing does not require GPS or a device-location permission. The retained IP-derived country is treated as approximate location in our Google Play disclosures; this is distinct from GPS or precise device location.
Manage or cancel a subscription through your Apple App Store or Google Play subscription settings. Refund requests are handled by the store that processed the purchase under that store’s policies.
Google Privacy Policy:
https://policies.google.com/privacy
RevenueCat Privacy Policy:
4. Sharing Features
LIFFT allows you to export images of workouts or templates.
When you share this content, it is handled entirely by your device and your chosen destination (Photos, Messages, etc.).
Shareable links. When you create a link to a workout, template, folder, or workout history, the underlying data is uploaded to our backend server (Supabase) so the link can be opened by whoever you send it to. Anyone who has the link can view that content until the link expires. These links and their data are automatically deleted from our servers after 24 hours (see Section 5.2). Images exported through the device’s sharing controls are handled by your device and the destination you choose. Images submitted through Send Feedback are uploaded separately as described in Section 5.5.
5. Third-Party Services
LIFFT does not use third-party advertising, behavioral analytics, attribution, or tracking software, and does not track you across other apps or websites. RevenueCat provides Android purchase entitlement management and subscription reporting, not behavioral or cross-app tracking. The third-party services we use are:
- Apple — direct StoreKit and App Store purchase processing, and optional iCloud/CloudKit backup and synchronization on Apple devices.
- Google — Google Play purchase processing, optional Google Sheets export and sharing, and optional storage in Google Drive’s hidden application-data folder on Android.
- RevenueCat — Android purchase-history processing, subscription reporting, and entitlement management.
- Supabase — our backend provider for temporary coach–client handoffs, share links, and LIFFT LIVE sessions described in Sections 5.2 and 5.3, Spotter applications described in Section 5.4, feedback records and attached images described in Section 5.5, and optional discovery answers described in Section 5.6.
- Slack — our internal team chat. Spotter applications and feedback submissions are delivered to LIFFT team channels for review. Feedback includes any reply email, diagnostics or image you choose to submit. Slack also receives optional discovery answers. See Sections 5.4, 5.5 and 5.6.
We do not sell your data to anyone.
5.1 Google Account Integration (Optional)
LIFFT may allow you to connect your Google account to export workout data to Google Sheets and, on Android, to use optional Backup & Restore.
If you choose to connect your Google account:
- The App will request permission to create and manage Google Sheets files in your Google Drive
- Workout-related data (such as exercises, sets, and logs) may be written to a spreadsheet in your Google Drive
- On Android, if you use Backup & Restore, the App may create and manage LIFFT backup files in its hidden application-data folder in your Google Drive
For Google Sheets, LIFFT requests https://www.googleapis.com/auth/drive.file. This permission allows LIFFT to create and manage the specific Drive files used with LIFFT; LIFFT uses it for the Google Sheet it creates and cannot browse unrelated files in your Drive.
On Android, LIFFT requests https://www.googleapis.com/auth/drive.appdata only when you use Backup & Restore. This permission allows LIFFT to see, create, update, and delete only LIFFT’s own files in Google Drive’s hidden application-data folder. Those files do not appear in your normal Drive file list and cannot be accessed by other Drive apps.
LIFFT’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. This applies to everything LIFFT receives through the two scopes it requests—https://www.googleapis.com/auth/drive.file and https://www.googleapis.com/auth/drive.appdata. We use that information only to provide and improve the Google Sheets export and Backup & Restore features you turned on. We do not transfer it to others except as needed to provide those features, and we never use it for advertising, never sell it, and never allow humans to read it except with your explicit permission, for security or legal reasons, or on data that has been aggregated and anonymised. The policy is at https://developers.google.com/terms/api-services-user-data-policy.
LIFFT does not request your Google account email, profile, contacts, or other identity information. Google sign-in tokens are stored only in secure storage on your device—Keychain on Apple devices and Android OS keystore-backed secure storage on Android—and are never sent to LIFFT’s backend servers.
How your sheet can be shared. When you use sharing or coaching features, LIFFT may:
- If you choose Share Link and confirm the warning, LIFFT applies a public, view-only permission (“anyone with the link can view”). Creating a Sheet alone does not make it public. Once you approve sharing, anyone who has the link can read that Sheet without signing in.
- Grant your coach edit access by email. You are shown a consent screen naming the coach’s email; if you approve, LIFFT shares the Sheet with that address as an editor, and Google sends a notification email containing an app-composed message with the client’s display name.
- You can remove a coach's access (Remove Coach), delete the sheet, or manage permissions directly in Google Drive.
All data transferred to Google is initiated by your action and stored within your Google account.
Your use of Google services is subject to Google’s Privacy Policy:
https://policies.google.com/privacy
5.2 Coach–Client Connections (Our Backend)
LIFFT lets a coach invite a client through a private link. To pass the connection between two devices, a small record is created on our backend server (provided by Supabase). Depending on who you are, this record can contain:
- The client's first name (typed by the coach when inviting).
- The coach's profile card, if the coach created one: name, email, phone number, Instagram, website, bio, certifications, and a profile photo.
- A coach identifier used to match the coach and client.
- The client's Google Sheet link, written back so the coach can find the client's sheet.
When present, the coach profile’s optional email address and optional phone number are transmitted through Supabase to the invited client as part of the currently shipping handoff.
How long we keep it. These records are temporary couriers. They are automatically deleted from our servers within 24 hours, and also as soon as the receiving device has saved the information locally — whichever comes first. After that, the connection lives only on the coach's and client's own devices. Anyone who obtains a coach invitation link can view the coach's contact card until the link expires.
Deletion. A coach can remove a client, and a client can remove a coach, at any time in the app, which clears the local copy on that device and stops sheet access. Because the backend records expire automatically, there is no long-term server copy to request deletion of. We do not use this information for advertising, and we do not sell it.
5.3 Live Workout Pairing (Optional, Real-Time)
If you start a live paired session ("LIFFT LIVE") and share the link, your in-progress workout — workout name, exercises, sets, reps, weights, completion, notes, and your display name — is uploaded to our backend server (Supabase) and updated continuously so your partner can follow along. Pairing is shared editing: the person you pair with can view and modify the sets, reps, weights, and notes in that session, so only pair with people you trust. Active sessions are deleted from our servers after 24 hours of inactivity, and completed sessions within 1 hour of ending.
5.4 LIFFT Spotter (Website Application)
LIFFT Spotter is a small research panel of working personal Trainers. Applying is entirely optional, it happens on our website rather than in the app, and nothing about it is connected to your LIFFT account, purchases, or workout data.
What the form collects
- Your name and email address, so we can reach you.
- Your Instagram handle, if you choose to give one.
- Screening answers: whether you currently train clients, how many clients you train this month, and optionally how long you have been training professionally.
- Written answers about how you deliver workouts to clients today and what you still handle over text.
- Your consent choices, recorded separately: that your answers may be used as private research, that we may contact you up to twice a month, and — optional and off unless you tick it — that we may quote you publicly by name.
What the form never asks for
Spotter asks how you work, never about a body. The form has no health, medical, injury, diagnosis, medication, body-weight, body-composition, measurement, progress-photo or date-of-birth field, and our server rejects any submission that tries to send one. It also does not collect your clients' information.
How we use it
Your answers are private research. We read them to understand how Trainers actually work, and we may contact you about research questions or conversations up to twice a month. You can tell us to stop at any time.
Being quoted publicly by name is a separate, optional consent that is off by default. Consenting to research is never treated as consenting to attribution, which is why the two are recorded as separate facts. If you leave the attribution box unticked, your answers stay private research.
Who sees it
The LIFFT team. Applications are stored in our backend (Supabase) and are not readable by anyone using the app or the website — there is no path for a visitor to read an application, including their own. A notification is also posted to a private channel in our internal Slack so we see new applications, which means the name, Instagram handle and written answers on an application are visible to our team in Slack as well. We do not use any of it for advertising, and we do not sell it.
How long we keep it
Unlike the connection, share and live-session records above, a Spotter application is not a temporary courier and is not deleted on a timer. We keep it while you are part of Spotter, or until the Spotter program ends, so that we can contact you and so that your consent choices stay on file.
How to withdraw
Email us at contactus@lifft.app and we will delete your application and stop contacting you. You do not have to give a reason.
5.5 Send Feedback
When you submit Send Feedback, your category and message are sent to Supabase and delivered to our team in Slack for support and troubleshooting. You may also attach one image and provide an email address if you want a reply. Your submission may identify you or someone else through its contents.
Include Diagnostics is optional and off by default for each new submission. If enabled, it includes your app version, build number, iOS version, device model and locale (language/region setting). Reports also include a random report identifier and submission timing. Normal network and hosting processing occurs whether or not you include diagnostics.
An image you choose to attach is uploaded to private Supabase storage and separately copied to Slack. Supabase stores the feedback record, and Slack holds its own copies of the submitted content.
Feedback records and images do not currently have a verified automatic expiry and are not covered by the 24-hour expiry for sharing features. Deleting one copy does not automatically delete copies held by other providers. We do not promise a fixed deletion period for feedback.
Deleting LIFFT or using Delete All Data does not remove previously submitted feedback. To request removal, contact contactus@lifft.app with enough information to identify your submission.
If you choose the email alternative, your email app and the sending and receiving email providers process the message and any attachment you send.
5.6 How You Heard About LIFFT (Optional)
After your third completed workout, LIFFT may ask where you heard about us. You can skip the question. Choosing Send Answer sends your selected source or typed answer through Supabase to our team in Slack. We use these answers to understand where people discover LIFFT and where to share information about the app.
The submission includes a random report identifier and submission timing. It does not include your workout data, a reply email, diagnostics or an image. Normal network and hosting processing still occurs. Free text may identify you if you choose to include personal information. Previously saved local-only answers are not uploaded.
If sending is interrupted, the answer may remain on your device and retry when the app is active. Supabase and Slack retain separate copies after delivery. These answers have no verified automatic expiry and are not covered by the sharing-feature deletion schedule. Deleting LIFFT or its local data does not remove a submitted answer. Contact contactus@lifft.app with enough information to identify it if you want to request removal.
6. Optional Backup and Sync
If enabled, your data will be stored in your personal iCloud account managed by Apple.
LIFFT does not receive a copy of the backup on its own servers. The LIFFT app accesses it through CloudKit on your authenticated Apple device to provide backup and restore.
iCloud Backup is off by default. When enabled, the data stored in your private CloudKit database can include your LIFFT app data, including workout history; templates and folders; your local profile; saved friends, including names, usernames, status information, avatars, and live-state information; custom exercises, usage, and favorites; app settings and customizations; coach-side client and shared-link information; Google Sheets metadata; tags; cached identifiers for unlocked items; and your device name and identifier.
Turning off iCloud Backup or deleting LIFFT does not remove existing CloudKit records. LIFFT can delete individual manual snapshots from its backup-history screen. To remove all LIFFT CloudKit data, use iOS Settings → your name → iCloud → Manage Account Storage.
Android backup is off by default. If you enable it or choose Back Up Now, LIFFT stores a current backup and manual snapshots as JSON files in LIFFT’s hidden application-data folder in your Google Drive.
Those files can include workout and fitness history; templates and folders; your local profile, including an optional email address and photo; saved friends’ names, usernames, status information, and photos; custom exercises, favorites, and usage; app customization; coach roster and folder-link data, including any client profile already stored in the roster; Google Sheets metadata; preferences and tags; a random installation identifier; and a non-authoritative cache of some unlocked items. They do not include your complete payment-card or bank-account details.
The backup files travel directly between LIFFT on your device and your Google account and are not sent to LIFFT’s backend. Turning off backup, choosing Delete All Data, disconnecting Google, or deleting LIFFT from your device does not ask Google to delete existing backup files. To delete them, use Google Drive Settings → Manage Apps → LIFFT → Options → Delete hidden app data.
7. Device Permissions
LIFFT requests device permissions only when needed for the related feature. You can review or change them in your device settings:
- Notifications — to alert you when a rest timer finishes. On Apple devices, optional iCloud Backup also uses Apple’s silent background notifications to keep backup data synchronized.
- Camera — to scan a gym membership barcode or capture a photo or video for a workout Story.
- Photos — to choose a profile photo, display a recent photo or video in the Story picker, and save workout images or Story media.
- Microphone — to record sound when you choose to record a Story video with audio.
Camera frames and Story recordings are processed on your device. LIFFT does not automatically upload Story media to its backend. You can save media or share it through the device’s sharing controls. Separately, an image you attach and submit through Send Feedback is uploaded as described in Section 5.5.
8. Data Security
Because LIFFT stores data locally, the security of your information depends on the security of your device.
We recommend enabling a passcode, keeping your device’s operating system updated, and using its built-in privacy protections.
9. Your Rights
Where your data lives determines how to remove it:
- On your device: Delete individual items or use the available deletion controls. In the current Apple app, Delete All Data clears workout history, templates, pinned templates, user-created exercises, and favorites; it does not clear every other local profile, setting, or connection. On Android, Delete All Data clears LIFFT’s on-device app data. Neither platform’s Delete All Data action removes the cloud or provider records below.
- In your Google Sheet: Use Delete Sheet in LIFFT, or delete the file or change its permissions in Google Drive. Disconnecting Google stops LIFFT’s future access but does not ask Google to delete the Sheet.
- In Apple iCloud or CloudKit backup: Delete individual manual snapshots through LIFFT’s backup-history screen. Use iOS Settings → your name → iCloud → Manage Account Storage to remove all LIFFT CloudKit data.
- In Android backup: Delete LIFFT’s hidden app data through Google Drive Settings → Manage Apps → LIFFT → Options → Delete hidden app data. Delete All Data in LIFFT and Disconnect Google do not ask Google to delete these backup files.
- In Google Play and RevenueCat: Delete All Data does not erase purchase or subscription records maintained by those providers under their policies.
- A coach's access to your sheet: Use Remove Coach, or manage sharing in Google Drive.
- On our backend (Supabase): Connection, share, and live-session records are automatically deleted within 24 hours (live sessions within 1 hour of completion). Spotter applications, feedback submissions and discovery answers are not covered by that expiry. See Sections 5.4, 5.5 and 5.6.
- Your feedback and discovery answers: Deleting the app or its local data does not delete submitted feedback, discovery answers, uploaded images or Slack copies. Contact contactus@lifft.app to request removal. See Sections 5.5 and 5.6.
- Your Spotter application: Email us and we will delete the application and stop contacting you. See Section 5.4.
- In iCloud Backup: See Section 6; deleting the app does not remove it.
Requests about RevenueCat billing-profile data
Contact contactus@lifft.app to ask about or request deletion of RevenueCat billing-profile data. We need enough information to identify the correct record, such as a valid Google Play transaction reference for a purchaser or the RevenueCat App User ID from the device. Android 1.0 does not display that anonymous ID. For a non-purchasing installation without the ID, we may be unable to locate its RevenueCat record reliably; we will explain that limitation rather than claim deletion occurred.
For an identified record, RevenueCat's customer-deletion operation removes its customer, linked IDs and aliases, and the purchase and entitlement records RevenueCat holds for that customer. Processing is asynchronous. It does not cancel or erase the Google Play purchase or Google's own records. Later SDK activity, restoration or purchase can recreate billing-profile or transaction information. Local Delete All Data does not request deletion of provider records.
RevenueCat says logs, backups, archives and other historical systems can have separate retention and deletion timelines. It has not supplied exact categories and periods for those systems. We do not promise immediate removal from every historical system or a fixed provider deadline that has not been established. Google's own transaction-record retention is separate.
If you have a request about your data that these controls don't cover, contact us at contactus@lifft.app and we will help.
If you choose to use third-party integrations such as Google, you may manage or delete your data directly through those services.
10. Children’s Privacy
LIFFT is intended for users aged 13 and older and is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided us with personal information, contact us at contactus@lifft.app and we will delete it.
11. Changes to This Policy
We may update this Privacy Policy if our features change in ways that affect privacy.
If so, we will revise the date at the top of this page.
12. Contact Us
If you have any questions or concerns about this Privacy Policy, please contact us at:
contactus@lifft.app