Privacy Policy for EVENTLISTENER

Effective date: July 16, 2026

This Privacy Policy explains how EVENTLISTENER, a Chrome extension for monitoring tab and page activity, handles user data. EVENTLISTENER is designed to help users monitor browser tabs they choose to arm and run user-configured actions when selected conditions are met.

This policy is written for the EVENTLISTENER Chrome extension and for the Chrome Web Store listing. It explains what data the extension handles, why the data is needed, how the data is stored, and what data is not collected.

Short Summary

• EVENTLISTENER does not require an account.
• EVENTLISTENER does not sell user data.
• EVENTLISTENER does not use user data for advertising.
• EVENTLISTENER does not collect personal identity information such as name, email address, phone number, address, government ID, or age.
• EVENTLISTENER does not collect health information, financial information, payment information, authentication information, personal communications, or precise location.
• EVENTLISTENER does not transmit browsing data to the developer's server.
• EVENTLISTENER stores extension settings and monitoring state locally using Chrome extension storage.
• EVENTLISTENER only monitors tabs that the user chooses to arm.
• EVENTLISTENER uses tab and page activity data only to provide its user-facing monitoring and automation features.

Extension Purpose

EVENTLISTENER has a single purpose: to monitor browser tabs that the user chooses to arm and run selected actions when user-configured tab or page conditions are met.

Users can configure rules for signals such as URL changes, page title changes, loading state, audio state, click activity, scroll activity, keyboard activity timing, page visibility, and DOM-change counts. When a rule matches, EVENTLISTENER can run actions such as playing an alarm, showing a notification, running an in-page shortcut, attempting to stop a tracked screen share, closing the tab, or disarming monitoring.

Data Categories Disclosed in the Chrome Web Store

For the Chrome Web Store privacy form, EVENTLISTENER discloses the following user data categories:

• Web history: EVENTLISTENER may store URL and page title information for tabs the user chooses to arm, plus related monitoring event records.
• User activity: EVENTLISTENER may process activity signals such as clicks, scroll activity, keyboard activity timing, page visibility state, and DOM-change counts on tabs the user chooses to arm.

These disclosures do not mean EVENTLISTENER collects a user's full Chrome browsing history. EVENTLISTENER is designed to work with tabs the user actively arms for monitoring. The extension stores only the information needed to provide its monitoring rules, popup status, dashboard status, cooldowns, and trigger actions.

Information EVENTLISTENER Handles

1. Extension Settings

EVENTLISTENER stores settings needed for the extension to work, including:

• Selected event groups
• Rule conditions
• Rule templates
• Trigger action choices
• Alarm sound selection
• Alarm duration
• Cooldown settings
• Shortcut settings
• Dashboard and popup configuration

This information is stored locally using Chrome extension storage so the user's configuration can be restored across browser sessions.

2. Armed Tab Information

When a user arms a tab, EVENTLISTENER may store information about that monitored tab, including:

• Tab ID
• Tab title
• Tab URL
• Time the tab was armed
• Current monitoring rule state
• Last trigger event for that tab
• Timing data used for cooldowns and inactivity rules

This information is used to show the user which tabs are being monitored, apply configured rules, update the extension badge, and run selected actions when a rule fires.

3. Web History Data

EVENTLISTENER may handle URL and title information for tabs that the user chooses to monitor. This is necessary for features such as URL-based rules, title-based rules, loading-state rules, live coverage status, popup status, dashboard status, and alarm event descriptions.

EVENTLISTENER does not collect the user's complete browser history. It does not create a general browsing profile. It does not use browsing data for advertising, analytics, or monetization.

4. User Activity Data

EVENTLISTENER may process user activity and page activity signals on monitored tabs, including:

• Click activity
• Click inactivity timing
• Click burst timing
• Scroll activity
• Scroll inactivity timing
• Scroll depth percentage
• Keyboard activity timing
• Keyboard inactivity timing
• Keyboard burst timing
• Page visibility state
• DOM-change counts
• DOM quiet-period timing
• DOM burst timing

