Mockpup Add to Chrome

Privacy Policy

Mockpup collects no data. No analytics, no ads, no tracking, no account, no servers. Nothing you do in Mockpup is sent to the developer or to any third party.

What Mockpup stores, and where

All of this is stored locally in your browser, on your device, and is only used to draw the overlay again when you come back to a page. It is never uploaded or synced. You can delete it at any time by removing the layers in Mockpup or uninstalling the extension.

Page captures

When you use the match analyzer, the loupe or “Export PNG”, Mockpup captures the visible part of the current tab. The analyzer and the loupe use that capture in memory and discard it; “Export PNG” saves the image to your downloads folder. When you pin a layer to an element, Mockpup remembers that element's CSS selector. All of this stays on your device. Captures and page details are never sent anywhere.

Network requests

Mockpup makes network requests only when you ask it to:

There is no remote code, and nothing is ever sent to the developer.

Figma integration (optional)

If you choose to connect Figma, you give Mockpup a Figma personal access token. It is stored locally in your browser and is only ever sent to Figma's API (api.figma.com). When you paste a layer you copied in Figma, Mockpup sends that token, the file's key and the copied layer's id to Figma to get a PNG image of the layer, then downloads that image from the address Figma returns. Nothing else is sent. You can disconnect at any time from Mockpup's menu (Figma… → Disconnect), which deletes the token. Figma's handling of those requests is covered by Figma's privacy policy.

Permissions

Changes

If this policy ever changes, the new version will be published on this page. Mockpup will not start collecting data without an explicit, opt-in change to the extension.

Contact

Questions: hello@mockpup.com

Applies to Mockpup 1.0.0 for Chrome and Firefox.