← GoLightWeight

Privacy Policy

Last updated: November 16, 2026

1. Information We Process

For guests, workout data, routines, settings, and records stay on the device. Information you provide or choose to connect—such as a display name, optional body weight, Apple or Google account details, synced records, purchase status, or body weight you accept from Apple Health or Health Connect—is processed when you use the corresponding feature. If you use Community, public Community posts can include your username, post text, publication time, edited status, and the completed-workout card fields you choose to publish. Separately, Free-tier use may automatically generate advertising data for Google Mobile Ads, and, when Sentry is configured with a DSN, app use may automatically generate crash diagnostics, as described below. Visiting our website, golightweight.app, generates the aggregate page-view data described under Website Analytics. Unless you turn it off in Settings, the app also sends a few anonymous daily counts about the Free tier's daily workout limit, about whether Community was used, about whether the program finder was used, and about whether the program generator was used, with no account or device identifier, as described in “Anonymous Usage Counts” below. If you make a program with “Make a program for me”, the choices it is built from (your four answers, the equipment you ticked, any joints you asked to go easy on, and any areas you asked for more of) are stored with that program as fixed values from a short list, on your device and, if you are signed in, with your synced data. If you write the optional note there, the note's text is sent once to our server and to our AI model provider (Google) only to be turned into those fixed choices. The text itself is not stored by us and is not logged; we keep only a count of how many notes you had read that day, to limit it to three a day. Google does not use the note to train its models; it keeps the note and the model's answer for up to 55 days in logs used to detect abuse of its service, and authorized Google staff may review them there. It is not medical advice. If you subscribe to Pro, your monthly report can include an AI analysis: two short sentences about the month. To write it, the app sends a summary of that month to our server and to our AI model provider (Google): the month, your language, totals (workouts, volume, time, reps, active days, and longest streak), how workouts and volume changed from the month before, each muscle group's share of your sets and its usual share, the names and number of exercises in which you set a record, whether you were following a program, and how many planned workouts you completed. No individual workout, no date other than the month, and no name, email address, or account ID is sent to Google. We do not keep a copy of that summary; we store only the two resulting sentences, with your account and on your device, so the same month is not written twice. Google handles the summary as it handles the note: it is not used to train its models, and it is kept for up to 55 days in abuse-detection logs. From version 1.12.0, the app asks for your permission once before it sends either the note or the summary to Google, and you can withdraw it under Settings → App → Google AI features.

2. Local Storage and Cloud Sync

Signing in starts an initial backup to or restore from Supabase so account data can be synchronized. Signed-in users can start a manual sync, and verified Pro users receive periodic automatic sync. Guests can keep their workout information local by not signing in.

3. Apple Health and Health Connect

Health integration is optional on both platforms. It stays off until you turn it on in the app's Settings, and each permission is requested separately through the platform's own permission screen. On iOS, GoLightWeight uses Apple HealthKit. If you allow it, the app reads your body weight from Apple Health to prefill your profile weight and keep bodyweight-exercise volume accurate, saves each finished workout to Apple Health as a workout, removes only its own entries when you discard a workout, and, while a workout runs on your Apple Watch, reads your heart rate and active energy so the saved entry is accurate. Heart rate read this way is shown on your Apple Watch while you train and, afterwards, in that workout’s details in the app; it is never stored in our database or synced. If you turn on showing workouts from other apps, the app also reads workouts other apps recorded so they appear in your log for that day; they are shown read-only and are never counted in your statistics. If you turn on workout location, the app captures your location once at the start of a workout and attaches it to that Apple Health entry; it never tracks your movement. On Android, GoLightWeight uses Health Connect with the same scope. If you allow it, the app reads your body weight, saves each finished workout as a strength-training exercise session, removes only its own sessions when you discard a workout, and, if you turn on showing workouts from other apps, reads exercise sessions recorded by other apps for read-only display that is never counted in your statistics. Health data read on either platform stays on your device, except that a body weight you accept into your profile is stored as your profile weight and, if you sign in, syncs like any other profile data. The app requests no background access to health data. We never sell health data or use it for advertising, and you can revoke any of these permissions at any time in the Health app on iOS or in Health Connect settings on Android.

4. Authentication and Profile Data

