Privacy

volleyOS is run by Logan Burney (sole trader), Hertfordshire, England. For UK GDPR purposes Logan Burney is the data controller for the account and club data described below. Contact us about your data at [email protected].

The app can keep your chosen next step privately on your device for up to seven days, including an invitation link you opened and a team name entered for unfinished setup. This does not grant access to a team; the app checks your current permissions when you return. A small sample observation batch records the first report view, drill view and choice to score a real match. It binds once to the first signed-in account, is not uploaded, and is cleared when you sign out. It contains no player names or notes and is not used to identify installs. Expired local state is discarded when the app next reads it. Uninstalling the app removes this local state; reopen your original link after installing.

When you sign up we store your email address and a display name. If you sign in with Google or Apple, we receive your email and name from them. We never see your password. Authentication is handled by Google Firebase Authentication.

A club record holds its name and, once a club chooses to publish a page, its branding, its town, a short description and any contact details it decides to show. Which accounts are its members and admins, and the code teammates use to join, are kept in a private area of the club that only members can read. They are never part of the public record. Teams hold a name. Player records hold a name, a shirt number, and a position. Players are entered by club members and are not accounts. A player cannot sign in, and we ask for nothing else about them.

Rosters are private to the club. The roster itself is never shown on a public page, even when a club publishes one. Whether a player's name can appear in a public match timeline is a separate, per-team setting, described under “What is public” below.

A match holds the two team names, an optional venue, the scoring format, the match-day squad, and every point as it was scored, including which player it was credited to, when a club is recording that detail. Scores are recalculated from that log rather than stored as a number.

A result for a match played before you started using volleyOS can be entered by hand instead. That is stored as its set scores and the winner only. There is no point-by-point log behind it, because there were no taps to record.

When a match is scheduled, the organizer chooses which players are invited to it. If you are invited, your answer (Yes, Maybe or No) is stored against that match, along with an optional note you can add for the organizer. That note is free text you write yourself, so it holds whatever you put in it. It is readable only by the match organizer, which means a club admin, the team's Coach seat holder, or whoever created the match. It is never shown on a public page and never to the rest of the team. An organizer can also record an answer on your behalf, and when they do, both your view and theirs say who set it.

An organizer can send a match to their team as a reply link. Anyone holding that link can see the squad list and answer for a name on it, without an account. On a junior team the list shows only shirt numbers. Other teams follow the full, initials or hidden setting chosen by the club and match organiser. Individual answers are never shown on the page, only how many are in, maybe or out. An answer given this way is stored like any other and marked as coming from the link. Someone not on the list can ask to be added; that request holds the name and number they typed.

From a match link you can ask for a team's results by email. We store your email address, the team, and when you confirmed. Nothing is sent until you confirm from the email we send you, every result email has a link to stop them, and stopping deletes your address. We send these through Resend, our email provider.

A team's matches can be added to a calendar app through a private calendar link. It lists each match's teams, time and venue, and works for anyone who has the link.

An admin can invite someone by email, or by a link they send themselves, for example in a team chat. A link invitation holds no email address: whoever opens it and accepts first joins the club and is connected to the squad place it was made for. A club member can also ask to be added to a team's squad. That request holds the name and shirt number they typed and is readable only by them and the team's organizers.

A club can group matches into seasons, and can keep a competition table holding the names of teams it plays against. Those opponent names are entered by the club and are not accounts.

If you buy a subscription we store what you are entitled to and until when: which plan, when it lapses, whether it came from a store purchase or from us, and the identifier of the store product responsible for it. We also keep a record of each billing event your store sends us: its event identifier, type, the product, whether it was a real or a test purchase, and when it arrived. That record is what stops the same purchase being applied twice.

A Club plan is bought by an administrator for a club, so we also store which volleyOS account is paying for which club, and the size band it was bought at. Only members of that club can see it; it is never part of the club's public page.

We never receive or store your card details, billing address or store account. The purchase itself happens entirely inside Apple's or Google's payment flow.

If a club uploads a logo it is stored in Google Firebase Storage and is publicly readable, because it appears on the club's public page. Don't upload anything you wouldn't put on a poster.

