Privacy notice

Information we handle

We handle account information such as your name, email, password credentials and profile details; team and player information submitted by users; match events, statistics, notes and uploaded images; and billing references and subscription status. Player records may include names, birth dates and guardian or performance links, depending on what users provide.

Why we use information

We use information to authenticate accounts, manage teams, show match activity and statistics, provide requested features and notifications, process subscriptions, answer support requests and protect the service from misuse. Shortly after you sign up, we send one welcome email with tips for getting started. It has an unsubscribe link, and you can turn these emails off in Account settings › Notifications. Stripe processes checkout and payment methods.

When you look for an athlete’s team records, we compare the athlete profile’s name, birth date, strong foot and location with the roster of the team you choose, and show you only likely matches. Roster details used for matching are not shown to you. Linking a record adds its performance statistics to the athlete profile; a public athlete profile shows them to signed-in users.

Visibility and sharing

Team context and follower relationships may be visible to others. Detailed player information is subject to access permissions. Anyone holding a match’s live link sees that match in full, including player names, with or without an account. Uploaded images have shareable URLs, so do not treat an image URL as a private vault. People who receive information may save or share it outside PlayState.

Service providers and optional features

We use services that help run PlayState, including payment processing through Stripe, email through Resend, email forwarding through Cloudflare and image storage through Cloudflare R2, along with hosting and database infrastructure. AI features send the inputs needed for the feature to OpenRouter and its selected model providers. These features include summaries, roster-image extraction and speech. Browser push services deliver enabled notifications.

Cookies and viewing activity

Session cookies keep you signed in. Where usage analytics is enabled, PostHog helps us understand pages visited, features used, signup and other completed actions, referral sources and repeat usage. We use a browser identifier and, when signed in, an internal account identifier. Events include your device type, operating system and browser name, and whether PlayState was opened as an installed app. For signed-in accounts, we also record the highest team role you hold, such as owner or follower. Our servers receive connection information such as your IP address. Usage events pass through our servers to our analytics provider without your sign-in cookies. Your IP address is passed on with them and PostHog discards it without storing it. We do not send player names, birth dates, form contents or private notes to PostHog, and session recording is disabled. When usage analytics is on, PostHog also receives reports of errors in PlayState: the error's type, message and where in our code it happened, without form contents or database values.

PlayState also stores match-viewing records: a hashed browser identifier, session times, visible watch time, referral source and an account reference when signed in. These records support match-viewing statistics. These identifiers do not make the records anonymous.

You can disable both PostHog and stored match-viewing analytics in Privacy choices. The preference is saved in this browser and applies across its open PlayState tabs. We also disable these analytics when your browser sends Global Privacy Control. For signed-in users, usage analytics is enabled by default unless disabled in this browser. We rely on our legitimate interests in understanding product use and improving PlayState for this signed-in analytics. Until visitors who are not signed in make a choice, PostHog counts their visits without storing anything in their browser: events are sent without an identifier, and PostHog derives one from a daily hash of the IP address, browser user agent and site, then discards the IP address and user agent. These counts can't be linked across days or to an account. Allow turns on the analytics described above; Decline stops this counting too. You can object to this analytics by turning it off in Account settings → Privacy or Privacy choices. Saved choices continue to apply after signing in or out. Your preference does not interrupt sign-in, match logging, follows, live updates or the connection-based watching-now count. Turning it off stops future collection and clears applicable browser analytics identifiers; it does not erase previously collected records. Deleting your account does not remove analytics records either; contact us to request that.

Teen accounts and younger players

Accounts are for people aged 13 or older. Younger players may appear in team records supplied by other users. Users must have authority to submit that information. Contact us if you believe an under-13 child has created an account, or to raise a concern about a child’s records. We may need to verify your identity and authority before acting on a request.

Retention

Ending a subscription preserves existing team history under its usual access permissions; paid tools stop when coverage ends. We keep information needed to provide the service and handle security, disputes and recordkeeping obligations.

You can delete your account in Account settings → Sign-in & security. Deleting it removes your name, email, photo, sign-in details, follows and reactions, and athlete profiles only you manage. Teams you own stay with their history, without an owner until an administrator assigns one; teams you own with no matches are deleted. Matches and events you logged stay without your name, because they belong to other people’s team history. An active subscription ends at once without a refund. Billing records stay for legal and financial reasons, and deletion from backups, cached images or third-party systems may not be immediate.

Your choices and requests

You can update available profile and notification settings in the app, and delete your account in Account settings. Contact warren@keypressworks.com to request access, correction or deletion of other records, or to ask about privacy rights available where you live. Include enough context to identify the account or team, but do not email passwords, full card details or unnecessary information about children. Requests affecting other people’s records may require additional verification.

Security and updates

We use access controls and other safeguards to protect information, but no service can guarantee absolute security. This notice may change as the service changes. We identify revisions by date and provide additional notice when required.

Contact us