Privacy policy

Cacambo is built to need as little personal data as possible. Visitors to the map are anonymous: no accounts and no tracking across sites. While you browse the map, the only cookie is the one described under Reserve a Table below (signed-in accounts also use sign-in cookies).

Visitors

• Analytics. We count anonymous events (a deal was seen, opened, shared, or its directions tapped) so venues can see how their deals perform. Events carry no user, device or session identifier and are not linked to you.
• Reserve a Table. When you tap Reserve a Table, a random first-party cookie lets us count the click for the venue; the cookie value is stored only as a salted hash, and we do not store your IP address. If you are signed in, the click is linked to your account.
• Location. Only if you tap "near me". Your exact location stays in your browser and is never sent to us. To draw the 10-minute walking area, your browser sends an approximate location (rounded to about 100 m) to Mapbox; we do not store it.
• Preferences. Your light or dark theme choice is saved in your browser's local storage on your own device.

Booking a table

When you book a table through Cacambo, you sign in and we store the venue, date, time, party size, the name and mobile number you give us, your account email and any note you add. We pass the name, mobile number and note to the venue (and to its booking system when we book it there) so it can hold your table, and we email you when it is confirmed. The venue and the Cacambo team can see the booking; other guests cannot. While you fill in the form, your choices are kept in your browser's session storage so they survive signing in. You can cancel an upcoming booking in Your Bookings.

Venues

Venue owners sign in with an email address or Google. We store the email, the venue profile you provide, your deals, bids and billing status. Card details are handled by Stripe and never touch our servers. We email you about approvals, auctions and billing.

Who we share data with

Service providers that run the product on our behalf: hosting and database (Supabase), payments (Stripe), email delivery (Resend) and maps (Mapbox). When you book a table, the venue you book receives the booking details described above. We do not sell personal data.

Receipts

We first try to read a receipt photo on your own device. If it can't be read there and cloud reading is switched on, the photo is sent to Google Cloud Vision to read the total. For that step our server holds the photo in memory only while the request runs and does not store or log it; the receipt you submit is kept only as part of the receipt flow you already used.

Your rights

Venue users can ask to see, correct or delete their data. Contact us through the for-venues page and we will respond within a reasonable time.