Privacy Policy for Impulse: Website Blocker & Screen Time Control

Last Updated: November 4, 2025

At Impulse, your privacy is our top priority. This Privacy Policy explains how we handle your information within the extension, ensuring that we do not collect or store any personal data on external servers. All information and settings you use with Impulse remain exclusively on your device. We fully comply with Google Chrome Web Store's privacy guidelines and other applicable regulations to safeguard your information.

1. Information We DO NOT Collect

   Impulse is designed to operate locally on your device. We do not collect, store, or share any personal data or usage information with external servers. This means:

• No account required: You do not need to create an account or provide personal details such as email or name to use the core features.
• No external storage: All your settings and data remain solely on your device using Chrome's local storage.
• No tracking: We do not track your activities or send analytics data to external servers.

1. How Impulse Works

   All features of Impulse, including website blocking, usage limits, impulse controls, and screen time tracking, operate entirely locally on your device. This means:

• Data such as blocked website lists, usage statistics, and schedules is never transmitted to external servers.
• We do not use external servers to store or process your information.
• All tracking happens locally within your browser.

1. Information We Collect Locally

   While we don't send data to external servers, the extension does store information locally on your device to provide its functionality.

What is stored locally:

• Website blocking rules: URLs you choose to block, blocking schedules, and difficulty settings.
• Screen time data: Time spent on websites and visit counts (tracked locally for statistics).
• User preferences: Quick Focus settings, theme preferences, and other customization options.
• Email addresses (optional): Only if you use "Hard" difficulty mode for blocking.

How we use this local data:

• To enforce the blocking rules you configure.
• To show you screen time statistics and usage patterns.