Privacy policy

Information stored on your device

Your personal Food-Dex is stored locally on your iPhone and, after you sign in, eligible Dish Logs can sync privately to Foodex. It may include Dish Logs, original photos, transparent food stickers, ratings, notes, saved places, capture dates, and collection progress.

Creating or syncing a Dish Log does not publish it. Sharing to the Feed, submitting public media, and contributing to the catalogue are separate actions with their own controls.

Catalogue data

Foodex downloads the current dish catalogue from a Foodex service and caches it on your device. Catalogue entries are product content, not your personal Dish Logs. A failed refresh may continue using a complete cached catalogue.

Accounts and profiles

Foodex uses Convex to provide accounts and connected features. If you sign in with Apple or Google, Foodex receives the provider account identifier and may receive your email address. Google may also provide your name and profile image. Foodex stores the unique username and optional profile image you choose for public community surfaces. Apple and Google process sign-in under their own privacy terms.

Dish Logs and connected features

A signed-in player's private Dish Logs can sync through Convex. Synced fields may include the Dish identity, capture time, rating, restaurant or place name, private note, coarse country or region, collection progress, and bounded capture-integrity status. Exact coordinates are not uploaded to Foodex.

Community features store the actions needed to operate them, such as Feed consent, the public fields you choose to share, reactions, saves, friendships, blocks, rankings, contributions, reports, and appeals. Private Dish Log fields are not made public unless the sharing screen specifically offers that field and you include it.

Camera, photos, and recognition

• Camera access is used only when you choose to photograph a dish.
• Photo Library access is limited to photos you select.
• Current dish recognition starts with on-device image analysis.
• Hosted recognition redraws the image without EXIF, GPS, Photos identifiers, or the original file metadata, then sends that redraw to Foodex through Convex and to Google's Gemini service.
• A permitted recognition input and its bounded recognition record are stored privately by Foodex and linked to your Foodex identity. A content-policy-blocked image is processed by Gemini but is not stored as Foodex media.
• When private media sync runs for a signed-in account, Foodex may store a redrawn original receipt and personal sticker privately. Public Feed or catalogue media requires a separate sharing action.

Location

Location is optional. If you allow it for a capture, Foodex can save exact coordinates with the local Dish Log and may use Apple MapKit to suggest a nearby place. Foodex does not upload exact coordinates to its servers. A derived coarse country or region and a place name you accept may sync with the private Dish Log and may appear publicly only when you explicitly share that field. Foodex does not use location for advertising or tracking.

Purchases

Apple processes App Store purchases. Foodex uses RevenueCat to check and restore subscription entitlement. RevenueCat receives purchase history together with an assigned Foodex customer identifier, so Foodex declares purchase history as linked to your Foodex identity. It is used for app functionality, not advertising or tracking.

Analytics and advertising

Foodex does not use advertising identifiers, third-party advertising, or cross-app tracking. The release app does not send a general event property bag to an analytics SDK. Recognition inputs and the resulting selection record may be reviewed to evaluate and improve recognition; they are not used for advertising.

Service providers

Foodex uses Convex for accounts, server data, and media storage; Apple and Google for sign-in; Google Gemini for hosted recognition and media screening; RevenueCat for purchase entitlement; and Apple for App Store purchases and MapKit. These providers process only the data needed for the feature being used under their applicable terms.

Retention and your controls

You can remove individual Dish Logs, erase the local Food-Dex, revoke camera, photo, or location permissions in iOS Settings, and manage App Store subscriptions through Apple. Connected data is retained while needed to provide the account and feature, unless a shorter period is stated in the app. Recognition inputs remain private until the associated Foodex cloud identity is deleted. Inactive anonymous cloud identities enter deletion after 90 days. Raw linked growth receipts, when release collection is enabled, expire after 90 days.

In-app account deletion removes or anonymizes connected account, Dish Log, media, social, and provider data as described in the deletion screen. Valid catalogue publications and safety audit history may remain without your identity. Deleting a Foodex account does not cancel an Apple subscription, and it does not erase the local Food-Dex on that device.

Website language preferences

Foodex uses your browser's preferred languages to choose a supported website language. If none is supported, we use the hosting provider's country code as a fallback. When you choose a language manually, we store that choice in the first-party functional foodex-language cookie for up to one year. This cookie is not used for advertising or tracking.

Contact

Questions about privacy can be sent to admin@evergoodsholdings.com.

Developer: Evergoods Holdings LLC.