Gaumo

Privacy Policy

Version 2026-10-17 · Effective 2026-10-17

1. Who we are

Gaumo is operated by Alexander Turbin, an individual developer based in Germany. Contact: hello-gaumo@parrotlabs.xyz.

2. Information we collect

Account information

When you create an account, we collect your name and email address. If you sign up with email and password, your password is stored in hashed form via our authentication provider. If you sign in with Sign in with Apple or Google, we receive your name and email from that provider (Apple may provide a private relay email address) and store a provider identifier so you can sign in again. We do not receive your Apple or Google password.

Android waitlist (marketing site)

If you join the Android release waitlist on our marketing website, we collect your email address and record that you accepted the current Terms of Service and Privacy Policy. We may also store technical metadata (IP address, browser user agent, referring page, and optional campaign parameters such as UTM tags) to measure interest and attribute sign-ups to marketing campaigns. We use this information to notify you when an Android app becomes available and to understand demand. You do not need a Gaumo account to join the waitlist.

User-generated content

When you use Gaumo, we store content you submit, including dish ratings (score, optional comment and photo), saved dishes, hidden items, private venue notes, dishes and venues you add, and profile photos.

Location

With your permission, we use your device's location to show nearby dishes and venues. Location is used when you grant "while using the app" access; we do not track location in the background.

Restaurant catalog data (OpenStreetMap and other sources)

Some venue listings in our catalog (name, street address, city, postal code, and map coordinates) were seeded from OpenStreetMap using the public Overpass API. That location data is © OpenStreetMap contributors and available under the Open Database License (ODbL). We store it in our database together with Gaumo-owned content such as menus, photos, and ratings. We may also seed venues from municipal or other open datasets when licensed for reuse; those rows are tagged with the applicable license in our internal import records.

We use Google Places when you search for venues or when we link a catalog row to Google's place identifier and official website URL. We do not use Google name or address fields as the bulk seed for new venues when OpenStreetMap or licensed open data already supplied that information.

We do not offer a public download of raw OpenStreetMap restaurant extracts. If we publish open data exports in the future, we will separate third-party licensed fields from Gaumo-owned catalog content.

Device and usage data

We collect technical information needed to operate the service, including session identifiers, IP address, and user agent when you sign in, accept legal documents, or interact with our marketing pages (for example, viewing the Android waitlist page or tapping its download button).

Crash and error reporting

If configured, we use Sentry to collect crash reports and error diagnostics. This may include device type, app version, and stack traces. Sentry is optional in local development.

App usage (EAS Insights)

On release builds distributed via Expo Application Services (EAS), we use EAS Insights to collect aggregate app-open events (cold starts). This may include platform (iOS/Android), app store version, and timestamps. It does not include your account details, ratings, or location. EAS Insights is not active in local Expo Go development.

Product analytics (PostHog)

If configured, we use PostHog to understand how people use Gaumo — for example, which screens are viewed, whether guests sign in after an auth prompt, and whether flows like saving a dish or adding a place complete. Events may include action names, related entity identifiers (such as dish or venue IDs), app version, platform, and similar device/app metadata. We do not send precise GPS coordinates in analytics events. Analytics may be linked to your account after you sign in. PostHog may process data in the EU when we use PostHog Cloud EU. PostHog is optional in local development when no analytics key is configured. See PostHog’s privacy policy.

Operations notifications (Telegram)

If configured, we send best-effort operational notifications to a private Telegram chat operated by the Gaumo team when certain high-signal actions occur — for example, account sign-up or deletion, adding a venue or dish, submitting a rating with a photo or comment, reporting a price, setting a profile photo, opening a moderation review, or submitting a content report. These messages may include your display name, a short portion of your internal user ID, and metadata about the action (such as dish or venue names, rating details, moderation status, or report reason). We do not include your email address in Telegram notifications. Telegram is optional; when not configured, no notifications are sent. Messages are transmitted via the Telegram Bot API and processed by Telegram according to their privacy policy. See Telegram’s privacy policy.

Menu translation (DeepL)

If configured, when you tap Translate on a dish we send that dish’s description, variant label, group name, or extra name to DeepL (DeepL API Free), together with the source and target language, so DeepL can return a translation. We do not send your name, email, account identifier, ratings, comments, private notes, or dish and place titles. DeepL’s free-service terms say it processes that text for a limited time to produce the translation and to train and improve its models, and that personal data must not be submitted. We store the translation we receive with the dish so we can show it again and match it in search without sending the same text again. See DeepL’s privacy policy.

Content safety (OpenAI Moderations)

