Last updated: 2026-08-07
Quick API Client does not collect, store on a remote server, or share any user data with its developer or any third party. It does send network requests — but only the ones you explicitly compose and click "Send" on, to the destination you specify.
This extension is a request-composer side panel: you fill in a method, URL, headers, and body, and click Send. It then makes that exact HTTP request on your behalf, using your browser, and shows you the response. It can also pre-fill a request from a curl example or a URL you select and send via the right-click menu. No request is ever sent automatically or in the background — only when you click Send.
The extension itself does not collect, log, or transmit any data about you to its developer or to any analytics/third-party service. Your last-used request (method, URL, headers, body) is saved using Chrome's local storage API purely so it's still there next time you open the panel — this stays on your device and is never sent anywhere.
When you send a request, the URL, headers, and body you typed are of course sent to whatever server you pointed the request at — the same as if you'd used curl, Postman, or your browser's address bar. That's between you and the API you're calling; this extension is just the messenger.
The extension uses sidePanel (to show the request panel), storage (to remember your last request locally), and contextMenus (for the right-click "Send to Quick API Client" entry). It also requests optional host permissions (<all_urls>), but only per-domain and only at the moment you send a request to a new domain — Chrome shows you its own permission prompt for that domain, and the extension never gets broader access than the domains you've actually used it against.
This extension does not integrate with, or share data with, any third-party service, advertiser, or analytics provider. It only talks to the servers you explicitly direct it to.
If this policy ever changes, the updated version will be published at this same URL.
Questions about this policy can be raised via GitHub Issues on the project repository.