Your information at Winevery.

Who to contact

Winevery is the service responsible for the processing described here. The Winevery team handles privacy, account and security requests at hello@winevery.com. See support for the information to include in a request.

Information you provide

When you create an account, Winevery stores your email address, a salted password hash and account and membership records. If you choose Google sign-in, we receive the account identifiers and profile information needed to link that sign-in. We do not receive your Google password.

Features you use can store saved wines, quantities, cellar locations, preferences, wine and pairing ratings, tasting notes, tasting dates, optional photos, companions, places, occasions, journey progress and travel plans. Gift purchases can include the names and message you enter. Avoid adding another person’s private information without permission.

Signed-in sommelier conversations can be stored in your Winevery account to provide conversation history. Support messages contain whatever you send us. Password reset credentials are one-use, time-limited and stored as hashes.

Technical information and cookies

Our hosting infrastructure processes connection details such as IP address, request path, time and technical errors. Winevery uses essential cookies for sign-in, language preferences, guest sommelier allowances, search-event deduplication and optional Google sign-in security. An account session normally expires after 30 days.

Website analytics use Pirsch to measure aggregate use. The integration disables query-string and referrer collection and excludes account and private share routes. Country lookup for membership currency is performed locally from connection information. Browser visits to documentation pages can be included in website analytics.

Why we use information

We use information to provide accounts and wine records, personalise recommendations, manage access and gifts, process membership transactions, respond to requests, send necessary service emails, preserve security and prevent abuse. Where applicable, these activities support the service you request, our legitimate interests in operating and protecting it, your choices for optional features, and legal obligations.

Optional community rating sharing is controlled from your account. The recommendation system can use ratings shared by participating members and requires several supporting members before it returns a community signal. Private tasting notes and photos are not exposed through the public MCP connector.

Service providers and optional AI features

Railway provides application hosting and operational logs. Stripe handles payment details, invoices and subscription processing; Winevery stores transaction identifiers and access state rather than full card numbers. PostShiba handles transactional email, LogSnag receives configured product-event notifications, Pirsch provides website analytics, and Google processes sign-in if you choose it.

When an optional AI feature is available and you request it, relevant input such as your sommelier question, tasting note, wine context or travel request can be sent to OpenAI. The application requests that responses are not stored by that API; the provider’s own processing and retention terms still apply. Live travel research can involve web-search results. These optional AI calls are separate from the four public MCP tools, which use local catalogue and matching code.

When you use Winevery inside Claude, Anthropic receives the tool results. See our MCP privacy notice for the exact connector data flow. Providers may process information in countries other than your own. Their applicable terms and privacy practices govern their own processing.

Provider notices: Railway, Stripe, Pirsch, Google, OpenAI and Anthropic. Ask support for the current email and notification provider contacts.

Public sharing

When you deliberately create a public Passport share link, its selected content can be viewed by anyone with that link. You can revoke the share from Winevery. Copies, screenshots, third-party caches or responses already returned to another service may remain outside Winevery’s control. Your ordinary journal and cellar are account-scoped.

Retention

Winevery keeps account and saved-feature records while needed to provide your account, until you remove individual records or ask us to close it, subject to necessary security, dispute and transaction retention. Billing providers maintain their own legally required records. Expired sessions and temporary security records are cleaned up by the relevant service flows.

The MCP application does not persist tool arguments or create a conversation archive. Its source-throttling entries expire after one minute and are removed during later requests or when the process restarts. Tool name, success and duration can appear in application logs. Infrastructure logs follow the hosting provider’s configured retention; contact support for the current operational window. We do not promise immediate removal from all backups or third-party systems.

Your choices and requests

You can edit or remove individual journal and cellar records, export your journal, change optional rating sharing and email preferences, and revoke public share links. To request account access, correction, export, closure or deletion, contact support from your account email. We may need to verify ownership before disclosing or deleting records. Depending on your location, you may also have rights to object to processing, restrict it, withdraw consent or complain to your data-protection authority.

Disconnecting Winevery in Claude stops future connector use through that connection. It does not close a separate Winevery website account or remove results already held by Anthropic.

Security, age and changes

Winevery uses password hashing, expiring sessions, origin checks, account-scoped queries and request limits. No internet service can guarantee complete security. Winevery is intended for adults of legal drinking age in their location. We update this page when these practices materially change and show the revision date above.