Last updated: 2026-08-27
Batru (“we”, “us”) operates the website batru.gg and companion services, including our hosted MCP server and the Batru in-game coach for Dota 2 on Overwolf (together, “the Service”). This policy explains what data the Service collects, why, and your choices. Website analytics choices are described below and do not control server-side operational logs generated when the hosted MCP server or public API is called.
Calls to https://batru.gg/mcp are logged by default to measure adoption, understand which tools agents need, improve result quality, diagnose errors and prevent abuse. MCP analytics may include the caller’s IP address, client and user-agent information, a pseudonymous identifier derived from network and client information, tool names, inputs and outputs, agent-provided intent, duration and error details. These records are not used for advertising or sold to third parties.
Hosted MCP logging is server-side and is separate from the website analytics choice above. No Batru account or API key is required. The local stdio package started with uvx batru-mcp does not send MCP tool-call analytics such as agent intent or tool inputs and outputs. Its calls to the public Batru API remain subject to ordinary server logs.
When you run the Batru overlay alongside Dota 2, we read the in-game telemetry that the Overwolf Game Events Provider (GEP) exposes for your own game client:
This snapshot is sent to our servers at https://batru.gg/api to compute your live win probability and item/skill recommendations, and to train and improve our prediction models. We do not transmit or store personal identifiers from the overlay — no Steam names or IDs, real names, emails or payment information — and the overlay does not read files on your computer outside the app itself.
(Dota 2 requires -gamestateintegration in its launch options for these events to be available.)
We do not sell or rent your data, and we do not share it with third parties for their own marketing. Overlay telemetry is anonymous gameplay data and is kept within the Batru ecosystem to power the Service and improve our models. Hosted MCP analytics is used only to operate and improve Batru, diagnose failures, understand adoption and prevent abuse.
We rely on trusted processors to run the Service: Google (Analytics), PostHog and Microsoft (Clarity) for website analytics; PostHog also processes hosted MCP analytics. Google Cloud provides storage and Vertex AI for model training, and our managed database provider supports the backend. They process data on our behalf under their own terms.
Analytics is optional and the tools continue to work without it. Where consent is required, the first layer offers equally accessible “Only necessary” and “Allow analytics” choices; no analytics tool loads before that choice. Advertising storage remains disabled even when analytics is allowed. You can change your choice at any time through “Cookie choices” in the footer, or clear it through your browser settings.
We keep analytics and operational records only as long as reasonably needed for the purposes described above. You can avoid hosted MCP analytics by using the local stdio package, stop overlay data collection by closing or uninstalling the app, unsubscribe from the newsletter via any email, and contact us with questions or objections about your data. Because MCP identifiers are pseudonymous and overlay telemetry is not tied to an account, we may not always be able to trace a specific record back to an individual.
The Service is not directed to children under 13 (or the minimum age of digital consent in your region), and we do not knowingly collect data from them.
We may update this policy as the Service evolves. The “Last updated” date above reflects the current version.
Questions about this policy? Reach us via our contact page or at batru.gg.
One data-driven email a week — tier shifts, counters and duos across the games Batru covers. When a big patch lands, you get the winners & losers breakdown.
One email a week. No spam, unsubscribe anytime.