Privacy Policy

Last updated: 12 November 2026

Barberry Garden (barberry.io) is a wine-writing project run by Boris Buliga, registered as a sole proprietor in Ukraine. Most of the site is free to read; it also offers paid memberships and a personal balance. This policy explains what data is collected and how it is used. The short version: we collect little, we don't sell it, and we don't share it with advertisers.

What we collect

Account data

If you create an account, we store your email address and a hashed password. Your account may be linked to a convive profile (public name, avatar) that you provide. This data is stored in our Supabase database and is used solely for authentication and site functionality.

Events and community gatherings

When you sign up for an event or community gathering, we store your registration status (confirmed, waitlisted) and any related event data, such as settlement balances. This information is only visible to you and site administrators.

Payments and balance

If you take a paid membership or top up your balance, the payment is processed by Monobank acquiring. We never see or store your full card number; the processor handles card data on its own secure systems and returns only the result. We keep a record of each transaction (amount, date, the tier or top-up, and its status) tied to your account so your subscription and balance ledger stay accurate.

Cookies and browser storage

We use essential cookies only. If you sign in, Supabase Auth sets session cookies to keep you logged in. These are strictly necessary for authentication and cannot be used to track you across other websites. We do not use any advertising or marketing cookies.

The site also keeps a few things in your browser for your own convenience, such as tasting notes you haven't submitted yet during a live event, or a photo on its way into a form. They stay on your device and aren't used to track you. If you turn off PostHog page analytics (below), that choice is kept there too. When you are signed in, the PostHog script that reports errors keeps nothing in your browser.

Analytics

When you are signed in, we record how the platform is used: the action (for example, that a draft was published or that you signed up for an event), the kind of page it happened on (a wine page, never which wine), the app you used and your membership tier. It also records how quickly the site's pages load and respond for you, by the same kind of page. Each event carries a random member id, never your name or email, and never what you write or what is in your cellar. Events go from our servers to PostHog in the EU, are visible only to admins, and PostHog keeps them for a year. You can turn this off at any time in your account settings, under Share usage statistics.

If you are not signed in, we count page views with PostHog in cookieless mode: nothing is stored in your browser, and visits are told apart by a hash of your IP address and browser that changes every day, so the same visitor looks new each day. The IP address itself isn't kept. We record the kind of page, how quickly it loaded and responded, how long you stayed, how far down you scrolled, the site that linked you here, and your browser, system, device type, language and time zone, never the full address, and nothing that identifies you.

When something breaks, the site, the apps and our servers send an error report to PostHog in the EU: what went wrong and where in our code, the address of the page you were on, including any id in it but nothing after its question mark (for visitors, only the kind of page), your browser or device, its system, and the app version. No location is recorded. A report from your own devices carries your random member id, so we can tell how many members a problem hits. We never attach what you write, and we cut anything that looks like a token, a key, an email address or a database row from the message before it is sent.

Turning off Share usage statistics also stops error reports from your devices. Errors on our servers are still reported; if you have turned it off, they carry no member id. If you are not signed in, reports carry no member id, only the daily hash described above, and turning off PostHog page analytics turns them off too. In the iPhone app, reports sent while no one is signed in carry a random id of the app on that phone instead, and follow the choice of the last member who signed in there. PostHog keeps error reports for a year.

Connected assistants and the command line

You can connect an AI assistant (Claude, ChatGPT or another) to your account, and sign in to the barberry command line. Either then acts as you: it reads what you ask about, such as the wine catalogue, your notes, your cellar (with what you paid and where each bottle is), events, posts, producers, your ledger and your account settings (read, never changed). It writes what you ask it to: a note, a bottle, a wine for the catalogue, or the scores of the room at a tasting you host or speak at. The command line can also delete one of your notes or remove a bottle, each only after you confirm in the terminal; an assistant can do neither. Neither can do anything your account can't. Some of what it reads is about other people, as you see it on the site: the names and scores of those who tasted with you, and how a host you owe asks to be paid.