Apple or Google authentication may provide a user ID, email address, identity provider, and account metadata such as a name. On the first Apple sign-in, a name supplied by Apple may become the display name stored locally in the app.

5. Advertising

Free users may receive banner, app-open, and rewarded ads through Google Mobile Ads. Ad requests are currently non-personalized, but Google and its advertising partners may process an IP address or coarse location, device and app identifiers, ad impressions and interactions, performance information, and diagnostics to deliver ads, apply frequency limits, provide aggregated reporting, maintain security, and prevent fraud. We do not sell workout data. We do not use or transmit workout or HealthKit data for advertising purposes. The same applies to Health Connect data.

6. Crash Reporting

When Sentry is configured with a DSN, app use may automatically send crash, error, device, and operating-system diagnostics to help us find and fix reliability problems. Sentry is configured not to receive default personally identifying information. These diagnostics do not include workout numbers, heart rate, calories, or exercise names. To check that Apple Watch workouts are working properly, technical status not linked to your account (such as whether the session started and why it ended) may be sent when a workout ends.

7. Anonymous Usage Counts

To understand how the Free tier's one-workout-a-day limit works for the people who use it, the app keeps a few counters on your device for each calendar day: whether the limit took effect (a Free workout was finished), whether two or more workouts were finished, how many times starting or logging another workout was blocked and from which of five screens (counted up to 20 times per screen), roughly how long after your last workout that happened (under 10 minutes, under 2 hours, under 8 hours, or longer), what happened on the upgrade screen it opened (shown, purchase tapped, purchased, or closed), and, for a new user, whether it was their first day with a finished workout or their first block. To decide what to build next for Community, the app also notes for each calendar day only whether each of these happened at least once: the Community tab was opened (or, in a version where Community is not available yet, its “Coming soon” screen), the Explore feed was shown, the Following feed was shown, each of those feeds was shown with no posts in it (noted separately for each), a post was opened, and the screen for writing a new post was opened. These are yes-or-no answers for the day, not how many times; they never say which post or person was involved, and publishing a post is not noted. To see whether the program finder (“Find my program”) helps people get started, the app also notes for each calendar day only whether each of these happened at least once: the finder's questions were opened, its results were shown, the equipment you chose left fewer than three programs to show, a program was started from it, and the upgrade screen was opened from it (this last one only in a version that offers it). These are yes-or-no answers for the day as well. They do not include your answers themselves or which program was involved. To see whether making a program (“Make a program for me”) helps the lifters the catalog serves least, the app also notes for each calendar day only whether each of these happened at least once: its card was shown, its screen was opened, a program was built, a note was read into choices, “Generate again” was tapped, and a generated program was started. These are yes-or-no answers for the day as well. They do not include your answers, your equipment, your note, or anything about the program. When you open or return to the app after midnight in your time zone, the app sends the counters of each day that has ended, at most the two most recent, to our Supabase server with only that day's date, your platform (iOS or Android), and the app version. The report contains nothing else: no account or user ID, device or advertising identifier, time of day, workout content, or health data, and it is not linked to your sign-in. Like any internet request, the report reaches our server with your IP address and basic request details such as your device's user agent, which our hosting provider keeps in its standard request logs for a limited time for security and operations; it is never added to the counts. The server adds each report into totals per date, platform, app version, and screen (the Community, program finder, and program generator answers into totals per date, platform, and app version) and keeps no record per person or per device. This works the same for guests and signed-in users. It is on by default, and you can turn it off at any time in the app under Settings → App → Share anonymous usage counts; turning it off also deletes counts that have not been sent yet.

8. Website Analytics

Our website, golightweight.app, is hosted by Vercel and uses Vercel Web Analytics to count page views in aggregate. When a page loads, Vercel records the page address, the website that referred you, the time, your browser, operating system, and device type, and an approximate location (country, region, or city) derived from your IP address. Vercel Web Analytics uses no cookies, stores nothing on your device, and collects no personal identifiers: visits are told apart by a hash of the incoming request that is discarded after 24 hours, the recorded data is not tied to your IP address, and it cannot be used to follow you across other websites or apps. We see only aggregated statistics, such as how many visitors a page had, and we do not use them to identify you, combine them with app or account data, or use them for advertising. Like any web host, Vercel also processes the technical information every request carries, such as your IP address and browser details, to deliver pages and keep the website secure. The website itself sets one session cookie, NEXT_LOCALE, which records the language version you opened; it holds no identifier and expires when your browser session ends. The app does not use Vercel Web Analytics.

