The short version: we do not see your documents.
DocRedact.in processes your file entirely in your browser tab. It never leaves your device. We have no servers that touch your document, no database that stores it, no API that analyzes it. If you disconnect from the internet after loading this page, the tool still works — because everything runs locally.
What we do collect
- Page view counts, via Cloudflare Web Analytics. This tells us which pages are visited, from which country (state-level at most), and from which referring site. No cookies. No IP addresses stored. No fingerprints. No ability to identify you.
- If you use the B2B API waitlist form: your email, company name, and use-case selection. Stored in Cloudflare Workers KV. We use it only to contact you about the API.
- If you use the contact form: your email and message. Forwarded to our inbox. We keep it as long as needed to respond to you.
What we never collect
- Your documents, or any part of them.
- OCR text extracted from your documents.
- Detection coordinates, filenames, or file sizes of what you redact.
- Cookies. Tracking pixels. Third-party trackers. Session replay.
Verify it yourself
Our full code is public on GitHub under AGPL-3.0: github.com/shadabkhan/doc-redact-in. The “no network calls during redaction” property is tested in CI. Open your browser's DevTools, go to the Network tab, and watch — you will see no requests leave your machine while you redact.
Your rights
You can request deletion of any contact or waitlist data at any time by emailing hello@docredact.in. Because we never receive your documents, there is no document data to request deletion of — there was nothing to delete to begin with.
DPDP Act framing
DocRedact.in is not a Data Fiduciary for the documents you redact, because your document contents do not traverse our infrastructure at any point. We are a Data Fiduciary for the small amount of contact information you may voluntarily submit via the waitlist or contact forms, and we handle that information as described above.
Changes to this policy are announced in the GitHub repository commit history. The “last updated” date at the top of this page reflects the latest version.