Privacy policy
Last updated: 1 October 2026. Applies to version 1.0.0 and later.
Jharokha collects no data.
What this means
- No personal information, browsing history, page content or usage analytics is collected, stored on a server, sold or shared.
- There are no accounts, no servers run by us and no analytics or advertising code.
- The extension makes no network requests of its own and loads no remote code. Pages you preview load exactly as they would in a normal tab.
What is stored on your device
Your settings (theme, last device, zoom and similar), favourite devices, recent devices and custom devices are saved in your browser's extension storage on your own computer. They are never uploaded or synced by Jharokha, and you can delete them at any time with "Reset" on the options page or by removing the extension.
Screenshots
Screenshots are created on your device, only when you ask for one, and saved or copied only where you choose. They are never sent anywhere.
Recordings
"Record video" (Chrome and Edge) records the preview of the tab you choose, only after you press Record and only while the red REC sign is shown. The video (and a GIF, if you export one) is made in memory on your device and saved with your browser's normal download. Recordings never leave your device and are never uploaded or shared.
The pages you preview
Jharokha shows the page of the tab you opened it on inside a device frame. It does not read, record or transmit that page's content. Whatever the page itself does (for example loading its own scripts or sending its own analytics) is the same as in a normal tab, and is governed by that site's own policy.
Permissions and why they are needed
| Permission | Why |
|---|---|
storage |
Saves your settings, favorite devices, recent devices and custom devices on your own machine. |
activeTab |
Lets the simulator open on the tab you clicked, only after you click the icon or press the shortcut. |
scripting |
Injects the simulator overlay into that tab on demand, so nothing runs on pages where you never open it. |
declarativeNetRequestWithHostAccess |
Some sites refuse to load inside a frame. For the preview frame in that one tab
only, it removes X-Frame-Options and (only if it contains
frame-ancestors) the page's CSP header. Optionally sends the device's
user agent for that frame.
|
<all_urls> (optional, asked at runtime) |
Asked only when a site blocks framing and you press "Allow on this site". Needed for the rule above. You can revoke it in your browser's settings. |
tabCapture (optional, asked at runtime, Chrome and Edge) |
Asked only when you first press "Record video". Records the simulator preview of the tab you chose, only while the red REC sign is shown. The video is saved on your machine and never uploaded. |
offscreen (optional, asked at runtime, Chrome and Edge) |
Asked together with tabCapture. A hidden extension page turns the tab recording into the video file, because the background service worker cannot record video. |
The extension's own pages also allow 'wasm-unsafe-eval' so it can run its
bundled WebAssembly image code. That does not allow eval() or code from the
internet.
Real device mode
A separate build of Jharokha may offer "Real device mode", which uses Chrome's
debugger and sidePanel permissions to emulate a device on a tab
you choose, only until you press Stop. It collects no data either, and nothing leaves your
machine. This policy applies to it as well.
Children
Jharokha is a developer tool and collects no data from anyone, including children.
Changes to this policy
If this ever changes, the new policy will be published here before the change ships, with a new date at the top, and the change will be listed in the extension's release notes.
Questions
Email Abhishek Kumar Singh at abhisheksinghinfo7@gmail.com.