PRIVACY WITHOUT SMALL PRINT

Your working files stay with you.

RedactKit is designed so the PDF and image content you open is processed by code running in your browser.

No document uploads

The site host delivers the application files. RedactKit does not send your selected PDF or image to an application server, cloud storage or a conversion API.

No account or history

There is no login, user database or document history. Active files live in browser memory and disappear when you close or reload the workspace.

No AI inspection

No AI service reads, classifies or extracts your files. Text search uses ordinary PDF text extraction inside the browser.

No document analytics

RedactKit does not include analytics that receive filenames, document text, image pixels or extracted metadata. Normal hosting infrastructure may process basic web requests for app assets.

What secure PDF redaction means here

Every modified PDF page is rendered into a new page image with the chosen redactions already applied. The original page objects are not copied into that output page. RedactKit then reopens the export and checks that no selectable text remains on modified pages. This makes text, vector art, scans, signatures and annotations beneath a selected rectangle irrecoverable from the exported PDF page. Rasterizing a page can reduce vector sharpness, remove interactive links and forms, and does not certify that you selected every sensitive region. Unmodified pages remain as original PDF pages.

Image cleanup

Protected image exports are redrawn into a fresh JPG, PNG or WebP canvas. RedactKit re-reads the exported file and stops the download if readable location, camera, date or author metadata remains. Blur and pixelation are visual effects and can reveal shapes; use a solid mask or crop for information that must not be visible.

Closing the page clears the workspace.

RedactKit does not use LocalStorage or IndexedDB for document bytes, image pixels, previews or extracted metadata.