Privacy Notice

Effective and last updated: 16 September 2026

This Notice explains what the current experimental free Gemlah service processes, why it is used, which providers are involved, and how to request access, correction or deletion.

Operator and contact

Gemlah is currently operated by an individual in Malaysia. Send privacy questions and verified access, correction or deletion requests to gemlahteam@gmail.com. Do not send passwords, verification codes, cookies, tokens or unnecessary identity documents.

Information processed

• Guest and account identifiers: an anonymous browser identifier, its server-side hash, Supabase user ID and Google account identity used for sign-in.
• Search and location: the dish or restaurant query, typed area or coordinates submitted for a nearby search, selected distance and request identifiers.
• Saved places and activity: Google Place IDs, Favourite and Want to Try state, search-session identifiers, recommendations shown, details opened, saves and navigation actions.
• Operational records: quota counts, timestamps, request digests, security/error information, issue reports and communications needed to operate, protect and review the service.

How information is used

Gemlah uses this information to provide nearby search and matching, enforce usage limits, prevent duplicate or abusive requests, maintain saved choices and account continuity, recover unresolved attempts, secure and troubleshoot the service, respond to privacy or correction requests, and preserve evidence where a dispute or legal obligation requires it. Gemlah does not sell personal data.

Feedback and support

When you send feedback, we store your message, category, submission time, guest or account identifier, page category, app version and mobile or desktop category. If you request an email reply, we also store the reply address you confirm. Feedback is private to authorised administrators, who may record ticket status, department, assignment and reply drafts. It is not published as a restaurant review or used for marketing. The form does not automatically include precise location or search history. Avoid putting sensitive personal information in your message. Retention and deletion follow the section below.

Location and search handling

Browser location is requested only when location functionality is used. You may decline and type an area instead. When you submit a search, the query and location are sent through Gemlah to Google Places. Precise coordinates or query text are not intentionally stored in Gemlah's search database. They may exist temporarily in the request and current page, and unresolved recovery information may remain in that browser tab's session storage until resolved or cleared.

Sign-in and account linking

Google sign-in is handled through Supabase Auth. Authentication credentials are kept in protected server-managed cookies rather than browser JavaScript storage. When you sign in, Gemlah may associate the current guest history and allowance with the authenticated account. Signing out ends the current device session but does not itself delete online account data.

Saved state, history and profile

Gemlah stores Place IDs and event records needed for Favourite, Want to Try, Recently Viewed, quota and continuity functions. Removing a current save adds or changes the current state; it does not automatically erase the event history. Restaurant names, addresses and result details are fetched for display and are not intentionally kept as Gemlah's permanent restaurant-fact database.

Browser storage and cookies

During Beta, we record coarse interaction events such as search outcomes, saved actions, navigation, picker use and return visits. We do not include search text, precise location or restaurant names in these discovery events. An existing pseudonymous browser identifier supports rate limiting and a 7-day return estimate. Discovery events are removed after 30 days during routine event processing. Browser Do Not Track and Global Privacy Control disable this optional browser event reporting.

Gem Reveal sound is disabled during this Beta update. Any previously saved sound preference stays in this browser and is not used while sound is disabled. Clear this site’s browser data to remove that preference. Administrators may choose to load a Google map preview when correcting a spot; this sends the spot’s coordinates to Google.

Gemlah uses protected cookies for guest/account identity and session storage for bounded unresolved operations. Session storage may include a query, coordinates, request ID, opaque identity/scope marker and requested Place IDs. It remains in that browser tab until resolved, cleared or the tab/session ends. Clearing browser data does not delete records already stored online.

Service providers and international processing

Google processes restaurant searches and Google sign-in information; Supabase provides authentication and database services; Vercel hosts pages and requests. These providers may process technical and personal information in locations outside Malaysia under their own terms, privacy notices and safeguards. See the Google Privacy Policy, Supabase Privacy Policy and Vercel Privacy Policy.

Disclosure

Gemlah may disclose limited information to service providers acting for the service, when required by a valid legal process, to protect users or the service from a serious threat, or to investigate abuse and disputes. Gemlah does not disclose a user's identity or private logs to a restaurant merely because the restaurant requests them.

Retention and deletion

Gemlah currently has no automated periodic deletion schedule for activity, quota or issue history. Records are retained while needed for the functions described above, security, duplicate/abuse prevention, dispute evidence or legal obligations, and are removed or restricted through applicable deletion processes. Provider backups may persist for their documented backup cycles.

You may request access, correction or deletion by email. Gemlah may verify that the request relates to you and may retain a limited restricted record where reasonably necessary for security, fraud prevention, a legal requirement or an existing dispute. A public removal and restricted legal-evidence retention are separate actions.

Security

Gemlah uses access restrictions, server-managed credentials, protected cookies and database controls intended to reduce unauthorised access. No online service can guarantee absolute security. If you believe your account or personal information is at risk, contact Gemlah promptly through Report an Issue.

Changes

This Notice will be updated when material data practices, providers, product functions or the operator change. The effective date identifies the current public version.