The short version
1. Who We Are
PagePulse Pro is a free Chrome browser extension developed and maintained by Sayak Biswas, an independent developer. This Privacy Policy explains what information is accessed when you use the extension, how it is used, and what is not done with it.
If you have any questions about this policy, you can reach the developer via LinkedIn.
2. What Data PagePulse Pro Accesses
2a. The URL of the active tab
When you click the PagePulse Pro icon and choose to run an audit, the extension reads the URL of the current tab. This URL is sent to Google's public PageSpeed Insights API solely for the purpose of fetching performance metrics. The URL is not stored on any server controlled by PagePulse Pro, and is not retained beyond the duration of the API request.
2b. The page's DOM (for SEO analysis)
To perform the 14-point SEO audit, the extension runs a content script that reads the HTML structure of the active page — things like the title tag, meta description, heading hierarchy, image attributes, and link elements. This analysis happens entirely within your browser. No page content is transmitted to any external server by PagePulse Pro.
2c. Audit history (local storage only)
To provide the History tab feature, PagePulse Pro stores a record of past audits using Chrome's built-in chrome.storage.local API. This data is stored exclusively on your own device and never leaves it. It is not synced to any cloud service, and is not accessible to the developer or any third party.
You can clear this history at any time from within the extension. Uninstalling the extension also removes all locally stored data.
3. What We Do Not Collect
- Personal information (name, email, address, phone number)
- Browsing history beyond the single URL you actively audit
- Device identifiers or hardware fingerprints
- IP addresses or geolocation data
- Crash reports, usage analytics, or telemetry of any kind
- Cookies or tracking pixels
PagePulse Pro contains no analytics SDK, no advertising framework, and no third-party tracking of any kind — beyond the Google PageSpeed Insights API call described above.
4. Third-Party Services
Google PageSpeed Insights API
When you trigger a speed analysis, the URL of the current page is sent to Google's publicly available PageSpeed Insights API. This API call is governed by Google's Privacy Policy and Google APIs Terms of Service. PagePulse Pro has no control over how Google processes data on its own infrastructure.
AI Fix Guide
The AI-powered fix suggestions feature uses a publicly accessible AI endpoint to generate recommendations. The data sent consists only of the audit findings (metric values, SEO check results) — not any personal information and not the full content of the page being audited.
5. Permissions Used
The extension requests the following Chrome permissions, and only these:
- activeTab — to read the URL and DOM of the tab you are actively auditing, on demand (only when you click the extension icon).
- storage — to save your audit history locally in your own browser via
chrome.storage.local. - scripting — to inject the content script that reads SEO-relevant elements from the page's HTML.
6. Children's Privacy
PagePulse Pro is a developer tool intended for general audiences. It does not knowingly collect or solicit information from anyone under the age of 13. If you believe a child has provided information to this extension in violation of this policy, please contact the developer immediately.
7. Security
Because PagePulse Pro does not operate any servers or databases that store your personal information, there is no centralised data store that could be breached. All audit data lives locally in your browser under Chrome's standard storage isolation model.
8. Changes to This Policy
This Privacy Policy may be updated from time to time as the extension evolves. Any material changes will be reflected in the "Last updated" date at the top of this page. Continued use of the extension after changes constitutes acceptance of the updated policy.
9. Your Rights
Since PagePulse Pro does not collect personal data, there is nothing to request access to, correct, or delete on our end. If you would like to remove the audit history stored locally on your device, you can do so from within the extension's History tab, or by uninstalling the extension entirely.
10. Contact
If you have any questions, concerns, or feedback about this Privacy Policy or the extension's data practices, please reach out via:
- LinkedIn: linkedin.com/in/sayak-biswas
This policy is effective as of April 14, 2026.