Anonymized scenarios

Customer Stories

How law firms, corporate legal, arbitration & field compliance redact on-device

Anonymized scenario composites based on real workflows — not named-client endorsements.

Law firmGuangzhou / Shenzhen matters

Local redaction for cross-border M&A diligence packs

A South China commercial partnership firm

Client MSAs barred cloud tools; packs mixed bilingual clauses and scanned statements.

Review cycle: ~60%+ shorter
Compliance bounce: 0 on this deal
Deploy: Offline dual seats

Context

The deal team had two weeks to deliver redacted diligence summaries and contract exhibits to overseas counsel. Materials were mostly Word/PDF with scanned bank pages. The client’s NDA barred uploading originals or derivatives to any third-party system. Manual find-replace was slow and review was visual only.

What they did

Dual-device desktop licenses on two deal machines, fully offline. Mixed zh/en detection plus OCR on scans; templated pseudonyms for parties and short org names; human review focused on amounts, accounts, and addresses; PDF + mapping kept on encrypted local disks only.

What changed

Typical 60–90 page packs moved from “half a day+” to “reviewable within a couple of hours.” The team could answer the client security questionnaire with on-device processing and no outbound channel; diligence delivery was not bounced for tooling.

Diligence exportBilingualScan OCR

“They asked which cloud redactor we used. We said none — that was the answer they wanted.”— Lead counsel · M&A

Corporate legalSuzhou industrial park

Batch redaction of labor dispute archives

Legal team at an East China manufacturing group

Filings, payroll slips, and attendance screenshots — manual replace kept missing IDs.

Monthly volume: ~120–180 docs
Spot-check misses: Down vs. manual
Environment: Isolated terminal

Context

Peak months meant 100+ filings, mediation notes, and payroll copies for internal archive. Word find-replace failed on OCR scans and could not keep stable pseudonym IDs. An external spot-check once found two unmasked card numbers.

What they did

Shared desktop workstation: folder batch import; template “pseudonym names + mask IDs/accounts”; quality score for second pass; Excel column redaction for payroll. Terminal stayed off the public internet.

What changed

Peak-month batches became predictable; second-pass misses dropped vs. manual era. IT did not need a cloud tenant — fitting the group’s “classified endpoints stay offline” rule.

Batch archivePayrollQuality score

“We can live with slower — we cannot live with one leaked card number. The score panel gave the second pass a handle.”— Legal lead

ArbitrationSouthwest China

Pre-hearing evidence redaction on air-gapped seats

Case terminals for a regional arbitration commission

Evidence binders included Japanese excerpts and chat screenshots; physical disconnect required.

Network: Air-gapped
Formats: PDF + screenshots
Languages: zh / ja

Context

Before hearings, staff must produce redacted copies for the panel and clerk. Packs included Japanese clause pages, long WeChat screenshots, and stamp pages. The room policy is physical disconnect — no always-online installers.

What they did

Desktop build on air-gapped seats with egress blocked; Japanese NER set; screenshot OCR plus manual boxes; stamp/QR color masks; dual paper/PDF archive by case ID.

What changed

Passed the zero-external checklist; Japanese party names and contacts were acceptable after human review; processing notes could be retained per case ID.

Pre-hearingJapaneseAir-gapped

“Security only asks: can it still run after you pull the cable? This can.”— IT liaison

Cross-border practiceShanghai

Consistent pseudonyms across Korean correspondence packs

A Yangtze Delta foreign-related desk (coop. with overseas counsel)

Bilingual email export packs needed stable aliases without mangling clause numbers.

Alias consistency: Cross-doc
Formats: Word / PDF
Languages: zh / ko

Context

The desk redacts Korean-side letters and attachment digests before client review. Korean names, short company forms, and English emails mix in one file; brittle rules hit clause numbers; the client wanted stable aliases across the same matter.

What they did

Desktop Korean recognition plus case-batch shared pseudonym dictionary; pseudonym parties/orgs; amounts/dates by template; filterable review then layout-preserving Word export.

What changed

Alias IDs stayed consistent across letters in the matter; fewer mangled clause numbers; counsel time shifted to semantic review instead of find-replace.

Shared pseudonymsKorean NERClause fidelity

Field complianceNorth China store audits

Same-day photo capture redaction before HQ upload

Regional compliance for a consumer brand

Store paper addenda and payment chats had to be masked before leaving the site.

Use case: Same-day filing
Devices: Phone + desktop
Bounce cause: Fewer open phones

Context

Auditors photograph paper addenda, POS slips, and payment chats at stores and must file the same day. Raw album uploads leaked staff phones and full card data; waiting for the office desktop missed the cutoff.

What they did

Mobile document-scan and chat-screenshot flows; on-device OCR and color masks; system share into the work WeChat group. Complex binders still finish on desktop. Bonus Android / HarmonyOS seat from the desktop plan covers field staff.

What changed

Same-day packs stopped bouncing for plaintext phones; field staff could send a first cut without returning to the office; desktop still owns the archive version.

Document scanChat screenshotsSecure share

“It does not replace the PC — it solves “can we send this at all?” first.”— Regional compliance

Banking complianceCoastal province

Complaint attachment masking before audit handoff

Retail compliance cell at a city commercial bank

ID and bank-card images in complaint packs needed a uniform mask before transfer.

Attachments: ID / screenshots
Network: Compliance LAN
Standard: Templated masks

Context

Escalated complaint packs often attach ID photos, card photos, and SMS screenshots. Before audit or outsourced assist, policy requires masking. Past practice used image editors — uneven and hard to explain.

What they did

Desktop on the compliance network (no public net): PDF/image packs with entity detect + color masks for IDs/cards; manual boxes on SMS shots; export filed under ticket IDs.

What changed

Handoff attachments share a clearer masking standard; audits can cite “tool + human review”; outsides no longer receive full ID numbers.

ID maskingComplaint handoffPrivate LAN

Keep sensitive files on your machines — same offline core for desk and field