Privacy Policy

Food Log Data: Food names, macros, servings, dates, meal types, weigh-ins, nutrition targets, and weekly check-in history are stored locally on your device and optionally synced via iCloud.

HealthKit Integration: With your explicit permission, the App reads your body weight, strength workouts, and energy burn from Apple HealthKit and writes your logged dietary samples (calories, protein, carbohydrates, fat) back so other apps can see your intake.

Food Search and Barcode Requests: Search terms and barcodes are sent to the Compound Fuel backend. The backend searches its local food corpus first and may query food-data providers when local results are insufficient. To improve result ordering, we store de-identified selection feedback containing the normalized query, selected food identifier and rank, top-result identifiers, and request time for up to 90 days. Access logs may also contain request time and IP address for reliability, abuse prevention, and debugging. These records are not joined to your food log, iCloud identity, or an advertising identifier.

Meal Photos: If you choose the Pro meal-photo feature, the App creates a compact JPEG and sends it to the Compound Fuel backend over TLS. The backend forwards the image through OpenRouter to Google Gemini on Google Vertex using a zero-data-retention processing route. Compound Fuel does not write the source photo to backend storage. The structured estimate returns to the App for your review; only foods and macros you explicitly confirm are added to your log.

iCloud Sync: If enabled, your food log is encrypted and stored in iCloud to sync across your Apple devices. iCloud syncing uses Apple's end-to-end encrypted database.

Subscription Verification: Apple-signed StoreKit transaction information and App Attest proofs are processed to verify Pro access and protect the meal-photo endpoint. Raw transaction assertions and meal photos are not written to application storage.

Compound Fuel does not collect or use:

• Advertising identifiers such as IDFA
• Precise or coarse location
• Contacts, browsing history, or advertising profiles
• HealthKit data on our backend
• Meal photos for advertising, model training, or cross-app tracking

We do not sell personal data and do not run third-party advertising SDKs.

Apple provides CloudKit, HealthKit, StoreKit, App Attest, and App Store distribution. Food searches may query USDA FoodData Central, Open Food Facts, Nutritionix, or FatSecret when the local corpus is insufficient.

Meal-photo analysis uses OpenRouter as the model gateway and Google Gemini on Google Vertex as the inference provider. The route is configured for zero data retention. These services receive the compact meal image and request instructions only to produce the estimate.

Compound Fuel does not use third-party advertising or cross-app tracking services.

Your food log is stored on your device until you delete it. Synced data remains in your iCloud account according to your Apple account settings.

Meal photos are held in memory only for the analysis request and are not written to Compound Fuel storage. De-identified food-search selection feedback is retained for no more than 90 days. Backend access and diagnostic logs are retained only as needed for service reliability, security, abuse prevention, and troubleshooting, then removed through infrastructure log rotation.