Privacy Policy

API Payload Debugger · Version 1.0.0 · Effective

In short

API Payload Debugger is a local-only developer tool. It collects no personal data, has no analytics or telemetry, requests no Chrome permissions, and does not transmit your JSON anywhere. The only outbound network request the extension can make is the Load URL feature, and that only happens when you click the button and type a URL yourself.

1. Who this policy applies to

This policy covers the Chrome extension “API Payload Debugger” (hereafter, “the extension”) distributed via the Chrome Web Store. It applies to anyone who installs and uses the extension on a Chromium-based browser.

2. Information we collect

None. The extension does not collect, transmit, or store any personally identifiable information, health data, financial data, authentication credentials, personal communications, location data, browsing history, user activity, or website content.

The data you paste, type, or fetch into the extension (JSON payloads, JWT tokens, JSONPath expressions, mask patterns, etc.) is processed exclusively inside the browser tab the extension runs in. It is held in JavaScript memory for the lifetime of that tab and is discarded when the tab is closed or reloaded. It is never sent to the extension author, never written to disk by the extension, and never shared with any third party.

3. Analytics, telemetry, and tracking

None. The extension contains no analytics SDKs, no crash reporters, no usage trackers, no advertising identifiers, and no fingerprinting code. No background script polls a remote server. No “phone home” request is made on install, on update, or on use.

4. Network activity

The extension makes no automatic network requests. The only outbound request it can ever perform is initiated by the user via the Load URL feature on the top toolbar:

The author of the extension has no involvement in or visibility into these requests. They are a direct connection between your browser and the URL you typed.

5. Permissions requested

The extension’s manifest.json declares:

The extension cannot read, modify, or observe the content of any web page you visit. It cannot access your browsing history, your tabs, your cookies, your bookmarks, your downloads, or your clipboard without an explicit user action (such as pressing the copy button inside the extension’s own UI).

6. Storage

The extension uses no persistent storage. It does not write to chrome.storage, localStorage, sessionStorage, IndexedDB, or cookies. Every input you provide lives only in the memory of the tab until that tab is closed or reloaded.

7. Remote code

The extension uses no remote code. The complete application is bundled into the .zip package distributed by the Chrome Web Store. No JavaScript, WebAssembly, or other executable code is fetched from any external origin at runtime. The bundle contains no eval(), no new Function(), no chrome.scripting.executeScript(), no importScripts(), and no dynamic import() of a URL.

8. Third-party services

The extension uses no third-party services, no third-party SDKs, no embedded fonts loaded from a CDN, and no remote stylesheets. All assets (JavaScript, CSS, fonts, icons) are bundled and served from inside the extension package.

9. Open-source components

The extension is built with the following open-source libraries, all compiled into the bundle at build time:

None of these libraries perform network activity on their own in the manner the extension uses them.

10. Children’s privacy

Because the extension collects no information from anyone, it knowingly collects no information from children under 13 (or the equivalent minimum age in the user’s jurisdiction).

11. Your rights

Because the extension stores no user data and transmits no user data, there is no data to access, export, correct, or delete on the author’s side. Uninstalling the extension via chrome://extensions removes it entirely.

12. Changes to this policy

If material changes are made to this policy in a future version of the extension, the Effective date at the top of this page will be updated, and the prior text will be retained in the project repository’s git history.

13. Contact

Questions, concerns, or reports about this policy can be sent to the author through the support email listed on the extension’s Chrome Web Store listing page.