Privacy Policy
This policy explains what information Build A Player uses, why it is used, and what choices visitors have. The game is designed to work without creating an account or providing a real name.
Information stored on your device
Standard game progress is stored in your browser using local storage. That data can include the current game mode, a randomly generated game seed, selected players and traits, whether a skip was used, team fit, and the resulting simulated season. Daily challenge progress may also be stored with the challenge date so a completed board can be resumed on the same device.
Local storage remains in the browser unless you clear site data, use a private browsing session, or the browser removes it. Build A Player does not use this local progress to identify you. Clearing local storage resets unfinished and saved runs on that browser.
Shared challenge links
When you choose to share a result, the link contains a compact game payload. It can encode the game version, mode, simulation seed, selected team, player choices, and chosen attributes. Anyone who receives the link may be able to reproduce the same challenge. Do not put personal information into a shared URL, post title, or message that accompanies a link.
Opening a shared link also creates an ordinary web request. As with most websites, hosting and security providers may process limited technical information such as an IP address, browser type, requested path, timestamp, and diagnostic or abuse-prevention data.
Daily challenge and infrastructure
The Daily page may request the current challenge configuration from the project database. The request is used to retrieve the date, game mode, and deterministic seed for that day. The public game does not require an account, and the Daily request is not designed to attach the challenge to a named profile.
Build A Player relies on hosting, database, and delivery providers to make the site available and keep it secure. Those providers may process standard server logs under their own terms and privacy obligations. Logs may be retained for reliability, security, debugging, and prevention of abusive traffic.
Cookies and similar identifiers
Build A Player does not currently require advertising cookies to play the game. Essential browser storage may still be used for game continuity and technical operation. If advertising is enabled, third-party vendors, including Google, may use cookies, web beacons, device identifiers, IP addresses, or similar technologies to deliver, measure, limit, and personalize advertising.
Google and its advertising partners may use advertising cookies to serve ads based on a visitor's prior visits to this site or other sites. Other authorized advertising vendors may also use cookies or similar identifiers for ad delivery and measurement. The vendors that actually serve ads may change over time, and their processing is governed by their own privacy policies.
Advertising choices
You can manage or opt out of personalized Google advertising through Google Ads Settings. You can also learn about choices offered by participating advertising companies at YourAdChoices. Browser controls can block or delete cookies, although some preferences and saved game progress may then stop working.
For visitors in the European Economic Area, the United Kingdom, or Switzerland, personalized advertising will only be enabled with an appropriate consent process. When required, the site will use a Google-certified consent management platform so visitors can accept, reject, or adjust applicable advertising purposes before eligible personalized ads are requested.
Analytics and measurement
Basic, non-sensitive analytics may be used to understand whether pages load, which game modes are completed, and where reliability problems occur. Analytics should be configured to avoid intentionally sending names, email addresses, phone numbers, or other direct personal identifiers. If a new analytics service materially changes this processing, this policy will be updated before or when that service is introduced.
Data we do not ask for
The public game does not ask for payment information, government identifiers, health information, precise location, or a profile containing sensitive characteristics. Browser geolocation is not requested. Simulation results have no monetary value and are not connected to gambling, prizes, or a real sports account.
Children
Build A Player is a general-audience sports game and is not designed as a service directed specifically to children. Visitors should not send personal information through shared links or contact messages. A parent or guardian who believes a child has provided personal information can contact the site to request review.
Retention and your choices
You can delete locally stored game data through your browser's site-data controls. Shared URLs may remain wherever you or another person posted them. Standard infrastructure logs are retained according to operational, security, and provider requirements, then deleted or aggregated when they are no longer needed.
Policy changes and contact
This policy may change when advertising, analytics, community features, or infrastructure changes. The date at the top will be updated when material revisions are published. Questions about this policy can be sent to hello@buildaplayer.games or through the Contact page.