Security & Permissions

Every permission Rendry asks for, in plain English — and exactly what leaves your machine. (Spoiler: your captures never do.)

The short version

Rendry can only see a page when you click its icon or press the keyboard shortcut on that page. It has no access to your other tabs, your history, or anything in the background. Every capture — including redaction and text extraction — is processed on your own device, on the free tier and Pro alike.

The only network request Rendry ever makes is the Pro license check via ExtensionPay: your email (if you've signed up) and your subscription status. Never your pages, captures, or browsing data.

Why this is different

Most screenshot extensions request broad host access, which makes Chrome show this warning at install: "Read and change all your data on all websites." An extension with that access can technically see every page you visit, all the time.

Rendry uses activeTab instead — permission for one page, at the moment you click. It structurally cannot read pages you didn't click on. This isn't a promise you have to trust; it's a limit Chrome itself enforces, and you can verify it on our Chrome Web Store listing under "Privacy practices".

Every permission, explained

Permission	Why Rendry needs it	What is sent anywhere
`activeTab`	Lets Rendry see the current page — only when you click the icon or use the keyboard shortcut. No background access to any tab, ever.	Nothing. The page is read on your device.
`scripting`	Runs the capture routine on the page you clicked: scrolling it, measuring it, and hiding cookie banners for a clean shot.	Nothing. Runs entirely in your browser.
`downloads`	Saves the finished screenshot or PDF to your Downloads folder.	Nothing. The file goes straight to your disk.
`storage`	Remembers your preferences (format, toggles) and caches your license status so Rendry doesn't have to check it constantly.	Nothing. Preferences sync only through your own Chrome profile if you're signed into Chrome.
`offscreen`	Assembles the page segments into one finished image in a hidden page instead of a visible tab. Required by modern Chrome for image work.	Nothing. Image assembly happens on your device.
`clipboardWrite`	Copies a capture to your clipboard — only when you've turned on "Copy to clipboard" or click Copy in the editor. Never on its own.	Nothing. Clipboard stays on your machine.

What Rendry will never request

<all_urls> or any host permissions — the "all your data on all websites" access
cookies, history, or webNavigation
Access to your bookmarks, passwords, or other browsing data

The one thing that does use the network

Rendry Pro subscriptions are handled by ExtensionPay with payments processed by Stripe. The license check sends your email address (if you've signed up for Pro or the trial) and receives your subscription status back. That's the complete list — no capture data, no page content, no URLs, no analytics, no telemetry.

Verify it yourself

Chrome Web Store listing — see the declared permissions and privacy practices Google displays for Rendry
Privacy policy — the full policy, including data storage and third-party services
Public issue tracker — bug reports and answers, in the open
Changelog — every release, documented

Questions

Security question we haven't answered here? Email support@rendry.app — we'd rather over-explain than leave you guessing.