Privacy Policy

What GBot is

GBot is a Chrome extension that provides user-configured automation and helper controls for the browser game Gladiatus. This policy applies to the extension, the QAutomatika licensing and activation pages, and related support processes.

Gladiatus page and game data

GBot reads the currently open Gladiatus pages and their visible game state so it can perform enabled actions and show status. This can include inventory, packages, shop and auction data, combat pages and reports, character statistics, cooldowns, messages, configured targets, and other page values needed by the selected feature.

That game data is used in the browser to run the feature the user enabled and to maintain local checkpoints, statistics and settings. It is sent to Gameforge as part of the normal authenticated game requests required to perform those actions. GBot does not send the complete game page to the QAutomatika licensing API.

Identity, licensing and the free trial

For server-authoritative trial and license binding, the extension sends the current Gladiatus region, server and player identifier to the QAutomatika API over HTTPS. The trial is limited to one use for that stable game identity and does not reset when the extension or browser storage is removed.

On the backend, the identity is normalized and immediately converted with a server-secret keyed HMAC into a pseudonymous lookup value. The raw player identifier is not persisted as the licensing identity, placed in a website URL, included in an entitlement token or email, returned in normal API responses, or written to normal application logs.

Local extension storage

GBot uses Chrome local storage for user settings, per-character checkpoints, planner data, reports and statistics, interface state, the local activation credential and signed entitlement-token cache, and optional Telegram configuration. This data supports operation across page navigation and service-worker restarts. You can clear it from the browser or by removing the extension.

License activation and verification

A license key is sent to the QAutomatika licensing API only when the user explicitly activates a license. After activation, routine checks use a separate random activation credential and a short-lived signed entitlement token instead of repeatedly sending the license key. The token contains only opaque entitlement information required by the extension and does not contain a player identifier, email address or Gumroad order.

The licensing service stores the information needed to validate entitlement, enforce binding, handle trials, process refunds or disputes, and provide support. It does not expose another user's identity or license through an email address or player identifier alone.

Telegram integration

Telegram is optional and is used only when the user enables it. The bot token is stored in the extension's local storage and is sent directly to Telegram's API for the requested bot operations. The QAutomatika licensing API does not receive the Telegram bot token.

When enabled, GBot can send user-requested status, start and stop commands, game messages and replies through Telegram. It can also forward selected private or guild game messages to the paired Telegram chat. Telegram receives the chat identifier and the content needed to deliver those messages. Telegram's own policies govern its handling after delivery.

Gameforge session data

GBot may read the Gameforge session information available to the logged-in game or lobby page in order to make authenticated Gameforge requests, including the optional lobby relogin flow. Those credentials remain in the browser's Gameforge request context and are not sent to the QAutomatika licensing API.

Purchases and license email

Gumroad processes the payment checkout. QAutomatika receives verified sale information from Gumroad's seller integration, such as the sale, product, purchased version, status and purchase email, so it can create or extend the corresponding GBot license and handle refunds or disputes. GBot does not use Gumroad's built-in license keys.

The license email is sent to the purchase email supplied to Gumroad through a transactional email provider. The browser cannot choose a different delivery address after payment. License emails do not contain the raw Gladiatus player identifier.

What we do not do

• We do not sell user data.
• We do not use user data for advertising profiling.
• We do not use invasive device or browser fingerprinting.
• We do not use game data for unrelated analytics.
• We do not collect payment card or bank details through the extension.

Retention

Local extension data remains until the user clears it or removes the extension. Server-side licensing, trial, purchase, refund, dispute, email-delivery and support records are retained for as long as needed to provide entitlement, prevent repeated trial abuse, reconcile purchases, support customers and meet applicable operational or legal obligations. Retention can differ by record type.