Developer privacy
What an API request shares.
This notice covers the Winevery developer dashboard and authenticated wine API. It supplements the website privacy policy. The public MCP connector has its own notice.
Last updated 2 November 2026.
Account information and credentials
Your developer account uses your existing Winevery account email and sign-in session. We store API key names, prefixes, one-way hashes, creation and expiry times, revocation status and last-use times. Full API keys are shown once at creation or rotation; they cannot be recovered from the dashboard.
Keys identify your developer account for authorization and quota enforcement. The wine API does not return your personal account records, cellar, journal or billing information.
Requests and usage
We process wine queries, wine IDs, filters and dish descriptions to provide the requested results. Avoid including personal or sensitive information in these fields. The application’s API usage tables record account and key identifiers, endpoint category, UTC day, request counts and credit totals. They do not store raw search queries, dish text or API response bodies.
Quota counters and per-minute request windows protect your allowance and the service. Diagnostic errors record a request identifier and status. Railway hosts the service and can process connection metadata and operational logs under its configured retention. Retained usage totals support billing, account history, abuse prevention and troubleshooting.
Payments and providers
Stripe processes payments and subscription changes. Winevery stores your API plan, Stripe customer and subscription references, subscription status, billing-period dates and cancellation status. Winevery does not receive your full card number. API subscription records are separate from Passport membership entitlements.
The five version 1 wine API endpoints use local catalogue and matching code. They do not send their query or dish content to OpenAI. Visits to the developer pages are covered by the website’s analytics practices described in the website privacy policy.
Control and contact
Revoke keys to stop future requests and cancel subscription renewal from the developer dashboard. Revocation does not erase usage already recorded or cancel a subscription. For account deletion, retained usage, data access or other privacy requests, contact hello@winevery.com. We may retain records needed to resolve billing, prevent misuse or meet applicable obligations.
See API terms, security reporting and MCP privacy. Never send API keys, account passwords or payment-card details in a support request.