Privacy Policy
TeamBalance Pro ("we", "us") is a web app that helps organizers of pickup and recreational sports groups manage players, attendance and balanced teams. TeamBalance Pro is operated by an individual under the AYBIA Labs brand; AYBIA Labs is a brand name, not a registered company. This policy explains what information the service handles, why, who can see it, and the choices you have.
Effective date: October 27, 2026
Contact: support@teambalancepro.com
1. Account holders, organizers and players
- Account holders sign in to TeamBalance Pro. Accounts are only for adults aged 18 or older (see section 13).
- Organizers are account holders who create an organization and groups and manage their players.
- Players take part in a group. A player may have a TeamBalance Pro account linked to their player profile, or no account at all — in that case the player profile exists only because an organizer created it. Player profiles can belong to minors when the organizer has appropriate authority (section 13).
Much of the player information in the service (for example names, ratings and attendance) is entered and managed by the group's organizer, who decides what to record and who can see the group. If you are a player and want information about you corrected or removed, you can ask your organizer or contact us (section 12).
2. Information we collect
Account information
- Your name and email address.
- If you sign up with email and password: your password, stored only as a one-way bcrypt hash. We never store your password itself.
- Whether and when your email address was verified.
- If you use Google Sign-In: see section 3.
- Your organizations, groups and role (owner, admin or member), invitations you send or accept, and group join requests you make.
Information organizers enter about players
- First and last name, playing position, a skill rating, a stamina value and whether the player is active, plus the communities (rosters) the player belongs to.
- Attendance for matches (playing, maybe, not playing), whether the answer came from the player or was set by the organizer, and when.
- Matches (date, time, venue, attendance deadline), generated and published teams, results, Player of the Match and match recaps.
- Venue names and addresses, and a map location for a venue when the organizer confirms one.
Information from players
- Attendance answers given through a personal attendance link, the signed-in "My Games" page, or a Telegram poll.
- Group join requests: the first and last name you enter, your account email and the date.
Telegram information (only for groups that connect Telegram)
- The Telegram group's chat id and title.
- For people who vote in the group's attendance or Player of the Match polls: their Telegram user id, username and first and last name as Telegram provides them, and their vote.
- The link between a Telegram user and a player in the group, when the player or organizer connects them.
- Records of the messages the service posted to the group (for example polls and published teams), so nothing is posted twice.
Billing information (organization owners who subscribe to Pro)
- The organization's Stripe customer and subscription references, the plan and billing period, the subscription status, billing and renewal dates, and whether and when a cancellation is scheduled.
- The billing address you enter when subscribing. It is sent to Stripe and kept by Stripe, where it is used to calculate sales tax; we keep only a one-way fingerprint of it to avoid reusing a checkout created for a different address.
- When you agreed to the Terms for the subscription.
- Payment card details are entered on Stripe's pages and handled by Stripe. We never receive full card numbers.
- If you ask for a refund, your request and our reply.
Security and technical information
- To protect sign-in and password reset against abuse, we keep keyed one-way digests (HMAC-SHA256) of the email address and the client network address of sign-in and password-reset attempts — not the email or address itself.
- Short-lived, single-use tokens for email verification, password reset, invitations and links, stored only as hashes.
- Our hosting provider processes standard technical request data, such as IP addresses and request logs, to operate and secure the service.
3. Google Sign-In
If you choose "Continue with Google", Google asks you to share your basic profile with TeamBalance Pro. We request only the standard sign-in permissions: openid, email and profile. We do not request access to your Gmail, contacts, calendar, Drive or any other Google data.
- What Google provides: your Google account identifier, your email address and whether Google has verified it, your name, and possibly a profile picture link.
- What we keep: your Google account identifier, the email address at the time your Google account was linked, and when the link was created and last used. A new account created with Google uses your verified Google email and your name. We do not store your profile picture, and we do not store Google access or refresh tokens.
- How we use it: only to sign you in — to create your account or to recognize the account your Google account is linked to.
- No automatic merging: a Google account is never connected to an existing password account just because the email address matches; you connect it yourself from your account settings after confirming your password. You can disconnect Google there too.
- Sharing: we do not sell Google user data, use it for advertising, or share it except with the service providers that run the app (section 8). Our use of information received from Google follows the Google API Services User Data Policy, including its Limited Use requirements.
- Deletion: you can ask us to delete your account and the Google information we keep (section 11).
4. How we use information
- To provide the service: accounts and sign-in, groups and rosters, attendance, balanced team generation, publishing teams, results and recaps.
- To send the emails described in section 7.
- To post to a connected Telegram group when an organizer asks (for example an attendance poll or the published teams), and to read the answers to those polls.
- To keep the service secure (sign-in limits, abuse prevention) and to apply plan limits.
- We do not sell personal information and do not use it for advertising.
5. Who can see player information
- Organizers (owners and admins) of a group see its players — including skill ratings and stamina — attendance, join requests (including the requester's account email) and match information. Organization members with the "member" role can view the roster without skill ratings or stamina.
- Players never see skill ratings or stamina. A player with a linked account sees their own attendance and their group's upcoming matches and published teams. A personal attendance link shows only that player's own name and answer, plus the match details.
- Group visibility is chosen by the organizer:
- Public — the group's page can be opened by anyone with its address and shows the roster (first and last names, positions and whether each player is active), published teams, results, Player of the Match and published recaps.
- Link — anyone the organizer gives the group's share link to can see recent published teams (names and positions); anyone with a match link can see that match's details, published teams, result, Player of the Match and recap.
- Private — none of this is shown through links; only organizers and players linked to the group can see it.
- Telegram: in a connected Telegram group, attendance and Player of the Match polls are not anonymous — members of the Telegram group can see who voted and how — and the published teams posted there include player names.
- AI recaps: a published recap can mention team names, scores and Player of the Match names, and is visible wherever the match's published information is visible.
- Billing: an organization's owners and admins can see its subscription status and billing dates; only owners can start or manage the subscription.
6. Match recaps written with AI
If an organizer asks for an AI-written match recap, we send OpenAI only the facts needed to write it: sport, date, venue name, team names, scores, the Player of the Match names and the number of participants — no email addresses, ratings, stamina or Telegram identities. The request asks OpenAI not to store it. The organizer reviews and edits the text before anything is published.
7. Emails we send
- Account emails: email verification, password reset and organization invitations.
- Organizer notifications, for example when attendance for a scheduled match is ready.
- When enabled, reminders to organization owners about the end of the 90-day Pro trial.
- Billing emails for organization owners who subscribe: payment receipts and other subscription emails sent by Stripe, and notice of price changes sent by us.
We do not send marketing emails. Emails are delivered by our email provider (section 8).
8. Service providers and sharing
We share information only with providers that run parts of the service for us, and only what each needs:
- Vercel — hosting and delivery of the website and application.
- Neon — database hosting (Amazon Web Services, US East).
- Resend — sending the emails in section 7.
- Google — Google Sign-In, when you choose it.
- Telegram — posting to and reading polls in Telegram groups that organizers connect.
- OpenAI — AI-written match recaps, when an organizer requests one (section 6).
- WeatherAPI.com — the weather forecast for a match, using the venue's map coordinates.
- Geoapify — finding a venue's map location from the address an organizer types.
- Google Analytics — website usage statistics on our public pages, only if you accept analytics cookies (section 9).
- Stripe — processes Pro subscription payments and calculates sales tax. Stripe collects payment details directly, may email receipts, and receives the subscribing owner's email address, the organization name and the billing address.
We may disclose information when required by law. Map links open Google Maps or OpenStreetMap only when you choose to follow them.
9. Cookies, browser storage and analytics
Cookies and storage the service needs
- Sign-in cookies set by our authentication system: a session cookie (keeps you signed in until you sign out; it expires after 30 days without use), a security (CSRF) cookie, and short-lived cookies used during Google Sign-In.
- A short-lived cookie (10 minutes) when you connect Google to your account.
- When you open a group invite link, your browser keeps the invitation for up to one hour so you can sign in and come back to it.
- Your analytics choice (accepted or declined) and the date you made it, kept in your browser's storage so we don't ask again.
Optional analytics cookies (Google Analytics)
Only if you accept analytics cookies, we use Google Analytics 4, a service provided by Google, to understand how visitors find and use our public website — which pages are visited, how visitors arrived (for example from a search engine or a campaign link), and general device, browser and approximate location (country or region) information. We use this only to improve our website and how we describe TeamBalance Pro.
- Where: only on our public pages — the home page, Pricing, the Terms of Service, this Privacy Policy, and the sign-in, sign-up, password-reset request, email-verification and create-organization pages. Never on player pages (match links, attendance links, group pages, invitations) and never in the signed-in organizer area.
- What is sent: only a page view for each of those pages — the page's address without query details (such as email addresses or private link codes; only campaign tags such as
utm_sourceand the chosen plan are kept), a fixed page title, and the page of ours or the website you came from (another website's address without its path). Like any web request, it also carries technical information such as your device and browser type, language and screen size, which Google uses to estimate your approximate location. We do not send scrolling, clicks or other interactions, and we do not send Google your name, email address, or any account, organization or player information. - Cookies: Google Analytics sets first-party cookies named
_gaand_ga_followed by an identifier, lasting up to 13 months. - Google receives your IP address in order to provide the service; Google Analytics 4 does not store IP addresses. Google processes this information as described in the Google Privacy Policy.
- Retention: Google Analytics keeps this event-level data for the retention period set in our Google Analytics account (2 months); summary reports may be kept longer.
- We do not use Google Analytics for advertising: Google signals and ad personalization are turned off, and we do not sell personal information or share it for cross-context behavioral advertising.
Your choice
Analytics cookies stay off until you choose Accept. You can change your choice at any time with the "Cookie settings" link at the bottom of our public pages. If you withdraw your consent we stop collecting analytics and delete the Google Analytics cookies for this site. You can also block cookies in your browser settings.
We do not use advertising or cross-site tracking cookies.
10. Security
Connections use HTTPS. Passwords are stored only as bcrypt hashes; sign-in, invitation, claim and attendance links use random tokens of which only a hash is stored; access to every organization and group is checked on each request; and sign-in and password reset are rate-limited. No system is perfectly secure, and we cannot guarantee absolute security.
11. Retention and deletion
Retention
- We keep information for as long as it is needed to operate the service.
- Some records expire automatically: security digests of sign-in attempts after 1 day (successful sign-ins after 30 days) and password-reset request records after 1 day.
- Single-use tokens expire: email verification after 24 hours, password reset after 1 hour, organization invitations and player claim links after 7 days, group invite links after the period the organizer chose (30 days by default), and personal attendance links when attendance for the match closes.
- Other account, organization, roster, match and attendance information is not deleted automatically; it remains until it is deleted by an organizer or by us on request.
- We may keep certain information where it is reasonably needed for security, legal or operational purposes, such as resolving disputes or preventing abuse.
- Billing records (subscription references, status and dates) are kept while the organization exists and as needed for accounting, tax and dispute purposes. Stripe keeps payment records under its own policies.
Deletion and correction
- Organizers can edit or delete the player profiles they manage. Players can disconnect Telegram from their linked profile.
- There is no self-service account deletion. To ask for your account or information to be deleted or corrected — including information we received through Google Sign-In — email support@teambalancepro.com. Requests are handled manually.
- We may need to verify your identity, and your authority to act for someone else, before acting on a request.
- Player information in a group is managed by that group's organizer; a request about it may require coordination with the organizer, and organizers and players may have different rights over it.
- Some information may be retained where required by law or otherwise justified (see above). Deleted information may remain in backups or logs for a period before it is overwritten.
12. Your choices and how to contact us
From your account settings you can change your password and connect or disconnect Google. Changing your name or email address is not self-service today. To access, correct, export or delete your information, or for any privacy question, email support@teambalancepro.com. If information about you was entered by an organizer, you can also ask that organizer. Depending on where you live, you may have additional rights under applicable law.
13. Adults-only accounts and youth player profiles
- TeamBalance Pro accounts are only for adults aged 18 or older. The service does not verify ages.
- Organizers may create and manage player profiles for minors — for example on youth teams — only when they have appropriate authority, such as permission from a parent or guardian. Minors should not create accounts or use the service directly; the service does not verify parental consent.
- Youth player profiles are handled exactly like other player profiles — there are no separate youth protections. In particular: in a Public group, anyone with the group's address can see the roster with each youth player's first and last name and position; in a Link group, anyone holding a group share link or match link can see their names in published teams, results, Player of the Match and recaps; and in a connected Telegram group, members can see names in posted teams and who voted how in the non-anonymous polls (section 5). Organizers decide these settings; organizers of youth groups should consider Private visibility and not connecting a Telegram group.
- If you believe a minor created an account, or that information about a minor was entered without appropriate authority, contact us at support@teambalancepro.com and we will review it.
14. Where information is processed
TeamBalance Pro runs in the United States: the application runs on Vercel in its iad1 (Washington, D.C., United States) region, and our database is hosted by Neon on Amazon Web Services, US East (N. Virginia, us-east-1). Vercel may deliver pages to you through its global network. Our other service providers (section 8) may process information in the United States or other countries. If you use the service from outside the United States, your information is processed in the United States.
15. Changes to this policy
We may update this Privacy Policy to reflect changes in our services, technology, legal requirements, or privacy practices. When we make changes, we will publish the revised Privacy Policy on this page. We may provide additional notice of material changes when appropriate or required by law. The effective date displayed above applies to the published Terms and Privacy Policy version and may be updated when a new version is formally issued. See also our Terms of Service.
