Privacy Policy

The short version

WideEye runs entirely on your own machine. It has no accounts, no servers of ours, and no analytics. We never receive your designs, your screenshots, the pages you visit, or your access token — there is nowhere for that data to go, because the extension does not send anything to us.

What the extension handles

Design images you add

Image files you drop on a page, and frames imported from a design file you have access to, are stored in your browser’s local extension storage together with their position, opacity and scale, so your work is still there after a reload. They stay on your device and are deleted when you remove the layer or uninstall the extension.

Screenshots of the page you are checking

Running a scan, using the colour picker, or exporting a report captures the visible area of the current tab. That capture is compared against your design in the browser’s memory and then discarded. It is never uploaded. If you export a report, the image is written into an HTML file that is downloaded straight to your computer.

Your personal access token

Importing a frame by link is optional and requires a read-only personal access token that you create and paste in yourself. It is kept in Chrome’s extension storage, which syncs across the Chrome instances you are signed into, and is sent only to the design service’s own API to fetch the frame you asked for. We never see it. Clearing it in the popup removes it.

Network requests

The extension makes exactly one kind of outbound request: to the design service’s API, and only when you paste a frame link and have saved a token. It fetches the rendered image of that frame. Nothing else leaves your browser — no telemetry, no crash reports, no usage statistics.

What we never do

• We do not sell or transfer your data to third parties.
• We do not use or transfer your data for anything unrelated to the extension’s single purpose.
• We do not use or transfer your data to determine creditworthiness or for lending.

Permissions and why they exist

Access to the sites you use it on

The extension has to draw the overlay on whatever page you are checking — a staging server, a localhost address, a live site — so there is no fixed list of hosts that would work. The same access lets it capture the current tab for the pixel comparison. It does nothing on pages where you have not added a layer.

Storage

Keeps your layers and settings between sessions. Design images can be several megabytes each, which is why the extension asks for storage without the default cap — otherwise your saved overlays would be dropped without warning.

Changes and contact

If this policy changes, the date at the top changes with it. Questions about anything here — write to call2margino@gmail.com.