What PII patterns get flagged?

Email, international phone number, IBAN, US-format SSN and UK-format NI numbers, and Luhn-valid credit-card numbers. Free-form addresses don't match a regex and need to be drawn manually — the editor's region tool is built around that being normal.

Will redaction survive someone trying to lift the original text?

Solid-block redaction at export replaces the pixels entirely — there's no underlying text to recover. PDF redaction tools often fail at this (they hide text without removing it). We're working with raster images, which makes this honest.

Does the OCR text leave my session?

The OCR call goes to Google Cloud Vision, which returns the text to us. The PII regex runs locally inside our Lambda. Neither we nor Google retain the text beyond the request lifetime.

Not directly — Blurify takes images (JPEG, PNG, WebP, HEIC/HEIF). Photograph or scan the page — or screenshot the PDF page — then redact it here and share the exported image. PDF support is on the roadmap.

Is an ID or passport photo safe to process here?

To read the text, the image goes to Google Cloud Vision for OCR — the same vision API every document here uses — and is auto-deleted within an hour; beyond that one call it reaches no other third party. The export strips metadata, and for the highest-stakes documents, Solid fill is the style that leaves nothing to reconstruct.

Redact a document online — forms, scans, IDs

Open the editor How it works

A redacted document with names, numbers and addresses hidden — Blurify result — Google Cloud Vision OCR finds the text; our local regex flags the PII.Photo · Unsplash

A redacted document with names, numbers and addresses hidden — original — Google Cloud Vision OCR finds the text; our local regex flags the PII.Photo · Unsplash

How it works for documents.

Drop the document photo or scan
Booking confirmations, ID cards, invoices, letters, forms — a photo or a flatbed scan. Anything with text that shouldn't be public.
Text + PII patterns highlighted
Google Cloud Vision DOCUMENT_TEXT_DETECTION reads every word. A local regex pack flags emails, phone numbers, IBANs, US/UK SSN/NI numbers, and Luhn-valid card numbers — those regions are pre-selected for you.
Pick a redaction style — export
Solid black block is the default (the journalism convention). Or pick gaussian / pixelate / color overlay. EXIF stripped automatically.

Questions, honestly answered.

What PII patterns get flagged?: Email, international phone number, IBAN, US-format SSN and UK-format NI numbers, and Luhn-valid credit-card numbers. Free-form addresses don't match a regex and need to be drawn manually — the editor's region tool is built around that being normal.
Will redaction survive someone trying to lift the original text?: Solid-block redaction at export replaces the pixels entirely — there's no underlying text to recover. PDF redaction tools often fail at this (they hide text without removing it). We're working with raster images, which makes this honest.
Does the OCR text leave my session?: The OCR call goes to Google Cloud Vision, which returns the text to us. The PII regex runs locally inside our Lambda. Neither we nor Google retain the text beyond the request lifetime.
Can I upload a PDF?: Not directly — Blurify takes images (JPEG, PNG, WebP, HEIC/HEIF). Photograph or scan the page — or screenshot the PDF page — then redact it here and share the exported image. PDF support is on the roadmap.
Is an ID or passport photo safe to process here?: To read the text, the image goes to Google Cloud Vision for OCR — the same vision API every document here uses — and is auto-deleted within an hour; beyond that one call it reaches no other third party. The export strips metadata, and for the highest-stakes documents, Solid fill is the style that leaves nothing to reconstruct.