Last updated: March 21, 2026
PD Counter does not collect, transmit, or share any user data. All data stays on your device.
PD Counter stores the following data locally on your device using Chrome's storage API (chrome.storage.local):
— List of websites you choose to block
— Impulse log: the number of times you clicked "Open" per day
— Temporary allow status for active sessions
This data never leaves your browser. It is not sent to any server, third party, or analytics service.
PD Counter does not collect any personal information, browsing history, cookies, or analytics data. There are no accounts, no sign-ups, and no tracking.
PD Counter includes an optional content detection feature that checks page content against a keyword list to suggest sites for blocking. This analysis happens entirely within your browser. No page content is ever transmitted externally.
PD Counter requests the following Chrome permissions:
— webNavigation: To detect navigation and redirect blocked sites to the block page.
— storage: To save your block list and impulse log locally.
— tabs: To manage temporary allow sessions and tab updates.
— Broad site access (<all_urls>): So the extension can run on pages you visit to apply blocking, show the optional on-page controls, and perform local content checks. No data from those pages is sent off your device.
PD Counter does not use any third-party services, APIs, or SDKs.
If this policy changes, the update will be posted on this page with a new date.
For questions about this policy, open an issue on GitHub.