Privacy, plainly.

Restaurant discovery needs a point on the map. When you grant browser location or type an address, the coordinates are rounded to roughly a city block (~110 m) on our server before any restaurant or geocoding lookup happens. Precise coordinates are never stored, never logged, and never sent to third parties.

Your browser keeps the rounded point and a neighborhood label (like “Capitol Hill, Seattle”) in local storage so you can skip the location step next visit. Clear it anytime with the “change” control or your browser settings.

Preferences, sound setting, recent results, and saved picks live in your browser's local storage only. There is no server copy. Clearing site data removes everything.

When you press the button, your rounded location and current preferences are sent to our API to compute a recommendation, used in memory, and discarded. Standard rate-limiting uses your IP address transiently; we don't keep request logs tying IPs to locations.

Lookups are proxied through our server so these services never see your IP or browser:

• OpenStreetMap / Overpass— nearby restaurant data when the DoorDash CLI isn't configured (© OpenStreetMap contributors, ODbL).
• Nominatim & Zippopotam — turning addresses and ZIP codes into coordinates, and coordinates into neighborhood labels.
• DoorDash CLI— only if the operator has configured it; used read-only for restaurant and menu discovery. Ordering happens on doordash.com under DoorDash's own terms and privacy policy.

A share link encodes the decision seed, your preferences, and the rounded location in the URL itself so a friend sees the same pick. Only share them with people you're happy knowing roughly where you eat.

None. Not even the polite kind.