Last updated · May 10, 2026
hiphip is a strength training app focused on 5/3/1 programming, workout logging, progress monitoring, optional WOD features, and an optional AI coach. We collect as little as we need, and most of what we collect never leaves your device.
hiphip stores workout and profile information locally on your device so the app can function. This may include:
If you enable Apple Health access, hiphip may read body weight data from Apple Health and write body weight or workout data back when those features are enabled.
You can revoke this access at any time in iOS Settings → Health → Data Access & Devices.
If you are signed into iCloud and iCloud Drive is enabled for hiphip, your training data — workouts, sets, training maxes, personal records, body weight entries, AI conversation history, and preferences — is synced to your private iCloud container so it’s available across your Apple devices.
This data is encrypted in transit and at rest by Apple and is only accessible from devices signed into your Apple ID. agostolabs does not have access to it, and Apple does not share it with us.
To stop syncing, sign out of iCloud or turn off iCloud Drive for hiphip in iOS Settings → [your name] → iCloud. The on-device copy remains until you delete it.
If you use the AI coach, hiphip sends your message and relevant training context to an Agosto Labs backend at api.agostolabs.com, which forwards the prompt to Google’s Gemini API to generate a response.
Context sent may include your prompt text, unit preference, current cycle/week, training maxes, schedule, recent PRs, recent sessions, and progression summaries. We don’t share this data with advertisers, and the conversation content is not used to train any model.
We retain short-term request logs for rate limiting and abuse prevention. These logs don’t contain your name, email, or Apple ID and are deleted on a rolling 30-day window. If you’d rather no chat content leave your device, don’t use the AI coach feature.
If a crash occurs, an anonymized report may be sent through Apple’s standard reporting and through Firebase Crashlytics so we can fix the bug. Reports never contain training data, message content, or anything that identifies you personally.
hiphip uses Firebase Analytics for auto-collected events (such as first_open, session_start, and screen views) and Firebase Crashlytics for crash reports with stack traces, OS version, device model, and breadcrumbs we attach in code.
Firebase generates an App Instance ID — a pseudonymous identifier local to hiphip on your device — used to deduplicate sessions and crash reports. We do not set a user identifier on these services, and we do not link this data to your Apple ID, email, or name.
This data is processed by Google (Firebase’s operator). Google’s handling is governed by firebase.google.com/support/privacy.
hiphip uses Apple’s StoreKit framework to load products, process purchases, and verify entitlements for WOD library access, AI coach subscriptions, and optional tip jar purchases.
Payment processing is handled by Apple. hiphip does not collect or store your full payment card information.
If you enable workout reminders, hiphip schedules local notifications on your device. Export files are generated on your device only when you choose to export them.
hiphip does not use your data for cross-app tracking and does not include third-party advertising SDKs for targeted advertising.
hiphip relies on a small set of third parties to function:
api.agostolabs.com) — generates AI coach responses.You can control privacy-related features by choosing whether to enable Apple Health, iCloud sync, notifications, and the AI coach, and by deleting app data from inside the app (Settings → Delete All Data) or by deleting hiphip from your device.
Questions about this policy? Write to [email protected]. One human reads every email.