HolySnap Privacy Policy

Last updated: October 5, 2026

HolySnap ("HolySnap", "we", "us") is a Chrome extension that captures webpages as images. This policy explains what data the extension handles and where it goes. Contact: hello@holysnap.app.

Summary

  • Your screenshots, the pages you capture and their URLs never leave your device.
  • There is no account, no sign-in, no analytics and no tracking.
  • To check HolySnap Pro and count free captures, the extension sends only a random, anonymous activation code to our license server.
  • If you restore a purchase, the email you type is used once to find your purchase and send you a code — it is not stored.
  • Payments are handled by Paddle, our reseller and merchant of record.

Data processed only on your device

When you start a capture, HolySnap reads the visible pixels and layout of the tab you chose in order to scroll it, stitch it and encode the image. Captures, their file names, sizes, capture times and the site domain are stored in the extension's local storage (IndexedDB) in your browser so you can preview them and find them in the gallery. You can delete any capture from the gallery at any time; uninstalling the extension removes all of them.

This data is never uploaded, synced or shared. Nothing is downloaded or copied to the clipboard unless you click Download PNG, export a PDF or click Copy PNG. Clipboard access is requested only when you first click Copy PNG.

Activation code and license server

On first use the extension generates a random activation code (for example HS-XXXXX-…). It contains no personal information and is not derived from your device, browser or identity. It is stored locally and shown in Settings so you can restore Pro after reinstalling or on another computer.

When you start a Full page or A–B range capture, open HolySnap, start a checkout or restore a purchase, the extension may send this activation code to our license server (multipay-auth-worker.timori.workers.dev, hosted on Cloudflare). The server stores only:

No page content, URLs, screenshots, browsing history or device information is sent. Like any web server, Cloudflare processes the request's IP address to deliver it; we do not store or use it.

Restoring a purchase

If you reinstall HolySnap or move to another computer, you can restore Pro with the email you used at checkout. Only when you do this, the extension sends that email address and your activation code to our restore service at holysnap.app (hosted on Cloudflare). The service looks up completed HolySnap purchases for that email with Paddle and, if one exists, emails you a 6-digit code through our email provider Resend (resend.com) from mail.holysnap.app. Entering the code switches this installation to your purchase.

We don't store the email address. The pending code is kept, hashed, for up to 15 minutes, and one-way hashes of the email and of your IP address are kept for up to one hour to limit repeated requests. Whether or not the email has a purchase, the extension shows the same message.

Payments

If you buy HolySnap Pro, the extension opens our checkout page at pay.exportlab.pro, where Paddle (paddle.com) processes the payment as merchant of record. Paddle collects your payment details, email address and billing country to process the order, calculate tax and send receipts, under Paddle's own privacy policy (https://www.paddle.com/legal/privacy). We do not receive or store your card details. Paddle tells our server which activation code was paid for, and we receive order details (such as your email) through Paddle only to support your purchase, handle refunds and answer your requests.

What we don't do

We do not sell or rent data, use it for advertising or credit decisions, or use it for anything other than providing HolySnap and its Pro license. HolySnap contains no AI features and sends nothing to AI services.

Retention and your choices

Children

HolySnap is not directed to children under 13 and we do not knowingly collect their data.

Changes

We will update this page if the extension's data handling changes, and change the date above.