Nothing is public unless someone chooses to publish it.

So we can see where new clubs get stuck, we record when a club first reaches a few setup steps: adding a squad, scheduling a match, sharing a link, getting a reply, recording a result and gaining a second member. For your own account we record when you first tried the scoring demo, when you created or joined a club, and, if you choose to answer, where you heard about volleyOS. These are dates, not a history of what you do in the app. They are kept on our servers, are never shown to other users and are never shared.

The volleyOS website counts a small set of actions, such as opening the pricing page or choosing a start button. These are stored only as daily totals. We do not use analytics cookies, visitor identifiers, account identifiers or an individual event history, and we do not store your IP address, browser details or referrer with those totals.

Data protection law asks us to name a legal basis for each use. These are ours:

volleyOS runs on Google Firebase (Authentication, Firestore, Storage, Cloud Functions and Cloud Messaging), which stores and processes this data on our behalf. Data is held on Google infrastructure in the United States.

Notifications, such as a reminder to answer availability, are delivered through Firebase Cloud Messaging. We publish to a channel per account rather than keeping a list of your devices.

If you buy a subscription, the payment is taken by Apple or Google through your device's app store and we never see your card details. Apple and Google hold the purchase and the payment method under their own privacy policies, and they are the only parties who can cancel or refund it.

RevenueCat processes the store's receipt on our behalf so we know your subscription is active, and tells our server when it starts, renews or ends. It receives your volleyOS account identifier and your purchase history for this app (which products, when, and in which currency), and not your name, email address or payment details. Your volleyOS account identifier is a random string that means nothing outside our systems. RevenueCat processes this data in the United States.

Google, RevenueCat and Resend process data in the United States. Where that data is about people in the UK or the EU, the transfer relies on each provider's data processing terms, which include the European Commission's Standard Contractual Clauses and the UK addendum to them, and on the EU-US Data Privacy Framework and its UK Extension where a provider is certified under it. Email us for a copy of the relevant terms.

You can delete your account from inside the app: You → Manage clubs and account → Delete account. That permanently removes your login, your email address and display name, and your membership of any club. If you were the last member of a club, that club, its teams and its rosters are deleted with you.

Matches a club has already played stay with the club, because they belong to the club rather than to one member, but they no longer connect to you. If you want a club and its entire history erased, email [email protected] from the address on the account and we will do it.

Your subscription records go too. Any pending purchase, and the link between you and a club you were paying for, are deleted; a club you paid for keeps the plan it has already paid for, but stops naming you. We keep the record of each billing event with your identifier removed from it, so a repeated message from the store cannot re-create a subscription for an account that no longer exists. What is left says that a purchase happened, not who made it.

Deleting your volleyOS account does not cancel a subscription bought through Apple or Google. Only your store account can do that, and you should cancel there first, otherwise it keeps renewing with nothing to unlock. The plans screen has a Manage subscription button that opens the right page for whichever store you bought from.

Junior players are often on a roster. A roster entry is a name, a number and a position, entered by a club. The roster is never public, a roster entry is never an account, and a team marked as a junior team always keeps names hidden from public match pages. The name setting cannot be changed while a team is marked junior. volleyOS accounts are for the adults running the club, including coaches, organizers and volunteer scorers. They are not intended for children.

On a junior team, the account connected to a player's place is a parent's or guardian's. They get that player's matches, answer for them, and see their numbers, as the player would.

You can ask for a copy of your data, ask us to correct it, or ask us to delete it, by emailing [email protected]. UK and EU users have these rights under UK GDPR and GDPR. You can also ask for your data in a portable format, object to a use that relies on legitimate interests, and withdraw consent at any time.

If you are unhappy with how we handle your data, please tell us first so we can put it right. You can also complain to a data protection authority: the ICO in the UK, or the authority in the EU or EEA country where you live or work, for example the BfDI or your state's authority in Germany, the Garante in Italy, or UODO in Poland.

If this policy changes, the date at the top changes with it, and material changes will be flagged in the app.