catchroll

Security Position

Last updated: 25 July 2026

This page describes catchroll’s security position as it stands today. It is deliberately scoped to what the shipping code actually does — not to promises.

On-device by construction

catchroll has no backend. It makes no network calls, sends no telemetry, and uploads nothing. Your captures live in local browser storage and in files on your own disk. The safest place for your data is a place it never leaves — so that is where catchroll keeps it.

Redaction is destructive on purpose

When you redact part of a capture (blackout, blur, or pixelate), catchroll permanently destroys those pixels in the saved image. Redaction is not an overlay you can peel back and it is not undoable — the point of redacting is that the sensitive content is actually gone.

Redaction protects the text and the trail, not just the pixels

A capture can carry the page’s text alongside the image, and a link back to where it came from. Hiding pixels while leaving those behind would be a false sense of safety. So when you redact a capture:

  • the saved text for that capture is destroyed, and
  • the link back to the original source (its URL and title) is withheld.

The reasoning: an image redaction is only real if someone can’t recover what you hid by reading the leftover text — or by simply following a link to the un-redacted original. catchroll closes both doors.

Folder access is scoped, not broad

catchroll can connect to a folder you choose to hold your saved library. That access is granted through your browser’s own file picker and is limited to the single folder you select — not your drive, not your other files. It is mediated by the browser, and you can revoke it at any time. catchroll uses it to read and write your library locally; nothing in that folder leaves your device. It is a scoped, revocable key to one folder — not general access to your computer.

Scope and honesty

This is a position statement, not a certification. A formal, code-level security audit of catchroll is planned, and this page will be updated with its findings when it is complete. Until then, everything stated here describes shipping behavior you can verify: there is no network code to send your data anywhere.

Reporting a concern

If you find a security issue, please report it to security@catchroll.com.