MicroBreaks

Privacy Policy

Last updated: July 2026

Short version: MicroBreaks has no servers of its own and collects no personal data. Settings sync between your own devices using Chrome's built-in sync feature — the same mechanism Chrome uses for bookmarks and passwords — and nothing is ever sent to us or any third party.

What data we collect

MicroBreaks stores the following data using Chrome's built-in chrome.storage APIs. Most settings sync automatically across your signed-in Chrome browsers via chrome.storage.sync; session-only timer state stays local to each device via chrome.storage.local:

What we do NOT collect

Permissions explained

MicroBreaks requests the following Chrome permissions:

None of these permissions are used to collect, transmit, or share any data.

Strict mode

When strict mode is enabled, MicroBreaks injects a visual overlay onto your active tab at break time. This overlay is rendered entirely within your browser. No content from your tab is read, captured, or transmitted.

Idle detection

MicroBreaks uses Chrome's built-in idle API to tell whether you're actively using the computer — it only sees a system-level state (active, idle, or locked), based on keyboard/mouse/touch input timing. It does not record what you type, what you click, or what applications you use, and this state is never stored beyond deciding whether to pause or resume the timer, and never leaves your device.

Support links

The extension and its options page include an optional link to a Buy Me a Coffee page for anyone who'd like to support development. Clicking it takes you to a third-party site outside the extension, governed by that site's own privacy policy and terms — MicroBreaks itself doesn't process, store, or see any payment or donation information.

Children's privacy

MicroBreaks does not knowingly collect any information from anyone, including children under 13.

Changes to this policy

If we make changes to this policy, we will update the date at the top of this page. Continued use of the extension after changes constitutes acceptance of the updated policy.

Contact

If you have any questions about this privacy policy, please open an issue on our GitHub repository or contact us at the email listed on the Chrome Web Store listing.