In this policy, “we”, “us”, and “Gravus” mean Gravus App Operator. The public contact is support@getgravus.com.
This policy is for the Gravus iOS app (com.gravus.app) and the pages on getgravus.com. It matches the v1.0 App Store binary: local-first logging, optional Apple Health (read-only), and subscriptions via Apple / RevenueCat. It also matches the App Store Connect App Privacy nutrition labels for that binary.
1. Plain-language summary
- Your workouts, weigh-ins, goals, and body metrics stay on your iPhone in a local SQLite database (
gravus.db). v1.0 has no Gravus cloud account and does not back your log up to our servers. - Name and email are required during onboarding. They stay on device and are also sent to RevenueCat (
$displayNameand$email) so support can find your subscription. Email is not used for marketing messages. - Health and Fitness include what you type in the app plus optional Apple Health (HealthKit) reads. HealthKit is optional and read-only. We never write to Apple Health. We never send Health or Fitness data to RevenueCat. We never use Health or Fitness for advertising, analytics, or product personalization.
- Payments are handled by Apple. We never see your card number. RevenueCat sees the Apple receipt, purchase status, an anonymous App User ID, Identifier for Vendor (IDFV), and the name and email attributes above.
- We do not track you across other companies’ apps or websites. We do not use the Identifier for Advertisers (IDFA). We do not use App Tracking Transparency. We do not sell personal information.
- Uninstalling Gravus deletes the on-device database. Name and email stored with RevenueCat or in our support inbox are removed when you ask (see §9).
Every data type we declare on the App Store is linked to your identity, used only for App Functionality, and not used for tracking.
2. App Store privacy labels
The App Store product page lists these types under Data Linked to You. This is the same list we filed in App Store Connect for v1.0.
| App Store type | Linked to you | Used for tracking | Purpose | What it is in Gravus v1.0 |
|---|---|---|---|---|
| Name | Yes | No | App Functionality | First and last name from onboarding |
| Email Address | Yes | No | App Functionality | Onboarding email; RevenueCat $email; optional Mail prefill for support |
| Health | Yes | No | App Functionality | In-app height, sex, date of birth, weight, body fat; optional HealthKit reads |
| Fitness | Yes | No | App Functionality | In-app workout / session log; optional HealthKit workouts and active energy |
| Customer Support | Yes | No | App Functionality | Optional emails you send to support@getgravus.com |
| Other User Content | Yes | No | App Functionality | Optional session titles and notes in on-device SQLite |
| User ID | Yes | No | App Functionality | RevenueCat anonymous App User ID and local profile UUID |
| Device ID | Yes | No | App Functionality | Identifier for Vendor (IDFV) collected by the RevenueCat SDK. Not IDFA |
| Purchase History | Yes | No | App Functionality | Apple + RevenueCat receipts, product IDs, entitlement and trial status |
We do not collect, and we do not list on the App Store, any of the following: phone number, physical address, payment card / PAN, precise or coarse location, contacts, photos / video / audio, browsing history, search history, product interaction / analytics, advertising data, crash or performance diagnostics, or IDFA.
3. Who is responsible
Gravus App Operator is the controller of personal data processed through Gravus, except:
- Apple is the controller of your Apple ID, App Store account, and in-app purchase receipts, and of HealthKit data in the Health store.
- RevenueCat, Inc. processes subscription status, name, email, User ID, Device ID (IDFV), and purchase history as our processor (see §7).
Gravus App Operator is established in the Republic of North Macedonia. Contractual disputes relating to Gravus are subject to the governing law and exclusive jurisdiction of the courts of Skopje, Republic of North Macedonia, as set out in the Terms of Use. This does not limit your right to lodge a complaint with a data protection authority in your country of residence where the law provides that right.
If you are in the EEA, UK, or Switzerland, you may contact us at support@getgravus.com. We do not currently appoint an EU/UK representative; we will update this policy if that changes.
4. What each type is
All nine types below are stored or processed in a way that is linked to your identity (name and email live on the same device as your log). None are used for tracking. The only purpose is App Functionality.
4.1 Name
First and last name from onboarding. Stored on device. Also sent to RevenueCat as $displayName so support can find a subscription without a Gravus login.
4.2 Email Address
Required in onboarding. Stored on device. Sent to RevenueCat as $email. The Help & feedback compose window may prefill this address and your app version; you choose whether to send the message. We do not use your email for marketing.
4.3 Health
In-app: height, sex, date of birth, weight, and body fat (and related body-composition settings you type). Optional Apple Health (HealthKit) read access for:
- Dietary energy consumed
- Dietary protein, carbohydrates, and fat (if available)
- Body mass and body-fat percentage (if you share them)
- Optional heart rate if present on a workout
HealthKit is optional and read-only. We do not request write access. We never write to Apple Health. We never send Health data to RevenueCat. We never use Health for advertising, analytics, or product personalization.
Cached HealthKit copies live in on-device tables so Calendar and Progress still work offline. Revoking access in the Health app stops new reads; existing cache remains until you delete the app or clear local data.
4.4 Fitness
The in-app workout / session log is core (sessions, exercises, sets, duration, distance, optional RPE). Optional HealthKit workouts and active energy burned follow the same HealthKit rules as Health: read-only, on-device cache, never sent to RevenueCat, never used for advertising, analytics, or product personalization.
4.5 Customer Support
The content of optional emails you send to support@getgravus.com. You choose whether to send. This is not required to use the app.
4.6 Other User Content
Optional session titles and notes stored in on-device SQLite. They are not uploaded to Gravus servers.
Settings you pick in the app (units, timezone, week-start) stay in on-device SQLite with your log. They are not a separate App Store nutrition-label type.
4.7 User ID
RevenueCat’s anonymous App User ID, plus a local profile UUID on the device. Needed to restore Premium. You cannot opt out of this identifier if you use Gravus.
4.8 Device ID
Identifier for Vendor (IDFV) collected by the RevenueCat SDK. This is not IDFA and is not used for tracking. You cannot opt out of IDFV if you use Gravus. We do not use App Tracking Transparency.
4.9 Purchase History
Apple and RevenueCat receipts, product IDs, and entitlement / trial status (premium). Needed to unlock Premium and restore purchases. We never see your card number; Apple processes payment.
4.10 Data we do not collect in v1.0
- Phone number
- Physical address (Apple may hold a billing address; we do not collect one)
- Payment card number / PAN
- Precise or coarse location (timezone is a label you confirm, not GPS)
- Contacts, photos, video, or audio
- Browsing history or search history
- Product interaction / analytics (no PostHog or similar in this binary)
- Advertising data
- Crash or performance diagnostics (no crash SDK in this binary)
- IDFA, and we do not show an App Tracking Transparency prompt
- Account password (there is no Gravus account)
- Data from children we knowingly onboard (see §10)
If we add analytics, crash reporting, iCloud backup, or cloud sync, we will update this policy and the App Store privacy labels before that binary ships.
4.11 Website
getgravus.com legal pages are static. We do not set advertising cookies. The host may process standard server logs (IP address, user agent) as needed to serve the page and protect the site. Website logs are not an App Store nutrition-label type.
5. Why we use the data (purposes and legal bases)
For users in the EEA/UK, GDPR requires a legal basis. Health, sex, and body-composition data can be special-category / health data (GDPR Art. 9). We only process that data to provide the fitness-tracking service you asked for. App Store purpose for all nine declared types is App Functionality only.
| Purpose | Data | Basis (GDPR) |
|---|---|---|
| Provide the app: calendar, goals, progress, estimates | On-device profile, Fitness log, Other User Content | Contract (Art. 6(1)(b)); health data: explicit consent (Art. 9(2)(a)) by entering it and using the feature |
| Read Apple Health to enrich calories / workouts | HealthKit samples + on-device cache | Explicit consent via the Health permission sheet (Art. 6(1)(a) + Art. 9(2)(a)); you can refuse and still log manually |
| Start trial, subscribe, restore, show status | Name, Email Address, User ID, Device ID, Purchase History | Contract (Art. 6(1)(b)); Apple’s processing under Apple’s terms |
| Support | Customer Support messages; name and email | Legitimate interests (Art. 6(1)(f)) and/or contract |
| Legal obligations (tax, accounting on our side; consumer law) | Limited billing metadata we may receive | Legal obligation (Art. 6(1)(c)) |
We do not use Health, Fitness, or body data for third-party advertising, our own advertising, analytics, product personalization, data mining unrelated to the app, or sale.
California (CCPA/CPRA): we do not sell or share (for cross-context behavioral advertising) personal information. Sensitive personal information (health, precise body metrics) is used only to provide Gravus on device.
6. Apple Health and App Store health rules
Gravus is a fitness tracking and education app, not a medical device and not a source of diagnosis or treatment. See the Health & Fitness Disclaimer.
Consistent with Apple’s HealthKit and Guideline 5.1.3 / 5.1.7:
- HealthKit data is used only to display and compute in-app progress (calories remaining, imported workouts, optional body metrics) — App Functionality.
- We do not give HealthKit data to advertisers, data brokers, or information resellers.
- We do not use HealthKit data for marketing, analytics, or product personalization inside or outside the app.
- Permission strings explain why we read Health, not only what.
You control sharing in iPhone Settings → Health → Data Access & Devices → Gravus (or Account → Data sources → Manage).
7. Who we share with
We do not sell your information. Sharing in v1.0 is limited to:
| Recipient | Role | What they get |
|---|---|---|
| Apple (App Store / StoreKit / HealthKit) | Payment platform / OS | Purchase History; Apple ID; Health store if you grant Health |
| RevenueCat, Inc. | Processor for subscriptions | Name ($displayName), Email Address ($email), User ID, Device ID (IDFV), Purchase History. Not Health, Fitness, Other User Content, or Customer Support message bodies |
| Email provider / host | Inbox for support@getgravus.com | Customer Support messages you send |
| Hosting for getgravus.com | Website | Server logs as above |
There is no PostHog, crash SDK, ad network, or mobile measurement partner in the v1.0 binary.
If we are required by law to disclose data, we will do so only to the extent required.
International transfers: RevenueCat and Apple may process data in the United States. Where GDPR applies, transfers rely on the recipient’s stated mechanisms (e.g. Standard Contractual Clauses / Data Privacy Framework as they publish). Using Gravus means this processing is necessary to provide IAP.
8. Retention
| Data | Retention |
|---|---|
| On-device SQLite (profile, Health cache, Fitness log, Other User Content) | Until you delete the app or wipe the device. v1.0 has no cloud copy, so uninstall is deletion of the log. |
| RevenueCat subscriber record (Name, Email Address, User ID, Device ID, Purchase History) | For the life of the subscription relationship plus a short period needed for restore, refunds, tax, and dispute handling (typically aligned with Apple’s receipt lifetime). Name and email attributes are removed on request. |
| Customer Support emails | As long as needed to resolve the ticket, then deleted or minimized; we may keep a brief record if required for legal claims. |
| Website logs | Per the host’s default (typically days to weeks). |
We do not keep a Gravus-side copy of your workout history in v1.0.
9. Your rights and how to delete data
On-device data
Delete Gravus from the iPhone (or offload and delete app data). That removes gravus.db. Reinstalling starts empty.
There is no Gravus account in v1.0, so there is no in-app “delete account” control. Guideline 5.1.1(v) account deletion will apply when sign-in ships.
Email and subscription records
Email support@getgravus.com from the address you used in the app and ask us to:
- Remove your name and email from RevenueCat subscriber attributes, and
- Delete support threads we hold.
We will confirm. Apple still holds the purchase record on your Apple ID; cancel or request refunds through Apple. Uninstalling does not cancel a subscription.
Access / correction / portability (GDPR and similar laws)
Most data lives only on your device — you already have it. For name, email, or other subscriber attributes we hold, email support@getgravus.com. We may need to verify that you control that address.
You may lodge a complaint with your local data protection authority.
California
You may request to know, delete, or correct personal information we hold off-device (email / support / RevenueCat attributes) via support@getgravus.com. We will not discriminate against you for exercising these rights. We do not sell or share PI as defined by CPRA.
10. Children
Gravus is not directed at children under 13 (COPPA) and is intended for users 16 or older.
We do not knowingly collect personal information from children under 13. If you believe we have, contact support@getgravus.com and we will delete off-device data we hold.
Calorie targets and body-composition estimates are inappropriate as a product for younger children. Parents should not set up Gravus for a child.
11. Security
- Workout and body data stay on the device, protected by iOS app sandboxing and the device passcode / Face ID you configure.
- We do not operate a Gravus production API for user logs in v1.0, which reduces our server-side breach surface for that data.
- Email and RevenueCat access are limited to people who need them for support and operations.
- No method of transmission or storage is 100% secure.
Treat the phone as the source of truth. Back up the device with Apple’s tools if you want a copy; v1.0 does not offer Gravus iCloud backup.
12. Automated decisions
Gravus calculates calorie and protein estimates from the profile and goal you enter. These are planning aids, not decisions that produce legal or similarly significant effects. They are not medical advice.
13. Changes
We will update this page and the “Last updated” date when practices change. Material changes (new vendors, Health write access, cloud sync, tracking) will also be reflected in App Store privacy labels before that version is released. Continued use after an update means you accept the revised policy, except where the law requires a new consent (for example a new HealthKit type).
14. Contact
Privacy and data requests: support@getgravus.com
App Store listing and in-app About must use this same URL: https://getgravus.com/privacy