Privacy Policy

Effective date: May 4, 2026

mesoHungy ("we", "our", or "the app") is a mobile application that helps you discover restaurants nearby. This policy explains what information we collect, how we use it, who we share it with, and the choices and rights you have. It applies to the mesoHungy iOS app, Android app, and the website at mesohungy.com.

1. Information We Collect

1.1 Account Information

To use account-based features, you must sign in. We collect:

• Email address — used to authenticate you and send account-related messages such as password resets and security notices.
• Display name (nickname) — a name you choose. It is shown to you in-app and may be visible to other users in features such as Friends.
• Authentication metadata — a unique account identifier (UUID), sign-in provider (email, Google, or Apple), account creation date, and most-recent sign-in timestamp.

Account data is stored using Supabase, our backend and authentication provider.

1.2 Sign-In With Apple and Google

You may choose to sign in using Sign in with Apple or Sign in with Google. When you do, the provider sends us your email address (or, with Apple, a private relay email if you choose) and a stable user identifier so we can create or look up your account. With Apple, you may also choose to share your name on first sign-in; if you do, it is used only to suggest a default display name and is not stored separately. We do not receive your password. We do not request access to your contacts, calendar, photos, or other Apple/Google data.

For Sign in with Apple specifically, we additionally store an Apple-issued refresh token on our server, associated with your account. This token is used for one purpose only: when you delete your account, we send it to Apple's /auth/revoke endpoint so the app no longer appears under "Apps Using Apple ID" on your device. The token is never used to access any other Apple data and is permanently deleted when your account is deleted (or sooner if you sign in with Apple again, which replaces it).

1.3 Location Data

With your permission, we access your device's precise location (GPS) to show restaurants near you. You may also set a location manually using search or the in-app map picker. Your precise location is used only on your device and to query nearby places — we do not store it on our servers, and we do not associate it with your account.

You can revoke location permission at any time in your device's system settings (iOS: Settings → Privacy & Security → Location Services → mesoHungy).

1.4 Usage Analytics

We use PostHog, a third-party analytics service, to understand how the app is used so we can improve it. The data collected through PostHog includes:

