Who is responsible
The controller is Simion Gorgos, an individual established in the Republic of Moldova. Contact: help@metabolicpause.com.
Website visitors
This section covers only metabolicpause.com. It does not describe analytics in the Pause iPhone app. The website stores your versioned cookie preference in local storage. The website’s Google Tag Manager is loaded only after you affirmatively accept; nothing is requested from Google before that. Once you accept, _ga cookies are set and analytics_storage is granted for website analytics. Advertising storage, ad user data, and ad personalization signals are always denied, whether or not you accept.
The Pause iPhone app: what is collected and why
The app collects the following, synced to Supabase:
- Email, sign-in provider identity, and account ID: authentication.
- Full name, if you choose to keep one: profile display. It is optional, editable, and removable.
- Date of birth: the 18+ age gate and profile.
- Sex and height: required explicit answers for new-user setup, used only for profile capture and display. Goal weight is also required for new-user setup and is used for goal display and app behavior, not health analysis. A legacy account may show Not set for one of these answers. You can fill in or edit an answer, but cannot remove it after it is set.
- Unit preference, fasting plan, and other goals: app configuration.
- Current weight and weight history: core app function.
- Fasting records (start/end time, goal, timezone): core app function.
- Water entries and daily hydration goal: core app function.
- Reminder preferences: notification scheduling.
A profile photo, if you choose to add one, is optional and is stored in a private Supabase Storage bucket. You can remove it at any time.
How information is collected
Directly from you in the app; from Apple or Google when you sign in; from Apple Health only if you grant explicit permission; and from Apple through StoreKit and RevenueCat for purchase and entitlement information.
Accounts and sign-in
Accounts are handled by Supabase Auth. You can sign in with Apple (native) or Google OAuth; there is no email/password account option. Apple’s Hide My Email relay addresses are supported.
Pause may seed your optional Full name from a valid name supplied by your sign-in provider. Because Apple may supply that name only once, Supabase Auth metadata and a protected, account-scoped on-device retry may preserve it until the profile is saved. The pending retry is cleared after the name is saved, when you log out, or when account deletion is confirmed. It is not independently synced or exported and is not used for analytics or diagnostics. A name you edit or remove in Pause takes precedence over a provider-supplied name.
Purchases
Apple and StoreKit handle purchases, payment-card information, billing, renewal, cancellation, and App Store refunds. Pause does not receive your payment-card information.
RevenueCat receives your Supabase user ID (a UUID) as its customer ID, together with Purchase History, entitlements, subscription status, promotional grants, and refund-request information. It uses these linked records for app access, subscription operations, and purchase analytics. Purchase History is used for App Functionality and Analytics purposes and is not used for tracking. Pause does not send RevenueCat your name, email address, health or profile data, or custom attributes. These purchase records are not synced to the Pause database or included in your Pause data export.
A promotional Premium grant is not an Apple purchase and expires within one year.
Apple Health
Apple Health access is optional. With permission, Pause reads body mass and active energy, and writes body mass and dietary water. Raw Apple Health samples, sample identifiers, source and device metadata, and your authorization state never leave your device. Active energy is display-only; it is never stored, synced, or exported. The one exception: if you import a weight from Apple Health, it becomes an ordinary Pause weight entry and syncs like any weight you enter manually. Apple Health data is never used for advertising, marketing, analytics, or diagnostics.
Disconnecting Apple Health in Pause stops future Health reads and writes for that Pause account, but does not revoke Apple’s system permission or erase existing Pause records or Apple Health samples. Review or revoke Apple’s permission separately in Health → Data Access & Devices → Pause. Turning off Write Weight or Write Water stops future changes in that direction and does not erase either store.
Pause keeps each account’s Health connection choices, read cursor, opaque import keys, and sample mappings separate and on-device. Apple Health authorization and store access apply to the app and device, however. If another Pause account on the same device explicitly connects Apple Health, iOS may reuse the app’s existing authorization and available external Health data may be imported into that account. Pause filters out samples previously written by Pause before importing weight.
Profile photos
Photos are picked using Apple’s system photo picker; Pause never receives access to your photo library, only the image you choose. Before upload, the image is sanitized on-device: resized to 1024px or less on the longest edge, converted to sRGB JPEG, and stripped of EXIF and GPS metadata. It is then stored in a private, owner-prefixed storage bucket. The original picked file never leaves your device.
What Pause does not do
The iPhone app does not load the website’s Google Tag Manager or use an analytics SDK for health, profile, or product-usage events. RevenueCat processes only the purchase analytics described above. There is no advertising identifier, no ad networks, no cross-app or cross-site tracking, and no App Tracking Transparency prompt; the app’s privacy manifest declares NSPrivacyTracking: false with an empty tracking-domains list. There is no remote crash-reporting processor: crash and error diagnostics are kept in an on-device ring buffer of scrubbed text alongside an anonymous per-install id, and nothing is transmitted off the device.
Who else receives app data
The app uses the following service providers:
- Supabase: authentication, database sync, file storage, and serverless functions, hosted in the United States.
- Apple: StoreKit and the App Store, for purchase, billing, renewal, and refunds.
- RevenueCat: the Supabase UUID and linked Purchase History, entitlements, subscription status, grants, and refund-request information for app access, subscription operations, and purchase analytics. It receives none of the health or profile data listed above.
The optional Apple HealthKit integration reads from and writes to the on-device Apple Health store as described above; it is not a transfer to a remote app-data processor. Each third party that receives user data is contractually required to provide the same or equal protection of user data as stated in this policy.
On-device storage and security
Local data is stored encrypted on-device and excluded from device backups. Notifications are local-only; there are no push tokens and no APNs. The Home Screen widget and Live Activity make no network calls and contain no health values or identity data. On the server side, data is protected with encryption in transit and access controls.
Retention and deletion
Pause data is retained while your account is active. Account deletion removes your account record; synced profile, fasting, hydration, weight, preference, and reminder data; stored profile photos; and that account’s on-device data and local Apple Health integration state. Apple authorization tokens are revoked for Sign in with Apple accounts. Residual copies in encrypted daily backups are overwritten within 7 days, and service logs are retained for 7 days. Pause account deletion is irreversible.
As part of deletion, Pause requests deletion of the RevenueCat customer identified by your Supabase UUID before removing your authentication account. RevenueCat processes an accepted erasure asynchronously, so completion of Pause account deletion does not mean that RevenueCat’s erasure has already finished. RevenueCat may retain information as described in its privacy policy and as required by law.
Deleting your Pause account does not cancel an Apple subscription; subscriptions and Apple billing records are managed separately by Apple. You can export your Pause data as JSON or CSV from within the app before deleting.
Your choices and rights
You can disconnect future Apple Health exchange within Pause, review Apple’s system permission separately, delete your account from within the app, and withdraw consent for website analytics using the Cookie settings control in the website footer. For access, correction, export, or deletion requests, contact help@metabolicpause.com.
International transfers
Supabase and RevenueCat process app data in the United States. Where information is transferred internationally, it is protected by contractual safeguards.
Age
Pause is restricted to adults aged 18 or older. Date of birth is collected to enforce that age gate and is displayed in your profile.
Changes and contact
We may update this policy from time to time; material changes will be announced in the app or on this site before they take effect. Questions and rights requests may be sent to help@metabolicpause.com.