EatLah Privacy Policy

1. Who we are

Intraverse Software Ltd is the developer and data controller responsible for EatLah. We are a company registered in England and Wales under company number 17413062, with registered office at 124 City Road, London, England, EC1V 2NX.

Privacy contact: dev@intraversesoftware.tech.

2. Information EatLah uses

EatLah does not ask you to register with a name, email address or password. Continuing in the app creates an anonymous Supabase Auth user identifier and session credentials, which the app stores on your device so it can recognise the same installation later.

Depending on how you use EatLah, we process:

• App language, preferred search radius, budget, dietary preferences, halal preference and familiar-versus-new preference.
• Food intent such as cuisine, dish, mood, spice, price, distance, occasion, dietary and halal choices. Free-text requests are converted into a structured food intent; the raw wording is not stored in EatLah’s database.
• Recommendation sessions, ordered provider place identifiers, suggestions displayed, selections, alternatives, skips or rejection reasons, directions opened, “love”, “been here”, post-visit feedback and learned taste affinities.
• Coarsened location stored with a recommendation session, as explained below.
• First-party product and reliability events linked to the anonymous identifier, session or request identifier.
• Optional menu or photo contributions, including submitted restaurant or dish details, permission confirmation, files, optional public credit and a private business contact email where a restaurant submits content.

3. Location information

EatLah requests foreground location only when you ask it to find nearby food. It uses balanced device location and does not register background or continuous location tracking. Your current coordinates are used for availability checks and nearby search. Google receives a search centre, radius and relevant food query to return nearby places.

EatLah stores recommendation-session coordinates rounded to three decimal places—roughly a neighbourhood-scale point rather than a precise movement trail. It does not build a continuous location history.

4. Food preferences and recommendation activity

We use your stated preferences and previous interactions to filter, rank and improve suggestions, show past choices and reduce repeated unsuitable results. Rejection reasons such as “too far”, “too expensive”, “not in the mood” or “been here” can update the relevant preference or familiarity signal. EatLah does not require a named user account for this personalisation.

5. Analytics and diagnostics

EatLah uses first-party beta telemetry stored in its Supabase database. This includes event names, anonymous user/session/request identifiers, timestamps, coarse beta-area labels, selection position, rejection or failure category, provider operation type, field tier and billing quantity. It helps us understand whether suggestions are useful, diagnose failures, measure return use and estimate provider cost.

Telemetry does not contain raw typed requests, voice recordings, exact coordinates, prompts, authentication tokens or Google response payloads. Vercel and Sentry may process limited error, performance, device and operational diagnostics needed to deliver, secure and troubleshoot the service. We configure error reporting not to intentionally send food-request text, precise coordinates, credentials or contribution files.

6. Voice, reminders and device storage

If you choose voice input, a recording is sent through EatLah’s authenticated API to OpenAI for transcription. EatLah does not save the raw audio in its database or object storage, and the temporary recording is deleted from the device after success or failure. The editable transcript then follows the same flow as typed text.

If you opt into a visit reminder, it is scheduled locally on your device. EatLah does not register a push token or subscribe you to marketing notifications. Pending reminder state—including the chosen provider place identifier and restaurant name—expires after seven days and is cleared when answered, dismissed or your EatLah data is deleted. The app also stores its session, language and onboarding state locally.

7. Third-party services

• Supabase provides anonymous authentication, database and private file storage for EatLah-owned data.
• Google Places / Google Maps supplies nearby place results, place details, map links and, when enabled, photo previews. EatLah stores provider place identifiers but does not persist or cache Google response content as its own place database.
• OpenAI processes free-text food requests to create structured intent and processes audio when you choose transcription. Service credentials remain on EatLah’s server.
• Our API and hosting providers process requests and limited operational logs needed to deliver and secure the service.

These providers process information under their contracts and privacy terms. We do not sell your information or use it for third-party advertising.

8. How information is used

We use the information above to provide and personalise EatLah, remember choices, show nearby results, handle support and privacy requests, operate optional contributions, prevent abuse, diagnose problems, measure the beta and improve reliability. Our legal bases depend on the activity and may include providing the service you request, our legitimate interests in operating and improving a privacy-conscious beta, consent for device permissions, and compliance with law.

9. How long information is kept

User-linked preferences, recommendation history and learning signals remain while the anonymous EatLah user exists, unless you delete the data sooner. First-party analytics and reliability events are retained for up to 24 months. Pending on-device visit-feedback state expires after seven days. Raw voice recordings are transient and are deleted from the device after the transcription attempt; EatLah does not retain them in its database or file storage.

Incomplete contribution uploads expire after two hours. Completed contributions that remain pending are deleted after 90 days, and rejected contributions and their private files are deleted after 30 days. Approved, non-user-specific content may be retained as explained below. Backups, fraud-prevention records and provider-side processing may have separate, limited retention periods.

10. Your choices and controls

You can decline location, microphone, photo, camera and notification permissions in device settings, although the related feature will not work. You can edit saved preferences in EatLah, avoid voice input or contributions, and contact us about privacy rights that apply to you.

11. Deleting or resetting your data

In EatLah, open Preferences → Your data → Delete my EatLah data. This deletes the anonymous Auth user and cascades through linked preferences, affinities, sessions, events, telemetry, pending contribution records and private uploads. It also clears the active local anonymous session and pending visit-reminder state. A new anonymous identifier is created if you continue using EatLah.

Shared provider place identifiers, separately reviewed non-user-specific restaurant information and statistics that can no longer be linked to the anonymous user may remain. See Manage your EatLah data for external instructions.

12. International processing

EatLah is available across Malaysia and is developed by a UK company. Its primary application and database regions are in Singapore, while OpenAI, Google, Vercel, Supabase, Sentry and their subprocessors may process information in the United Kingdom, Malaysia, Singapore, the United States or other countries. Where required, we use contractual and organisational safeguards for international transfers.

13. Children’s privacy

EatLah is not designed for children under 13 and does not knowingly ask for a child’s name, contact details or date of birth. Contact us if you believe a child has provided personal information through an optional contribution or support message.

14. Changes and contact

We may update this policy as EatLah develops. We will change the date at the top and provide an appropriate notice for material changes.

Questions or privacy requests: dev@intraversesoftware.tech. You can also visit EatLah Support.