Privacy Policy for DeskPulse

Effective date: August 15, 2026

DeskPulse ("the extension") is a browser extension that reminds you to take short eye breaks following the 20-20-20 rule. This policy explains what data DeskPulse accesses, how it's used, and what it does not do.

Summary

DeskPulse does not collect, transmit, sell, or share any personal data. It has no servers of its own and does not communicate with the internet in any way. Everything the extension needs to function is stored locally on your device (and, optionally, synced through your own Google Account via Chrome's built-in sync — see "Chrome Sync" below).

Information We Do Not Collect

DeskPulse does not collect or have access to:

There is no backend server for DeskPulse to send data to, and the extension contains no analytics, tracking, or advertising code of any kind.

Information Stored Locally

To function, DeskPulse stores a small amount of data using the browser's built-in storage API, entirely on your device:

None of this data is sent anywhere. It stays on your device unless you have Chrome Sync enabled (see below).

Chrome Sync

If you're signed into Chrome and have sync enabled, your reminder preferences (interval, on/off, paused state) may be synced across your own devices using Chrome's built-in storage.sync mechanism. This sync is handled entirely by Google as part of your Chrome/Google Account — DeskPulse does not operate, access, or have visibility into this sync process. If you have Chrome Sync turned off, this doesn't apply, and your settings simply stay on the one device.

Permissions We Use

DeskPulse requests the minimum browser permissions needed to function:

DeskPulse does not request access to your browsing data, tabs, or any website content, and does not need to.

Children's Privacy

DeskPulse is not directed at children and does not knowingly collect any information from anyone, regardless of age — because it does not collect information from anyone at all.

Third-Party Services

DeskPulse does not use any third-party services, SDKs, or libraries that collect or process user data. (If this changes in the future — for example, if a paid tier is introduced using a third-party payment processor — this policy will be updated in advance to describe exactly what that processor does and does not have access to.)

Changes to This Policy

If this policy changes, the updated version will be posted at this same location with a revised effective date. Continued use of DeskPulse after a change constitutes acceptance of the updated policy.

Contact

Questions about this policy or DeskPulse can be sent to: richard.krieger@gmx.net