Privacy Policy
Effective date: March 15, 2026
Overview
Browser Peek is a browser extension that monitors button clicks and page interactions on websites you configure, then forwards those events to your chosen observability platform. This policy explains what data the extension records, where it is sent, and how credentials are handled.
Data We Record and Forward
Browser Peek does not permanently store event data. When a click matches your configured actions, the extension records the following and forwards it to the connector you have selected. If delivery fails, events are briefly queued in memory and retried until the browser closes:
- Timestamp, button text, and page URL of the click
- A randomly generated correlation ID per event
- Browser name and version
- Any additional context fields you have configured
If you enable network request observation (off by default), the extension also records URL, HTTP method, status code, and response duration for matching requests. It does not read request or response bodies.
Data We Do Not Collect
- Passwords, form values, or cookie contents
- Full page content or browsing history
- Personal identity information (unless you configure a custom user identifier field)
- Data from pages that do not match your configured actions
Where Data Goes
Event data is sent exclusively to the observability platform you select in the extension settings. You choose and configure the destination — the extension does not send data to any service you have not configured.
For license management, the extension communicates with the Peekmon service to validate your license and manage seats. A one-way device identifier is generated locally and sent to the Peekmon license server for this purpose.
Local Storage
- Credentials (API tokens, license keys) are stored on your device only and are never synced across devices
- Configuration (actions, context fields, watchers) syncs across your browser instances but contains no credentials
When you export settings, credentials are automatically stripped from the export file.
Data Retention
The extension does not persist event data locally. Events are forwarded to your configured connector in real time. Failed events are briefly queued in memory and retried; the queue is cleared when the browser closes.
License data is stored locally and refreshed periodically. Deactivating your license removes all stored license data from the device.
Third-Party Services
We do not sell, rent, or share your data with third parties. The only external services that receive data from the extension are the ones you explicitly configure. Each third-party connector has its own privacy policy governing how it handles data after receipt.
Changes to This Policy
We may update this policy as the extension evolves. Changes will be posted on this page with an updated effective date. Continued use of the extension after changes constitutes acceptance of the updated policy.
Contact
If you have questions about this privacy policy or how Browser Peek handles your data, contact us at [email protected].