• Events you trigger in the app (e.g., opening the app, liking or skipping a restaurant, viewing details, toggling settings)
• Screens you visit and session duration
• Properties of those events (e.g., the restaurant's rating and price level)
• App version, device brand, model, operating system, screen dimensions, and whether the device is a physical device or emulator
• An anonymous distinct ID generated by PostHog
• Your IP address, which PostHog uses to derive an approximate location (typically city and region) and which is then discarded after that derivation

If you are signed in, we associate these events with your account by sending PostHog your account UUID and, if you have set one, your display name. We do not send your email address to PostHog. If you are signed out, events are associated only with the anonymous distinct ID.

PostHog's privacy policy is available at posthog.com/privacy.

1.5 Swipes, Saved Restaurants, and Friends Data

When you are signed in, the restaurants you like or skip are stored on our server (Supabase) so they remain available across your devices and so the Friends feature can work. Each saved swipe consists of a restaurant identifier, an action (like or not_now), the timestamp, and a snapshot of public information about the restaurant (name, rating, address, photos, hours, phone number, website). We do not store anything about you in this row beyond your account UUID.

If you use the Friends feature, we additionally store: friend requests you send or receive (sender UUID, recipient UUID, status, timestamps) and accepted friendships (the pair of UUIDs and the date the friendship was formed). Once two users are friends, each can see the other's saved restaurants and swipe history within the app.

When you are signed out, your liked and dismissed restaurants are kept only on your device. If you later sign in for the first time, you'll be offered the option to upload them so you can keep your history; declining leaves them on the device.

1.6 On-Device Storage

App preferences (such as cuisine filters, radius, dark mode, and your most recent search location) and a local copy of your saved restaurants are stored on your device using AsyncStorage. On-device data is removed when you uninstall the app or clear its data. There is also an in-app "Clear Saved Data" option that wipes both the local copy and, if you are signed in, the server-side copy of your swipes.

2. How We Use Your Information

• To provide the service: authenticate you, show restaurants near your location, save your preferences, and operate features such as Friends.
• To communicate with you: send account-related messages (e.g., password resets). We do not send marketing email.
• To improve the app: understand which features are used, diagnose problems, and prioritize improvements through analytics.
• To enforce our terms and protect users: investigate abuse and enforce our terms of service.
• To comply with legal obligations: respond to lawful requests from authorities.

3. How Information Is Shared

We do not sell your personal information, and we do not share it for cross-context behavioral advertising. We share information only as follows:

• With service providers who process data on our behalf (Supabase, PostHog, Google Cloud, and Apple — see Section 4).
• With other users, only the parts you choose to make visible. Your invite code can be shared by you to allow another user to send you a friend request. Once you and another user are friends, your display name and your saved restaurants (the snapshot data described in Section 1.5) become visible to each other within the app. You can end this sharing at any time by removing the friendship.
• For legal reasons, when we believe in good faith that disclosure is required by law or necessary to protect the rights, property, or safety of users or the public.
• In a business transfer, such as a merger, acquisition, or sale of assets, in which case we will notify you and provide a meaningful choice where required by law.

4. Third-Party Services

The app relies on the following third-party services. Each has its own privacy policy governing its handling of your data.

• Supabase — authentication and database. Receives: email, hashed password (for email sign-up), display name, account UUID, invite code, sign-in timestamps, your saved swipes and the public restaurant snapshots attached to them, your friend requests and friendships, and (for Apple sign-in users only) the Apple-issued refresh token described in Section 1.2. Privacy policy.
• Google Places API — restaurant information lookup. Receives: search queries (cuisine, radius) and approximate coordinates. Does not receive your account information. Privacy policy.
• Sign in with Google (optional) — authentication. Subject to Google's terms when you choose this method. Privacy policy.
• Sign in with Apple (optional) — authentication. Subject to Apple's terms when you choose this method. Privacy policy.
• PostHog — product analytics. Receives the data described in Section 1.4. Privacy policy.

5. Information We Do Not Collect

• We do not collect your real name, phone number, mailing address, or government identifiers.
• We do not collect payment or financial information — the app is free.
• We do not access your contacts, calendar, photos, microphone, or camera.
• We do not run third-party advertising SDKs, and we do not use your data for advertising.
• We do not sell your personal information.

6. Data Retention

• Account information (email, display name, account UUID, invite code, sign-in timestamps), saved swipes, and friend graph are retained for as long as your account exists. When you delete your account in-app, all of this is removed from our active systems immediately as part of the deletion request. Encrypted database backups held by Supabase are overwritten on a rolling basis within 90 days.
• Apple refresh token (Apple sign-in users only) is retained until your account is deleted, and is used at deletion time to revoke your Apple sign-in grant. It is then permanently deleted along with the rest of your account.
• Precise location is used in real time on your device and is not retained on our servers.
• Analytics data is retained by PostHog according to its data retention settings (currently 7 years for events; we may shorten this in the future). When you delete your account, we no longer associate your account UUID with new events, but historical events that were already linked to your UUID remain in PostHog until they age out under PostHog's retention.
• On-device data remains on your device until you clear the app's data or uninstall the app.

7. Your Rights and Choices

You have the following rights with respect to your personal information. To exercise any of them, email us at matthewzhenghi@gmail.com from the email address associated with your account.

• Access — request a copy of the personal information we hold about you.
• Correction — update inaccurate information. You can change your display name in the app at any time.
• Deletion — you can permanently delete your account from the in-app Account screen. Deletion is immediate: your profile, saved swipes, friend graph, and (if applicable) Apple refresh token are removed from our active systems as part of the request, and your Apple sign-in grant is revoked at the same time. Encrypted Supabase backups are overwritten on a rolling basis within 90 days. If you cannot use the in-app option for any reason, you may also email us to request deletion.
• Withdraw consent — revoke location or notification permissions in your device settings at any time.
• Object or restrict processing — applicable to users in jurisdictions that grant these rights (e.g., the EEA, UK).
• Lodge a complaint — you may complain to your local data protection authority. We hope you'll contact us first so we can address your concern.

Depending on where you live, you may have additional rights under the General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA/CPRA), or similar laws. We honor verifiable requests under these laws regardless of your location.

8. Data Security

We use industry-standard safeguards to protect your information, including HTTPS/TLS in transit, encryption at rest for our databases (provided by Supabase), and restricted access to backend systems. No method of transmission or storage is 100% secure, and we cannot guarantee absolute security.

9. International Data Transfers

Our service providers may store and process your information in the United States and other countries. Where required by law, we rely on appropriate safeguards (such as the Standard Contractual Clauses) for international transfers.

10. Children's Privacy

mesoHungy is not directed to children under the age of 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, please contact us and we will delete it.

11. Changes to This Policy

We may update this privacy policy from time to time. We will post the updated policy on this page with a revised effective date. Material changes will be communicated through the app or by email where reasonably possible.

12. Contact Us

If you have questions about this privacy policy or how we handle your data, contact us at:

Email: matthewzhenghi@gmail.com
Subject line: "mesoHungy Privacy"