Privacy policy
Updated November 19, 2026 · Describes WebTracker 1.2.1
WebTracker helps you understand browsing time and active-tab network activity. This policy explains the extension's collection, use and storage of information, including processing by its service providers. Contact the WebTracker developer at tomaszjc250@gmail.com.
What the extension handles
- Full URLs and hostnames of tracked active pages, session start and end timestamps, duration, tab identifiers, session completion reason and measured received bytes.
- A generated installation identifier, a technical account identifier and a generated account email in the form of an installation identifier at webtracker.local.
- A generated password and authentication access/refresh tokens used by that technical account.
- Language and appearance preferences, and a local queue of sessions awaiting upload.
The extension does not ask for your real name, personal email or passwords from other services. It does not scrape page text, form entries or keystrokes. However, full URLs can contain names, search terms, account identifiers and other sensitive information. Pseudonymous identifiers do not guarantee anonymity.
Why and where data is processed
Completed browsing sessions are sent over HTTPS to the configured Supabase backend to store and display your statistics. Authentication requests send the generated technical credentials to Supabase; access tokens authorize subsequent requests. The extension stores its installation ID, credentials, tokens and pending-upload queue in Chrome's local extension storage. Language and appearance preferences use Chrome sync storage and may be synchronized according to your browser settings.
Network measurements use Chrome's debugger API on the active supported tab. Chrome shows a debugging notification while attached. The extension reads received-byte counts for its meter; the measurements do not represent all browser or device traffic.
Connection tests and service logs
When you start a connection test, WebTracker contacts Cloudflare at speed.cloudflare.com and 1.1.1.1 to estimate latency, jitter, download and upload speed. These requests transfer test data and expose connection metadata, such as your IP address, to the provider.
The browsing-session table has no IP-address field. Hosting, authentication and infrastructure logs may nevertheless contain IP addresses, approximate location, user-agent and request metadata. Provider log retention and access depend on their service settings and practices. This policy does not promise the absence of such logs.
Access, sharing and security
Authenticated client access is restricted to the account's own records. Privileged database administrators can access stored browsing records. Records are not end-to-end encrypted against administrators. HTTPS protects transmission, but no system can guarantee absolute security.
Supabase processes account and session data to support the extension. Cloudflare processes connection-test requests. WebTracker does not sell browsing data or use it for advertising. Service providers and their infrastructure may process request metadata as described above.
Limited Use
WebTracker's use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. Browsing activity is used to provide the disclosed browsing statistics and network-measurement functionality, not advertising or unrelated profiling. Transfers are limited to what is needed to provide that functionality, applicable legal obligations, security purposes, or a permitted business transfer with the required consent.
Retention and your choices
There is no automatic deletion period implemented by the extension for server-stored browsing sessions. Uninstalling or disabling WebTracker stops future collection through that installation; it does not itself delete records already stored on the server. Clearing extension storage can create a new installation identity and does not remove the old server records.
For questions, access or deletion requests, email tomaszjc250@gmail.com. Requests may require information sufficient to identify and verify the relevant technical account. Do not email passwords, access tokens or refresh tokens. Because accounts are pseudonymous and not linked to your personal email, locating records may be difficult if the installation identity has been lost. Provider operational or audit logs may be retained separately.
This website
This product and policy website contains no analytics scripts, tracking pixels or forms. It is hosted through GitHub Pages, whose infrastructure may process normal connection and access-log metadata. Following an external link takes you to the respective provider's website.
Policy updates
Changes to this policy will be published on this page with an updated date. For support or privacy questions, contact tomaszjc250@gmail.com.