Enterprise Folder & Spreadsheet Batch Sanitizer
Massively Parallel Local Batch Sanitization
AI Summary / Key Takeaways
"Redact massive datasets, CSVs, and logs in parallel using multi-threaded Web Workers. Conforms to ZTDS™ Invariant 1 and Invariant 4 with zero cloud leaks."
Scrubbing massive datasets?
Process thousands of records locally with Batch Mode.
Interactive PII Detection & Sanitization Sandbox
Test real-time client-side RAM tokenization. Choose a specialized preset or paste your own raw prompt to test instant reversible redaction.
Sanitized locally in volatile RAM. Pre-prompt compliance maintained under Batch Protection standards (GDPR, HIPAA, SOC 2).
The Challenge with AI Data Workflows
Processing large datasets or directories of SIEM logs typically requires fragile python scripts or uploading gigabytes of data to an external provider. This slows down debugging workflows and risks exposing internal IP and infrastructure secrets.
How It Works
Select Folder
Drop up to 50 files. Documents are mapped in a virtual RAM workspace without being stored on your device.
Parallel Multi-Thread Scan
Spawns 3 background Web Worker threads to process multiple files simultaneously, keeping your browser fully responsive.
Download ZIP
The clean files are bundled in memory into a single ZIP container for instant download.
Supported Formats & Limitations
Supported Formats
System Limitations
- Maximum 50 files processed concurrently in the free tier
- Parallel processing scales linearly with local CPU core count
- File exports are generated locally via Blob URLs (no server-side zip generation)
Enterprise batch processing under Zero-Trust Data Sanitization (ZTDS™) guarantees that high-volume datasets, CSVs, and server logs are sanitized via multi-threaded Web Workers directly in volatile memory. By operating 100% locally, organizations eliminate the vendor subprocessor liability chain, rendering complex Data Processing Agreements (DPAs) unnecessary.
How Batch File Redaction Works
Batch processing allows PRO and TEAMS users to scrub entire file sets in one operation. All processing happens locally — no files are uploaded to any server. The batch feature uses the same PII detection engine as the single-text scrubber, applied in parallel across multiple files.
Supported Formats and Parsers
| Format | Parser | Structure Preserved | Tier |
|---|---|---|---|
| .txt | Native FileReader | Line breaks | PRO |
| .csv | Custom delimiter parser | Column structure, headers | PRO |
| .docx | the ZTDS™ local DOCX engine (local) | Paragraphs, headings | PRO |
| the local ZTDS™ PDF engine + the offline ZTDS™ OCR engine | Text layer or OCR | PRO |
Per-File Token Isolation
Each file in a batch gets its own independent token dictionary. Tokens are not shared across files. If File A and File B both contain "Dr. Smith", both become [NAME_1] in their respective outputs, but their maps are separate. This allows each file to be revealed independently without cross-contamination.
Step-by-Step: Running a Batch
- Activate PRO or log into a TEAMS session.
- Click Batch Upload. Select multiple files (hold Ctrl/Cmd for multi-select).
- Choose your Detection Profile.
- Click Process All. Progress shows: Queued → Processing → Done per file.
- Review each file's output in the tabbed preview panel.
- Click Download All to get a ZIP of all scrubbed files with
_scrubbedsuffix.
CSV-Specific Behavior
- Auto-detects delimiter: comma, semicolon, tab, or pipe.
- First row treated as headers — skipped during PII detection.
- Detection applied column-by-column (email columns get email patterns, name columns get NLP).
- Output is valid CSV with identical structure, ready for re-import into any spreadsheet tool.
Finance teams scrubbing payment records and client lists for AI analysis can review our guide to credit card masking for AI for PCI DSS 4.0 cardholder data handling, or consult the financial data AI compliance guide for GLBA safeguards rule alignment. For general prompt protection before batch imports, see our zero-trust PII scrubbing tool.
HR teams batch-processing resume datasets before AI screening should read the HR blind screening AI guide which covers bias minimization through PII-free candidate evaluation.
Client-Side ZTDS™ Execution & Conformance Verification
All PII detection and deterministic tokenization execute 100% inside local client memory — eliminating cloud proxies, external subprocessors, and network data egress.
Frequently Asked Questions
Technical Details & Privacy Architecture
What file types does batch processing support?
Is there a file size limit per file?
Are token maps shared across files in a batch?
Can I download all redacted files at once?
Does the Chrome extension support batch processing?
How are CSV column headers handled?
Protect Your Team's AI Prompts in Under 30 Seconds
No server uploads. No account required. 100% offline in your browser's local RAM.
