Bounds

• 

• 

• 

  Homepage

💡 Inspiration

On 27 March, the European Commission confirmed a breach. 350 gigabytes. Confidential documents. Contracts. Cloud infrastructure. The files were on a server. That was enough.

In Switzerland, a data breach doesn't just fine your company. It fines you up to CHF 250,000, personally.

Bounds has no server. Nothing to breach.

🔒 GoCalma's challenge | AI-Powered Privacy Redaction: Own Your Data

Why Bounds

• Data that stays in bounds — nothing crosses the boundary of your device. The whole product promise is that your files never go "out of bounds" to a server.
• Setting bounds on what's visible — redaction is literally drawing a box (a bound) around sensitive information and limiting what can be seen.

What it does

• ✈️ Fully offline — works in airplane mode after first load
• 🧠 Hybrid AI detection — multilingual BERT NER + 40+ regex patterns, all local
• 🔍 Auto-detects PII — names, addresses, IBANs, SSNs, emails, phones, passports, DOB, health data, credit cards
• 🌍 8 UI + document languages — EN, DE, FR, IT, ES, PT, NL, PL
• 📷 OCR for scanned PDFs — Tesseract.js with spatial word reconstruction for form layouts
• 👤 Face detection — universal browser face detection with TinyFaceDetector fallback
• ⬛ True redaction — pages rasterised to image, original text layer removed entirely
• 🗝️ Reversible encryption — AES-256-GCM vault + .key file, restore original values any time
• 📋 Audit trail — timestamped JSON report, no document content included
• 📦 Batch processing — drop multiple PDFs, processed sequentially with default options

GenAI Integration

The Problem: Organisations want to use ChatGPT, Claude, or custom LLMs to analyse documents but sending unredacted files violates GDPR/HIPAA and exposes data to training pipelines.

The Solution: Bounds sits upstream of GenAI workflows:

Sensitive PDF → Bounds (local redaction) → Redacted PDF → Safe to send to: ├─ AI provider for summarisation ├─ Custom RAG pipelines └─ Your platform

Generative AI components running entirely in the browser:

• BERT multilingual NER (430MB ONNX) — discriminative AI for named entity detection across 104 languages
• LaMini-Flan-T5-77M (77MB) — generative AI produces plain-language privacy risk summaries: "This document contains 3 names, 2 addresses and 1 IBAN. Risk level: High."

🏗️ How I Built It

The entire pipeline runs in WebAssembly inside the browser. No backend, no server, no environment variables.

Architecture:

• @xenova/transformers — quantised multilingual BERT NER (~430MB ONNX) in Web Worker, cached in IndexedDB after first download
• tesseract.js — OCR for scanned PDFs with spatial row reconstruction to handle two-column form layouts
• pdfjs-dist — text extraction with precise bounding boxes
• pdf-lib — rasterises redacted pages to PNG, rebuilds clean PDF with no text layer
• Web Crypto API — AES-256-GCM reversible encryption vault, no library needed
• React 18 + Tailwind + Vite — 4-step wizard UI
• Deployed as fully static site on Vercel

Hybrid detection: regex runs in parallel with NER for structured identifiers (IBANs, credit cards, passports, phone numbers) with deduplication between layers. 40+ regex rules with per-pattern confidence thresholds and label-context lookbehind for form-style documents.

🚧 Challenges I Ran Into

• WASM + SharedArrayBuffer: Requires both Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Embedder-Policy: require-corp headers. Easy to miss, hard to debug when it fails silently.
• Bounding box alignment: Mapping pdfjs extraction coordinates to pdf-lib render coordinates required careful calibration across different PDF structures.
• OCR form layout: Two-column forms get read column-by-column by Tesseract, so "Emergency contact:" and "Jean Dubois" end up 20 lines apart in the text stream, breaking label-context regex. Fixed by reconstructing reading order from word bounding box positions.
• Progressive loading: Fitting a 430MB model into a UX that doesn't feel broken required progressive loading states, a network request transparency panel, and IndexedDB caching so the download only happens once.
• Face detection cross-browser: Chrome's Shape Detection API requires an experimental flag. Replaced with a universal fallback using TinyFaceDetector via ONNX, so face blurring works in all browsers without flags.

Built With

• api
• crypto
• pdf-lib
• pdfjs-dist
• react
• tailwind
• tesseract.js
• vercel
• vite
• web