About this notice
BotFight is an independent project operated from Azerbaijan. This notice covers botfight.live, its request form, analytics.botfight.live and Brickworld at brickworld.botfight.live.
BotFight has no site accounts, paid subscriptions, purchase flow or automated AI conversations. It offers optional project support by USDT transfer on TRON (TRC20). Brickworld has its own guest/account entry and saved world. Other external services have their own notices.
Contact us through the private form. No BotFight account is required and messages are not published.
Information used to run the services
- Connections: servers receive IP addresses, requests and browser headers to deliver pages, enforce limits and investigate failures. HTTP access logging is disabled for the covered public services; error/system logs can still contain connection information.
- Ideas and requests: we receive your message and any supplied email. Private requests require a reply address and text. Send only necessary information, without passwords, identification documents, payment details or sensitive personal data.
- Community: discussion titles, messages, replies, public chat messages, submission times and a stable browser guest number are stored to provide conversations. Approved discussions and chat messages are public. Pending submissions, reports, moderation reasons, sanctions and audit entries are restricted to the author where relevant and authorized operators; reports are not public.
- AI moderation: when enabled for discussions or chat, the server sends proposed message text, its title/category, room context and limited excerpts of recent published messages to OpenAI for safety and community-rule checks. Guest identifiers, cookies, IP addresses, private reports and administrator credentials are excluded. The interface explains this before submission. Results and suggested wording are stored with the private moderation record; provider processing is subject to its API data policies.
- Brickworld: nickname/name, optional registered login and password hash, account/world identifiers, hashed session tokens, progress, builds and gameplay communication/history support the game. Player names and builds can be visible within the shared world; credentials and private inventory are not published. Its essential host-only session cookie lasts up to 30 days. Game data stay separate from audience analytics.
- Hero: device time and time zone set the lighting. Optional browser location permission enables sunlight calculation with coordinates in page memory. Coordinates are not sent to BotFight or analytics. Clear them with the location control or by leaving the page.
Optional project support
The support dialog displays a locally hosted QR code and receiving address and can copy that address. It does not connect to your wallet, submit or verify transfers, or collect donor identity, balances or transaction records.
If you choose to transfer USDT, your wallet or exchange service and the public TRON network process the transfer outside this website under their own rules. Blockchain records can be publicly visible; BotFight cannot delete those records. Do not send wallet credentials or sensitive financial information through our contact form.
Optional audience analytics
Analytics is off until explicitly allowed. Website and game each manage their own preference. Refusal does not prevent browsing, ideas or gameplay.
Allowed self-hosted Umami collection includes cleaned page paths/referrers without query strings or fragments, language, screen size, browser/device information and limited named events: game details, Play Game, successful idea submission, game start and coarse visible play-time intervals.
The collector processes IP/user-agent for approximate country, region or city and limited visit/session identifiers derived using daily values. Location can be inaccurate and is not Hero GPS. Identifiers can associate events; they do not guarantee anonymity.
Analytics excludes search/form text, email, nicknames, account/game-session identity, authentication secrets and coordinates. There are no advertising pixels, session replay or an analytics SDK automatically loading other services. Do Not Track and Global Privacy Control override saved allowance.
Why information is used
Necessary information delivers pages, maintains game progress, handles ideas/requests and protects the services. Optional statistics help improve pages and games.
Optional analytics relies on separate consent where a legal basis is required. Service delivery, requests and security use bases available under applicable law, including requested services, legal obligations or legitimate interests where permitted. This notice alone does not fulfill every processing requirement.
Retention and deletion
- Analytics: a 90-day retention target in the active database and a 14-day target for restricted backup archives. Each daily cleanup can add up to 24 hours during normal operation. Restoration requires cleanup before collection resumes.
- Ideas and private requests: 365 days from receipt for review, response and a handling record, followed by the next daily cleanup, which can add up to 24 hours during normal operation. A specific legal requirement can require longer retention.
- Community conversations and their guest identities remain while the community or contribution exists, subject to moderation and manual deletion requests. Private moderation evidence and reports support review and appeals. Clearing a browser cookie does not erase a submitted message or the moderation record; include the guest number, message and approximate time in a private deletion request.
- Browser analytics choice: up to 180 days, without a visitor identifier. Clearing storage removes it.
- Brickworld profiles/progress: while the account or project exists, with verified deletion requests handled manually. Clearing a cookie does not delete the server world. Game backups rotate under the game’s own backup plan.
- Error/system logs: limited by size and rotation; duration depends on traffic, faults and investigation needs. They are separate from audience analytics.
Access, hosting and external services
Private messages, game data, analytics and backups are restricted to authorized operators and necessary hosting infrastructure. Operating from Azerbaijan does not mean every server or access location is in Azerbaijan.
We do not sell these data or use personalized advertising. Disclosure can be required by law or a valid security/rights request. External services control their own processing.
Your choices and requests
Withdraw optional analytics through Analytics choices at any time. This stops future collection, not past processing. Browser settings can clear storage and revoke location permission.
Applicable rights can include access, correction, deletion, restriction, objection, portability and complaints to an authority or court. Identify the service/data in the private form. Proportionate verification may be needed; never send a password.
Requests are reviewed manually within applicable deadlines. Azerbaijan-law requests receive a response within 7 working days, with a permitted further 7-working-day third-party inquiry extension explained. Analytics records may not be locatable by name because they are not connected to player identity; we explain limits rather than collecting new identifiers solely to identify visitors.
Young visitors and changes
Young visitors’ consent rules vary. Where guardian authorization is required, do not enable analytics or submit personal data without it. We provide no verified parental-consent mechanism; an age statement is not one.
Future BotFight accounts, paid products, payment integrations, AI conversations or providers need fresh review and notices. Material new optional purposes need a new choice.