One question first

Are you of legal drinking age?

CYRUS makes wines, spirits, and beers. Before you come in, we have to ask — most of the EU and the UK draw the line at 18, a handful of countries at 16 for beer and wine. If you're at or above the threshold where you live, click yes.

Please drink responsibly. We don't market to minors, and we'd rather you come in legally than not at all.


Legal

Security is not a feature we bolt on.

This page explains how we protect your data and payments, and how to tell us — responsibly — if you find a problem. We would rather hear about a vulnerability from you than read about it somewhere else.

Report a vulnerability

Contact

Email security@cyrusdrinks.com. We acknowledge every report within two working days.

What to include

A description of the issue, how to reproduce it, the impact you believe it has, and how you would like to be credited.

Safe harbour

If you act in good faith — avoid privacy violations, data destruction and service disruption, and give us reasonable time to fix the issue before disclosing it — we will not pursue legal action.

Scope

The shop at cyrusdrinks.com and the APIs behind it. Third-party services we rely on (Shopify, our payment provider, our email provider) are out of scope — report those to the provider directly.

How we protect your data

All traffic is served over HTTPS (TLS 1.2 or newer). Passwords are stored only as salted hashes — we never see or keep them in plain text. Access to production systems is limited to the people who need it, protected by strong authentication, and reviewed regularly.

We keep only the data we need to fulfil your order and run the shop, and we delete it when the legal retention period ends. See our Privacy Policy for the full picture of what we hold and why.

Payment security

Card payments are handled entirely by our PCI-DSS-compliant payment provider. Card numbers never touch our servers — we receive only a token and the last four digits, enough to show you the card you paid with and nothing more.

Keeping up to date

We keep our dependencies patched, monitor for abuse, and run automated checks in our build pipeline. When a serious issue affects our users, we will say so plainly and fix it.