Summary
- Puro does not collect, transmit, sell, or share any user data.
- No account or sign-in is required, and none exists.
- There are no ads, no analytics, and no tracking of any kind.
- The extension makes no network requests. It has no server.
- Everything — capture, editing, and export — happens locally in your browser.
- Puro is not directed to children under 13.
Information we collect
Puro collects no personal information and sends nothing off your device. It does process the following locally, only when you explicitly start a capture:
- Screenshot images — the rendered image of the page you chose to capture. Created only when you click the Puro toolbar button or press its keyboard shortcut. Stored locally in your browser's IndexedDB so the editor can open them.
- Page URL and title — read from the captured page. Used only to name the exported file and to draw the optional URL/timestamp header, which you can switch off in the editor.
Puro does not read your browsing history, form input, cookies, passwords, or page content beyond the visual screenshot you asked it to take.
How we use information
- To render the screenshot you requested and display it in the editor.
- To apply the edits you make (crop, text, highlight, blur, shapes, step badges).
- To produce the file you export as PNG, JPEG, or PDF, or copy to your clipboard.
There are no other uses. Nothing is profiled, aggregated, or analyzed.
Extension permissions
Chrome requires Puro to declare the permissions it uses. Each one is used strictly for the purpose below:
- activeTab — grants access to the current tab only at the moment you trigger a capture. Puro has no standing access to any tab.
- scripting — injects a helper script into the active tab at capture time to measure the page and, as a fallback method, scroll through it. Nothing is injected otherwise.
- debugger — the core capture mechanism. Used solely to render the full page in one pass through the DevTools protocol, which is what makes a pixel-accurate full-page screenshot possible. It is attached only for the duration of a capture you started and detached immediately afterwards. No other debugger capability is used, and no page data is read beyond the resulting image.
- clipboardWrite — used only by the editor's "Copy" button, when you click it.
Data storage and retention
- Captures are stored locally in your browser's IndexedDB, on your own computer.
- They are deleted automatically after 2 hours.
- You can remove them at any time by clearing the extension's site data, or by uninstalling Puro, which deletes all of its local storage.
- Files you export (PNG, JPEG, PDF) are saved by your browser wherever you choose and are outside Puro's control from that point on.
Security
Puro keeps everything on your device and transmits nothing, which removes most classes of risk by design. We take reasonable technical measures to reduce risk, but no method of storage is 100% secure.
Children's privacy
Puro is not directed to children under 13, and we do not knowingly collect personal information from children. Puro does not collect personal information from anyone.
Your choices
- Captures happen only when you start them — Puro never runs on its own.
- The URL and timestamp header can be turned off in the editor before you export.
- Use the blur tool to pixelate anything sensitive before exporting or sharing an image.
- Uninstalling the extension removes all locally stored captures.
Changes to this policy
We may update this policy from time to time. Material changes will be reflected by updating the effective date at the top of this page.
Contact
If you have questions about this policy, get in touch: