Bezlo Chrome & Edge extension

Privacy Policy

Bezlo does not collect, store, transmit, or sell any personal data.

Last updated: 2026-10-27 (version 1.0.0). Chrome/Edge Manifest V3.

There is no account, no analytics, no telemetry and no crash reporting. It has no server and receives no data. Everything the extension shows and captures happens in your own browser, on your own machine. The one network connection it makes is to a relay you configure yourself for Live device; if you never open Live device, there is no such connection.

Short version

• No account. There is nothing to sign up for.
• No telemetry, no analytics, no crash reporting. We have no server and receive no data.
• No ads, no tracking, no sale of data.
• Everything the extension shows and captures happens in your own browser, on your own machine.
• The one network connection it makes is to a relay you configure yourself for Live device (loopback by default, 127.0.0.1:7333). If you never open Live device, there is no such connection.

What the extension stores (and where)

All of it is on your device, in the browser's extension storage (chrome.storage.local, plus chrome.storage.session for the current browser session only). None of it is synced to an account or sent anywhere.

• Selected device, board layout, recent devices to remember what you were testing (local).
• Theme (light/dark) so the stage and popup look the way you left them (local).
• Capture options (framed/frameless, viewport/full page) for the same reason (local).
• The last device URL you typed in the light table to prefill the URL field next time (local).
• First-run explanation seen (a boolean) so the card is not shown again (local).
• Live device settings: relay address, relay token, last device and URL, so it can reconnect without retyping (local).
• Which tabs currently have the framed light table open, to keep the toolbar popup's state correct for this session (session, cleared when the browser closes).

The token is the relay's own token, generated by the relay you run; it never leaves your machine except back to that relay. Uninstalling the extension or clearing its storage deletes everything listed above.

What the extension never does

• It does not collect personal data, browsing history, page content, form input, cookies or credentials, and does not transmit any of them to us or to a third party.
• It does not use remote code. The package contains no eval, no new Function, and loads no script from the network. Everything that runs is in the extension package the store reviewed.
• It does not inject content scripts on pages you did not activate it on: no content script is declared in the manifest. Injection happens once, into the tab whose toolbar button you pressed.
• It has no account system, no cloud sync, no affiliate code, no analytics SDK and no crash reporter.

The permissions, in plain language

The manifest asks for exactly five things. Here is what each one is for.

debugger

This is the engine of the product, and it deserves a plain explanation. To make a page behave as if it were on a phone, the extension uses Chrome's own DevTools emulation layer: the same machinery behind DevTools' device toolbar. The only way an extension can reach that layer is chrome.debugger, which is why the permission is there. While a device is emulated, Chrome itself shows a bar saying the browser is being debugged; that bar is Chrome's, not ours, and pressing Cancel on it ends the session. The debugger attaches only after you click the toolbar button or a control inside the light table, only to the tab (or the device) you picked, and detaches when you close the frame, press Stop, or reload the page. It is not left attached in the background.

<all_urls> (host permission)

The page you want to test is your own work: localhost, a staging host, a logged-in app, a public site. There is no way to list those hosts in advance, so the extension asks for http(s) pages in general. It uses that access for three things and nothing else: attach the debugger to the tab, mount the framed light table in it, and let the device frame load the page being tested. It does not read or store page content for any other purpose.

activeTab

The toolbar click is the only way in. activeTab gives access to the current tab at the moment of that click; both the framed overlay and the plain real-tab mode start there.

scripting

Used once per activation to inject the framed light table's overlay host into the tab you clicked. No other tab is touched.

storage

The list above, on your device only.

Network connections

Two kinds exist, and neither talks to us.

• The page under test loads exactly as it would in a browser. The device is a real page load: its requests go to the site you chose. That is the point of a simulator, and it is the same traffic the tab would make anyway.
• Live device (optional) connects to a relay you run. The default endpoint is ws://127.0.0.1:7333/ws on your own machine; before connecting, the extension probes http://127.0.0.1:7333/health. You can point it at another host (your own VM, or a wss:// endpoint behind TLS you control). The connection carries the rendered frames of the page you chose to test, and your tap/scroll/key input back to that relay. We host no relay and receive nothing. If you never open Live device, this connection never happens.

What we receive

Nothing. There is no server component operated by us, no endpoint that extensions report to, and no identifier tied to your install.

Your control

• Stop in the light table ends emulation (and the debugger detaches).
• Cancel on Chrome's debugging bar does the same.
• chrome://extensions → this extension → Site access can restrict the host permission; the product will stop working on sites you exclude.
• Removing the extension deletes all stored settings listed above.

Children

The extension is a developer tool, is not directed at children, and collects no data from anyone.

Changes

If a future version changes how data is handled, this page is updated before that version ships, and the "last updated" date changes. The current version is 1.0.0.

Contact

Owen (gba3124): open an issue on the project's public page, or use the support link on the Chrome Web Store listing.