Privacy Policy URL: https://www.rirlift.com/privacy/
Privacy Policy
RIRLift is a local-first training log for iPhone, Apple Watch, and Android. This policy explains what information the apps and website handle, why it is used, and which controls are available to you. The sections on iCloud, Apple Health, App Tracking Transparency, Sentry, and Google Analytics for Firebase describe the iPhone and Apple Watch app; what the Android app does is described in Android app and Health Connect.
Effective date: November 18, 2026
Summary
RIRLift does not sell personal information and does not include third-party advertising. The app stores routines, exercises, sets, RIR, notes, workout history, and weekly volume locally first on your devices. If iCloud is available, the app backs up your training log and training preferences to your private iCloud database so they can be restored after reinstall. Network services are also used for purchase status, support requests, crash, error, and performance diagnostics, explicit product analytics, selected logs, measurement of RIRLift's own ad campaigns, connected-AI features you explicitly enable, Friends if you set it up, and backend operations. The web planner at app.rirlift.com has no accounts and stores your drafts in your own browser. The Android app works the same way without iCloud, Apple Health, or Sentry; it uses Android's encrypted backup with an encrypted copy on RIRLift's servers that only your phone can read, optional Health Connect, and Google Play billing, and both its in-app analytics and its advertising measurement can be turned off. You can delete your data in the app at any time (see Delete your data).
Workout data on iPhone and Apple Watch
Your training log is stored on your iPhone and Apple Watch. iPhone and Apple Watch sync data with each other so planned routines, active workouts, completed sessions, support ID, and purchase access can stay consistent across devices. If iCloud is available, RIRLift backs up routines, custom exercises, full workout history, training units, weekly hard-set target, and muscle-map model preference to your private iCloud database. The current app version does not upload your full training log to a RIRLift account-sync backend. Product analytics may include summary workout metrics such as duration, exercise count, set count, and whether a workout used substitutions, but not your exercise names, notes, or full set-by-set log.
Apple Health
If you grant permission, RIRLift can save completed workouts to Apple Health. During Apple Watch workouts, RIRLift can read heart rate and active energy recorded by Apple Watch for the workout session and store a workout heart-rate summary in your local training log. On iPhone, RIRLift can read matching workout records when you choose to delete a workout from both RIRLift and Apple Health. Limited HealthKit diagnostic metadata, such as a RIRLift workout ID, HealthKit source bundle identifier, operation status, and error messages, may be sent to logs to troubleshoot Health integration issues. Apple Health permissions are controlled by iOS and watchOS settings, and Health data is not used for advertising or tracking.
Android app
The Android app stores routines, exercises, sets, RIR, notes, workout history, body measurements, and settings on your phone. It has no sign-up, no email or password, and no RIRLift account, and it does not sync your training log between devices. It does not use iCloud, Apple Health, Sentry, Google Analytics for Firebase, or ad-serving SDKs. It uses Android's advertising ID only for the advertising measurement described below.
Backup. If Android backup is on for your Google account, Android includes one RIRLift backup file in its device backup: your training log, settings, and, only if you turn on that option in the app, your Coach conversations and memories. Android sends it to Google's cloud only when the backup can be end-to-end encrypted with your screen lock, and also uses it for device-to-device transfer. RIRLift cannot read this backup; it is managed by Android and your Google account. Your analytics and attribution choices are included, so turning analytics off carries over to a restored or new phone. Purchase state, Health Connect permissions, and Coach credentials are not included. You can also export a .rirlift backup or, with Pro, a CSV file yourself; those files go only where you send them.
Server backup. Because Android backs up only from time to time, the app also keeps an encrypted copy of that same backup file on RIRLift's servers (Cloudflare), so a reinstall or a new phone that restores your Android backup also gets back the workouts logged since Android last backed up. The file is encrypted on your phone before it is sent, with a key created on your phone that travels only inside your Android backup; RIRLift never has the key and cannot read the copy. Our servers keep the latest two versions, a random identifier derived from that key, their size and the times they were uploaded or read, and, for rate limiting, the connecting IP address while a request is handled. Delete your data in the app erases the server copy first. A copy that is neither updated nor read for 365 days is deleted automatically.
Purchases. RIRLift Pro is sold through Google Play billing and managed by RevenueCat. RevenueCat assigns the app an anonymous app user ID; its automatic collection of device identifiers is turned off. RevenueCat and RIRLift's backend receive the purchase records described under Purchases. For the paid Coach allowance, RIRLift's server checks the subscription's current status with Google Play and stores a one-way hash of the purchase token, not the token itself, so the allowance follows the subscription across renewals, reinstalls, and restores.
Referral codes. If you enter a creator's referral code, the app sends it to InfluTo (influ.to), which checks the code and credits the creator when you subscribe. If the code is a free access code, InfluTo records the grant and adds it to your RevenueCat customer, which unlocks Pro. Nothing is sent to InfluTo unless you enter a code. With the code, the app sends its version and your RevenueCat app user ID (a random ID, or your anonymous Coach account ID once Coach has been used), and InfluTo sees your IP address as any server does. The code is also kept with your purchase records at RevenueCat, which reports your subscription's purchases, renewals and refunds to InfluTo so the creator is paid. InfluTo does not receive advertising identifiers and does not track you across other apps or websites. To have InfluTo delete this data, contact us or InfluTo at hello@influ.to.
Coach and access codes. Coach works as described under Coach. On Android, the app signs in with Firebase Anonymous Authentication when you first use Coach or redeem an access code, and Firebase App Check uses Google Play Integrity to confirm that requests come from RIRLift installed from Google Play. Coach requests also carry a random ID created by the app for that installation. Each Coach request sends your message, up to the last 12 messages of that conversation, the Coach memories that apply, your language and time zone, and the training records the request needs. If you report a Coach answer, that answer is sent for review and kept for 30 days.
Support and diagnostics. Send feedback sends the topic, your message, your reply email, and your support ID, with the app version, device model, Android version, and language. The app keeps a local crash and exit report on your phone; it is attached to a support request only if you turn that on in the form. There is no automatic crash reporting on Android.
Analytics and advertising measurement. Product analytics (PostHog EU Cloud) is on by default, as in the iPhone app, and you can turn it off in Settings › Sharing & export › Privacy choices at any time. Analytics sends only a fixed list of app events, such as app opened, onboarding completed, or paywall opened, with the app version; it never includes workouts, health data, or Coach conversations, and screen capture, session replay, and person profiles are disabled. AppsFlyer measures which ads brought people to RIRLift: it receives app installs and opens, trial starts, purchases, and a return to the app, with Android's advertising ID, and shares them with the advertising partners described under Advertising measurement. The Android ID, app set ID, and network operator details are not collected. In the European Economic Area, the United Kingdom, and Switzerland, AppsFlyer runs only if you allow it when the app asks, once, after onboarding, and that consent covers measurement only, not personalized advertising; elsewhere it is on by default. You can turn it off in the same Privacy choices screen, and you can reset or delete your advertising ID in Android's settings (Privacy › Ads, or Google › Ads, depending on your phone). Turning either off stops it on your phone; events already sent stay with the provider under the retention described below. Separately from these choices, RIRLift's backend records the purchase-confirmation event described under Purchases.
Other connections. Exercise demonstration videos stream from media.rirlift.com. Google Play is used to show the rating sheet and to check for app updates. Sharing a workout card goes through Android's share sheet or, if you choose it, to the Instagram app on your phone.
Health Connect (Android)
Health Connect is optional and off until you connect it, during onboarding or in Settings › Devices & sensors › Health Connect, and grant permissions in Android's Health Connect screen. RIRLift requests only these permissions:
- Write exercise: when you finish a workout, RIRLift saves it to Health Connect as an exercise session with its title, activity type, start time, and end time, and, while connected, updates or removes that session when you edit or delete the workout in RIRLift. Sets, loads, and notes are not written.
- Write weight: body weight you log in RIRLift is saved to Health Connect and, while connected, removed from it if you delete that entry in RIRLift.
- Read weight: RIRLift reads body-weight records from the last 30 days that other apps saved to Health Connect, to show your body-weight log and trend and to calculate the effective load of bodyweight and assisted exercises.
Imported body weight is stored with your training data on your phone and included in your own backups and exports. It reaches RIRLift's servers only when you use Coach and a request needs your training records, for example as the effective load of an assisted pull-up. Data from Health Connect is never used for advertising, never sold, never shared with data brokers, and never used to train AI models. Disconnecting Health Connect in RIRLift revokes RIRLift's permissions and removes the imported body weight from RIRLift; records already saved in Health Connect stay there for you to manage. You can also revoke each permission in Android's Health Connect settings.
RIRLift's use of information received from Health Connect adheres to the Health Connect Permissions policy, including the Limited Use requirements.
Connected AI, Coach, and ChatGPT plugins
RIRLift can connect your training log to an AI service you choose, such as Claude or ChatGPT. This user-chosen connection is off by default. When you connect one, RIRLift uploads a replaceable training snapshot to its Cloudflare backend and binds access to a revocable grant for this installation. The snapshot can include your app version, unit and reply-language preferences, current program and routines; recent workout dates, duration, routine names, exercises, sets, reps, load, bodyweight, timed-work duration, and RIR; and derived summaries such as weighted muscle volume, estimated strength trends, effort accuracy, consistency, personal records, and modeled muscle freshness. It does not include your name, email, workout notes, heart rate, or other Apple Health data.
The connected service receives only the parts of that snapshot needed when you ask it to use RIRLift. Its handling of that copy is governed by your agreement with that service. If you ask the service to send a program to RIRLift, RIRLift stores the proposed program as a pending draft for you to review; it does not become part of your training until you approve it in the app. Pending drafts expire after 30 days, and resolved or expired draft records are removed later as part of routine cleanup.
A new snapshot replaces the previous one rather than creating a server-side history. Disconnecting an AI or unpairing a browser revokes that connection's access and removes its pending drafts. RIRLift stops uploading and deletes the snapshot after you have disconnected every AI and unpaired every browser that used it. You can manage both connections from the app at any time.
Coach is RIRLift's built-in AI feature and is separate from those user-chosen connections. When you send a message to Coach, RIRLift sends that message and the training context selected for the request through RIRLift's service to Google Vertex AI. Depending on where you opened Coach and what you asked, that context can include relevant routines, recent workouts, exercise progress, training volume, recovery, the current or completed workout, and Coach preferences you saved.
Your message is also processed by TypeSafe (api.typesafe.ai), a second AI service RIRLift uses to decide which of your training records a reply needs. TypeSafe receives your message and the screen you opened Coach from; it does not receive your training records or the reply. TypeSafe does not train on this data. It retains it only as long as needed to process the request under its data-processing terms, and it is based in the United States, so that data is transferred outside the European Economic Area under the safeguards in those terms.
Coach conversations, confirmed memories, session feedback, and accepted-change review records are stored locally. After you accept the Coach disclosure, these records also participate in your private iCloud backup when it is available. Coach archives are separated by iCloud account. Unsent drafts and pending request credentials remain on the device. You can inspect and remove Coach records in the app; deletion records prevent an older iCloud copy from restoring removed conversations or memories. RIRLift's backend temporarily stores the request, selected tool results, and response to support interrupted requests and checked delivery, to review the quality of Coach replies, and to diagnose requests that fail or are cancelled. This content expires no later than 24 hours after the request begins, including retries. An hourly cleanup removes expired content; longer-lived quota records contain usage metadata rather than conversation or training content. It also stores authentication, operation, purchase-access, and usage metadata needed to verify access, prevent duplicate or concurrent requests, and enforce usage limits. Coach analytics can record events such as a request, completion, failure, cancellation, or proposal action, together with technical IDs, mode, outcome, and error code; raw chat messages and assistant responses are not sent in this telemetry. Firebase Anonymous Authentication provides an anonymous account identity, and Firebase App Check verifies that requests originate from the app. Existing purchases and RevenueCat identities remain unchanged; for the hosted Coach allowance, the server separately verifies Apple's signed purchase data and current status.
Friends
Friends lets you see the training of people you add, on iPhone and Android. It is off until you set it up by choosing a display name, and nothing is sent before then. Your Friends identity is a random key created on your phone and kept in your iCloud Keychain on iPhone or in your Android backup on Android; RIRLift's servers (Cloudflare) store only a one-way hash of a token derived from it. It is not linked to your Coach sign-in, your purchases, or your analytics ID. There is no public profile, no search, and no chat.
What is sent. Once Friends is set up, the app sends the display name you chose, your platform, weekly session target, first day of the week, time zone, the number of sessions you logged in the last four weeks, and your notification switches; a training summary (workouts per day and hard sets this week, your week streak, total workouts, and the day of your last workout); session and hard-set counts for each of the last 31 days; and, for each workout you finish, a card with its routine name, duration, sets, hard sets, volume, sets per muscle group, and up to three personal records. Personal records on cards, and your best lifts on built-in exercises, are sent only while Share lifts is on. While Show when I'm training is on, the app also sends that a workout is in progress, with its routine name and current exercise. Cheers, friend requests, invites, streaks, challenges (including the challenge name you type), blocks, and reports are stored on RIRLift's servers so they work; blocks and reports keep the other person's display name, and a report carries a fixed reason, without free text. The server also notes which days of the past week you opened Friends. Workout notes, set-by-set logs, heart rate, and Health data are not sent.
Who sees it. Only friends you have accepted see your week, workout cards, training status, and streaks, and personal records and lift bests are shown only to friends who also share theirs. A friend request shows only your display name. People in a challenge with you who are not your friends see your display name and your challenge total. Anyone who enters your friend code or opens your invite link in the app sees your display name; the invite web page shows only its first word and, if you chose to show it on that invite, your current week's progress. Friends notifications carry display names and numbers, never routine, workout, or challenge names. They are delivered through Firebase Cloud Messaging and, on iPhone, Apple Push Notification service; your device's push token is stored encrypted.
Other uses. Friends data is not used for advertising and is not shared with advertising partners. RIRLift's backend sends product analytics only daily totals that identify nobody and, for each report, its reason. The app's product analytics also records Friends actions such as sending a cheer or joining a challenge, with counts but no names or workout content (on Android, only if you turned analytics on). Reports are read by RIRLift to deal with abuse. Your IP address is used to limit abuse and is kept in rate-limit counters for up to two days. Scanning a friend's QR code uses the camera on your phone only; no images are sent.
Retention and leaving. Daily counts, workout cards, and cheers are deleted after 90 days, training status after at most three hours, reports after 90 days, invite links when they expire, and challenges about a month after they end. A Friends profile that has not been used for a year is erased with everything it holds. Leave Friends, at the bottom of the Friends screen, erases your profile, friendships, cards, daily counts, cheers, training status, lift bests, streaks, blocks, reports, invites, and push tokens at once. In a challenge others are still in, your total stays as an anonymous former member, and a challenge you created stays with them under its name.
Purchases
RevenueCat handles purchase, restore, entitlement, and paywall state for RIRLift Pro, through the App Store on iPhone and Google Play on Android. On iPhone, RIRLift uses a local device ID as the RevenueCat app user ID so your Pro access can be restored and synced. The backend also stores RevenueCat webhook events and entitlement projections, including app user ID, product ID, environment, purchase dates, renewal and expiration dates where applicable, and event identifiers, to reconcile your purchase or subscription status. When RevenueCat notifies the backend that your access changed, the backend also records a purchase-confirmation event to RIRLift's own product analytics; that event carries the app user ID, product ID, environment, entitlement, and those dates, and no training data.
Support requests
When you submit the support form, RIRLift stores the topic, reply email, optional support ID, message, source, user agent, ticket status, and timestamps. This information is used to answer the request, diagnose reliability issues, and protect the support form from abuse.
Android waitlist
When you join the Android waitlist, RIRLift stores your email address, the page you signed up from, the country Cloudflare reports for the request, your browser's user agent, and the time. The address is used once, to tell you the Android app is available, and the rest to read where demand comes from and protect the form from abuse.
Analytics and crash reporting
RIRLift uses PostHog EU Cloud for explicit product analytics, selected logs, and handled error reporting. The app identifies analytics with a generated local device or support ID and basic entitlement status. The app disables broad screen-view capture, element autocapture, and session replay. Events focus on activation, summary workout completion metrics, watch sync, paywall views, purchases, restores, and reliability. RIRLift also uses Sentry for crash, error, and performance diagnostics.
The rirlift.com website measures how its pages are used, in PostHog EU Cloud, without cookies and without storing anything on your device. Our server records each page request and App Store button click, and, when you submit a calculator, the values you entered rounded (weights and bodyweight to the nearest 2.5, height to 5 cm or 2 inches) with the result it showed. A script on the page records page views, how far you scroll and how long you stay, which links, buttons and form controls you use (never what you type), where on the page you click, video plays, and text you copy from the page. Each event records the page, the referring site, any campaign tags in the link, your country and time zone, and your device type; any other part of a link is removed first. To count unique visitors, PostHog combines your IP address and browser user-agent with a random value that is replaced every day and deleted within a few days, and discards the IP address and user-agent before storing the event. The result identifies a visit for at most one day and cannot be linked to you or to later visits.
Advertising measurement
RIRLift uses Google Analytics for Firebase and AppsFlyer to measure its own advertising campaigns. Firebase receives app start-up events and trial, purchase, and return events linked to a pseudonymous app-instance identifier, with technical context such as app version, device model, operating system, language, and approximate region. RIRLift's backend also sends Google purchase events with the product identifier, actual amount, and currency from RevenueCat purchase records. AppsFlyer receives install, trial, purchase, and return events; the trial and purchase events sent by the app contain a product identifier, without a price. These services do not receive your training log or Apple Health data.
AppsFlyer shares advertising-measurement events with configured advertising partners. For ChatGPT ads, only installs attributed to OpenAI are reported to OpenAI, with AppsFlyer's Advanced Privacy enabled and advanced matching disabled. Direct App Store attribution links record the ad engagement with AppsFlyer and use OpenAI's ad click reference to match the install to the ad. This integration does not send workout data, Apple Health data, your name, or your email address to OpenAI.
RIRLift can request Apple's App Tracking Transparency permission after onboarding. If you allow tracking, Firebase and AppsFlyer can use Apple's advertising identifier (IDFA) for advertising measurement. You can change that permission in iOS Settings. Attribution may also use Apple's privacy-preserving reporting or other attribution methods supported by the measurement provider. Apple's own attribution API tells RIRLift which App Store campaign, ad group, or keyword an install came from; those campaign identifiers are stored with the app's product analytics.
On Android, AppsFlyer uses Android's advertising ID and Google Play's install referrer, including Meta's install referrer when the Facebook or Instagram app is installed, as described under Android app.
Apple may also send advertising networks, including Google, Reddit, and Meta, SKAdNetwork install postbacks. Apple prepares, signs, and delays these reports and withholds details below its privacy thresholds. These postbacks contain no name, email address, device identifier, or advertising identifier.
Web planner
The web planner at app.rirlift.com lets you build a training program in a browser and send it to the app. It has no accounts and no sign-in. Programs you build are held in your browser's local storage on your own device. When you choose to send a program to your phone, the program itself may be stored briefly on RIRLift servers so the phone can fetch it: this holds the program content only, is not linked to you or to any device or account identifier, and is deleted automatically after a day. Nothing is stored server-side until you ask to send a program, and your training log is never uploaded by the planner. The planner writes programs to the app; it never reads or writes your workouts, sets, or records.
The planner uses PostHog EU Cloud for anonymous usage measurement, configured without cookies and without persistent identifiers, so visits cannot be linked to each other or to you across days. Events record only how the planner itself is used, such as that a program was built or a delivery method was chosen. Program names, routine names, and exercise selections are not sent to analytics.
Shared program pages
The planner can publish a program to a public page at www.rirlift.com/p/…. This is the one place where content you write becomes readable by anyone, so it is worth being precise about it. Publishing is never automatic: it happens only when you press the share button, and the planner warns you first.
A published page holds the program you wrote — its name, the names of your training days, the exercises, and any notes you added. Do not put other people's names or health details in those fields if you intend to share the page. The page holds nothing else: no account, no device identifier, no IP address, and no part of your training log. The page address is a long random value that is not listed anywhere and is not guessable, and search engines are told not to index it unless you opt in when you publish.
You can delete a published page at any time from the planner in the browser you created it in, which keeps the delete key for you; the key is also shown once at creation so you can keep it elsewhere. Deleting removes the page and its record immediately, though a copy already held by a content delivery cache can remain readable for up to five minutes. A page that nobody opens for twelve months is removed automatically. If a page carries something that should not be public, report it with the form at the bottom of the page; reports go to the same inbox as other support requests and are read by a person.
Sharing and processors
RIRLift uses service providers only to operate the app and website: Apple platforms and Apple Health, Google (Google Play billing, Play Integrity, Firebase Anonymous Authentication, and Firebase App Check; Health Connect stores its data on your phone under Android's control), Apple iCloud for private backup and restore, RevenueCat for purchases, PostHog EU Cloud for analytics and logs, Sentry for crash, error, and performance diagnostics, Google (Google Analytics for Firebase, and Google Ads), AppsFlyer, and OpenAI for measuring RIRLift's own advertising campaigns, Google Vertex AI and TypeSafe for Coach as described above, Google Firebase Cloud Messaging and Apple Push Notification service for Friends notifications, and Cloudflare for hosting, backend services, Android's encrypted server backup, connected-AI snapshots, program drafts, Friends, and support-ticket storage. When you connect an AI service, Anthropic or OpenAI receives the requested training data under your agreement with that service. This user-chosen AI connection is separate from the advertising measurement described above. Separately from those service providers, the advertising networks described above — Google, Reddit, and Meta — can receive Apple's SKAdNetwork postbacks for RIRLift's own campaigns. When they do, they act on their own behalf rather than as RIRLift's service providers, because the postback is sent by Apple and is used by the network to measure its own advertising. Those providers are based in the United States, so the advertising-measurement data described above is transferred outside the European Economic Area under the safeguards set out in each provider's own data-processing and advertising terms. RIRLift does not sell your data. The only data shared with an advertising network is the measurement described above, for RIRLift's own campaigns; your training log and Apple Health data are not shared for advertising.
Retention and controls
- Training data remains on your devices until you delete it in the app or remove the app data.
- Private iCloud backups are managed through the iCloud account and app data controls on your Apple devices.
- Apple Health access can be changed in iOS and watchOS Health permissions.
- Support requests are kept as long as needed to respond, investigate issues, prevent abuse, or satisfy legal obligations.
- Purchase and backend operational records are kept as needed to provide access, restore purchases, and maintain auditability.
- Analytics, logs, and diagnostics are kept as needed to understand app use, troubleshoot reliability, and operate the service.
- Advertising-measurement data is retained under the applicable Google, AppsFlyer, and OpenAI retention settings and terms. Google Analytics events use the retention setting configured for RIRLift's property.
- App tracking permission can be changed in iOS Settings under Privacy & Security → Tracking.
- On Android, analytics and attribution can be turned off in Settings › Sharing & export › Privacy choices, Health Connect access in Android's Health Connect settings, and Android backup in your phone's Google backup settings.
- Android's encrypted server backup keeps the latest two versions and is deleted by Delete your data, or automatically when it has been neither updated nor read for 365 days.
- On Android, Delete your data in the app erases your training, Coach, and Friends data; what it removes, what is kept, and how to ask us to delete the rest are on the Delete your data page.
- Friends data is kept as described under Friends and erased at once by Leave Friends on iPhone and Android.
- Programs you build in the web planner stay in your browser until you clear them; a program sent to your phone is deleted from RIRLift servers automatically after a day.
- A connected-AI snapshot replaces the prior snapshot and is deleted after you disconnect every AI and unpair every browser that used it; pending AI program drafts expire after 30 days.
Children
RIRLift is not directed to children under 13. If you believe a child has submitted personal information through the support form, contact support so it can be reviewed and removed where appropriate.
Changes
This policy may be updated as RIRLift changes. Material updates will be posted on this page with a new effective date.
Contact
RIRLift is provided by DATAFINITY AB. Use the support page for privacy questions, data questions, purchase help, accessibility, or account support, or email contact@rirlift.com.