WineBlinders I have a code
English
Menu

WineBlinders

Privacy policy

Last updated · 21 October 2026

The data controller is LLM driven, LLC, a Delaware limited liability company in the United States operating WineBlinders.

Company address: 1111b South Governors Ave, STE 26919, Dover, DE 19904, US. Data enquiries: hola@wineblinders.com.

  • No account is needed to taste. When you join a room with a code we store the name you choose, your scores, your guesses and changes to them, with their times, as well as when you close each round. They feed the averages, ranking and your personal journey. They are linked to your participation in the room; the name you choose may identify you even without an account.
  • If you leave your email (to keep your history or open your dashboard) we store that email, the name you choose and the link to your participations. Purpose: to let you see your tastings, results, stats and reports. Legal basis: performance of the account service you request. Optional marketing, if introduced, requires a separate basis and is not enabled by requesting a sign-in link.
  • A tasting organiser may link your email to your participation if they know you (your club, for instance). We send nothing in that case: only when you request the link with that email does the tasting show up in your dashboard. Legal basis: the organiser's legitimate interest in keeping records of their tastings; you can ask us to unlink it.
  • Optional AI wine import: if you upload a PDF sheet or photo, the file and extracted details are temporarily stored on Cloudflare for background processing and review when you return. Only an organiser can view that draft. They are deleted when you accept the review or no later than 24 hours after processing finishes. The file may reveal the wine before unveiling; enter the details manually if you do not want this processing.
  • Emails we send: sign-in links, club invitations and personal reports for tastings linked to your verified account. Reports arrive as PDF attachments after every bottle is revealed and all rating windows close. No newsletters or advertising.

Once the wines of a tasting are unveiled, we keep each wine (name, producer, technical data and price) in a catalogue, together with what happened with it in that tasting as a whole: average score, the share of tasters who identified it, and which countries, grapes or vintages were guessed blind. We use this for aggregated studies (per wine, per club or overall). Within a tasting or club, names, attendance, scores and rankings may be visible to other authorised participants or members. Public club pages show organisation information and explicitly published announcements. Personal tasting history and club rankings remain on authorised club surfaces.

Tasting data, as long as the tasting exists (the organiser can delete it). You can request account closure from the dashboard or by contacting us. The closure option registers a request with a reference and response deadline; it does not immediately delete your profile, links or participations. We review identity, scope and retention obligations before executing withdrawal. Statistical results that are retained require an anonymisation review; records subject to legal retention remain protected and restricted. Sessions expire after 90 days; sign-in links after 30 minutes.

We use service providers with roles determined by their services and contracts: Cloudflare (hosting, database, sheet storage and the AI models that write the report tips; data on Cloudflare's network, with international-transfer safeguards) and Resend (transactional emails and attachments, with stored data in the United States and international-transfer safeguards; selecting a European sending region does not restrict storage to Europe). See Resend security and retention. When you book a paid experience or agree to save a card as an attendance guarantee, Stripe handles the card and payments. WineBlinders stores booking details, accepted terms, amounts, status and card, payment, refund and dispute references, not your full card number. See Stripe privacy. Tasting organisers see their tasters' names and results; other tasters see names and, at the end, the tasting's results.

As checked on 30 September 2026, the production database and file bucket report Western Europe. They are not configured with an EU-only jurisdiction guarantee. Live tasting rooms, application processing, AI and operational logs are not restricted to the EU. Some providers process data outside the EEA. Applicable transfer safeguards and provider agreements must cover these processing operations; European storage alone does not cover every data flow.

You can access, correct, delete, restrict or object to the processing of your data and request portability by writing to hola@wineblinders.com. From the dashboard you can change your name, download your reports, export in JSON the data linked to your account in the active organisation, and request account closure or data withdrawal. The export identifies participations for which only the historical archive is available. You may also lodge a complaint with your data protection authority (in Spain, aepd.es).

We use GoatCounter for page visit statistics and fixed restaurant purchase steps, such as choosing a plan or requesting a sign-in link. These events do not include venue names, addresses, email addresses, invitation codes or purchase identifiers. The integration sends the domain and path, excluding query strings, URL fragments, room codes, access tokens and personalized page titles. See GoatCounter privacy. We do not use tracking cookies. The browser keeps in local storage what the app needs: access to rooms you joined, your session if you signed in, and your preferences (language, scoring style). A restaurant purchase draft is kept for up to one hour to resume after email verification. It contains the name you entered, the Google place ID, selected plan, declared country and purchase reference, not your email, billing address or card details.

Restaurant searches send the name, address or city you type, and the interface language, to Google Maps Platform. Search results are displayed temporarily. We keep the place ID and your own restaurant name and declared country to establish the commercial location for your plan; we do not store Google's returned name or address in the purchase record. Confirming a venue does not publish it or establish tax registration. The restaurant address may temporarily fill the billing fields. You can correct it and must confirm that it is your billing address before continuing to payment. Only the billing details you submit enter the contract and invoicing process; they are not saved in the browser draft. See the Google privacy policy.

If you choose Search near me, your browser asks for location permission. Coordinates are rounded to two decimal places before being sent to Google as an approximate search area. Device coordinates and autocomplete session tokens are not saved in purchase drafts, URLs, analytics or application records. You can enter a city or address instead.

To understand restaurant interest, we retain daily counts of search requests, matching place IDs, venue selections and requests to see plans for 90 days. These are activity counts, not unique visitors, verified owners, purchases or permission to contact anyone. This record does not contain your search text, Google names or addresses, account, email, purchase reference, IP address or coordinates. Random result receipts prevent duplicate events and expire after one hour; scheduled cleanup removes expired receipts. Access is restricted to our operators. These first-party statistics help us improve the restaurant purchase flow.

If you ask AI to interpret your needs, your description, limited to 500 characters, is processed by Cloudflare Workers AI. Do not include personal or contact details. WineBlinders does not retain the description or model output. You review the extracted needs before requesting a plan recommendation. The model cannot set prices or activate a subscription. Hashed IP rate counters limit use independently of restaurant searches.