What an assistant reads goes to the company that runs it and is handled under that company's terms and privacy policy, and that company keeps what it already read after you disconnect. We don't send it anywhere else. The command line runs on your own computer and talks only to us; if you let an AI assistant run it (as barberry skill install sets up), what it prints goes to that assistant's company, as above.

For each connected assistant we keep its name and the address it registered with, which permissions it holds, when it was connected and last used, and a fingerprint of its tokens, never the tokens themselves: an access token works for an hour, and the right to renew it lapses 90 days after the last renewal. A command-line sign-in keeps the same kind of record, with a token that works for 90 days. We delete these records 90 days after they expire or you disconnect them.

Each request is logged with which part of Barberry it reached, its result, the app and its version, and which connection made it, never with what it carried or your IP address; logs are kept for 30 days. If you share usage statistics, we also record which assistant tool or command was used, never what you asked or what came back.

You see every connected assistant and command-line sign-in under Signed-in terminals and connected apps in your account settings, and can revoke any of them there; it stops working at once.

Third-party services

  • Supabase: database and authentication. Your account data is stored on Supabase infrastructure.
  • Vercel: hosting and image storage (Vercel Blob).
  • Amazon Web Services: our API server runs on AWS in Stockholm, so requests from the site and apps pass through it. Account emails, such as sign-up confirmations and password resets, are sent with Amazon SES.
  • PostHog: usage analytics and error reports, as described above. Data is stored in the EU (Frankfurt, Germany). PostHog is a US company and may access it from the US; such transfers are covered by the EU-US Data Privacy Framework and standard contractual clauses. Page analytics for visitors who aren't signed in reach PostHog through relay.barberry.io, which PostHog runs on Cloudflare.
  • Anthropic: if you use the AI tools (identifying or adding a wine from label photos, or reading a receipt), the photos you submit are sent to Anthropic to be read. Anthropic doesn't train its models on them and deletes them within 30 days, unless they are flagged for abuse or the law requires longer. Data is stored in the US and may be processed elsewhere; transfers are covered by standard contractual clauses.
  • GitHub: hosts our code, and keeps encrypted backups of our database for seven days.
  • Telegram: if you link our Telegram bot, your Telegram user ID is stored for notification delivery. Curators who linked the bot also hear of wines waiting for review, with the wine and the name of the member who added it.
  • Discord: what we need to know to run the service reaches us in private Discord channels and stays there until we delete it: alerts about errors and about our servers, with the error's name and message and, when it happened to a member, their name; payment notices, with the member's name, the membership or top-up, the amount, and the invoice; a new sign-up, with the member's name, email, and sign-up note; and wines waiting for review, with the wine and the name of the member who added it. Discord is a US company.
  • Monobank: payment processing (acquiring) for memberships and balance top-ups. Card details are entered on Monobank's own secure systems; we receive only the result of a transaction, never your card number.

Data retention and deletion

Account data is retained for as long as your account exists. If you ask us to delete your account, we remove or anonymise the personal data that identifies you, such as your email, name, avatar, and messenger identifiers, and we delete your usage events from PostHog. Error reports from your devices carry your member id but no profile, and PostHog can't always delete those by id: what it can't, it keeps for the rest of its one-year retention. They say what broke, not what you wrote or own. Notes, ratings, and catalogue entries you contributed may be kept in anonymised form, detached from your identity, because they are woven into shared event reports and aggregate scores. Encrypted database backups roll over within seven days. To request deletion, contact boris@barberry.io.

Your rights

You have the right to:

  • Access the personal data we hold about you
  • Request correction of inaccurate data
  • Request deletion of your account (see how deletion works above)
  • Receive a copy of your data in a portable format

To exercise any of these rights, email boris@barberry.io.

Jurisdiction and terms

Barberry Garden operates under the laws of Ukraine. The terms that govern memberships, the balance, and use of the platform are set out in the public offer.

Changes

This policy may be updated occasionally. Significant changes will be noted on this page with an updated date.

Contact

Questions about this policy? Email boris@barberry.io.

Privacy Policy - Barberry Garden