PayloadScope — Privacy Policy
What PayloadScope accesses
PayloadScope uses Chrome's devtools.network API to read network request and response data for the page currently open in the DevTools window you have it active in. This is the same network activity already visible in Chrome's built-in Network tab — PayloadScope does not gain access to anything Chrome doesn't already show you.
What PayloadScope does with that data
All captured request and response data is held in memory, within your browser, for the duration of your DevTools session. Nothing is sent to any external server. PayloadScope makes no network requests of its own. Closing the DevTools panel or the tab clears all captured data.
What PayloadScope does not do
PayloadScope does not use cookies, does not set any tracking identifiers, does not communicate with any remote server or analytics service, and does not share data with any third party, because no data ever leaves your browser in the first place.
Credential handling
When you use the "Copy as cURL" feature, PayloadScope automatically redacts common credential fields (cookies, authorization headers, API keys, session tokens, and CSRF tokens) by default. A separate, explicitly-labeled option lets you include real credentials when you need a fully runnable command, with a confirmation prompt before doing so.
Permissions
PayloadScope requests no host permissions and no broad data-access permissions. It declares devtools_page, the minimum required to add a panel to DevTools, and storage, used only to remember whether a Pro license has been activated on this device. The storage permission does not grant access to browsing data, page content, or network activity.
Changes to this policy
If PayloadScope's data practices ever change, this page will be updated and the effective date above will be revised accordingly.
Contact
Questions about this policy or how PayloadScope works can be sent to [insert your contact email].