Privacy Policy

Developer: Omnivore Studio, operated by Tanatas Srisuksai, Thailand
Privacy contact: omnivorecodex@gmail.com

1. What this policy covers

OMNIVORE CODEX (the App, we, us) is a food-discovery and sensory-recording app. This policy explains the information the App accesses or collects, why it is used, the service providers involved, how long it is kept, and how you may request deletion.

2. Account and identity

You may use the App without providing your real name, email address, or phone number. The App creates an anonymous Firebase account with a random user identifier so that your records can be saved. You choose a callsign (a nickname displayed in the App). Do not use your real name if you do not want it associated with your activity.

3. Information the App accesses or collects

Account and user-provided information

• Anonymous Firebase user identifier.
• Callsign or nickname that you enter.
• Food and sensory records that you submit, including taste or mastery scores, dish or menu names, restaurant or place records (called Gates), timestamps, and progression information.

Location

With your permission, the App accesses your precise location while the App is in use. It uses location to centre the map, find nearby restaurants or Gates, and support on-location features. A restaurant or Gate location and the anonymous identifier of the user who charted it may be stored when a Gate is created. The App does not provide continuous background-location tracking and does not show your current live location to other users.

You can deny or withdraw location permission in Android or iOS settings. Search may remain available, but nearby-map, mark-here, or on-location features may not work.

Photos and user content

When you choose to photograph or select a dish image, the App uploads that image to private account storage so it can create and preserve the reading. Other users do not receive access to the original dish image in the current MVP. Dish names and Gate names may contribute to shared place history.

App activity, diagnostics, and identifiers

Release builds include Google Analytics for Firebase and Firebase Crashlytics. Firebase may collect app-instance or device identifiers, approximate geography derived from network information, app opens, sessions, screen or feature interactions, device model, operating-system information, crash reports, and diagnostic or performance information. Android advertising-ID collection is disabled and advertising/attribution-ID permissions contributed by the Analytics SDK are removed from the App manifest. We use this information for analytics, reliability, and improvement—not to show ads or sell personal information. The App's diagnostic events exclude callsigns, email addresses, precise coordinates, photos, dish names, sensory values, free text, and record identifiers.

Purchases and patronage

If voluntary patronage is available and you choose to purchase it, Apple App Store or Google Play processes the payment. RevenueCat receives the store product, transaction and receipt information, App platform, and the App's pseudonymous user identifier so it can validate and restore purchases. We do not receive your full payment-card details. Patronage does not unlock readings, history, sync, export, progression, Rank, rarity, EXP or other gameplay power.

4. How we use information

We use the information described above to:

• authenticate an anonymous session and save your records;
• provide the map, nearby-place search, Gate creation, sensory recording, and progression features;
• create shared or aggregated dish and place patterns without displaying your live location;
• maintain security, diagnose failures, measure use, and improve the App; and
• comply with legal obligations and enforce applicable terms.

We do not use precise location for advertising.

5. Service providers and disclosure

The App uses service providers that process information to operate the App:

• Google Firebase — anonymous authentication, database hosting, analytics, and related diagnostics;
• Google Maps Platform and Places — maps, place search, restaurant information, and location-based results;
• Google Play — distribution, app integrity, payments, and platform services;
• Apple — iOS distribution, TestFlight, App Store payments, and platform services; and
• RevenueCat — validation and restoration of voluntary patronage purchases when that feature is configured.

These providers process data under their own terms and privacy documentation. We may also disclose information if required by law, to protect users or the App, or as part of a lawful business transfer with appropriate safeguards.

We do not sell personal information. We may use or disclose statistics that have been aggregated or de-identified so that they no longer identify an individual.

6. Visibility to other users

The current MVP does not provide chat, direct messaging, comments, or live-location sharing. Restaurant or Gate records and aggregated sensory results may be visible within the App. A charted Gate may be associated with a pseudonymous callsign or anonymous account identifier. Do not put personal information into a callsign, dish name, or Gate name.

The App filters obvious prohibited text before publication. You can report a public dish record for review and optionally block its author, which hides that Hunter's public records from your own Gate history. Blocking does not create a public label. You can review or reverse blocks under Settings → Blocked Hunters. We may hide content or restrict accounts when reasonably necessary to address abuse, safety, legal obligations, or these Terms.

7. Retention and deletion

We retain account and submitted records while they are needed to operate and secure the App, unless a longer period is required by law. Analytics retention is governed by our Firebase configuration and Google’s applicable controls.

You can permanently delete your anonymous account and associated personal readings in the App under Settings → Delete my data. Shared Gate records may remain after the account identifier and personal attribution have been removed, so that records used by other Hunters are not broken. You may also email omnivorecodex@gmail.com. We will delete or de-identify associated personal data unless retention is legally required. Aggregated or irreversibly de-identified information may remain.

8. Security

We use HTTPS/encryption in transit provided by the platform and access controls for backend services. No security method is perfect, and we cannot guarantee absolute security. If we become aware of a material incident, we will respond in accordance with applicable law.

9. Children

The App is intended for adults aged 18 or older and is not directed to children. We do not knowingly collect personal information from children. If you believe a child has provided information, contact us so that we can investigate and delete it where appropriate.

10. International processing and your rights

Google and other service providers may process information outside Thailand. Depending on where you live, you may have rights to request access, correction, deletion, restriction, objection, or portability, or to complain to a data-protection authority. Contact us to exercise an applicable right.

11. Changes

We may update this policy as the App changes. We will publish the revised policy and change the effective date. Material changes may also be communicated in the App or through the store listing where appropriate.

12. Contact

Privacy questions and requests: omnivorecodex@gmail.com