TB Turbo — Privacy Policy
Last updated: 27 October 2026
TB Turbo ("the extension") is a browser extension that automates gameplay
tasks within a supported web-based game. This policy explains exactly what data
the extension handles and why. We keep this short because the extension is
designed to handle as little data as possible.
What we handle
- Your licence key. When you activate the extension, your
licence key is sent to Gumroad (our payment provider) to verify the purchase,
and stored in our licensing database to track your activation and remaining
credits.
- A device identifier. We generate a non-reversible
identifier for your browser/device and store it against your licence. This is
used solely to enforce one active device per licence (so a single key cannot
be shared across many machines). It is not used to track you and is not linked
to your identity.
- Your settings and credit balance. Your in-extension
preferences (selected mode, language, captain count, etc.) and your current
credit balance are stored locally in your browser and, for credits, in our
licensing database.
What we do NOT do
- We do not ask you to provide your name, email or address
to use the extension. Game names or chat may be visible in the game captures described below.
- We do not collect your browsing history, the websites you
visit, your keystrokes, or any activity outside the supported game's page.
- Screen captures and vision checks. To automate the
game, the extension captures the game screen. Standard automation analyses these captures on your device using on-device image recognition. From version 3.0.21, vision assistance is enabled by default for licensed users and can be disabled in Having issues?. When assistance or optional decision comparison is enabled, cropped game regions are sent through our service to TypeSafe. These crops may include visible game names, queue labels and chat within the cropped area. Your assistance choice is saved; decision comparison is off by default. If the vision service is unavailable, automation falls back to standard on-device checks for the current run without resetting its march or credit limits. Comparison records observations. Recovery checks can stop uncertain progress, help locate march controls and retry known failures within the original march allowance.
- We do not sell or rent your data, and we do not use it for advertising or any purpose
unrelated to running the extension and its licensing.
Who receives data, and why
Optional support report. Having issues? can prepare a report
locally with browser and reported operating-system versions, display and game
dimensions, selected automation settings and run counters. It does not include
screenshots, account names, licence keys, credit balances, URLs, browsing history,
device identifiers or raw logs. You can review and edit it before downloading or
copying it. Collection uploads nothing. If you choose to email support, your
email application sends your message and any report you attach to
tbturbodev@gmail.com; your own description and sender address are included in that
email. The extension does not send the email automatically.
- Gumroad — receives your licence key to verify your
purchase. See Gumroad's own privacy policy for how they handle it.
- Google Firebase — hosts our licensing database, which
stores your licence key, device identifier, and credit balance so licensing
works across sessions.
TypeSafe receives cropped game images when vision assistance or optional decision comparison is enabled. Our service processes images in memory and logs check results, token usage and image hashes, without retaining the uploaded image. Provider processing is subject to TypeSafe’s privacy policy.
Permissions
The extension requests broad host access so it can communicate with our
licensing services (Gumroad and Firebase) and run on the supported game's page.
It only acts on that game's site; it does not read or modify other websites.
Data retention
Our vision relay verifies your licence with Gumroad to issue short-lived access. It keeps hashed licence identifiers, request counters and limited check metadata to enforce usage limits; it does not retain uploaded image files. Connection IP addresses are hashed for in-memory request rate limiting and are not included in the relay's retained check logs. We do not request GPS or precise device location. Per-request metadata is retained for up to 48 hours and usage counters for up to four days. Licensing records are kept for as long as your licence is active. You can
request deletion of your licensing records by contacting us at the address below.
Contact
Questions or deletion requests: tbturbodev@gmail.com