Privacy and permissions
What Nitpique can see, what it stores, and why it asks for each permission.
Your data#
Nitpique has no account, no analytics and no server. It reads a page only after you turn it on for that tab, and nothing it reads leaves your browser. The one thing it requests is what the AEO view needs: the page's own robots.txt, its HTML (twice, once asking for Markdown) and its sitemap, and on request its API catalog and discovery files, from the page's own site, and only when you open that view; and what the Stack view needs: the page's own address once more, without cookies and often from the browser's cache, to read its response headers. To see what the page's scripts set, the Stack view also runs a short read-only check in the page itself. Your settings, grid, toolbar, shortcuts, guides, colour history and capture options are stored in your browser.
Permissions#
| Permission | Why |
|---|---|
| activeTab, scripting | Add Nitpique to the tab you turn it on for, only then |
| storage | Keep your settings, toolbar, shortcuts, guides, colour history and capture options |
| contextMenus | The Inspect with Nitpique item in the right-click menu |
| clipboardWrite | Copy values, colours and captures |
| Side panel (sidebar in Firefox) | Show the Element, Design and Page tabs |
| Access to sites (optional) | Asked only when a feature needs it |
| declarativeNetRequestWithHostAccess (optional) | Asked once, with access to all sites, the first time a page in the responsive canvas refuses to be framed, so pages show in its frames anyway. It applies only to frames in the tab the canvas is open in, while it is open |
Questions
Why does Nitpique ask for access to all sites?
Only when a feature needs it, such as the responsive canvas the first time a page refuses to be framed. Access to sites is optional.
Where are my settings and guides stored?
In your browser: settings, grid, toolbar, shortcuts, guides, colour history and capture options.