Don’t trust us. Check.
Redaktix removes sensitive data from PDFs and images inside your browser. Your files are never uploaded. That’s a claim, so here are three ways to test it yourself, easiest first. None needs technical skill, and each takes a few minutes.
1. Airplane-mode test
If Redaktix needs no internet to work, it can’t be sending your file anywhere while you use it.
- Open any Redaktix tool and leave it open for about 30 seconds on your first visit. The app is saving itself, including its text-recognition engine, to your device.
- Turn on airplane mode or disconnect from Wi-Fi. (On a computer you can also use DevTools: Network tab, then set “No throttling” to Offline.)
- Reload the page. It should still open, served from your device.
- Add your fake document, review the detected items, and export. It should work exactly as before.
Phone instructions
iPhone/iPad: in Safari, tap Share, then Add to Home Screen. Open it from there once while online, then switch on airplane mode and open it again.
Android: in Chrome, open the menu and choose Install app. Open it once online, then switch on airplane mode and open it again.
What this proves: processing doesn’t depend on a server. What it doesn’t: it says nothing about what happens while you’re online. Test 2 covers that.
2. Network-tab test
Your browser records every network request a page makes. Watch it while Redaktix processes a file, and you’ll see for yourself that your document isn’t in any of them.
- For a clean result, open a private/incognito window. Browser extensions are usually off there, and they can make their own requests that would muddy the test.
- Go to a Redaktix tool, then open DevTools: F12 or Ctrl+Shift+I on Windows/Linux, Cmd+Option+I on Mac. Click the Network tab.
- Tick Preserve log, make sure the filter is set to All, then click the clear button (the circle with a line through it) so the list starts empty.
- Add your fake document, run detection, edit the boxes, and export.
- Read the list. No request should carry your document. The app’s own files may appear: entries marked
(service worker)or(memory cache), and, on a first visit, same-origin requests under/assets/ocr/that fetch the text-recognition engine and language data. - To be thorough, type
method:POSTin the filter box. An upload would show up here. The list should be empty. Then check the summary at the bottom of the panel: it should show very little or nothing transferred. - If anything does appear, click it. The Headers tab shows where it went, Payload shows what was sent, and Initiator shows which code sent it.
Want to go further? A network monitor such as Wireshark or Little Snitch sees traffic outside the browser too.
3. Security policy and architecture
The browser enforces our promise
A Content Security Policy (CSP) is a rule list our host sends with each page. The browser, not us, enforces it. Our policy tells the browser it may only talk to Redaktix itself, so even a bug or compromised script on the page couldn’t post your file to another site.
| Directive | Plain meaning |
|---|---|
default-src 'self' | Load nothing from other sites unless a rule below allows it. |
connect-src 'self' | The page can only make requests back to redaktix.com. This is the rule that blocks uploads to anywhere else. |
script-src 'self' 'wasm-unsafe-eval' | Only our own scripts run, plus WebAssembly, which our text recognition needs. |
worker-src 'self' blob: | Processing runs in background workers we ship. |
form-action 'none' | No form on the page can post data anywhere. |
object-src 'none' | No plugins or embedded objects. |
The table is a summary. Here is what your browser actually receives right now:
Choose a page and press the button. This makes one request to our own site, for headers only.
What happens to your file
- You choose a file. It’s read into your browser’s memory. No request is made.
- Pages are drawn on a canvas, a drawing surface inside your browser.
- Text recognition (OCR) runs as WebAssembly in a background worker on your device.
- Detectors flag candidates: SSN-shaped numbers checked against the official validity rules, routing numbers checked against the ABA checksum, and card numbers checked with the Luhn checksum.
- You review every box. Nothing is final until you approve it.
- Export burns the redactions into the page pixels. The exported file contains images of the pages, so there is no hidden text underneath the black boxes. Original metadata is not carried over.
- The download is created on your device and handed to your browser’s download manager. Clear session in the export panel drops the image and the recognized text from memory; closing the tab also discards them.
Because export flattens each page, the result is no longer searchable. That is the trade for being unrecoverable.
What this doesn’t prove
- It can’t detect a compromised device or a malicious browser extension. Use a private window as described above.
- You’re trusting the code we ship. The footer shows the exact build you’re running, so an unexpected change is visible, and the policy above limits what any script on the page can talk to.
- Automatic detection can miss things, especially on blurry scans or handwriting. Always look over the result before you share it.
Found a way to make Redaktix leak data? Please contact us before disclosing it publicly.