In short
Page Pulse processes the content it inspects on your device, and that content is never sent to us. Some features do involve our servers — activating a licence, syncing your settings if you switch that on, or applying a policy your organisation set — and this policy sets out exactly which, and exactly what each one carries.
Accounts: Planned: no account for local checks, sign-in for hosted ones.
This extension has not been released yet. The practices below describe the intended design and will be finalised on this page before it ships.
01Scope
This policy applies to the Page Pulse browser extension published by ExtHive, on every browser where it is distributed.
It does not cover the websites you use Page Pulse on. Those sites have their own privacy policies, and using our extension does not change how they treat your data.
The general ExtHive Privacy Policy covers everything not specific to this extension, including your rights and how to exercise them.
02Permissions and why each one exists
The final permission set for Page Pulse will be published here before release, with an explanation of the feature that requires each one.
03What happens to each kind of data
The table below lists every category of data Page Pulse touches, how it is handled, and whether it ever leaves your device. Only if enabled means it stays local unless you turn on a feature that needs otherwise, or are on a plan that includes one.
| Data | Handling | Leaves device? |
|---|---|---|
| Watched pages and snapshots | Planned to be captured and compared locally on your device for browser-based checks, and stored on our servers for any watch you choose to have us run for you. Final data practices will be published here before launch. | Only if enabled |
04Accounts and features that use our servers
Checks that run in your browser need no account, but they only run while that browser is open. Watching a page overnight or while your laptop is shut means something has to do the checking for you, which is a hosted feature: it would require an ExtHive account and would mean we hold the URLs you watch and the snapshots we compare. We expect to offer both modes and to make clear which one each watch is using. Final practices will be published here before launch.
These are the only parts of Page Pulse that involve ExtHive servers. Everything else runs on your device.
| Feature | What it sends | Optional? |
|---|---|---|
| Hosted checks | Planned as opt-in per watch. Would store the URL, the region you selected and the captured snapshots on our servers so checks continue when your browser is closed. | Yes — off by default |
| Email and push alerts | Planned as opt-in. Delivering an alert off-device requires an address to send it to. | Yes — off by default |
Deleting your account removes the data held for these features. Where a feature is optional, turning it off stops any further data being sent and deletes what was already stored, as set out under Retention below.
05What we never collect
To be explicit, Page Pulse does not collect, transmit or store any of the following:
- your browsing history or the list of sites you visit;
- the content of pages you view, beyond the moment-in-time processing described above;
- keystroke logs or clipboard contents;
- device fingerprints, advertising identifiers or location data;
- anything used to build an advertising or behavioural profile.
We do not sell data, we do not share it with data brokers, and we do not use your content to train machine learning models.
06Local storage on your device
Page Pulse uses your browser’s extension storage to keep your preferences. That storage is sandboxed to the extension: other websites and other extensions cannot read it.
You can clear it at any time from the extension’s settings, or by removing the extension. Uninstalling deletes all local extension data permanently.
If you have enabled a feature that stores data with us — settings sync, or a plan that applies an organisation policy — uninstalling does not by itself delete that copy. Turning the feature off or deleting your account does, on the timeline set out under Retention.
If you enable your browser’s built-in extension sync, your browser vendor — not ExtHive — may sync those preferences across your own devices under their privacy policy.
07Retention
Page Pulse has not been released. Its data practices, including how long hosted checks keep the pages they watch, will be documented in full on this page before the extension ships.
08Extension store disclosures
Extension stores require developers to declare their data handling. Our declarations for Page Pulse state that we do not sell or transfer user data to third parties beyond the approved use cases, do notuse or transfer it for purposes unrelated to the extension’s single purpose, and do not use or transfer it to determine creditworthiness or for lending.
Those declarations match this policy. If you ever find a discrepancy between what a store listing says and what this page says, please tell us at privacy@exthive.com and we will correct it.
09Your rights and how to use them
Because Page Pulsekeeps your data on your own device by default, you can exercise most privacy rights directly: view your data in the extension’s settings, export it where an export exists, and delete it by clearing storage or uninstalling.
For anything held in your account — a licence record, synced settings, an organisation policy or a support email — write to privacy@exthive.com. Your full set of rights, and the timeframes we work to, are set out in the general Privacy Policy.
10Changes to this policy
If Page Pulse’s data handling changes, we will update this page and the date at the top before the change ships. A change that would send data off your device where it previously did not will always be announced in advance and, where the law requires, made subject to your consent.
Questions about this document?
Write to legal@exthive.com and a person will answer, usually within 1 business day.