Privacy Policy

PageProof is a user-initiated webpage snapshot and comparison extension. It allows a user to capture a bounded representation of a webpage, retain that snapshot locally, and later compare a fresh scan of the same canonical URL with a saved version.

This policy covers PageProof version 1.0.0, including page scanning, local snapshots, SHA-256 fingerprints, snapshot retention, link capture, the Snapshot Library, and the full comparison workspace.

This policy does not govern the websites you inspect, Chrome, the Chrome Web Store, your operating system, browser-profile backup software, or other extensions.

PageProof scans a page only after the user explicitly initiates a scan or capture from the extension.

A snapshot may include:

• The current page URL and a normalized or canonicalized URL used for matching.
• The hostname and page title.
• The local capture timestamp.
• Visible text from a bounded set of semantic content blocks.
• DOM paths used to match corresponding blocks later.
• Nearby heading context used to make comparisons easier to understand.
• A bounded list of visible links, link text, and normalized link destinations.
• A locally calculated SHA-256 fingerprint of the captured representation.

PageProof is designed to capture enough structure for useful change detection without storing a complete browser archive of the page.

Version 1.0.0 is not designed to read password values, browser cookies, saved credentials, bookmarks, download history, microphone data, camera data, local files, or physical location.

The page scanner does not intentionally read the current value of form controls. This reduces the chance of snapshotting text that a user is actively typing into an input field.

PageProof also does not continuously inspect all browser tabs. Access is tied to the user-selected active tab through Chrome's activeTab permission.

PageProof does not save a full HTML document. The scanner uses a bounded set of semantic elements and applies limits to the amount of information retained for each capture.

Version 1.0.0 is designed to retain up to:

• 180 text-oriented content blocks per capture.
• 220 visible links per capture.
• 1,400 characters for an individual captured text block.

These limits reduce storage growth and make the comparison process more predictable.

The extension also limits the number of retained snapshots for a URL and applies an overall local storage budget. Older retained snapshots can be discarded when those limits are reached.

PageProof uses chrome.storage.local for the saved snapshot library. The main state key used by version 1.0.0 is pageProofStateV1.

A retained snapshot can include the bounded page representation, capture metadata, normalized URL information, link information, and the local content fingerprint.

PageProof does not require a PageProof account or a developer-operated cloud database for normal snapshot storage.

When the user opens the full comparison workspace, PageProof may place the comparison payload in chrome.storage.session.

Session storage is used so the comparison page can receive the relevant before/after data without turning that temporary workspace payload into another long-term snapshot record.

The permanent retained records remain governed by the Snapshot Library and local storage limits.

PageProof calculates a SHA-256 fingerprint from the captured representation so the user can see whether two captured representations are identical or different.

The fingerprint is calculated locally. It is not submitted to a blockchain, public timestamp authority, remote notarization service, or developer server in version 1.0.0.

PageProof compares a saved snapshot with a newly scanned representation locally in the extension.

The comparison first uses stable DOM-path information where possible. For unmatched blocks, PageProof can use bounded text similarity to distinguish likely modifications, moves, additions, and removals.

Visible link sets are compared separately so link additions, removals, or destination changes can be surfaced independently from text-block changes.

Comparison results may be imperfect when a site significantly restructures its DOM, changes content dynamically, randomizes markup, or loads additional content after the scan.

PageProof uses the activeTab permission so the user can explicitly grant temporary access to the currently selected page.

This permission is used when the user opens PageProof and chooses to scan or capture the active page. It avoids the need for persistent host access to every website.

PageProof does not use activeTab to continuously monitor unrelated tabs in the background.

PageProof uses the scripting permission to execute its packaged scanner in the active tab after the user initiates a scan or capture.

The scanner reads the bounded page representation needed for the snapshot and returns that result to the extension for local processing.

No remote JavaScript is downloaded or injected as part of this workflow.

The storage permission allows PageProof to retain snapshots locally and to pass temporary comparison information to the full comparison workspace.

Version 1.0.0 does not use this permission to upload captures to a PageProof cloud database.

Chrome profile migration, device backups, or enterprise-management tools may separately copy browser storage according to their own behavior.

The Snapshot Library lists locally retained captures and provides user controls for managing them.

Users can delete individual snapshots and can clear the retained snapshot collection. Storage-budget cleanup can also remove older retained snapshots automatically when limits are reached.

Once a local snapshot is deleted, PageProof version 1.0.0 does not provide a normal cloud backup from which the developer can restore it.

PageProof version 1.0.0 does not include Google Analytics, Firebase Analytics, Mixpanel, Amplitude, Segment, PostHog, or a comparable analytics SDK.

It does not build a developer-side profile of which websites you capture, how often you compare pages, which changes you inspect, or which snapshots you retain.

The extension does not use advertising identifiers, tracking pixels, fingerprinting technologies, or cross-site behavioral profiling.

PageProof does not display third-party advertising and does not include an advertising network or retargeting system.

Captured page text is not sent to a remote AI service for summarization, classification, semantic comparison, content generation, or profiling in version 1.0.0.

The comparison logic and fingerprinting required by the current product operate locally.

The reviewed production package does not use fetch, XMLHttpRequest, or WebSocket to upload saved snapshots or page text to a developer backend.

The page being inspected may independently make network requests while it is open. Chrome, the operating system, security software, or other extensions can also make their own requests.

Those third-party requests are not PageProof snapshot uploads.

PageProof operates on webpages created and controlled by third parties. Those websites may have their own privacy policies, authentication systems, personalization, cookies, and data-collection practices.

PageProof does not control the accuracy, legality, availability, or privacy practices of a webpage being captured.

Users are responsible for deciding whether they are permitted to capture or retain content from a particular page.

The developer does not sell, rent, trade, license, or provide the local PageProof snapshot library to advertisers, data brokers, marketing companies, or analytics providers.

During normal use, the developer does not receive the locally stored page text, fingerprints, or comparison library.

If a valid legal request is received, only information actually possessed by the developer can be produced. PageProof's normal local snapshot library is not a developer-hosted archive.

PageProof limits privacy exposure by requiring user-initiated page access, keeping the snapshot library local, applying capture and storage limits, and avoiding a remote comparison backend.

Local Chrome extension storage is not an encrypted evidence vault. Someone with sufficient access to the same unlocked browser profile, device, browser files, or profile backup may potentially access local snapshots.

Users should avoid capturing confidential pages when local browser-profile storage does not meet their security requirements.

PageProof comparisons are informational and should not be treated as a substitute for professional archival, legal evidence preservation, or regulated records-management systems.

PageProof is a general webpage research and comparison utility. It does not create public social profiles, request dates of birth, provide user-to-user messaging, or operate a behavioral advertising profile for children or adults.

Because the local snapshot library is not intentionally uploaded to PageProof servers, PageProof does not ordinarily transfer that library between developer-operated data centers or countries.

Chrome, websites, operating-system backups, or enterprise tools may have independent international processing practices outside PageProof's control.

This policy may be updated to improve clarity, reflect changes to PageProof, address Chrome Web Store requirements, or describe new privacy practices.

Material changes such as cloud snapshot storage, accounts, analytics, remote AI, broader website access, third-party timestamping, or new permissions should be reflected in an updated privacy policy and store disclosures.

For privacy questions about PageProof, use the developer contact information shown on the Chrome Web Store listing from which you obtained the extension.

When contacting the developer, avoid including confidential page content unless it is strictly necessary to explain the request.