Privacy Policy — Flog

Last Updated: 09/2026

Flog is a photo-first nutrition log for iOS that can sync nutrition data to Apple Health and can run AI inference either on-device, on your local network, or via third-party cloud AI providers you configure — including an optional first-party option called Flog Cloud.

1) Summary

• No account required: Flog is designed to work without creating an account with us.
• Local-first by default: Meal photos, notes, and nutrition history are stored locally in the app’s container unless you choose features that involve other services (e.g., Flog Cloud, third-party cloud AI, iCloud export folder).
• You control AI sharing:
  • On-device inference: Data stays on your device.
  • Local-network inference (e.g., LM Studio): Data stays on your local network.
  • Third-party cloud inference (e.g., OpenRouter): Flog sends the content needed for inference to the provider you configure.
  • Flog Cloud (optional): Flog sends inference inputs to our servers, and we store certain content server-side and may use it to train and improve future AI models (details below).
• Usage analytics you can turn off: Flog records how the app is used (for example, which screens are opened or whether a meal analysis succeeded) to improve it. This never includes your photos, notes, or nutrition and health values, and you can turn it off in Settings.
• Apple Health is optional: Flog reads/writes Health data only if you grant permission, and you can revoke that permission at any time.

2) Information Flog processes

A) Content you provide

• Meal photos (captured in-app or imported from your Photo Library)
• Text notes you attach to meals (e.g., “half the fries,” “no bun”)
• Profile and preferences (e.g., region/cuisine context, finger/nail calibration values, targets)
• Exports/backups you choose to create (e.g., database + images packaged into an archive)

B) Nutrition data generated in the app

• AI estimates (meal title, item breakdown, macro/micro nutrients, reasoning text)
• Manual edits/overrides you make to nutrition values

C) Apple Health data (optional, permission-based)

If you grant permission, Flog may:

• Write nutrition samples to Apple Health (typically grouped as a meal/correlation)
• Read certain health metrics used for stats (e.g., latest body mass, energy burned), depending on what you enable

D) Device diagnostics (optional)

Flog may process limited diagnostic information:

• On-device logs for troubleshooting within the app
• Crash/diagnostic reports only if you choose to share them via iOS mechanisms or a support flow you initiate (if applicable)

E) Usage analytics (on by default, can be turned off)

To understand which features people use and where the app fails, Flog records app usage events, such as screens opened, buttons used, onboarding steps completed, whether a meal analysis succeeded or failed and how long it took, and settings changed. Events include coarse technical context such as app version, iOS version, device model, language, region, and which AI option you use.

• Analytics events never include meal photos, notes, food descriptions, nutrition values, Apple Health data, or profile values such as age, height, or weight.
• Events are tied to a random identifier created for your installation, not to your name or Apple ID. Flog does not use the advertising identifier (IDFA) and does not track you across other companies' apps or websites.
• Events are sent to Google Analytics for Firebase (operated by Google) and to our servers.
• You can turn analytics off at any time in Settings → Privacy → Share usage analytics. When it is off, Flog stops sending analytics events.

F) Flog Cloud identifiers and network metadata (only if you enable Flog Cloud)

If you enable Flog Cloud, we process additional data to operate, secure, and moderate the service:

• Flog Cloud “client signature”: A randomly generated cryptographic keypair (public/private) created by the app for your installation. This is not intended to be derived from your device identity. We use it as a pseudonymous identifier for moderation, abuse prevention, rate limiting, and enforcing bans.
• IP address of the network origin of requests (and related request metadata such as timestamps, request size, and basic technical logs).
• Service logs about Flog Cloud requests (e.g., which inference route/provider was used, success/error codes, latency).

3) How we use information

Flog uses your information to:

• Create and manage your meal log and nutrition history
• Run AI inference (on-device, local network, third-party cloud, or Flog Cloud)
• Sync nutrition data to Apple Health (when enabled)
• Provide statistics and trends (day/range views, nutrient breakdowns)
• Support backup/export and restore features
• Improve reliability and fix bugs (when you choose to share diagnostics)
• Understand how features are used, through usage analytics you can turn off (Section 2E)

If you enable Flog Cloud, we also use information to:

• Operate and secure Flog Cloud (including abuse prevention, moderation, and enforcement of our Terms)
• Store and process meal photos/notes submitted to Flog Cloud
• Develop, train, and improve our AI systems and models using content submitted to Flog Cloud (see Section 7)

4) Where your data is stored

• On your device: By default, meal photos, notes, nutrition entries, and AI results are stored locally in the iOS app container.
• Optional external folder (e.g., iCloud Drive): If you enable an export folder, Flog may copy or move images to that location. If that folder is in iCloud Drive, Apple may sync it across your devices under your Apple ID and Apple’s policies.
• Flog Cloud servers (optional): If you enable Flog Cloud, we store some or all of the inference inputs you submit (e.g., meal photos and notes) and related logs/metadata as described in this policy.
• Third-party partners (optional):
  • If you configure a third-party cloud AI provider (e.g., OpenRouter), that provider receives the inputs necessary for inference.
  • If you use Flog Cloud, we may route your request to third-party inference partners to produce results. Those partners may process the request content as part of providing inference.

