JIM Privacy Policy
Last updated: October 25, 2026
This policy explains how I, Kobey Buhr, handle information in JIM, the fitness app. It covers JIM’s mobile app, companion Watch features, and related cloud services.
Your workouts can stay on your device. An account is optional for local workout and nutrition tracking. Cloud backup is optional. Check Settings → Account & cloud → Backups on each device to see and change its upload setting. Purchases and restoring purchases do not require an account, cloud backups, or Health access.
Information stored on your device
JIM stores your workout history, exercises, templates, programs, notes, profile settings, food diary, custom foods, nutrition targets, goals, and body measurements locally. Selected profile photos and original imported files are also stored locally. You choose what to enter. Local data may also be included in device backups managed by your operating system.
Using JIM without an account does not mean every feature is offline: food searches, the shop, purchase services, and opening web links can contact their respective providers.
Accounts and cloud backups
If you create an account, Supabase processes your email address, authentication credentials, account identifier, and profile metadata to provide sign-in and cloud storage. Authentication and email-delivery providers process the email address and message information needed for verification, account recovery, and other account-related emails.
Backup controls are being updated to require an explicit choice before uploading. In versions with the new consent prompt, backups stay off until you enable them for that account on that device, after a disclosure of the information uploaded. Earlier TestFlight versions enabled automatic backups when you signed in unless you turned them off. Updating to the new controls requires a fresh choice; it does not delete copies already stored in the cloud.
When backups are enabled, JIM uploads a copy of your workout data and profile settings, food diary, custom foods, nutrition targets and goals, and manually entered bodyweight and body-fat measurements to Supabase. Backups can therefore contain sensitive fitness and nutrition information. Local photo files and original imported files are not uploaded in backups. Health-imported weight and body-fat entries are excluded from the backup’s measurement records; backups are not a copy of your entire health database.
Cloud backups provide recovery through an explicit restore; they are not continuous synchronization between devices. The service keeps the latest three backup revisions and removes older revisions when a new backup is saved. Turning backups off stops future automatic uploads; it does not delete existing backups. Signing out leaves your local data on the device.
Health, Watch, and device permissions
With your permission, JIM reads or writes supported information through Apple Health or Android Health Connect, such as workouts, activity, sleep, nutrition, and body measurements. The categories used depend on the platform, feature, and permissions you grant. This information supports your fitness tracking and related calculations. Paired Watch features exchange workout state with your phone, and widgets use shared storage on your device.
JIM does not use health information for advertising or sell it, and does not send your workout or health metrics to RevenueCat. You can change health permissions in the platform’s settings. Revoking access does not automatically erase records already saved in JIM or your health app; manage each separately.
Camera access is used when you scan a food barcode. Choosing a profile image lets JIM store the selected image locally. Notification permissions support reminders and workout alerts. You can change these permissions in device settings.
Food searches
Food search terms and scanned product barcodes are sent to Open Food Facts to retrieve product and nutrition information. Its servers receive ordinary request metadata, including your IP address. This lookup does not upload your complete food diary. Open Food Facts handles its service data under its privacy policy.
Purchases
Apple processes App Store payments; I do not receive your full payment-card details. RevenueCat helps verify purchases, manage subscriptions, and understand purchase activity. It processes purchase and receipt information, app-user identifiers, and information needed to operate its SDK and service.
You can buy and restore without an account. When you first buy or restore without signing in, JIM creates a random purchase identifier with no name or email address, stored in your device’s secure storage, so purchases can be verified and restored. If you later sign in, purchases made with that identifier move to your account. Restoring uses your Apple Account’s purchase history.
Supabase stores verified purchase transactions and program ownership so purchases can be fulfilled, restored, and protected against fraud. TestFlight transactions are recorded separately from real App Store purchases. See RevenueCat’s privacy policy and Apple’s privacy policy.
Sharing and exports
Creating a hosted sharing link uploads the selected workout or program content to Supabase. Anyone with an active link can view or import that content, so include only information you intend to share. Links normally expire after 90 days and can be revoked earlier. Expiration or revocation stops access through the link; it does not immediately delete the stored record or retract copies someone already downloaded. Old expired or revoked records are eligible for cleanup after 30 days, with cleanup performed during later link creation.
If you receive a shared plan, you can report it or block its sender. A report stores the link, the reason you chose, any details you add, the time, and your account identifier if you are signed in; reported plans are hidden while I review them. Blocking keeps an anonymous sender identifier on your device only. Senders agree to sharing rules before their first link, and accounts that break them can lose sharing.
Exporting a file sends it to the destination you choose through your device’s sharing tools. That destination’s privacy practices apply to its copy.
How information is used and protected
Information is used to deliver the features above, support you, recover accounts, maintain service reliability, and prevent abuse. JIM does not contain advertising SDKs or sell personal or health information. Service providers process information for these functions; infrastructure providers may retain request and error logs, including network and account identifiers, for operations and security. Information may also be disclosed when legally required.
Cloud connections use HTTPS and access controls restrict account data. No storage or transmission method can guarantee absolute security. Providers may process information outside your province or country. Supabase’s practices are described in its privacy policy. This policy page itself is hosted on Firebase and loads Google Fonts; those requests expose normal network metadata to those services.
Retention, deletion, and your choices
Local information remains until you remove it, wipe JIM’s local data, or remove the app, subject to any device backups or copies you have made. Cloud account information and current backups remain while your account exists unless removed through the available controls. Backup and sharing retention are described above.
To delete your cloud account, open Settings → Account & cloud → JIM account → Delete cloud account. This removes your authentication account, cloud profile, backups, hosted shares, and account-linked program ownership. It does not wipe this device’s local data; use Wipe all local data separately. Deleting a cloud account also removes access to its future owned-program downloads; installed local copies remain.
When you delete your cloud account, JIM also requests deletion of the associated RevenueCat customer record. RevenueCat processes that request asynchronously. Some transaction records are retained without the deleted account identifier to prevent purchase replay. Apple and other providers may retain records under their own policies and legal or fraud-prevention obligations. If you used purchases without an account, contact me to delete the purchase identifier’s records. You can request assistance with access, correction, or deletion of provider-held information at kobeydevapps@gmail.com. Deleting JIM or its account does not cancel an Apple subscription or erase Apple Health records; manage those through Apple’s settings and Health app.
You can use local features without an account, disable automatic backups, revoke device permissions, and choose what you share. Depending on your location, you may have rights to access, correct, export, or request deletion of personal information. Contact me to make a request; I may need to verify account ownership before acting.
Consumer health data
Some laws, including Washington’s My Health My Data Act and Nevada’s consumer health data law, treat fitness and nutrition information as consumer health data. For JIM, that includes the workouts, activity, body measurements, sleep, nutrition, and goals you enter or allow JIM to read from Apple Health or Health Connect, and estimates calculated from them.
- Why it is collected: to provide the tracking, progress, and recommendation features you use. It stays on your device unless you choose to enable cloud backups or share a plan.
- Sources: you, and Apple Health or Health Connect when you grant access.
- Sharing: with your consent, Supabase stores backups you enable and plans you choose to share. It is not shared with RevenueCat, advertisers, or data brokers, and it is never sold.
- Your rights: you can confirm, access, and delete this data, withdraw consent by turning off backups or Health access, and contact me at kobeydevapps@gmail.com. Appeals of a decision can be sent to the same address.
Users in the European Economic Area, UK, and Switzerland
I rely on contract to provide the features you request, your explicit consent for cloud backups and Health access (which you can withdraw at any time in the app), and legitimate interests for security and fraud prevention. Providers such as Supabase and RevenueCat may process information in the United States and other countries under appropriate safeguards such as standard contractual clauses. You may access, correct, export, restrict, object to, or delete your information, and you may complain to your local data protection authority.
Children
JIM is intended for people aged 16 and older and is not directed to children. If you believe a child under 16 has provided personal information to the cloud service, contact me so I can investigate and delete it.
Contact and updates
For privacy questions or requests, contact Kobey Buhr in Winnipeg, Manitoba, Canada at kobeydevapps@gmail.com.
I will update the date above when this policy changes and provide additional notice when appropriate. Use of JIM is also governed by the JIM Terms of Use. The other apps and website policy covers the rest of this site.