This activity data is used only to evaluate the monitoring rules selected by the user. For example, if the user enables a click inactivity rule, EVENTLISTENER needs to know when clicks happen so it can determine whether the page has been idle for the configured time.

5. Alarm and Trigger Event Records

When a rule fires, EVENTLISTENER may store a local event record that can include:

• The event category
• The condition that fired
• A short event label
• A short event detail message
• The monitored tab title
• The monitored tab URL
• The time the event occurred

This information is used to show the last alarm state, display meaningful notifications, update the dashboard, apply cooldown behavior, and help the user understand why a rule fired.

Information EVENTLISTENER Does Not Collect

EVENTLISTENER does not collect or request the following categories of information:

• Names
• Email addresses
• Phone numbers
• Home addresses
• Government identification numbers
• Age or date of birth
• Health information
• Financial information
• Payment card information
• Passwords
• Authentication credentials
• Security questions
• Personal identification numbers
• Emails, texts, or chat messages
• GPS coordinates
• Precise physical location
• Website screenshots
• Complete page text
• Images, videos, sounds, or hyperlinks from pages
• Form contents entered by the user

Website Content

EVENTLISTENER does not collect website content such as page text, images, videos, sounds, hyperlinks, form contents, emails, or chat messages.

EVENTLISTENER may observe that DOM changes occurred on a monitored page and may count those changes for rule matching. This is used for rules such as DOM quiet periods or DOM burst detection. The extension does not store the actual changed content of the page.

Keyboard Activity

EVENTLISTENER may observe keyboard activity timing on monitored tabs when the user enables keyboard-related monitoring rules. This is used to detect keyboard inactivity or keyboard burst conditions.

EVENTLISTENER is not designed to collect typed text, passwords, messages, or form contents. Keyboard monitoring is used for timing and rule matching, not for collecting what the user types.

How EVENTLISTENER Uses Data

EVENTLISTENER uses handled data only to provide its user-facing extension features, including:

• Saving user configuration
• Restoring saved monitoring rules
• Arming and disarming tabs
• Showing monitored tab status in the popup
• Showing live coverage in the dashboard
• Evaluating configured monitoring conditions
• Triggering selected actions when rules match
• Playing alarm sounds
• Showing browser notifications
• Running configured in-page shortcuts
• Attempting to stop tracked screen sharing when enabled
• Closing a monitored tab when the user enables that action
• Disarming monitoring when the user enables that action
• Applying cooldown settings
• Displaying last-event information to the user

Local Storage

EVENTLISTENER stores settings and monitoring state locally using Chrome extension storage. This local storage may include rule settings, templates, selected actions, alarm settings, shortcut settings, monitored tab state, and last alarm information.

Users can remove this locally stored extension data by removing the extension from Chrome. Chrome may also provide browser-level controls for clearing extension data, depending on the browser version and user settings.

Data Sharing

EVENTLISTENER does not sell user data.

EVENTLISTENER does not transfer user data to third parties for advertising, analytics, profiling, creditworthiness, lending, or marketing purposes.

EVENTLISTENER does not transmit browsing data, monitored tab data, rule data, or user activity data to the developer's server.

EVENTLISTENER may interact with Chrome APIs and the local browser environment as needed to provide extension functionality, such as Chrome storage, tabs, alarms, notifications, scripting, and offscreen audio playback.

Remote Code

EVENTLISTENER does not use remote code. The extension's JavaScript, HTML, CSS, icons, and local audio-generation logic are included in the extension package. The extension does not load remote scripts, remote WebAssembly, external modules, or code strings evaluated through eval.

Permissions Explained

Alarms

The alarms permission is used to schedule time-based monitoring conditions and cooldown behavior for armed tabs.

Notifications

The notifications permission is used to show a browser notification when a user-configured monitoring rule fires.

Offscreen

The offscreen permission is used to create an offscreen document for alarm audio playback. Manifest V3 service workers cannot reliably play audio directly, so EVENTLISTENER uses an offscreen document only to generate and stop local alarm sounds.

