Privacy

Effective date: August 5, 2026

Time Website Integration has one purpose: it adds the current website’s origin and path to the browser window title so the local Time desktop app can identify the website and make a privacy-reduced path available locally.

Data accessed and local handoff

On an ordinary top-level HTTP or HTTPS page, the extension reads only:

• the current page origin;
• the current page pathname;
• the current page title.

It writes only the current top-level page title. The value added to that title is exactly:

location.origin + location.pathname

The extension never includes query parameters, URL fragments, or credentials in its marker. It does not decode the pathname.

This title marker is a deliberately local handoff. It makes the reduced origin and path available to the operating system and to the local Time desktop app, which already reads the foreground browser title. Time validates the marker, derives the normalized website domain, and immediately discards the raw origin and path. Time’s separate Store window titles setting determines whether the ordinary page title is retained.

Browser stores classify this local handoff as handling browsing data even though nothing is sent over a network. Firefox therefore declares browsingActivity for the origin and path and websiteContent for the page title it reads and preserves.

Data not otherwise accessed or retained

The extension does not read page-body text, forms, passwords, cookies, browser history, browser storage, network traffic, downloads, clipboard contents, iframe URLs, or iframe contents.

It does not persist browsing data; send it over a network; upload it to the developer; or sell or share it with advertisers, data brokers, or other third parties. It has no storage, network requests, native messaging, remote code, analytics, advertising, telemetry, or crash-report uploads. It does not run in private or incognito windows.

Site-access warning

Your browser may warn that this extension can read and change data on websites you visit. Broad site access is required so the extension can update the title automatically on ordinary HTTP and HTTPS pages. That warning describes what a content script with this access could technically do, not the narrower behavior implemented here.

The source and final package are designed to be inspectable. Automated package checks reject named browser permissions, unexpected host scope, background processes, storage and network APIs, remote resources, telemetry, and divergent Chromium/Firefox functional code. Firefox’s data declarations describe the local handoff above; they do not grant an additional runtime API capability.

Path sensitivity and the operating-system boundary

Removing query strings and fragments materially reduces exposure, but paths can still contain reset tokens, document names, patient identifiers, account identifiers, or other private information.

The path is intentionally placed in the browser title. It is therefore visible to the operating system and to other software capable of reading window titles; it is not confined inside the browser.

Private browsing is excluded. Time desktop v1 is designed to validate the marker, derive the normalized website domain, and discard the raw origin and path. It does not retain path history. Time’s separate Store window titles setting determines whether the ordinary clean page title is stored and must not disable domain-based Website rules or exclusions.

Limited use

Browsing data is handled only to provide the extension’s single purpose: local website identification for Time. It is not used for advertising, analytics, profiling, eligibility decisions, or any unrelated purpose. This use complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.

Unsupported pages

The extension does not run on local files, browser-internal pages, extension pages, browser-store pages where injection is prohibited, protected pages, unsupported protocols, subframes, or private-browsing pages. The absence of a marker on those pages is expected.

Changes and contact

This policy may be updated if the extension’s behavior or requirements change. Material changes will be reflected by a new effective date.

Questions about this policy may be sent to support@trackwithtime.com.