Privacy, plainly.
Last updated · April 30, 2026
The short version: Framely runs on your machine. Nothing leaves it. There's no analytics, no tracking, no sign-in, no upload. Captured screenshots stay where you put them.
What it accesses
- The visible area of the active tab — only when you click the toolbar icon. Pixels are captured via Chrome's
tabs.captureVisibleTab API and used to render the framed mockup in-page.
- Local browser storage — used as a temporary handoff (key
framely-screenshot) when the active page can't host the in-page overlay (for example chrome:// pages). The entry is overwritten on the next capture.
- Host access on all sites — required so the capture and overlay can work on whichever page you invoke Framely from. Framely does not read page contents beyond rendering its own overlay.
What it doesn't do
- It doesn't transmit, sell, or share any data with anyone.
- It doesn't load remote code. All scripts are bundled at publish time.
- It doesn't include analytics SDKs, error reporters, or third-party trackers.
- It doesn't ask you to sign in. There is no account.
Children
Framely isn't directed at children under 13 and doesn't knowingly collect personal information from anyone.
Changes
If this policy changes, the updated version will live at this same URL with a new "Last updated" date.
Contact
Questions or requests — open an issue at github.com/flanker/framely.