Scripting

The scripting permission is used to inject packaged extension scripts into monitorable tabs so EVENTLISTENER can synchronize monitoring state and support user-enabled page actions. These scripts are local files included in the extension package.

Storage

The storage permission is used to save user settings, rule templates, selected actions, alarm choices, shortcut settings, monitored tab sessions, cooldown state, and last alarm state.

Tabs

The tabs permission is used to identify the current tab, arm and disarm monitored tabs, read tab URL, title, loading, and audible status for configured rules, update the extension badge, open the dashboard, focus monitored tabs, and close a tab only when the user enables the close-tab action.

Host Permissions

Host permissions are required because EVENTLISTENER's purpose is to monitor tabs and page activity on websites the user chooses to arm. The extension must support normal web pages across different sites. Packaged content scripts may load on monitorable pages and remain inactive for rule evaluation unless monitoring is enabled for that tab.

Limited Use Disclosure

EVENTLISTENER's use of user data is limited to providing and improving the extension's single purpose and user-facing features.

• EVENTLISTENER uses handled data only for tab monitoring, rule evaluation, trigger actions, local settings, popup status, dashboard status, and related extension functionality.
• EVENTLISTENER does not sell user data.
• EVENTLISTENER does not use or transfer user data for personalized advertising.
• EVENTLISTENER does not use user data for creditworthiness or lending purposes.
• EVENTLISTENER does not transfer user data except as necessary to provide or improve the extension, comply with applicable law, or protect against security abuse.
• Humans do not read user data unless the user asks for support and explicitly provides relevant information, or unless access is necessary for security, legal compliance, or aggregated/anonymized internal operations.

Security

EVENTLISTENER is designed to keep its handled data in the user's browser using Chrome extension storage. The extension does not transmit monitored tab data or user activity data to a developer-operated server.

No system can be guaranteed completely secure, but EVENTLISTENER is designed to minimize data handling by using local browser storage and limiting handled data to what is needed for the extension's user-facing monitoring features.

Children's Privacy

EVENTLISTENER is a general productivity tool and is not directed to children. EVENTLISTENER does not knowingly collect personal information from children.

Third-Party Services

EVENTLISTENER does not require a third-party account and does not send monitored tab data to third-party services controlled by the developer.

The Chrome Web Store, Google Chrome, Blogger, and other platforms used to publish or install the extension may have their own privacy practices. Those services are governed by their respective privacy policies.

User Choices And Controls

• Users choose which tabs to arm.
• Users choose which event groups and conditions to enable.
• Users choose which actions should run when a rule fires.
• Users can disarm a monitored tab.
• Users can disarm all monitored tabs.
• Users can change or delete rule templates.
• Users can remove EVENTLISTENER from Chrome.

Data Retention

EVENTLISTENER retains local settings and monitoring state for as long as needed to provide the extension's features or until the user changes settings, disarms tabs, deletes templates, clears extension data, or removes the extension from Chrome.

Because EVENTLISTENER stores data locally in Chrome extension storage, deleting or removing the extension is the main way to remove its locally stored extension data.

Changes To This Privacy Policy

This Privacy Policy may be updated from time to time to reflect changes in EVENTLISTENER, Chrome extension requirements, Chrome Web Store policies, or applicable privacy practices.

When this policy is updated, the effective date at the top of the page will be changed. Users are encouraged to review this page periodically.

Contact

If you have questions about this Privacy Policy or EVENTLISTENER's data handling, contact:

Email: boni.aditya@gmail.com

Chrome Web Store Disclosure Summary

For Chrome Web Store privacy disclosures, EVENTLISTENER handles:

• Web history: URL and title information for monitored tabs chosen by the user, used for monitoring rules, dashboard state, popup state, and event records.
• User activity: Activity signals such as clicks, scroll activity, keyboard activity timing, page visibility, and DOM-change counts on monitored tabs, used for rule evaluation and configured trigger actions.

EVENTLISTENER does not collect personally identifiable information, health information, financial or payment information, authentication information, personal communications, location, or website content.