When enabled, we send public user-generated text (for example display names, comments, and venue or dish descriptions you submit) to OpenAI’s Moderations API to detect policy violations before content is shown. We do not send your email, private venue notes, or precise location. See OpenAI’s privacy policy.

Decide — what should I eat? (OpenAI)

When the Decide feature is enabled, we send your brief (free text and optional situation chips), locale, a distance bucket (walking / short ride / farther — not raw GPS coordinates), your profile diet lock when set, category affinity weights derived from your saves and reactions when you are signed in, and a filtered list of public dish fields (names, categories, prices, diet flags, reaction summaries, and similar catalog facts) to OpenAI so the model can pick dish ids and fact keys from that list. We do not send your email, private notes, rating comments, or raw coordinates. The app builds the reason sentence from catalog facts; the model does not write free-form claims. We do not persist your brief on the server for this feature. See OpenAI’s privacy policy.

3. How we use information

We use your information to:

Provide and improve Gaumo (discovery, ratings, saves, contributions)
Authenticate you and maintain your session
Enforce our Terms of Service and protect the platform
Respond to support requests
Notify Android waitlist subscribers when an Android app is available
Measure marketing interest (page views and button taps on the Android waitlist page)
Diagnose crashes and errors (when Sentry is enabled)
Measure aggregate app usage on release builds (EAS Insights)
Measure product usage and funnels (when PostHog is enabled)
Monitor high-signal contributions and safety events for internal operations (when Telegram is enabled)
Translate menu descriptions, variant labels, group names, and extra names when you tap Translate (when DeepL is enabled)
Scan public text for policy violations (when OpenAI Moderations is enabled)
Suggest a dish from your brief when Decide is enabled (when OpenAI is configured for Decide)
Build and maintain the public restaurant catalog (including location data from OpenStreetMap and licensed open datasets)

We do not sell your personal information.

4. How we share information

We share information only as needed to operate Gaumo:

| Recipient | Purpose |

|-----------|---------|

| Cloud hosting (database, API) | Store and serve your data |

| AWS S3 | Host photos you upload |

| OpenStreetMap (Overpass API) | Source initial venue name, address, and coordinates for some catalog rows (see “Restaurant catalog data” above) |

| Google Places | Venue search and address autocomplete (queries sent when you search); place identifiers and website URLs for catalog linking |

| Google (Sign in with Google) | OAuth sign-in when you choose that option |

| Apple (Sign in with Apple) | OAuth sign-in when you choose that option |

| Sentry (optional) | Crash and error reporting |

| Expo (EAS Insights) | Aggregate app-open telemetry on EAS release builds |

| PostHog (optional) | Product analytics and funnel measurement |

| Telegram (optional) | Internal ops notifications for sign-ups, contributions, moderation, and reports |

| DeepL (optional) | Translate menu text when you tap Translate |

| OpenAI (optional) | Moderate public text; Decide dish selection when enabled |

| Email provider | Verification, password-reset, and waitlist notification emails |

We may disclose information if required by law or to protect rights and safety.

5. Cookies and sessions

Gaumo uses HTTP cookies to maintain your signed-in session. These are essential for authentication and are not used for advertising.

6. Data retention

We retain your account data while your account is active. When you delete your account (see Profile → Delete account):

Your name and email are masked and you cannot sign in again
Saved dishes, hidden items, venue notes, and price reports you submitted are removed
Your dish ratings may remain in anonymized form so aggregate scores stay meaningful
Records of your acceptance of Terms and Privacy are retained for legal compliance (no personal data in those records beyond your internal user ID)

Android waitlist emails are retained until we notify you about the Android release or you ask us to remove your address. Contact hello-gaumo@parrotlabs.xyz to opt out of the waitlist.

When menu translation is enabled, we keep each stored translation with the dish. We delete those translations when the source text changes or when the dish, group, or extra is deleted.

Decide briefs are not stored server-side as part of this feature.

7. Your rights

Depending on where you live, you may have rights to access, correct, or delete your personal data. Account deletion is available in the app. Contact hello-gaumo@parrotlabs.xyz for other requests, including removal from the Android waitlist.

8. Security

We use industry-standard measures to protect your data, including encrypted connections (HTTPS) and hashed passwords. No method of transmission is 100% secure.

9. Children

Gaumo is not directed at children under 13. We do not knowingly collect data from children under 13.

10. International transfers

Your data may be processed in countries where our service providers operate. We take steps to protect data in line with applicable law.

11. Changes

We may update this Privacy Policy. When we do, we publish a new version and may ask you to accept the updated policy before continuing to use Gaumo.

12. Contact

Privacy questions: hello-gaumo@parrotlabs.xyz.