API & MCP

TimeVerify

Verifies the system clock is accurate before allowing browsing, once per browser session.

As of July 2026, TimeVerify has users in the Productivity category.

Usersno change0%
Ratingno change0%
— reviews
Reviewsno change0%
Version
1.0.0
Manifest V3

History

1 snapshots

Tracking since Jul 15, 2026.

Not enough history yet for this metric — the chart fills in as we collect more snapshots.
View as table
DateUsersRatingReviewsVersion
Jul 15, 20261.0.0
Now1.0.0

Permissions & access

Permissions
declarativeNetRequestalarmsstoragetabs
Host access
<all_urls>

Screenshots

TimeVerify screenshot 1

About

TimeVerify checks your device's date and time against a verified, independent time source before allowing browsing — a simple safeguard against relying on a system clock that may be inaccurate.

How it works:
When the browser starts, TimeVerify compares your device's clock to real-world time. If they don't match closely enough, browsing is paused with a short explanation until the clock is corrected. Once verified, it steps out of the way completely for the rest of that session — no ongoing interruptions.

Key features:
- One check per browser session, not continuous — it won't interrupt work already in progress
- Cross-checks multiple independent time sources rather than trusting a single one
- Shows the reference time being used, so what's happening is never a black box

Data collection: TimeVerify does not collect, store, or transmit any personal data. It runs entirely locally in your browser.

Technical

Version
1.0.0
Manifest
V3
Size
10.67KiB
Min Chrome
88
Languages
1
Featured
No

Metadata

ID
ahdpefahbibojenkbbokiggccaacemck
Developer ID
u7642966c671fb53bb09583e772436829
Developer Email
[email protected]
Created
Jul 14, 2026
Last Updated (Store)
Jul 14, 2026
Last Scraped
Jul 15, 2026
Website
Support URL
Privacy Policy

Data sourced from the Chrome Web Store · last verified Jul 15, 2026.