Skip to content

Demonstration mode. Every producer, product and experience shown here is fictional and created for this demo. No bookings are charged and no alcohol is sold.

Privacy

There is very little to tell you.

This is the whole policy, not a summary of one. It is short because the site is short: there are no accounts, no payments and no analytics, so there is very little about you here to write a policy about.

That changes when booking opens. When it does, this page grows first and the feature ships second.

Last updated 7 August 2026

What we ask you for

The waitlist form is the only thing on this site that asks you for anything. It takes your email address, whether you are a guest or a producer, and which region you want opened next. Those three answers are stored with the time you sent them, and nothing else — no IP address, no device fingerprint, no advertising identifier, no referrer.

Each signup is written as its own private object in our host’s blob store. It is not public, it is not shared, and it has never been sent to a mailing-list product.

The region you vote for is the point of asking: it decides which region we open next. That is the only thing we do with any of it.

What we do not do

No analytics product. No tag manager. No advertising or social pixel. No A/B testing tool. No session recording. No heatmaps. There is no visitor profile here because nothing on the site builds one.

Two consequences are worth naming, because most sites cannot claim them:

  • Google never sees your visit. The three typefaces are compiled into the site when it is built and served from our own domain, so your browser makes no request to a font host.
  • The photo libraries never see it either. Every photograph is fetched and resized by our own image proxy before it reaches you, so the stock-photography hosts get a request from us and never one from you.

Where you are

Two different things can happen on the regions page, and the difference matters.

A guess from your network. Our host works out an approximate city from your IP address and passes it to the page. We use it to ask a question — “are you near Austin?” — and never to state where you are. It is read while the page is being built and then thrown away. It is not stored, and nothing downstream uses it until you say it is right.

A position you give us. If you press “Use my location”, your browser asks your permission and hands the coordinates to the page in your browser. They never leave it. The distances to our regions are computed there, and your city is named by matching a built-in list of towns within 75 miles — no geocoding service is called, so nobody is told where you are. Further than 75 miles from any of them, the page just says “your location”.

Your answer is remembered in this browser’s local storage under dc:origin and nowhere else. Clearing site data removes it. Picking a city from the list instead puts it in the URL, which is why that link is shareable and the device fix is not.

What you type into the concierge

When you describe what you want in your own words — “a distillery tour near Austin on Saturday for four” — that phrase is sent to Anthropic’s API to be turned into filters, which then come back and show up as chips you can edit.

The phrase travels on its own. No email address, no identifier, no session, no history of what you searched before. We do not keep the phrase either; it lives in the URL you are looking at, which is the point — that URL is the search, and it is yours to share or discard.

If the API key is missing or the call times out, a parser running on our own server reads the phrase instead, and you would not notice the difference.

The map, which is somebody else's

The map on the explore page is Mapbox. Opening that view requests map tiles from Mapbox’s servers, which means Mapbox sees your IP address and roughly what part of the world you looked at. Their map library also stores an identifier in your browser’s local storage, under keys beginning mapbox.eventData, and posts usage telemetry to them.

That is Mapbox’s collection, under Mapbox’s policy, and we cannot switch it off while using their maps. It happens only on the map view — the list view, the region pages and the homepage load no Mapbox code at all.

Our host

The site is served by Vercel, which keeps ordinary server logs — IP address, the URL requested, the browser’s user agent, the time — for a limited period, as every web server does. We do not join those logs to anything, and we do not use them to recognise you across visits.

How long we keep the waitlist

Until launch, and long enough after it to invite you. If we have not opened a region you would want by then, we will say so rather than sit on your address indefinitely. Ask us to delete it sooner and we will, without asking why — hello@drinkcard.app.

What you can ask for

One email covers all of it: a copy of what we hold, a correction, or deletion. There is no form and no account to log into, because there is no account.

Everything stored in your browser — dc:origin and, if you opened the map, Mapbox’s keys — clears when you clear site data for this domain, and is never written at all in a private window.

We do not sell your information

We do not sell personal information, and we do not share it for cross-context behavioural advertising. There is no opt-out link here because there is nothing to opt out of.

This section exists so the link at the bottom of every page goes somewhere that answers the question honestly, rather than to a switch that does nothing.

When this changes

Booking and gifting will need a payment processor, an email sender and an account of your own, and each of those is a real addition to this page. The date at the top will move when they arrive, and the sections will name them the way the ones above name Mapbox — by who they are and what they see.