5) When data leaves your device

Your data leaves your device only in these cases (depending on what you enable):

A) Flog Cloud (optional first-party cloud inference)

If you select Flog Cloud as your AI provider:

• Flog sends the necessary inputs for inference to our servers, which may include:
  • Meal photos and/or text notes
  • Your selected region/cuisine context
  • Any other inference context you enable (e.g., finger calibration, depth hints if used)
• We store content submitted to Flog Cloud server-side.
• We may route requests to third-party inference partners to generate results.
• We log IP address and process a client signature for moderation, abuse prevention, and enforcing bans.

Important: If you do not want your content stored server-side or used to train/improve models, do not use Flog Cloud. Prefer on-device or local-network inference, or configure your own third-party provider.

B) Third-party cloud AI inference (e.g., OpenRouter)

If you configure a third-party cloud AI provider, Flog sends the content needed for inference to that provider, which may include meal photos, notes, and context you enable.

Important: Third-party providers may log, store, or process requests according to their own terms. Flog does not control what those providers do with your data. Review the provider’s privacy policy before enabling third-party cloud inference.

C) Local network inference (e.g., LM Studio)

If you configure a local server on your network, Flog sends inference inputs to the server URL you provide. Data is transmitted over your local network to that machine.

D) Usage analytics

Unless you turn it off, Flog sends usage events (described in Section 2E) to Google Analytics for Firebase and to our servers. Google processes this data under its own terms and privacy policy.

E) Model downloads (e.g., Hugging Face)

If you download on-device models from a third-party host (such as Hugging Face), your device will connect to that host to fetch model files. This does not inherently upload your meal content, but the host may receive standard network metadata (e.g., IP address, user agent) as part of serving downloads.

F) Apple Health

When enabled, Flog writes nutrition data to Apple Health on your device. Apple Health data handling is governed by Apple and your device settings.

6) API keys and provider credentials

If you use “bring your own key” providers:

• Your API keys are provided by you and are used only to authenticate requests to the provider you selected.
• Keys are intended to be stored locally on your device (e.g., secure iOS storage) and are not sent to us.

Flog Cloud does not require you to bring an API key.

7) Data retention and deletion

Local data (default)

• Flog retains your local data until you delete it (or delete the app).
• You can delete individual entries or wipe app data using in-app controls.
• If Health sync is enabled, deleting or modifying entries may also delete/update corresponding Apple Health samples to keep things consistent.

Flog Cloud data (only if enabled)

• We may retain content submitted to Flog Cloud (including images and notes) to operate the service, prevent abuse, and develop/train/improve our models.
• We also retain logs such as IP address, timestamps, and the client signature for security, troubleshooting, and enforcement.

Deletion requests and limits (Flog Cloud)

• Because Flog does not require accounts and we do not seek to store identifying user information, you may be asked to provide your Flog Cloud client identifier (e.g., the public key/client signature shown in the app, if available) to help us locate and delete associated server-side data.
• If content has already been incorporated into trained model weights or aggregated datasets, we may not be able to remove that influence retroactively, but we will delete stored raw records when feasible.

Exports/backups

• If you create an export archive or store images in an external folder, you control those files. Deleting data in Flog does not automatically delete copies you exported elsewhere.

8) Sharing and selling

• We do not sell your personal data.
• We do not share your meal content with third parties unless you enable a feature that requires it, including:
  • Flog Cloud (our servers + possible routing to inference partners)
  • Third-party cloud AI providers you configure (e.g., OpenRouter)
  • Local-network inference servers you configure
  • Cloud storage you choose (e.g., iCloud export folder)
• Usage analytics events (which never contain meal content) are processed by Google Analytics for Firebase as our service provider.
• We may share information if required to comply with law, respond to lawful requests, or to report illegal content and protect users and the public.

9) Tracking and advertising

Flog does not track you across other companies' apps or websites, does not use the advertising identifier (IDFA), and does not show ads. Usage analytics (Section 2E) is used only to improve Flog and can be turned off in Settings.

10) Security

Flog relies on iOS security features (app sandboxing, device encryption when enabled, system permission controls). If you enable cloud features (including Flog Cloud), data is transmitted over the network and stored on servers; no method of storage or transmission is 100% secure. Avoid enabling cloud inference if you are not comfortable sending meal photos/notes over the network.

11) Children’s privacy

Flog is not intended for children under 13 (or the equivalent minimum age in your jurisdiction). We do not knowingly collect personal information from children.

12) Changes to this policy

We may update this Privacy Policy from time to time. The “Last Updated” date above indicates the latest revision. Material changes will be reflected in the app and/or our website.

13) Contact

For privacy questions or requests, contact: [email protected].