Your records stay yours.
Last updated: 21 August 2026
Loggy stores your workout, nutrition, hydration, weight, recovery, and template records on your iPhone. It does not automatically upload those records to iCloud or use them for advertising or tracking.
At a glance
- No Loggy account is required.
- Your core fitness and health records are stored locally on your device.
- Apple Health access is optional. Loggy may read selected data and, with separate permission, write completed workouts.
- Loggy sends privacy-preserving usage analytics automatically. Other network requests happen when you use an online feature.
- Loggy does not sell personal data and does not track you across apps or websites.
1. Information stored on your device
Depending on the features you use, Loggy may store:
- workouts, exercises, sets, repetitions, loads, durations, routines, and training history;
- food entries, calories, macronutrients, hydration, meal labels, and nutrition targets;
- weight entries, optional progress photos, goals, and trend data;
- recovery check-ins, reminder choices, weekly check-in preferences, and app settings;
- optional onboarding details such as your profile name, age, height, weight, activity level, and calorie-equation choice.
These records use Apple's local app storage technologies and standard iOS device protection. Loggy does not write them to CloudKit. You can remove records inside the app, use the app's reset controls, or delete the app to remove its local data.
2. Apple Health
If you choose to connect Apple Health, Loggy requests read access to activity and workout information used by the dashboard and related features. Permission is optional, can be limited by data type, and can be withdrawn in the Health app or iOS Settings.
If you enable workout syncing, Loggy also requests permission to write completed workout records, including completed runs, to Apple Health. Apple presents read and write permissions separately. Loggy does not upload your raw Apple Health database to Loggy's servers.
3. Usage analytics and optional online features
Usage analytics
Loggy initializes TelemetryDeck when the app starts. It automatically sends analytics signals on app launch, at the start of a new app session, and when selected actions occur. Those actions include fixed events such as progressing through onboarding, opening the planner, starting or finishing a workout or run, logging a meal, completing a weekly review, using a sharing or AI entry point, viewing a paywall, and completing a purchase. This helps Loggy understand aggregate activation, feature use, retention, and purchase-funnel performance so the app can be improved. It is not used for advertising or tracking you across other apps or websites.
An analytics signal can contain the event name; a fixed category such as the selected onboarding intent, session kind, meal source, share-card kind, paywall trigger, or purchased product identifier; the event time; a random session identifier; and SDK-provided app and device metadata. That metadata can include the Loggy and TelemetryDeck SDK versions, build number and distribution channel, device model and architecture, iOS version, screen characteristics, language, locale, region, time zone, selected accessibility or calendar settings, and aggregate session timing and count information.
To count repeat use without a Loggy account, the SDK derives a per-vendor device identifier from Apple's identifierForVendor and hashes it on the device before transmission. TelemetryDeck hashes that value again on its service. Loggy does not give TelemetryDeck your optional profile name, contact details, advertising identifier, Apple Health data, food or workout text, sets, repetitions, loads, calorie or macro values, weight, recovery answers, photos, precise location, or App Store transaction identifiers or signed proofs. Pending analytics signals may be cached on the device when a network connection is unavailable and retried later.
Features you choose to use
Core tracking works without these features. When you deliberately use an online feature, Loggy sends the minimum content needed to answer that request over HTTPS.
| Feature | Information sent | Why it is sent |
|---|---|---|
| AI meal estimate | Your meal description and selected meal category. | To return editable calorie and macro estimates. |
| AI photo meal analysis | The compressed meal-photo bytes, selected meal category, optional caption, a stable pseudonymous quota identifier, and—when claiming paid allowance—Apple-signed subscription and app transaction proofs. | To identify foods, return editable calorie and macro estimates, enforce an abuse limit, and verify paid allowance. |
| AI workout import | The workout text you paste or enter. | To turn the text into an editable workout draft. |
| Progression and coaching | Relevant exercise names, sets, reps, loads, targets, and recent performance. | To generate progression or coaching guidance you requested. |
| Weekly review | A relevant summary of workouts, nutrition, weight trends, goals, and recovery check-ins. | To generate the requested weekly review. |
| Food search | Food search terms or barcode identifiers. | To return matching food and nutrition information. |
| Community corrections | Food name and corrected nutrition values, only after you opt in. | To improve shared food results. |
Optional profile names, contact details, precise location, advertising identifiers, and weight-progress photos are not included in these requests. A meal photo is included only when you deliberately use AI photo meal analysis. Loggy does not use request content to build advertising profiles or to train a Loggy-owned general-purpose AI model.
AI photo quota identifier
The AI photo request includes a persistent pseudonymous identifier. For someone with an active App Store subscription, the app uses Apple's original transaction identifier; otherwise it uses a random installation identifier stored in the device Keychain. The identifier is used to group photo usage into a monthly counter. It is not your name or payment-card number, but it can remain stable across requests and, for a subscription, across reinstalls or devices using that subscription. The service routes it through a one-way digest to an atomic quota ledger retained for about 45 days. Because this identifier alone is supplied by the app, the server never treats it as proof of payment.
To receive the paid server allowance, the app also sends an Apple-signed current subscription transaction and an Apple-signed app transaction. These proofs can include the product, purchase and expiry dates, original transaction and app-download identifiers, storefront information, app version, and related App Store fields. Loggy verifies their Apple certificate chain and signature, production environment, bundle ID, numeric App Store app ID and approved product using Apple's official App Store Server Library. Loggy also checks the current expiry and any revocation information contained in the signed transaction. The full signed proofs are processed for that request and are not written into the monthly quota record; a one-way digest of the verified original transaction identifier routes the request to its quota ledger.
4. Service providers and data sources
Cloudflare
Loggy uses Cloudflare infrastructure to deliver its online food and AI features. Cloudflare may process request metadata and content needed to operate, secure, and troubleshoot those services.
TelemetryDeck
Loggy uses TelemetryDeck GmbH to process the usage analytics described above. TelemetryDeck states that it rounds event times to the nearest hour on its analytics servers, does not store source network addresses, and hosts usage data in the European Union. Analytics signals are retained under the retention terms of Loggy's TelemetryDeck service plan. See TelemetryDeck's privacy FAQ and privacy policy.
AI processing providers
Loggy's service currently uses Anthropic to generate the photo analysis, estimate, import, coaching, or review you request. Request content, including meal-photo bytes when applicable, is provided for that app function, not for advertising by Loggy. Under Anthropic's standard commercial API terms, inputs and outputs may be retained for up to 30 days, subject to Anthropic's policy and legal or security exceptions. See Anthropic's retention information.
Open Food Facts
Food searches and verification may query the public Open Food Facts service. Open Food Facts database content is made available under the Open Database License (ODbL); individual database contents and product images may have additional applicable licences.
5. Community food corrections
Sharing a correction is optional. Loggy asks before the first correction is shared, and you can change the preference later in Settings. Shared corrections contain the food description and corrected nutrition values, not your optional profile name or a Loggy account identifier.
A new community food remains pending and is not returned to other users until at least three sufficiently similar submissions confirm it. Corrections may then be retained in aggregated form so that corrected results remain useful. While a candidate is pending, Loggy retains a short one-way fingerprint derived from the request's network address and a server-only secret so the same network cannot provide every confirmation. The raw network address is not stored in the food record, and the fingerprints are discarded when the candidate is confirmed. Turning sharing off prevents new corrections from being sent. For a deletion request, contact hello@loggyapp.com with enough detail for us to locate the correction where reasonably possible.
6. Purchases
Loggy Pro purchases and subscription status are handled by Apple through StoreKit. Loggy receives entitlement and product information needed to unlock Pro on your device, but does not receive your full payment-card details. As described above, an AI-photo request may send Apple's signed subscription and app transaction proofs so Loggy can verify paid allowance server-side. Invalid, expired, mismatched, non-production, unapproved-product proofs, and proofs carrying a revocation receive no paid allowance. Apple's privacy policy applies to App Store purchases.
Usage limits
Some AI features have fair-use limits. AI coaching and AI meal features are part of Loggy Pro. AI photo meal analysis has an atomic server-side monthly abuse ceiling which resets on the 1st. A client-supplied quota identifier receives only the free ceiling. Free traffic also shares a daily service safety ceiling so repeatedly changing an identifier cannot create unlimited provider use. A higher allowance is granted only after both Apple-signed proofs pass the checks described above. Other AI features may carry fair-use limits. These limits protect the shared AI service from misuse; they do not change how your information is handled.
7. Retention and security
Local records remain until you delete them or remove the app. Online requests use HTTPS. Service providers may retain analytics signals or limited request and security logs as described above and for the time needed to deliver, protect, and troubleshoot their services. Loggy does not promise that internet transmission is risk-free, but it limits online sharing to the analytics described above and features you choose to use.
8. Your choices and rights
- Use core tracking without connecting Apple Health or enabling notifications.
- Use Loggy without purchasing Loggy Pro.
- Avoid optional AI and community features.
- Withdraw Apple Health read or write access in iOS or the Health app.
- Turn community correction sharing off in Loggy Settings.
- Delete local records in the app or by deleting the app.
- Contact us to exercise applicable UK GDPR, EU GDPR, or other privacy rights.
9. Age and health guidance
Loggy is a general fitness tool, not a medical device and not a substitute for professional medical or dietary advice. Personalised onboarding calorie estimates are limited to adults aged 18 to 99. Loggy is not designed to knowingly collect children's personal information.
10. Changes and contact
We may update this policy when Loggy's features or service providers change. The date above identifies the current version.
Privacy questions or requests: hello@loggyapp.com
Loggy Framework © 2026 · Standard EULA