This Privacy Policy explains how Page Autopsy (the "Extension") handles data when you use it. The Extension is committed to transparency and does not collect, sell, or share your personal data. All performance analysis runs entirely inside your browser — no page data is ever sent to a remote server.
1 Data the Extension collects
The Extension collects the minimum data necessary to generate a per-element performance report. All processing is done locally on your device.
| Data | Purpose | Stored? | Transmitted? |
|---|---|---|---|
| Page URL | Displayed in the side panel header; used as a key for before/after comparison snapshots | Not stored | No |
| Resource timing data (URLs, sizes, durations, cache/compression status) | Generating the per-element performance table, cache analysis, and third-party breakdown | Not stored | No |
| DOM structure (element count, heading hierarchy, image attributes, etc.) | DOM-size analysis, SEO scan, accessibility scan, image audit | Not stored | No |
| Performance metrics (LCP, CLS, INP, FCP, TTFB, layout shifts, long tasks) | Core Web Vitals display and score calculation | Not stored | No |
| Baseline snapshot (a copy of the analysis for the current domain) | Before/after comparison feature (user-initiated) | chrome.storage.local (one snapshot per domain) |
No |
| PRO license status (from ExtensionPay) | Unlocking PRO features in the UI | chrome.storage.local (cached) |
ExtensionPay only (see §3) |
2 Permissions used
| Permission | Justification |
|---|---|
activeTab | Inject the analysis script into the currently active tab when you click the extension icon. No background access to all tabs. |
scripting | Execute the performance-analysis functions in the context of the active page. |
storage | Cache PRO license status (to avoid flickering on every panel open) and persist your optional before/after snapshot. |
sidePanel | Display the analysis results in Chrome's side panel. |
host_permissions | Inject into whichever URL you choose to analyze. The Extension only runs when explicitly invoked via the toolbar icon. |
3 Payment processing (ExtensionPay)
PRO license purchases are processed by ExtensionPay (extensionpay.com), which uses Stripe for card processing. When you purchase a PRO license:
- Your email address and license status are shared with ExtensionPay so they can verify your entitlement each time the Extension checks.
- Payment card details are handled entirely by Stripe — the Extension never sees or stores them.
- ExtensionPay's own privacy policy and terms apply to the data they process.
- The Extension caches your license status locally to avoid redundant network calls; this cache is never transmitted anywhere else.
4 Data retention & deletion
- Runtime data (page metrics, DOM analysis, resource timings) exists only in memory while the side panel is open. It's discarded when you close the panel or navigate to a different page.
- Before/after snapshots are stored in
chrome.storage.localand persist until you clear them via the "Clear baseline" button in the side panel, or until you uninstall the Extension. - PRO cache is stored in
chrome.storage.localand is overwritten each time the license status is refreshed.
To delete all stored data at any time:
- Right-click the Extension icon → "Manage extension"
- Click "Clear storage" under the Storage section, or simply uninstall the Extension.
6 Your rights (GDPR / CCPA)
Because the Extension does not collect personal data, there is no personal data to access, correct, or delete on our end. If you've purchased a PRO license through ExtensionPay, please refer to ExtensionPay's privacy policy for rights related to that data.
For any questions, open an issue at the project repository (see §8).
7 Changes to this policy
If this policy changes materially, the updated version will be posted at this URL and the Extension's version number will be bumped. Continued use after changes constitutes acceptance of the new policy.
8 Contact
Page Autopsy is an open-source project maintained on GitHub.
Repository: github.com/anomalyco/page-autopsy
For privacy-specific inquiries, open an issue with the "privacy" label.