Privacy policy
Last updated 24 September 2026.
The short version
T3rnel Browser collects nothing by default. There is no account, no error reporting and no tracking, and there never has been a server that receives your browsing data. Since 1.3.0 there are two things you can opt into — an anonymous per-tool usage counter and a newsletter — and both are off until you say otherwise.
What is stored, and where
Everything the extension saves is stored locally in your browser, on your device:
- Settings and approval policies
- Screenshot history and visual regression baselines
- Recorded sessions and generated test code
- Vault entries, encrypted with a key derived from your master passphrase — the plaintext is never written
- Your licence entitlement, if you buy Pro
- Local usage counters — how many tool calls, on how many days, which tools. Shown in Settings.
- On the Free tier, a count of tool uses that decides when the next upgrade or rating prompt appears, and which T3raTech product it features
None of it is transmitted anywhere on its own. Uninstalling the extension removes it.
When the extension makes a network request
Seven situations, all either initiated by you, behind a switch you control, or read-only:
| Situation | Where it goes | What is sent |
|---|---|---|
| Activating a Pro licence | t3rnel-wavepay-production.t3ratech.workers.dev |
Your licence key and a public key identifying the installation. Once, when you activate. After activation your licence is verified offline. |
| Buying Pro | t3rnel-wavepay-production.t3ratech.workers.dev, then PayNow or PayPal |
The email address your licence key goes to and the payment method you chose — only when you press Pay. The payment itself happens on PayNow's or PayPal's own page. |
| Showing the payment methods on offer | t3rnel-wavepay-production.t3ratech.workers.dev |
A read-only request for the list of available payment methods when a panel, the popup or the setup page opens. Nothing about you or your browsing is sent. |
| Checking links on a page | The links on the page you asked to check | An HTTP HEAD request. Only when you run the link checker. |
| Optional AI analysis or cloud transcription | The endpoint you configured | The page data or audio for that request, with your own API key. Off unless you turn it on and supply a key. |
| Finding a local MCP bridge | 127.0.0.1, ports 17311–17318, on your own machine |
A request to the bridge's local health endpoint. It never leaves your device. |
| Newsletter signup | Your own mail client | A mailto: compose window to our address — the extension sends nothing itself. |
| Opt-in usage counter | t3rnel-wavepay-production.t3ratech.workers.dev and Google Analytics 4 |
Anonymous per-tool call counts — that a tool ran and how many times. Off by default; enabling it in Settings or onboarding is the only way anything is sent. No page content, URL, tool argument or identity is ever included. |
That is the complete list. The inspection and automation features — CSS, screenshots, Markdown, network and console capture, DOM snapshots, agent tools — send nothing anywhere. The usage counter always records on-device regardless of the toggle; the toggle only controls whether the anonymous counts are ever reported off-device.
Payments
Payment is handled by PayNow or PayPal through T3rnel WavePay, our own payment gateway. We never see or store your payment details. The gateway stores a one-way hash of your licence key, a keyed hash of your email, and a fingerprint of each activated installation's public key. It stores no raw licence key after you collect it, no payment credential and no browsing data.
Permissions
The extension requests the minimum at install and asks for anything else at the moment you first use the feature that needs it, with an explanation. Declining is safe: the feature reports what it needed, and everything else keeps working. See the manual for the full table.
Changes
If this policy changes, the revision date above changes with it and the change is recorded in the changelog.