Privacy Policy

Last updated: October 21, 2026

This Privacy Policy explains how BottleCount ("the app", "we", "us") uses your data when you use the BottleCount web application.

1. What BottleCount does

BottleCount helps you plan parties and manage tickets. It comes in three forms, and they differ in exactly one way that matters here: whether we hold any of your data at all.

2. Data stored in your browser

On every tier, your parties, drink menus, custom ingredients, cocktails, generated tickets, theme preference and app settings are stored locally in your browser (IndexedDB and local storage). On the free tier this is the only place any of it exists: we cannot read it, recover it, or hand it to anyone, and clearing your browser data deletes it permanently.

3. Data we hold when you sign in

Signing in with Google gives us the following, and nothing else:

We request no access to your Google Drive, Sheets, contacts, calendar or any other Google service. This record is stored in Cloudflare D1.

Your session is a signed token in an httpOnly cookie named session_token, valid for seven days. It is a strictly necessary cookie: it exists only to keep you signed in, and the app sets no analytics or advertising cookies.

4. Parties you share, and data about your guests

A party stays in your browser until you share it. Sharing — which both the invite link and co-organisers need — stores the whole plan on our servers: its name, date and venue, drink menu, quantities, costs, budget, ticket price and any ways to be paid you add. That is what lets your co-organisers open and edit it. Everyone on a party sees the plan and the other organisers' names, email addresses and avatars; you can remove a co-organiser at any time.

People holding the invite link see far less: only what an invitation shows — the party's name, date, venue and cover image — and, once they say they are coming, the ways to be paid you added (a PayPal.me username, a Satispay or Revolut link, or a bank account holder and IBAN). Your menu, shopping list, costs and budget are never shown to them.

We then store one record per person who opens that link: the name they type, their answer, when they opened it and answered, and who forwarded it to them. Guests are not asked to create an account.

If guests pay for your party (you set a ticket price and a way to be paid), a guest who says they are coming also gives an email address or a phone number, at least one. These are used only to send that guest their ticket for this party, by email or WhatsApp, from the organiser's own phone. You and your co-organisers can see them; nobody holding the link can, including the guest who entered them. A guest who changes their answer to no has them deleted. You can also add an email and phone number to a guest you type in yourself. When you mark a guest as paid we record when; BottleCount never sees or handles the payment itself.

When you send a guest their ticket from a shared party, the ticket — their name and ticket code, signed with the party's key — is stored with their guest record, so the short link you send can open it. The link works only while the guest is coming (and, on a party guests pay for, marked as paid), and the ticket is deleted with the party.

As the host, you decide what happens to those records. Closing the invite link stops new answers but keeps your guest list, so you can still send tickets and run the door. Stopping sharing the party deletes it from our servers together with every guest record, email addresses and phone numbers included. Under the GDPR you are the controller for your guests' data and we are your processor, which in plain terms means it is your party and your guest list — we hold it for you and delete it when you say so.

5. How we use it

Only to sign you in, to tell the app which features your plan includes, to run the features you use — keeping a shared party in step between its organisers, the invite link, and sending your guests their tickets — and to answer you if you contact support. We do not use your data for advertising or profiling, and we do not sell it or share it with third parties.

6. Processors

Cloudflare, Inc. hosts the application and the database. Google LLC provides sign-in. Both act as processors on our behalf; neither receives your data for their own purposes from us.

7. Retention and deletion

We keep your account record for as long as your account exists. Email us to have it deleted and we will remove it, along with any licence association and every party you own, within 30 days. A shared party is kept until you stop sharing it, which deletes it from our servers together with its guest records; closing only the invite link keeps them, so you can still send tickets and run the door. Data held only in your browser is deleted by clearing your browser's storage for this site, which happens without involving us.

8. Your rights and revoking access

If you are in the EU or the UK, you have the right to access, correct, export, restrict, object to and erase your personal data, and to complain to your local data protection authority. Email us to exercise any of them.

You can revoke BottleCount's access to your Google account at any time:

BottleCount's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy , including the Limited Use requirements.

9. Children's privacy

BottleCount is not directed to children under 13. If you are under 13, please do not use this app without parental supervision and consent.

10. Changes

We may update this Privacy Policy from time to time. When we do, we will update the "Last updated" date at the top of this page.

11. Contact

Questions? Contact the developer at marcoingalera@gmail.com.