9. Purchases and Subscriptions

Payment details are processed by the store you installed from — Apple for App Store purchases and subscriptions, Google for Google Play purchases and subscriptions. RevenueCat receives an app-specific user ID and purchase and entitlement status so the app can verify Pro access; it does not receive payment-card details.

10. Service Providers and Sharing

Apple and Google support authentication and platform services. Supabase provides authentication, hosting, storage, and sync infrastructure. Sentry supports crash reporting, RevenueCat supports purchase and entitlement management, and Google and its advertising partners support advertising. Vercel hosts our website and provides its page-view analytics. For synchronous OpenAI moderation, we send only submitted post text and custom exercise names; we do not send account IDs, email addresses, workout numbers, or other workout metadata for that purpose. Google provides the AI model that reads the optional note you can write when you make a program; we send it only the note's text and its language. Google also provides the AI model that writes the monthly report's AI analysis for Pro subscribers; we send it only the month's summary described in section 1. Under Google's terms for its paid AI API, Google does not use what we send or what the model answers to train its models, and keeps both for up to 55 days to detect abuse and meet legal requirements, during which authorized Google staff may review them. These providers may process information only for their relevant services and must protect it consistently with applicable law and their agreements. We may also disclose information when required by law or to protect rights, safety, and service security.

11. Data Retention and Deletion

A successful in-app account-deletion result means the app's request to our controlled Supabase deletion function succeeded; that function is designed to delete the account and server-side data under our control. Local cleanup is then attempted on a best-effort basis and may not finish. Uninstalling the app ensures its local app data is removed from the device. Public Community posts are retained until deleted under the service lifecycle; approved revisions and minimum audit, report, hide, block, and deletion records may be retained for safety, security, legal obligations, and service operation. OpenAI's moderation endpoint has no application-state retention listed in its API data-controls table, but provider retention and legal obligations can change; see OpenAI's current terms and controls. Google keeps the text of a program note, the monthly summary sent for a report's AI analysis, and the model's answers for up to 55 days in its abuse-detection logs. We send no account identifier with them and cannot delete them from those logs sooner. The AI analysis sentences we store are deleted with your account. Providers may retain security, fraud-prevention, transaction, or legally required records for their necessary retention periods. If you have already uninstalled the app, you can request deletion by email at privacy@golightweight.app. Deleting an account does not cancel a subscription; subscriptions are billed by the store you installed from and must be cancelled there.

12. Your Choices and Permissions

Staying a guest keeps your workout data, routines, and records off our servers (only the anonymous usage counts described in “Anonymous Usage Counts” are sent, and you can turn those off in Settings), and you can delete your account from Settings in the app or by request if you no longer have it installed. You can revoke Health access at any time — in the Health app or iOS Settings on iOS, or in Health Connect settings on Android — and you can turn off workout saving, workouts from other apps, and workout location in the app's Settings. You can allow or stop sending your program note and your monthly summary to Google's AI at any time under Settings → App → Google AI features; while it is off, programs are built without a note and reports show their standard suggestion instead of an AI analysis. Subscriptions are managed separately in the store you installed from — your App Store account on iOS, or Google Play on Android. Where available, you can use privacy choices offered by Google or your device, including your platform's advertising and privacy controls, to limit advertising data processing. For privacy questions or requests, email privacy@golightweight.app.

13. Security

We use reasonable administrative, technical, and organizational safeguards, including Supabase row-level security (RLS) for controlled cloud records. No storage, transmission, or security measure is absolutely secure, so we cannot guarantee absolute security.

14. International Processing

Our providers may process information in the United States and other countries, where privacy laws may differ from those where you live. Where required, processing is supported by applicable contractual or legal safeguards.

15. Children

GoLightWeight is not directed to children under 13 or under a higher minimum age required by local law. If you believe we knowingly hold a child's information, contact privacy@golightweight.app so the information can be reviewed and deleted as appropriate.

16. Changes and Contact

We may update this Privacy Policy as the service or legal requirements change and will revise the date shown above. This policy is effective as of November 16, 2026. Contact privacy@golightweight.app with privacy-related questions.