Local-first. No upload. No tracking.
Birdor JSON Lens
Local-first JSON reader
Back to help center
Privacy and permissions

Understand the privacy and permission model

Learn why JSON Lens uses explicit user actions and avoids broad browser permissions.

Updated2026-05-30
LevelBeginner
Read4 min
1Step 1

Start from an explicit action

JSON Lens begins from a popup click, selected-text action, pasted payload, or local file. It does not watch network traffic in the background.

JSON Lens opened after an explicit user action in the browser.
2Step 2

Know what the requested permissions do

storage saves preferences, contextMenus supports selected text actions, and activeTab plus scripting render the current page only after you click.

JSON Lens local reading interface with path actions.
3Step 3

Check what is deliberately not requested

The extension does not request webRequest, cookies, history, tabs, debugger, or persistent host access such as all_urls.

JSON Lens Scratchpad processing JSON locally without account or upload flow.

Related guides

Still need help?

Contact Birdor support or submit a ticket draft with the workflow, browser, and sanitized details we need to reproduce the issue.

Email support@birdor.com

Submit a support ticket

This static help center opens a prefilled email draft so you can review details before sending them.