Privacy Policy
What we collect, why, who we share it with (short list, no ad networks), and your rights over it.
1. Scope and who this policy covers
This Privacy Policy explains how LEAGUEBUCKET LLC ("LeagueBucket," "we," "us") collects, uses, and shares personal information through the LeagueBucket website and application (the "Service"). It covers everyone who interacts with the Service: league commissioners, Members (players, parents, spectators, officials, followers), people who submit the youth-league waitlist form, and visitors to our public pages.
This policy first took effect on October 20, 2026 and was last updated on October 25, 2026.
2. Two different roles: controller and processor
For account and billing information you give us directly (your login email, your subscription plan, your support requests), LeagueBucket decides how and why that information is used, and is the controller (or, in CCPA terms, the business) for it.
For information a league's commissioner enters about that league's own Members -- rosters, contact details, results -- the commissioner and their league decide what gets entered and why. LeagueBucket processes that information on the league's behalf and instruction, as a processor (or service provider). This distinction, and what it means for how league data is handled, is spelled out fully in our Data Processing Addendum, which every league is subject to.
3. Information we collect
We collect information in three ways:
- Information you give us directly: account email and password (handled by our authentication provider; we never see your password in plain text), league and season setup details, roster and schedule information a commissioner enters, messages sent through the Service, support requests, the adult contact details submitted through the youth-league waitlist form, and the email address you enter on the pricing page if you ask to be told when a paid plan goes on sale (used to send that one email and for nothing else), and what you send through the Contact us form: your message, the email address you give for the reply, your name if you add it, and whether you were signed in (kept so we can answer you and follow up).
- Information collected automatically: basic usage and diagnostic data (pages visited, error reports, device/browser information) needed to run and secure the Service. See the Cookie Notice for exactly what's stored in your browser. If you arrived through one of our tagged campaign links (an ad, for example) and then create an account, the campaign tags and the page you first landed on are saved with your account, so we can tell which of our ads, posts and links bring people in. That record is deleted with your account and never shared. We do not set that cookie for visitors in the European Economic Area or the United Kingdom.
- A record of your agreement to these terms: when you create an account we record which version of the Terms of Service, Acceptable Use Policy and this Privacy Policy you were shown, the date and time you accepted them, and the IP address and browser you accepted them from. We keep this for as long as the account exists and afterwards, because it is the record that answers a later dispute about whether an account holder agreed to the terms -- see "Data retention" below.
- If you sign up for text alerts: the mobile number you enter, and a record of that consent -- the date and time you gave it, the IP address and browser it came from, and the version of our terms in force -- together with when you confirmed it and when you stopped. We take a number for texts only from a signed-in league member entering their own; the Text Message Terms describe the program.
- Information from third parties: if you pay for a plan, Stripe (our payment processor) tells us the status of that payment -- we receive confirmation and billing metadata, never your full card number. If you choose Continue with Google, Google tells us your email address and name once you agree on Google's screen; the email becomes your account address. We never see your Google password, and we do not read anything else in your Google account.
4. How we use information
We use information to operate the Service: creating and running leagues, showing schedules and standings, sending the messages a league or its Members have asked for, processing payments, providing support, keeping the Service secure, and understanding usage well enough to fix problems and improve it.
We also use the agreement record described above, and our internal log of administrative changes, to resolve disputes -- including a dispute about a payment or about whether an account holder accepted these terms. This is the only purpose either record is used for.
We do not use Member information to build advertising profiles, and we do not use it for any purpose beyond running the Service for the league it belongs to. See the Ad-Free Pledge, both on its own page and as a binding term of the Terms of Service.
5. No sale of data, no ads
We do not sell, rent, or trade personal information to advertisers or data brokers, on any plan, for any reason. We do not run third-party advertising on the Service. This is written into our Terms of Service rather than living only in a policy page, and section 5a of those Terms commits us to 30 days' notice and an email before any of it changes -- so it cannot change quietly, even though we are not calling it permanent.
Mobile phone numbers and text-message consent are held to the same rule, stated separately because mobile carriers require it to be: no mobile information will be shared with third parties or affiliates for marketing or promotional purposes. A number given for text alerts is shared only with the provider that delivers the message, which is delivery and not marketing. The record of your consent to receive texts -- when you gave it, and from where -- is not shared with any third party for any purpose. Our Text Message Terms describe that program in full.
6. Who we share information with
We share information only with the service providers ("subprocessors") that help us run LeagueBucket, and only to the extent needed for them to do that job, under contracts that restrict them from using it for anything else. Our subprocessors are:
- Supabase -- database, authentication, and file storage.
- Vercel -- application hosting.
- Stripe -- payment processing (Commissioner/League Pro plans and League Pro dues collection). Stripe never shares full card numbers with us.
- Resend -- transactional email (invitations, notifications, and account mail), delivered through Amazon SES. It receives the email address the message is going to and the contents of that message.
- Twilio -- text message delivery, for Members who sign up for text alerts. It receives the mobile number a message is going to and the contents of that message. Texts begin once our carrier registration is complete; until then Twilio receives no personal information.
7. Data retention
If you ask us to delete your information (see "Your rights" below), we will, except for the records below that we keep to answer a dispute or meet a legal obligation. Nothing is deleted on a timer yet. What we keep, and when it goes:
- Your account: for as long as it exists. There is no self-serve delete button yet; email privacy@leaguebucket.com and we delete it by hand. Deleting an account also deletes its league roles, its plan record, its saved campaign source and its scorer assignments. Messages and Contact us messages you wrote stay with the league or with us, with your account removed from them.
- A league and everything entered about it (teams, rosters, schedules, results, Member contact details): for as long as the league exists. When a commissioner deletes a league, it is hidden from everyone but kept so it can be restored if the delete was a mistake. It stays that way until the commissioner asks us to erase it for good, which we do by hand.
- The record of your agreement to our terms and your sign-in history: kept after your account is deleted, for as long as a dispute or legal claim about the account could still be raised. They are used for nothing else.
- Text-message consent records: for as long as your membership in that league exists, including after you stop texts, so we can show when you agreed and when you stopped.
- Contact us messages: until we delete them.
- The `lb_src` campaign cookie: 30 days in your browser, or until you create an account.
- Payment records: Stripe keeps the payment and card details under its own legal obligations. We keep the records we need for tax and accounting for as long as tax law requires.
- Backups: our database provider keeps daily backups for 7 days, so deleted information can remain in a backup for up to 7 days before it is gone.
- Email delivery logs: our email provider keeps a log of each message it delivers for a limited period under its own retention rules, then deletes it.
8. Your rights
Depending on where you live, you may have rights to access, correct, export, or delete your personal information, and to object to or restrict certain uses of it. You can exercise any of these rights by emailing privacy@leaguebucket.com. We currently fulfill these requests manually; a self-serve export/delete tool is planned but not yet built, so please allow time for a human to process your request and expect us to verify your identity before acting on it.
If you are a Member of a league rather than its commissioner, some of your information (like your roster entry) may need to be corrected or removed by that league's commissioner rather than by us directly, since they control what's entered about their league -- we'll tell you which applies when you contact us.
9. Children's privacy
LeagueBucket is an adult-only service at this time (see the Terms of Service, "Who can use LeagueBucket"). We do not knowingly collect personal information from anyone under 18. If we learn that we have, we will delete it.
The one deliberate exception is the "youth leagues coming soon" waitlist: it exists specifically so we can gauge interest from youth leagues without collecting anything about the children involved. That form asks only for the requesting adult's own name and contact details -- never a child's name, age, birthdate, or contact information. If you run a youth league, please do not enter anything about your players there.
10. International visitors, including the EEA and the UK
LeagueBucket is operated from the United States and markets only in the United States. Our public pages can be read from anywhere, so if you use the Service from the European Economic Area (EEA) or the United Kingdom, the EU General Data Protection Regulation or the UK GDPR may apply to you, and this section says how.
The legal basis for each use of your information:
- Running your account and the Service you or your league signed up for (contract).
- Keeping the Service secure, preventing fraud and abuse, and answering a dispute about an account or a payment (legitimate interests).
- Text messages, and any email you asked to receive that is not about your account or your league, such as the note when a paid plan goes on sale (consent).
- Billing, tax and accounting records (legal obligation).
11. Your rights and the transfer to the United States, if you are in the EEA or the UK
Your rights: you may ask for a copy of your information, ask us to correct it or erase it, ask us to restrict how we use it, ask for it in a portable format, object to a use based on legitimate interests, and withdraw a consent at any time (which does not affect what we did before you withdrew it). Email privacy@leaguebucket.com. If you are a Member of a league, some requests go to that league's commissioner, as section 8 explains. You also have the right to complain to the data protection authority where you live or work, or in the UK to the Information Commissioner's Office.
International transfer: your information is transferred to and stored in the United States, where our service providers listed in section 6 also process it. The United States does not have the same data protection laws as the EEA or the UK. We have not appointed a representative in the EU or the UK.
Cookies: we do not set the `lb_src` campaign cookie for visitors in the EEA or the UK, so the only cookies set for you are the ones needed to keep you signed in (see the Cookie Notice).
12. Security
We use industry-standard measures to protect information in the Service, including encryption in transit and database access control (Postgres row-level security scoped per league). No system is perfectly secure, and we cannot guarantee absolute security.
13. Changes to this policy
We may update this policy from time to time. If a change is material, we will give notice before it takes effect, the same way described in the Terms of Service.
14. Contact
Questions about this policy, or requests relating to your personal information, can be sent to privacy@leaguebucket.com.