Privacy
What AbsoluteBalls stores and why.
Ballchasing tokens are stored in an encrypted, HttpOnly browser cookie. Replay caches remain on the server running AbsoluteBalls. Browser workspace history stays in local browser storage unless a future account-sync service is explicitly enabled.
Ballchasing access
A connected Ballchasing token is encrypted before being stored in an HttpOnly, SameSite cookie. It is used only by server routes to retrieve content the connected account is authorized to access. Disconnecting removes the browser session cookie.
Replay processing
The server may temporarily download replay binaries and cache compact analysis results to avoid repeated Ballchasing requests. Cache retention depends on the deployment operator. The launch Docker configuration stores caches in a persistent mounted volume.
Workspace history
Recent searches, datasets, report links, and coaching conversations are stored locally for offline continuity. When Ballchasing is connected, a compact copy is also saved in an account-scoped server workspace so the same Ballchasing identity can reopen it from another browser connected with the same token. Deleting cached data removes both the analysis cache and this server workspace.
OpenAI
Paid OpenAI calls are disabled by default. If the deployment owner explicitly enables them later, only the reduced active analysis, question, and conversation context are sent from the server. The Ballchasing token and replay binary are not included.
Independence
AbsoluteBalls is an independent Rocket League analytics companion. It is not affiliated with, endorsed by, or sponsored by Ballchasing, Psyonix, Epic Games, or OpenAI.