GYMGROVE

Privacy Policy

Effective October 1, 2026

Updated October 11, 2026 for GymGrove 2.0. Social is optional. Your personal workout log stays on your devices and, when enabled, in your private iCloud database. Joining Social also sends the workout information described below to Firebase so accepted friends can see your history.

Personal workouts and Apple Health

GymGrove stores your personal workouts, routines, sets and notes locally, with optional private iCloud synchronization. With your permission, it writes finished workouts to Apple Health and reads supported body measurements for training features. Weight entered in your profile is stored on your device; you can explicitly choose to save that measurement to Apple Health. Private notes, perceived-effort tags, raw body measurements and location are not included in Social uploads. If you enable relative strength sharing, we upload strength-to-bodyweight ratios calculated from weight you enter or allow us to read from Health. We do not share calories. Ratios and absolute lifting values together may allow friends to infer your bodyweight. These optional values are used only for the sharing features you request. Exercise artwork is bundled with the app.

Optional Social account and automatic history sync

Social uses Sign in with Apple and Firebase Authentication. With your permission, Apple can supply your name on the first sign-in so we can prefill it. Apple does not supply a profile photo. You choose a display name and username, and may provide a bio and profile photo. Creating a Social profile enables automatic synchronization of existing and future completed workouts to Firebase/Google Cloud: workout dates and duration, exercise names/identifiers, sets, weights/repetitions, derived training totals, muscle allocation and personal records. We also store the selected body figure used to render muscle maps.

Your name, username, bio and photo can appear in profile search. Individual progress comparisons are visible only to you and accepted friends, according to your privacy settings. There is no public workout feed. You can change categories shared with friends, disable progress sharing, remove friends or block people. These settings restrict friends' access; they do not delete your synchronized workout data. Deleting the Social account removes that server copy. Offline changes reach the server when the app reconnects; we cannot recall screenshots or information another person already saw.

Social content and moderation

Firebase stores friendships, requests, blocks, invitations, privacy preferences and reports. Profile photos are checked by Google Cloud Vision for inappropriate imagery; submitted text is filtered for known objectionable language. You can report and block people. The developer can review reported content and account records, remove content, and suspend abusive accounts. When a profile is reported, the developer receives a private Telegram notification containing the reason given and the name, username, bio and, on request, photo of the reported profile, and the name and username of the person reporting. See the Social terms and community rules.

Purchases and gift invitations

Apple processes purchases. We do not receive payment-card details. Firebase stores verified App Store transaction identifiers, membership status/dates and gift-invitation allocations to authorize Pro comparisons and enforce yearly invitation limits. Gift invitations lead to Apple offer-code redemption; Apple's eligibility, pricing, renewal and cancellation terms apply. Firebase does not replace the App Store as the source of purchased Pro access.

Notifications

Rest-timer alerts and routine reminders are scheduled locally. Social push notifications use Firebase Cloud Messaging and Apple Push Notification service. We store a device messaging token linked to the signed-in account and your notification preferences. You can change Social notification choices in the app and system permission in Settings.

Analytics and diagnostics

GymGrove uses Firebase Analytics and Crashlytics for app usage and reliability. Development builds disable collection; TestFlight disables Analytics while retaining crash reporting. Events describe product interactions and coarse counts, with app/device metadata and Firebase-generated identifiers. Social profile text, photos, workout details, private notes, HealthKit values and purchase verification tokens are not attached to analytics events or intentionally logged as diagnostic content. No IDFA, advertising networks or cross-app advertising tracking is introduced by Social.

Feedback

Sending feedback uses your Apple-backed Firebase account. Firebase stores your message, category, app version/build, submission time and account ID. If you choose to give an email address for a reply, it is stored with the message and used only to answer you. Your workouts and device logs are not attached. Previously submitted guest feedback may be linked to Apple with your explicit agreement. The developer receives a private Telegram notification containing your message, category, app version and any reply email you gave, but not your account ID. Feedback records expire after 365 days, or may be deleted sooner in the app. The Telegram copy may remain in the developer's private chat after the record is deleted.

Retention, deletion and your choices

Social account data and synchronized workouts remain until deleted; individual deleted workout payloads are removed while a minimal deletion marker prevents stale devices from restoring them. Profile → Social account → Delete account removes the Social account, shared history, relationships and feedback. It leaves your personal local/iCloud workout log and App Store subscriptions intact. Cancel subscriptions separately in Apple's subscription settings. Delete Feedback Data removes feedback while preserving the shared account. Uninstalling the app does not delete server data.

Contact the developer to request access, correction, portability, deletion or review of a moderation decision. Depending on where you live, you may also have rights to withdraw consent, object to or restrict processing, and complain to a data-protection authority. We use data to provide the features you request, with consent for optional sharing and legitimate operational interests in security and abuse prevention, subject to applicable law. We do not sell personal data or share it with data brokers or for cross-context behavioral advertising.

Service providers and processing locations

Apple provides iCloud, authentication, purchases and push delivery. Google/Firebase provides account hosting, the Social database/backend, photo moderation, messaging and diagnostics. Telegram delivers feedback and moderation alerts to the developer. These providers process service metadata under their terms. Social uses Google Cloud infrastructure in the United States; provider operations may involve other countries. Aleksey Lichtman is responsible for GymGrove's processing and can be contacted below.

Age and health information

The initial Social service is for adults 18 and older. Before you can create a Social profile, GymGrove asks iOS for the age range declared on your device (Apple's Declared Age Range feature) with a single question: 18 or older. We store only whether that check passed, on your device and in your Social account record. We never receive or store your birthday or the age range itself, and if the range is not shared or is under 18, Social stays unavailable. GymGrove is not directed at children under 13. Contact us if you believe a child has provided account information. GymGrove is not a medical device and does not provide medical advice. Exercise suggestions and estimated muscle/strength metrics are informational; consult a qualified professional about health or injury concerns.

Contact and updates

Privacy, support and moderation: aleksey.lichtman@gmail.com. We will update this page as practices change and explain material changes in the app where appropriate.