PageDiff — Privacy Policy

Effective date: 19 April 2026

Version: 2

TL;DR

  • Everything stays on your device. PageDiff does not transmit any data to any server we operate. We don’t have a server.
  • We don’t have an account system. There is nothing to sign up for.
  • We don’t track you. No analytics, no telemetry, no advertising.

1. Data controller

PageDiff is published by Kostiantyn Pavlovskyi (Weekend Empire), team@weekend-empire.com. For any privacy-related question, write to that address.

2. What PageDiff stores locally

PageDiff uses chrome.storage.local — a browser-provided, device-local storage area — to save:

  • The list of URLs you chose to track, plus any optional labels, CSS selectors, and bearer tokens you provided for those URLs.
  • Compressed HTML snapshots of those URLs, taken once a day or when you press “Snapshot now” / “Snapshot this tab”.
  • Snapshot metadata (timestamp, SHA-256 hash, source of the snapshot).

This data lives only in your Chrome profile on your computer. Uninstalling the extension deletes it.

Plain-text token disclosure: If you provide a bearer token, it is stored in plain text in chrome.storage.local. Anyone with access to your Chrome profile can read it. Treat it like any other local credential.

3. What PageDiff sends over the network

PageDiff makes outbound HTTP(S) requests only to URLs you have explicitly added to the tracked list. These requests are made from your browser, look like any other request from your browser, and go directly to the target site — never through any intermediate server of ours.

If you provided a bearer token for a URL, that token is sent as an Authorization: Bearer <token> header only to that specific URL.

PageDiff does not contact any third-party analytics, telemetry, advertising, or crash-reporting service.

4. Permissions and why we need them

  • storage — save your tracked URL list and snapshots locally.
  • unlimitedStorage — allow more than 10 MB of snapshots over time.
  • alarms — schedule the once-per-24-hour automatic snapshot.
  • scripting — execute a one-shot script in your active tab when you click “Snapshot this tab”.
  • host_permissions: <all_urls> — fetch any URL you explicitly add to the tracked list.

5. Legal basis (GDPR Art. 6)

The local storage and outbound fetch operations described above happen at your explicit request. The legal basis is Art. 6(1)(a) consent — by adding a URL or pressing a snapshot button, you instruct PageDiff to perform that operation. You may withdraw consent at any time by removing the URL or uninstalling the extension; this deletes the underlying data.

6. Retention

Snapshots and settings persist locally until you delete them (per-URL or by uninstalling the extension). PageDiff does not impose a retention period and does not have access to delete data on your behalf.

7. Your rights

Because all data lives on your device and never reaches us, the practical exercise of GDPR rights is direct:

  • Access (Art. 15): open chrome://extensions → “Storage Inspector” to view stored data.
  • Rectification (Art. 16): edit URL entries by removing and re-adding.
  • Erasure (Art. 17): click the “×” next to a URL, or uninstall the extension to delete everything.
  • Portability (Art. 20): snapshot data is plain JSON inside chrome.storage.local and can be exported via Chrome DevTools.
  • Object / restrict (Art. 21, 18): stop adding URLs, or uninstall.
  • Complain to a supervisory authority: you may file a complaint with your local data protection authority.

8. International data transfers

None. PageDiff does not transmit data to any server we control, and therefore performs no international transfers.

9. Children

PageDiff is not directed at children under 13 (or under 16 in jurisdictions that apply that threshold). It collects no information from any user.

10. Data sharing

We do not share, sell, transfer, or transmit your data to third parties. We have no way to — the extension has no backend.

11. Third-party libraries

PageDiff bundles two open-source libraries for computing diffs locally in the browser: diff (jsdiff) and htmldiff-js. Neither library makes network requests.

PageDiff does not use any third-party services, SDKs, or libraries that transmit data over the network.

12. Changes to this policy

If this policy changes, the updated version will be available at weekend-empire.com/privacy/pagediff and the version number plus effective date at the top of this page will be incremented.

13. Contact

Questions: team@weekend-empire.com