Huzzah! Privacy Policy
Effective date: July 30, 2026
Huzzah! helps you decide where to eat — on your own or with a group. This policy explains exactly what the app collects, why, and what it does not do. It reflects how the app actually works today. If that changes, we’ll update this page and the effective date above.
The short version
Huzzah! has no user accounts. We don’t ask for your real name, email, or phone number — a group “Dinner Party” just uses a display name you choose. We use your location to find restaurants near you, and a random device identifier to run those group sessions. We don’t sell your data, we don’t show third-party ad tracking, and group sessions delete themselves automatically. That’s the whole story — the sections below are the detail.
What we collect and why
Location. When you allow it, the app uses your device’s location to find places to eat nearby and to measure distance to results. You can decline the location prompt and type a location by hand instead — the app works either way. Your location is used to fetch results at the moment you ask and is not stored on our servers as a history tied to you.
A device identifier. The app generates a random identifier stored on your device. It lets your phone join a Dinner Party and be counted in that group’s result — nothing more. It is not your name, and it is not linked to any account, because there are no accounts.
Your picks during a session. When you swipe or set filters, those choices are used to compute your matches (and, in a party, the group’s shared matches). Party inputs live only for the life of the party.
Saved spots and app settings. Places you save, your decision history, and whether you’ve seen the tutorial are stored locally on your device only. They are not uploaded to us. Deleting the app removes them.
Anonymous usage data. To understand how the app is used and to improve it, we collect anonymous, aggregated usage events — for example, that a search happened, that results were shown, or that directions were opened — along with a separate random analytics identifier generated on your device. This identifier is not the Dinner Party identifier above and is not linked to party participation or to your identity; it exists only so we can tell, in aggregate, whether people come back. It is never sent to Google or any third party. You can turn this off any time under Settings → “Share anonymous usage data”, and it never uses cross-app tracking or Apple’s App Tracking Transparency.
What we do not collect
We do not collect your name — other than a display name you choose when joining a Dinner Party, which is temporary and is purged along with the party — nor your email address, phone number, contacts, photos, payment information, or health data. We do not track you across other apps or websites, and the app does not use Apple’s App Tracking Transparency because there is nothing to track.
How group sessions (“Dinner Party”) work
A party is identified by a short code, not by who you are. Each member enters a display name of their choosing — a nickname is fine — which is shown to others in that party; it is not verified and is not your account (there are no accounts). Members’ inputs are scoped to the code so one party can never read another’s data. Party data, including display names, is ephemeral: it is automatically purged on a rolling basis (within roughly 24 hours), after which it is gone.
Using Huzzah! in a browser
You can join a Dinner Party from a web browser at huzzah.food — for example, from a shared invite link — without installing anything. When you do: you enter a display name as above, your browser is given a temporary, session-scoped identifier that exists only for that tab and is cleared when you close it, and your swipe choices are submitted to the party. Nothing is kept once you close the tab, and any anonymous usage measurement in the browser is likewise session-scoped and not tied to you. The app-only items described elsewhere — saved spots and history, on-device settings, and the “Share anonymous usage data” toggle — do not apply to the browser experience, because there is no app installed and nothing to delete.
Service providers we rely on
To deliver results, the app sends the necessary request data (such as a search area and your food preferences) to:
- Google Places API (New) — to look up restaurants, details, and photos. Requests are routed through our own secure server, so your device never talks to Google directly and no personal profile is built for you there.
- Supabase — our backend, which caches restaurant lookups and runs the temporary party sessions described above.
- OpenStreetMap / Nominatim — a free fallback used for geocoding and basic restaurant data when needed.
These providers process data only to perform these functions. We don’t authorize them to use your information for their own advertising.
Data retention
Party session data is deleted automatically (about 24 hours). Anonymous usage events are kept for at most 90 days on a rolling basis and then deleted. Cached restaurant information is stored to reduce cost and speed up results and is not personal to you. Anything you save inside the app stays on your device until you delete it or remove the app.
Children
Huzzah! is a general-audience app and is not directed at children under 13. We do not knowingly collect personal information from children.
Your choices
You can deny or revoke location access at any time in your device settings and use manual location entry instead. You can clear your saved spots and history by clearing the app’s data or uninstalling it. Because we hold no account for you, there is no profile on our servers to delete.
Changes to this policy
If we change what the app collects — for example, if we later add accounts, sponsored placements, or a premium tier — we will update this policy before those features go live.
Contact
Questions about this policy? Email support@huzzah.food.