§ 01 Summary
Time Anchor reads visible timestamps on the pages you visit and converts them to your local timezone. All processing happens in your browser, on your device. We do not have a server. We do not collect any information about you, your browsing, or your usage. Your settings sync only through your own Google account via Chrome's built-in storage — never through anything we control.
§ 02 What Time Anchor accesses
To convert timestamps on a web page, Time Anchor's content script reads the following information from each page you visit:
- HTML
<time>elements — to extract theirdatetimeattributes - JSON-LD schema markup (specifically NewsArticle, Article, BlogPosting types) — to extract
datePublishedanddateModifiedvalues - Meta tags — including
article:published_time,article:modified_time, andog:updated_time - The visible text of
<time>elements when no machine-readable timestamp is available
We only look at timestamp data. We don't read article content, comments, your input, cookies, login state, or anything else on the page. The conversion happens in JavaScript running on your device — nothing leaves the browser.
§ 03 What Time Anchor stores
Time Anchor stores the following preferences using Chrome's built-in chrome.storage.sync API:
- Your preferred timezone
- Display preferences (12/24-hour format, seconds, day of week, relative time, freshness colors, toolbar badge)
- Customized thresholds (stale article days, silent update minutes)
- A list of domains where you have paused Time Anchor
- A list of domains you have explicitly blocked
This data lives in your browser. If you have Chrome Sync enabled, Google syncs it across your devices via your own Google account — Time Anchor does not have access to that sync infrastructure and cannot read this data from any device other than your own.
§ 04 What Time Anchor does NOT do
- No analytics or telemetry. Time Anchor never reports usage, errors, page visits, or any other event to any server.
- No tracking. The extension does not log which sites you visit, which articles you read, or any browsing history.
- No remote code. Time Anchor includes no remote scripts, dynamic imports, or fetches to external servers. All code is bundled in the extension package and reviewable on the Chrome Web Store.
- No third-party services. Time Anchor uses zero third-party libraries that make network requests.
- No advertising. Time Anchor does not show ads, contain affiliate links, or participate in any monetization scheme.
- No data sales. Because we don't collect data, there is nothing to sell.
§ 05 Permissions explained
Every permission Time Anchor requests, and why:
| Permission | What it's for |
|---|---|
storage |
Saves your preferences so they persist between browser sessions. |
contextMenus |
Adds a right-click menu on the extension icon to pause Time Anchor on the current site and open settings. |
tabs |
Detects page navigation so the toolbar age badge updates; reads the current tab's hostname so you can pause Time Anchor per-site; reloads the current tab when you change site-level settings. URLs are used only to extract hostnames — never tracked or logged. |
host_permissions: <all_urls> |
Lets the content script run on any page so it can find timestamps. Without this, the extension's core function would not work, since timestamps appear on countless different websites. |
§ 06 Children
Time Anchor is not directed at children under 13 and does not knowingly collect any data from anyone, including children. The extension functions identically regardless of who installs it.
§ 07 Changes to this policy
If this policy changes substantively, the new version will be reflected at this URL, and the "Last updated" date at the top will change. Continued use of Time Anchor after such changes constitutes acceptance.
For your reference, the current version is 2.2.0, effective May 26, 2026.
§ 08 Legal basis & jurisdictions
Common questions answered:
Is Time Anchor GDPR-compliant?
Yes. Time Anchor processes no personal data. The local settings storage is functionally equivalent to a single-purpose browser preference and qualifies for "strictly necessary" exemptions under GDPR.
Does Time Anchor sell my data under CCPA/CPRA?
No. There is no data to sell. Time Anchor has no servers, no database, no logging, and no data-sharing agreements with any third party.
Is the source code public?
The full source code is available for inspection through the Chrome Web Store. Anyone can unpack the .crx file and review every line. There is no obfuscation, minification, or compilation step — the JavaScript you receive is the JavaScript that runs.
What if I want to delete my data?
There is nothing on our end to delete. To remove all local preferences, uninstall the extension from chrome://extensions. Your Chrome Sync data tied to your Google account can be cleared from your Google Chrome Sync settings.
Who is the developer / data controller?
Time Anchor is built and maintained by Sadik Hossain, an independent developer based in Bangladesh. Contact information is provided in the section below.
§ 09 Contact
For privacy-related questions or any other concerns about the extension, you can reach us through the support page: