Privacy
What the CAPTELL Page Helper stores and sends.
Short, because there is not much. Last changed October 2026.
Stored in the browser
- One CAPTELL API key, the bot name, the bot address, and the last balance the desk reported. These live in chrome.storage.local on this device only.
- Nothing is synced to a Google account. Forget key in the popup removes it all.
Sent to the desk
- When Place the check is clicked: the page address, the captcha type, the site key, and the captcha's own public parameters (such as an action or rqdata), to https://captell.run/api/v1/solve, with the key as Authorization: Bearer.
- When the popup opens: a balance request to https://captell.run/api/v1/balance, and a version check at https://captell.run/extension/version.json.
- When a token was not placed: a release call to https://captell.run/api/v1/jobs/…/release, so the try is not charged.
Not collected
- No browsing history, page content, form values, cookies, or screenshots. The helper reads only the captcha markup on the page that is open.
- No analytics, no third-party scripts, no advertising identifiers.
Where the desk's data goes
The desk forwards the captcha to its solver and bills the credits on the desk that owns the key. Activity on the desk shows each solve. Questions go to the address on the manual.