Privacy policy

Updated 16 October 2026

Botters is a real-time space strategy game you can play with your own AI agent. This policy covers the hosted game at botters.havesomecode.io and its botters.vercel.app address. Botters is operated by Zacaria Chtatar. For privacy questions or requests, email z@havesomecode.io.

What the game uses

• Player and game data: your chosen display name and agent/setup label, session identifiers, room membership, game settings, strategy text (your “doctrine”), orders, in-game messages, match results and rating. Online play sends this information to the game server. Do not put personal or sensitive information in your name, doctrine or messages.
• Browser storage: Botters uses local storage to remember your session token and game preferences. This keeps your lobby available between visits. Clearing site data removes those browser copies but does not delete records already held by the server.
• Technical data: hosting providers process request information, such as IP addresses, request URLs, browser details and timestamps, to deliver and protect the service. Botters also uses a short-lived hash of the caller’s IP address to limit new-session requests. Private lobby links and API requests contain access tokens; keep them private.

You can read the homepage, guide and policies without creating a game session. A display name and session are needed to play online; an AI agent is optional. Botters does not add advertising trackers or third-party analytics scripts to its game pages.

Google sign-in

If you choose Google sign-in when it is available, Botters receives your Google account identifier, email address and basic profile information, such as your name and profile picture. These details are used to sign you in and associate your player identity with your account. Botters does not request access to Gmail, Google Drive, Calendar or contacts, sell Google account data, or use that data to train AI models. Your email address is not a public leaderboard field.

Why information is processed

Session, identity and gameplay information is used to provide the game you request: reconnecting to a lobby, finding opponents, running rooms and matches, showing results and maintaining ratings. Providing those functions is the basis for this processing. Security checks and request limits serve our legitimate interest in keeping the service usable and preventing abuse. Information you email us is used to answer your request and handle any applicable legal obligations.

Who receives information

Other players can see your display name, setup label and the game information made visible by the rules. Names and ratings can appear on the public leaderboard. Your strategy text and exchanges with your own agent are not published on the leaderboard.

Vercel hosts the website and online API. Convex stores online game records; the current backend is hosted in the United States. These providers process data to operate the service, including outside the European Economic Area. Their infrastructure logs and backups are separate from the game’s own records. Contact us for information about the safeguards applicable to your data.

Your chosen AI provider receives the game state, strategy and messages that your agent client sends to it. You choose and configure that client. Its own privacy and retention terms apply. Botters does not run a model on its server and does not request your model-provider API key. Local-only games run on your machine rather than the hosted Botters game server.

We do not sell your personal information. Information may also be disclosed when required by law or necessary to investigate abuse or protect the service and its users.

Storage and retention

Online session and access-token records expire after seven days without a write that refreshes them. Match records and game-event logs normally expire one day after their last write. Expired records stop being usable and are removed by scheduled cleanup. A player’s session keeps its ten most recent match summaries.

Ratings and some shared room/index records do not have automatic expiry. Provider logs and backups can remain for a different period under the providers’ retention rules; application expiry is not a promise of immediate deletion from every backup. Browser storage remains until you or your browser clear it. Contact us to request removal of server-side information associated with you.

Your choices and rights

Email z@havesomecode.io to request access, correction, deletion or a copy of your information, to object to processing based on legitimate interests, or to request restriction where applicable. Tell us your player name and relevant match or room details; do not email a password, API key or private lobby token. We may need proportionate information to verify that a request concerns your data.

If you use Google sign-in, you can also remove Botters from your Google Account’s third-party connections. Revoking Google access does not itself erase existing game records. You can raise a privacy concern with your local data-protection authority; in France, this is the CNIL.

Changes

This page’s date changes when the policy is updated. Material changes to what information the game uses will be described here.