Privacy Policy — Eye Flow

Last updated: 2026-05-12

Eye Flow is a free Chrome extension that delivers the 20-20-20 eye-break rhythm. This policy explains what data we handle and how.

The short version: we don't collect any data.


Information we collect

None.

Eye Flow does not collect, store, transmit, or share any personally identifiable information, health data, financial data, authentication data, personal communications, location data, web history, user activity, or website content.

We do not require an account. We do not ask for an email address. We do not generate or read any identifier that could be used to track you.


Information stored on your device

Eye Flow stores the following information locally on your device only, using Chrome's chrome.storage.local API:

This data never leaves your device. It is not transmitted to any server. It is not sent to us. It is not sent to any third party. It is not used for analytics, telemetry, advertising, or any other purpose.

If you uninstall Eye Flow, this data is deleted automatically by Chrome.


Permissions we request, and why

Eye Flow requests three Chrome permissions, each scoped strictly to the extension's single purpose:

Eye Flow does not request host_permissions for any website. It cannot read or modify the content of any page you visit.


Network requests

Eye Flow makes zero outbound network requests during normal operation. All code is bundled into the extension package; nothing is fetched from a remote server at runtime.


Third parties

Eye Flow does not use any third-party analytics, advertising, telemetry, or SDK. There are no third parties involved.


Changes to this policy

If we ever change the data practices of Eye Flow, we will update this page and bump the "Last updated" date at the top. Any change that would result in data collection will require an explicit opt-in from you and will be announced prominently in the extension's update notes.


Contact

If you have questions about this policy or the extension's privacy practices, open an issue on the project's GitHub repository.


Plain-English summary

That's the whole story.