License & privacy
Privacy and permissions
What Pickode does with your data and why it asks for each browser permission: everything runs locally, the license key goes only to Freemius.
Updated October 20, 2026
Pickode works inside your browser. It doesn’t collect or send your browsing data, and there is no Pickode server that sees the pages you analyze. This page explains what does leave your browser, and why the extension asks for each permission. The full policy is on the Privacy policy page.
What leaves your browser
| What | Where it goes | When |
|---|---|---|
| License key | Freemius only | To activate and verify Pro |
| Your library | Your own Google Drive, directly | Only if you connect Google Drive |
| Requests to the analyzed site | The site you’re analyzing | When GEO or Debug read its files and images |
Nothing else is sent. Pickode doesn’t use tracking cookies, and the pages you analyze never go through a Pickode server.
Requests to the site you analyze
Pickode isn’t “zero network requests”. GEO reads robots.txt, llms.txt, the sitemap and the initial HTML of the site you’re analyzing, and Debug’s image optimizer downloads that site’s images to convert them in your browser. These requests go only to the site you’re working on.
Google Drive sync
Library sync with Google Drive (Pro) uses Google’s drive.file permission. It only covers the files Pickode itself creates, in a visible “Pickode” folder; Pickode can’t read the rest of your Drive. Sign-in happens in your browser, your library goes straight from your browser to your Drive, and nothing passes through a Pickode server. The data isn’t shared with third parties or used for advertising or model training. “Disconnect” revokes access and leaves your files in Drive. See Library.
Permissions, one by one
| Permission | Why Pickode asks for it |
|---|---|
activeTab, tabs, host access (<all_urls>) |
To read the page you’re inspecting, exporting or analyzing |
scripting |
To run the inspector and the analysis panels in the page |
storage, unlimitedStorage |
To keep settings, your library and saved CSS in your browser |
downloads |
To save exports, ZIP files, screenshots and reports |
contextMenus |
To add Pickode entries to the browser’s right-click menu |
webRequest |
To find assets and streaming video the page loads from the network |
declarativeNetRequestWithHostAccess |
To apply network rules on the sites Pickode has access to |
sidePanel |
To open Pickode in the browser’s Side Panel (not in Firefox) |
browsingData |
Debug: clears the data of the open site only, and only when you ask |
identity |
Google Drive sign-in, only if you connect it |
Related
Still stuck?Contact us