PulseAgent Browser Monitor

1. Scope and single purpose

PulseAgent Browser Monitor is a browser extension designed for organization-managed endpoints. Its single purpose is to provide active browser-tab usage visibility to the PulseAgent endpoint monitoring system.

The extension identifies the currently active tab only while the relevant browser window is focused, measures how long that tab remains active, and sends the resulting telemetry to the PulseAgent Session component running on the same Windows device.

2. Information collected

The extension may process the following information for its disclosed single purpose:

Data	Purpose	Default behavior
Active website domain	Shows which website is actively in use.	Collected
Active page title	Identifies the title of the currently active page for endpoint visibility.	Collected
Supported search-engine search term	Identifies a search query when it is present in the active search-page URL and supported by PulseAgent.	Collected when applicable
Browser name	Identifies the Chromium-based browser reporting the active tab.	Collected
Start/end timestamps and active duration	Measures how long a tab was actively in use.	Collected
Full active-tab URL	Provides additional active-page detail when enabled by the user or organization.	Off by default
Endpoint/session and Windows-user context	The local PulseAgent Session component associates browser telemetry with the managed endpoint and interactive Windows user.	Added by PulseAgent Session

Chrome Web Store may classify active domains, page titles and related active-tab information as Web history and the monitoring of active/focused usage as User activity. This disclosure does not mean the extension reads Chrome's stored History database.

3. Information the extension does not collect

PulseAgent Browser Monitor is not designed to collect:

the browser History database or a bulk list of previously visited pages;
passwords, authentication credentials, authentication cookies or PINs;
form contents or text typed into ordinary website fields;
keystrokes or clipboard contents;
mouse position or click-by-click interaction logs;
page body text, images, videos or other website content;
screenshots or screen recordings;
personal communications such as email or chat message bodies;
financial, health or precise-location information as a dedicated data category.

4. How collection works

The extension observes only normal http:// and https:// pages.
Telemetry is generated only for the active tab of a focused browser window.
Periodic checkpoints are used to measure long-running active tabs accurately.
If the local PulseAgent bridge is temporarily unavailable, pending events may be queued locally and retried.
The extension does not load or execute remote JavaScript or WebAssembly code.

5. How information is used

Collected information is used only to provide and operate PulseAgent's active browser-usage visibility feature, including:

showing active browser time and active websites on managed endpoints;
showing page titles and supported search terms associated with active usage;
associating telemetry with the correct managed endpoint and interactive user;
maintaining the reliability of the browser-monitoring feature, including temporary local queuing and retry.

PulseAgent Browser Monitor does not use collected browser telemetry for personalized advertising, behavioral advertising, creditworthiness, lending, or unrelated marketing purposes.

6. Sharing and disclosure

The extension sends telemetry to the locally installed PulseAgent Session component on the same device. The PulseAgent endpoint software may then forward that telemetry to the organization's configured PulseAgent server so authorized administrators can use the PulseAgent dashboard for the disclosed endpoint-visibility purpose.

PulseAgent Browser Monitor does not sell user data and does not send browser telemetry directly to advertising networks, data brokers, third-party analytics platforms, or unrelated third parties.

Information may be disclosed where required by applicable law, or where necessary to investigate security abuse or protect the PulseAgent service and managed environment.

7. Local storage and retention

The extension uses Chrome extension storage for settings, temporary active-tab state, browser identification, and a limited pending-event queue when the local PulseAgent bridge is unavailable.

The extension's pending-event queue is limited to the most recent 1,000 events. Successfully delivered pending events are removed from the queue. Server-side retention is controlled by the organization operating the PulseAgent server and its internal retention policy.

8. Security and transmission

The browser extension itself communicates with the PulseAgent Session component only through the loopback interface on 127.0.0.1:32145. This address refers to the same local device and is not an external Internet host.

The extension's host permission is limited to the local PulseAgent bridge. It is not used to inject scripts into websites or to read arbitrary website content.

Any subsequent transmission from the installed PulseAgent endpoint software to an organization-configured server is controlled by that organization's PulseAgent deployment and network configuration.

9. User choices and controls

Full URL capture is disabled by default. Where the extension options page is available, the setting can be reviewed and changed there. The extension also provides a connection status check for the local PulseAgent Session bridge.

On organization-managed devices, installation, removal or configuration of the extension may be controlled by organizational browser-management policy.

10. Managed workplace deployments

PulseAgent Browser Monitor is intended for managed business endpoints. The organization deploying PulseAgent is responsible for providing appropriate notice to its users, obtaining any consent required by applicable policy or law, and configuring monitoring in accordance with its internal policies and legal obligations.

Authorized IT administrators may be able to view individual endpoint browser-usage telemetry in the PulseAgent dashboard as part of the extension's disclosed managed-endpoint visibility function.

11. Chrome Web Store Limited Use disclosure

PulseAgent Browser Monitor uses information obtained through Chrome extension APIs only to provide or improve the extension's disclosed single purpose: active browser-tab usage visibility on managed endpoints.

User data is not sold or transferred for advertising or unrelated commercial purposes.
User data is not used for personalized, retargeted or interest-based advertising.
User data is not used to determine creditworthiness or for lending purposes.
Use and transfer of collected data is limited to the disclosed PulseAgent functionality, operational security, legal obligations, and other uses permitted by the Chrome Web Store User Data Policy.

This extension is intended to comply with the Chrome Web Store Limited Use requirements and the Chrome Web Store disclosure requirements.

12. Access, correction and deletion

Requests relating to access, correction or deletion of PulseAgent telemetry should be directed to the organization that manages the endpoint. For Pasar Besar-managed devices, contact the IT team through the Pasar Besar Helpdesk.

13. Changes to this policy

This policy may be updated when PulseAgent Browser Monitor's functionality or data practices change. Material changes affecting data collection or use will be reflected in the Chrome Web Store listing and this page before the changed practices are introduced where required.

14. Contact

For questions about this privacy policy or PulseAgent Browser Monitor on Pasar Besar-managed endpoints:

Pasar Besar IT
Helpdesk: https://helpdesk.pasarbesar.com.my/