Privacy Policy — Loggy

Last Updated: June 2026
Effective Date: June 1, 2026

Overview

Loggy ("we," "us," "our," or the "App") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our iOS fitness and nutrition tracking application.

Please read this Privacy Policy carefully. If you do not agree with our policies and practices, please do not use the App.

1. Information We Collect

1.1 Health & Fitness Data (HealthKit)

When you grant permission, Loggy reads from Apple HealthKit:

Step count (daily steps, active minutes)
Workout data (exercise type, duration, calories burned)

You control what data Loggy accesses. You can revoke permission at any time in iOS Settings → Health → Data Access & Devices → Loggy.

We do not store HealthKit data on our servers. All health data remains on your device only.

1.2 Nutrition & Weight Data

You manually log:

Foods you eat (name, calories, macros, portion size, time)
Daily weight (in kg or lbs, with date/time)
Calorie & macro goals (your targets)

This data is stored locally on your device via SwiftData.

1.3 Workout Data

You manually log or import:

Exercise name, sets, reps, weight, duration
Workout templates (custom splits, exercise lists)
Workout history (completion date, performance metrics)

This data is stored locally on your device.

1.4 User Corrections & Community Data (Optional)

When you edit a food's nutrition (e.g., "this apple has 95 kcal, not 82"), you can choose to share that correction with other Loggy users. This is opt-in via an onboarding consent screen.

If you consent:

Your correction (food name, corrected calories/macros) is sent to our backend
It is stored in a Cloudflare KV database
Other users may see your correction if it meets our verification threshold (3+ users agree, and change ≤ 20%)
Your name/identity is never associated with your correction

You can revoke consent anytime in Settings → Data & Integrations. Previously shared corrections remain in the database but no new corrections will be sent.

1.5 Device Information

We collect limited technical data:

Device model, OS version (to debug crashes)
App version (to track compatibility issues)

2. Data Sources & Attribution

2.1 Open Food Facts

Loggy uses the Open Food Facts database (https://openfoodfacts.org) to provide ~139,000 UK food items and their nutrition.

Open Food Facts data is licensed under CC BY 4.0. You can use and modify this data freely, provided you attribute Open Food Facts.

2.2 AI Estimates (DeepSeek)

If you request an "AI estimate," Loggy uses the DeepSeek API to analyze a food description and return estimated nutrition.

What is sent to DeepSeek: Your text description of a food (e.g., "4 scrambled eggs with butter")
Not sent: Your identity, health data, previous logs, or location

DeepSeek's Privacy Policy: https://www.deepseek.com/privacy

3. How We Use Your Data

Data	Purpose
Nutrition logs	Display your nutrition ledger; calculate daily totals & macro tracking
Weight logs	Show weight history chart; calculate trends
Workout logs	Display workout history; track progressive overload
HealthKit (steps/workouts)	Display on dashboard; calculate activity metrics
User corrections	Improve food database accuracy for all users
Device info	Debug crashes; understand compatibility issues

We do not use your data for:

Advertising or marketing
Selling to third parties
Training AI models (except DeepSeek's own privacy terms)
Anything beyond running the Loggy app

4. Data Storage & Security

4.1 Local Storage (Your Device)

Nutrition logs, weight logs, workouts, goals: stored locally on your iPhone via SwiftData
Encrypted by iOS (standard device encryption applies)
Not synced to iCloud (currently local-only; future versions may add CloudKit sync)

4.2 Backend Storage (Our Servers)

Food corrections (optional): stored in Cloudflare KV database
Not linked to your identity
Encrypted in transit (HTTPS only)

4.3 Deletion

Local data: Delete by uninstalling the app or clearing app data in Settings
Backend corrections: Request deletion via hello@loggyapp.com; we will remove your corrections within 30 days

5. Third-Party Services

5.1 Cloudflare

We use Cloudflare Workers to host our food database backend.

What they see: Food searches, corrections (anonymized)
Privacy: https://www.cloudflare.com/privacy/

5.2 DeepSeek

Used only when you request an AI estimate.

What they see: Your food description text
Privacy: https://www.deepseek.com/privacy

5.3 Open Food Facts

Food database provider.

What they see: You query their public database (no personally identifiable info sent)
Privacy: https://world.openfoodfacts.org/privacy

We do not share your name, email, or identity with any third party.

6. Your Rights & Choices

6.1 Access Your Data

All your local data is stored on your device. You can export/view it anytime via the app or device settings.

6.2 Correct or Delete

Locally stored data: Delete via Settings or uninstall
Community corrections: Request removal at hello@loggyapp.com

6.3 Opt Out of Sharing

Revoke HealthKit permission: iOS Settings → Health → Data Access & Devices
Revoke corrections sharing: App Settings → Data & Integrations → toggle off

6.4 GDPR / UK GDPR

If you are in the EU/UK:

Right to access: Request a copy of your data
Right to deletion: Request we delete your corrections (local data is yours to delete)
Right to object: Stop sharing corrections
Data Portability: We can export your logs on request

Contact: hello@loggyapp.com

7. Children's Privacy

Loggy is not intended for children under 13 and we do not knowingly collect data from children. If we discover a child has provided information, we will delete it immediately.

8. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be effective when posted. Your continued use of Loggy means you accept the updated policy.

9. Contact Us

Questions or privacy concerns?

Email: hello@loggyapp.com