Vino2Vino Privacy Policy

Status: Draft for counsel review; not approved for publication. Permanent HubSpot erasure and form-cookie consent behavior must be verified before publication.

Effective date: August 20, 2026 Applies to: vinomate.ai, vino2vino.com, the VinoMate connector for AI assistants, and the VinoMate account portal (together, the "Services").

Vino2Vino ("Vino2Vino," "we," "us") operates the Services, including the VinoMate consumer product. This policy explains what we collect, how we use it, who we share it with, and the choices you have. We have tried to write it the way we built the system: collect as little as possible, keep identity separate from behavior, and tell you plainly what happens.

The short version

• You can use VinoMate without an account, and most people do. Anonymous use sends us your questions' content (via the AI assistant you use) but no name, no email, no account.
• If you create an account, we collect the minimum from Google sign-in: your Google account identifier, email address, and display name — plus a one-time 21+ attestation.
• Your identity is stored in a separate, restricted system. Our product database — ratings, cellar, taste profile — refers to you only by an internal random identifier, never by name or email.
• Marketing email (the notify list, the Discovery List) is managed in HubSpot and is strictly opt-in. Your taste data, cellar, and product activity are never shared with HubSpot or any marketing system.
• We do not sell personal information, we do not run ads, and no recommendation is ever paid for.
• You can delete your account and data at any time, and we built that path first, not last.

1. Information we collect

When you use VinoMate anonymously (no account). VinoMate is a connector ("tool") used inside AI assistants such as Claude. When the assistant calls VinoMate on your behalf, we receive the content of that tool call — for example, a wine name, a photographed wine list's extracted text, a price you mention, a dish you want to pair. We use it to answer the request. We retain certain tool-call content as pseudonymous observations — for example, "this wine was seen at this price at this store on this date" — with no link to you. We receive location context only if you volunteer it in the conversation (for example, naming a store or city); we do not derive your location from IP addresses or any other signal. Standard server logs (IP address, timestamp, request metadata) are kept briefly for security and rate limiting.

Your conversation with the assistant itself — everything you type into Claude or another assistant — is handled by that assistant's provider under its privacy policy. We receive only the tool calls the assistant makes to VinoMate, not your conversation history.

When you create a VinoMate account. We collect, via Google sign-in: your Google account identifier, email address, and display name. We also record a one-time attestation that you are 21 or older (the attestation and its date — we do not collect your birth date). With an account, the Services store the data that makes VinoMate yours: taste profile, saved wines, cellar contents and imports (for example, a CellarTracker or Vivino export you provide), check-ins and visit history you explicitly create, and conversation-derived preferences.

How identity is stored. Your identifying information (email, name, Google identifier, age attestation) lives on the PII side in HubSpot during the current interim architecture; a dedicated identity vault is the target. HubSpot also holds the random internal identifier needed to connect your account to the product database. Everything else — ratings, cellar, taste profile, history — stays in the product database under that identifier and is never sent to HubSpot. Access to the identity mapping is restricted to the identity service and authorized operators.

Claimed review profiles. If you choose to link a profile you control on another wine platform, we verify control, and connect that profile's public reviews to your taste profile. The connection is recorded in the restricted identity store.

Notify list and marketing signups. If you join our mailing list (on vinomate.ai or vino2vino.com), your email address, name if provided, signup source, and consent record go directly into our CRM (HubSpot) and are not added to the product database.

Website visits. Our sites are static pages served through Cloudflare. We do not run advertising trackers. We use minimal analytics and the cookies strictly necessary for the account portal to function; marketing pages using HubSpot forms may set HubSpot cookies as described in HubSpot's cookie documentation.

B2B contacts (vino2vino.com). If you contact us about CellarGraph or partnerships, we keep your business contact details and correspondence in our CRM.

2. How we use information

We use the information above to: provide and improve the Services (answering requests, computing recommendations, maintaining your taste profile and cellar); maintain the anonymous, aggregate wine-data layer (prices observed, drinking-window signals) that makes the product useful; send transactional email you request or that the Services require (sign-in links, confirmations, receipts); send marketing email only with your consent (see §4); secure and operate the Services (rate limiting, abuse prevention, debugging); and comply with legal obligations.

We do not: sell or rent personal information; run advertising or share data with ad networks; accept payment for recommendations or rankings; or use your personal data to train AI models or license it to others for training.

