Pure 75 Privacy Policy

Last updated: 23 September 2026

Pure 75 (App Store name: 75 Hard Tracker: Pure 75) is provided by Pavel Korkodinov. This policy explains the app's local storage, online features, purchases, and support. For privacy questions or data requests, contact ikorkod@gmail.com.

Release status on 23 September 2026: the published App Store version is 1.0.5. Version 1.0.6 is upcoming and has not yet been released. The version-specific controls described below will become available only after you install that update; they are not present in 1.0.5.

Information on your device

Your challenge history, daily logs, workout entries, water entries, books and reading records, progress photos, notes, personal motivation, and settings are stored in the app's local database. The iPhone app and its widgets use a shared local container. The current app does not provide automatic CloudKit synchronization of this database or photos. Device backups and copies you make are controlled separately through your device and Apple settings.

Camera access is used to take progress photos. Photos are stored in the app; the app does not upload the images to its analytics or Buddy servers. If you export a comparison, a report, or other content with the system share sheet, it is sent to the destination you choose, under that destination's privacy practices.

Apple Health

Connecting Apple Health is optional. With your permission, Pure 75 reads workout records to offer eligible workouts for import into your challenge. Imported records include workout timing, duration, activity type, and an identifier used to avoid duplicates. Pure 75 does not write health records to Apple Health. You can change its access in Apple Health or system settings; previously imported local entries are not removed automatically by revoking access.

Version 1.0.5 and earlier can send workout-related progress to product analytics, including duration, activity category, and the fact that a workout was imported from Apple Health, as described below. The upcoming 1.0.6 update will exclude HealthKit workout details from product analytics. General feature-use and day-completion events can still reflect that you used the app. The app does not send heart-rate samples, medical records, or workout routes through these analytics events.

Product analytics

The app sends product analytics to a Supabase-hosted database to understand usage, find delivery and feature failures, and improve the app. These records use a randomly generated installation identifier and session identifiers; they are not fully anonymous because events from the same installation can be connected.

Records include event names and times; app, build, and operating-system versions; language/region settings and time zone; onboarding steps; challenge day and attempt numbers; feature and paywall interactions; purchase and restore outcomes; and premium status. Progress events can also include selected diet category, water amounts and daily totals, manually logged workout duration/activity/indoor or outdoor status, reading page counts, rule completion, and photo-capture/comparison actions. They do not contain the photos themselves, book titles, free-text notes, or your personal motivation text. Region is derived from device settings, not GPS.

Upcoming version 1.0.6 — not yet released: product analytics will be optional and off by default. After installing that update, you will be able to enable or disable Share usage analytics during setup or under Settings → Privacy. Declining will not restrict tracking or paid features. Disabling will clear unsent analytics and stop new collection; a request already in flight may finish. The switch will not retrospectively delete data already delivered to the server.

Version 1.0.5 and earlier: these releases collect product analytics automatically and do not contain that switch. Their events can also include challenge day and attempt numbers, selected diet category, water amounts and daily totals, workout duration/activity/indoor or outdoor status, reading page counts, rule completion, and photo-capture/comparison actions. Apple's “Share iPhone Analytics” setting does not control these app-specific events. Update to a version with the privacy control when available, or contact us about previously collected data or an objection to this processing. The new setting does not retroactively give consent for earlier collection.

Optional Buddy sharing

When you use Buddy features, Supabase creates an account with a random user identifier without requiring an email address or password. The service stores your chosen display name, invitation code and expiry, the pairing between two users, and the latest shared challenge day, attempt number, completed-rule count, and update time.

The person who accepts your invitation, or whose invitation you accept, can see your display name and shared progress. Keep invitation codes private and choose a display name you are comfortable sharing. Buddy does not upload or share your photos, book titles, workout details, or water amounts. These limits concern Buddy sharing; product analytics is described separately above.

