Page to Layers privacy policy

Effective date: 2026-11-08

Page to Layers copies the page in your active tab to your clipboard as editable design layers.

When Page to Layers reads a page

Page to Layers reads the content of a page only after you click its icon and press “Copy page as layers” (or “Copy as image”). It uses the Chrome activeTab permission, so it can read only that one tab, and only at that moment.

The page content, its styles, the layers built from it and the clipboard payload stay on your device. There is no server of ours to send them to.

When the popup opens, it shows the title and address of the active tab. They stay on your device.

A welcome page opens once, when you install the extension. It opens again when you choose “How it works” or “Turn on images” in the popup. Neither the popup nor the welcome page loads a favicon or any other remote image.

Network requests

Page to Layers makes two kinds of network requests.

1. Fonts

To measure text, Page to Layers downloads font files from the fontsource CDN on cdn.jsdelivr.net.

So jsDelivr receives the font family names, and your IP address as any web request does. It also receives the origin of the captured page (as the Origin header), or the page's full URL in the Referer header if that page's referrer policy allows it.

2. Images

Page to Layers fetches the page's images from hosts the page already references.

• Direct fetches run in the page. A request to the page's own site carries your cookies for that site; a request to any other host carries none. Like any image load, the host sees the address of the page you are capturing.
• Images from other sites are fetched by the extension's background worker, and only if you grant the optional permission. It covers https sites only, for one site or for all sites, and you grant it with buttons in the welcome page or the popup.

Background fetches follow these rules:

• They are sent without cookies.
• They never follow redirects. An image address that redirects is not fetched, and the redirected request is never sent.
• They never contact localhost or private-network names or addresses. This is checked by name, not by DNS: a public name that resolves to a private address is not detected, and if such an internal server has a valid certificate for that name, the request goes through, without cookies.
• Only image responses are used, and they never reach the page's own JavaScript.

If you allow all sites, the captured page decides which https hosts the extension contacts, on any port, up to 400 images per capture.

Hosts the page points to see your IP address. Background requests send no Origin, Referer or cookie headers.

Permissions

activeTab and scripting let Page to Layers read the tab you capture.

The optional site permission is what lets the background worker fetch images from other sites. It covers https sites only. Page to Layers asks for it only when you press a button in the welcome page or the popup: one for a single site, or one for all sites.

Chrome shows the all-sites request as “Read and change all your data on all websites”. Chrome does not word it as https-only, but Page to Layers asks only for https sites. It uses that access only to fetch images, and it only reads the tab you capture. If you prefer not to grant it, use the per-site button.

Grants persist until you revoke them. To revoke, open chrome://extensions, choose Page to Layers, press Details, then Site access.

What is copied

Page to Layers copies the page's content, not only what is visible:

• text scrolled out of view
• text hidden by means other than display:none (text with visibility:hidden is skipped)
• closed dropdown option lists
• the whole page, down to 20000 px
• same-origin images, fetched with your login cookies

Some things are not captured as typed text:

• Values you typed in input and textarea fields, and passwords, are not captured. Only placeholders are. Text that is already part of the page's own HTML, such as the initial content of a text area, may be captured.
• Text in editable areas (contenteditable) is captured.

“Copy as image” is a button you can press at any time, and Page to Layers also uses it automatically if the layer copy fails. It copies a screenshot of the visible area, which can include pixels of cross-origin iframes.

Things to know

• The clipboard is readable by other apps on your computer while the payload is on it.
• If you capture a logged-in or personal page, its content is copied. Do not paste it where you would not share it.
• Images that need another site's login cookies appear as grey placeholders.
• The Figma clipboard format is undocumented and can change.
• Page to Layers is not affiliated with Figma.

Data sharing and sale

No data is sold, shared or used for advertising. The developer receives no data.

Data retention

None. Page to Layers stores nothing, and it does not request the storage permission.

Children

Page to Layers is not directed at children.

Changes to this policy

This policy is effective from 2026-11-08. Updates are posted on this page.

Contact

Questions? Write to sarvin.shrivastava@habuild.in. For help using Page to Layers, see support.