3. What we share, and with whom

We share personal information only with service providers ("processors") who handle it on our instructions, and only the slice each one needs:

Provider	Role	What it receives
HubSpot	Interim identity store, CRM and marketing email	Account identity: email, name, Google identifier, age attestation and opaque internal user ID; marketing contacts: consent, campaign engagement and coarse account status. Never taste, cellar, or product-activity data.
Google	Sign-in (OpenID Connect)	The sign-in interaction itself, under Google's own policy.
Transactional email relay (e.g., Amazon SES)	Delivery of sign-in links, confirmations, receipts	Recipient address and message content.
Cloudflare	CDN, security, email routing	Web traffic metadata; inbound mail routing.
Microsoft Azure	Hosting and storage	Hosted data as described in this policy.
AI assistant platforms (e.g., Anthropic)	The assistant you use VinoMate through	Your conversation, under the platform's own policy — this flows from you to them, not from us.

We may also disclose information if required by law or legal process (we produce only what exists — the architecture in §1 deliberately minimizes it), or in connection with a corporate transaction such as a merger or acquisition, in which case this policy continues to apply to the transferred data until amended with notice.

4. Marketing email and your choices

The notify list, the weekly Discovery List, and any future marketing email are strictly opt-in and sent via HubSpot. Every message includes a working one-click unsubscribe. Creating a VinoMate account does not subscribe you to marketing email; that requires your separate consent at signup or later. Unsubscribing from marketing email does not affect transactional email needed to operate your account.

5. Retention and deletion

• Anonymous observations (prices, aggregate signals) contain no personal information and are retained indefinitely.
• Server logs are retained for 30 days.
• Account data is retained while your account is active.
• Deletion: you can delete your account from the portal or by emailing us. Deleting your account removes your record from the identity store immediately, which permanently severs your product data from your identity — it becomes anonymous and unlinkable. On request, we will also hard-delete the severed product data (cellar, taste profile, check-ins, history). Deletion also removes your contact from our CRM (HubSpot), subject to a minimal suppression record so we don't email you again by accident.
• Claimed review profiles: on deletion, the link is destroyed; if you separately ask us to remove pseudonymous review data associated with a source profile you demonstrate you control, we delete it and keep a suppression entry so future data collection does not recreate it.

6. Your rights

Depending on where you live (including the EU/EEA and UK under GDPR, and California under CCPA/CPRA), you may have the right to access, correct, delete, or receive a copy of your personal information; to object to or restrict certain processing; and to opt out of "sales" or "sharing" of personal information — noting that we do not sell or share personal information as those terms are defined in the CCPA, and we do not use sensitive personal information beyond what is necessary to provide the Services. To exercise any right, email privacy@vino2vino.com or use the account portal. We will verify your request (for account holders, sign-in is the verification) and respond within the time the law requires. We will not discriminate against you for exercising your rights. EU/EEA residents may also lodge a complaint with their supervisory authority. Our legal bases under GDPR are: performance of a contract (providing the Services you use), consent (marketing email, claimed profiles), and legitimate interests (security, service improvement using pseudonymous data).

7. Age

The Services concern alcoholic beverages and are intended for people of legal drinking age — 21+ in the United States. Account creation requires a 21+ attestation, and the Services are not directed to anyone under 21 (or the applicable drinking age where you live). We do not knowingly collect personal information from anyone under the legal drinking age; if you believe we have, contact us and we will delete it.

8. Security

Identity data is stored separately from product data with independent credentials and restricted access; identifying fields are encrypted; access is logged and reviewed. Product data references you only by an opaque internal identifier. Transport is encrypted (HTTPS) everywhere. No system is perfectly secure, but this design means a breach of the product database alone would expose no identities. Report security issues to security@vinomate.ai.

9. International transfers

We are based in the United States and process data there. If you use the Services from outside the U.S., your information is transferred to the U.S. Where GDPR applies, we rely on appropriate safeguards, including our processors' standard contractual clauses and data-processing agreements.

10. Changes to this policy

We will post changes here with a new effective date. For material changes affecting account holders, we will give notice by email or through the Services before the change takes effect. Prior versions are available on request.

11. Contact

Vino2Vino — 12163 Mougle Ln, Truckee, CA 96161, USA Privacy requests: privacy@vino2vino.com Support: support@vinomate.ai · Security: security@vinomate.ai