What Food Diary currently stores and how deletion works.

Food Diary currently processes and stores the following categories of data:

• Meal photos uploaded to create diary entries and normalized before storage.
• Derived food metadata such as dish description, ingredient list, calories, meal type, and eaten-at date.
• Installation identifiers used to authenticate one app installation.
• App platform and app version details attached to an installation.
• Subscription state stored for that installation.

• Application data is stored in PostgreSQL on the server.
• Uploaded meal photos are normalized to a resized PNG and stored behind private storage instead of a public static directory.
• Photo reads are delivered through short-lived signed URLs generated by the backend or object-storage provider.
• Some installation credentials also live on the device so the app can authenticate that installation.

Food Diary strips image metadata other than GPS location tags during normalization. If an uploaded source image contains GPS EXIF data, that location metadata may be retained in the normalized PNG stored by the app.

Food Diary does not have a cross-device user account model yet. Data ownership is tied to an individual app installation.

• Single entries can be deleted from the app.
• Full installation deletion is initiated inside the native app from the Subscription screen using the Delete my data action.
• Installation deletion removes that installation's app data, but it does not cancel App Store or Google Play subscriptions.

For privacy questions or requests, contact support@fooddiary.app. This mailbox is also the public support contact for billing, restore-purchase, and app-issue triage.