Pausing Buddy sharing stops new check-ins, but previously shared information can remain visible. Successfully unpairing removes the active pair and its stored day-state records from the Buddy database. Unpairing does not delete the underlying account or separate analytics records. Losing the device's stored account credentials can prevent recovery of the same pairing.

Purchases

Apple processes in-app payments. We do not receive your payment-card or bank-account details. The app reads purchase status to unlock features and restore eligible purchases.

When RevenueCat is enabled in the installed version, it also processes purchase records, product and transaction identifiers, purchase and entitlement status, a generated app-user identifier, and relevant app/device information to validate purchases, restore access, and provide purchase reporting. The app does not intentionally send your Buddy display name, photos, or HealthKit records to RevenueCat.

Support and service providers

If you email support, we receive your email address and the message and attachments you choose to send. Please do not send progress photos or detailed health information unless they are necessary for the issue you want help with.

We use Apple for platform services and purchases, Supabase for analytics and Buddy infrastructure, and RevenueCat for purchase management when configured. Network services necessarily receive connection information such as an IP address when handling a request. Service providers may process data in countries other than yours. We require providers acting on our behalf to protect personal data consistently with this policy and their data-protection commitments. See Apple's privacy policy, Supabase's privacy policy, and RevenueCat's privacy information.

We do not sell your personal data or use it for advertising tracking across other companies' apps or websites. We do not use your health or fitness information for advertising or marketing.

Retention and deletion

Local records remain on your device until you remove them through available app controls or delete the app's local data. Deleting the app does not itself delete information already sent to online services, copies shared with another person, Apple purchase history, or device backups.

The upcoming 1.0.6 update will provide Settings → Delete Buddy Account for the Buddy account belonging to that installation. After successful server confirmation, it will remove that account, its invitation codes and pairs, and the pairs' shared progress. Your buddy's own account, local challenge history, photos, and purchases will remain. This operation will require an internet connection. If an older or shared account cannot safely be identified as a Pure 75 Buddy account, the app will report the limitation instead of claiming it deleted the account. Contact support for help with that case; currently published releases do not include this control.

Buddy day-state records are updated as new progress is shared and removed from the active database when the pair is successfully deleted. Invitation codes expire after seven days; expiry is a limit on using the code, not a promise that every stored copy is erased at that moment. There is currently no fixed automatic expiry period for analytics records or the automatically created Buddy account. They can remain until they are deleted. Provider backups and operational logs follow the provider's applicable retention processes; this policy does not promise immediate removal from those copies.

For access, correction, or deletion requests, email ikorkod@gmail.com. We may need enough information to locate the relevant generated identifiers and verify that a request concerns your records. An email address alone may not identify an installation or a Buddy account because those identifiers are not registered to your email. We cannot retrieve local-only data from your device. Records that must be kept under applicable law, and purchase records held by Apple, may be subject to separate requirements. We will explain any applicable limitation when handling your request.

Your choices and rights

You can decline camera, Apple Health, and notification permissions and change them later in system settings. You can choose not to use Buddy, pause future sharing, or unpair. Depending on the law that applies to you, you may also have rights to access, correct, erase, restrict, or object to processing, request a portable copy, withdraw consent where processing relies on consent, and complain to a relevant data-protection authority. Contact us using the address above to exercise applicable rights. Withdrawing consent does not undo processing that was lawful before withdrawal.

For the upcoming 1.0.6 update, consent will be the basis for optional product analytics and optional Apple Health access. Buddy and purchase processing support services you request. We process support correspondence to respond to your request, and service-security information to protect the service. Any processing required by applicable law remains subject to that law; this statement does not assert that earlier implementations provided the new controls.

This website and policy updates

These pages are hosted by GitHub Pages. They contain no analytics scripts, advertising, or forms. GitHub may process visitor connection information to serve and secure the site under its privacy statement. Following an external link takes you to that provider's site.

We will update this page when the described practices change and change the date above. A new policy does not by itself grant permission for an unrelated use of previously collected data.