For insurance

Proposal and claims documents, made safe to share

Insurance moves documents between more organisations than almost any other industry: the insurer, the intermediary, a TPA, a surveyor, a hospital, a reinsurer. Every hop is a copy, and every copy carries whatever was on the original.

Talk to us about your document volume Read the docs

Talk to our technical team → — for integration questions, a security review or a volume estimate.

Mumbaiap-south-1, data stays in India
In memory onlynever written to disk
PDF, JPG, PNGup to 50 MB per document
Batchone call, many documents
Per policy volumepriced on your monthly volume

The claim file is the hard part

Proposal-stage KYC is a known document set. A claim file is not: it is whatever the claimant sends, which is why an identifier-specific approach fails on it.

Health claims

Discharge summaries, prescriptions, diagnostic reports and hospital bills, carrying patient identifiers alongside the Aadhaar used for identification.

Motor claims

Driving licence, registration certificate, FIR copies. The licence number is an identifier most redaction tools do not detect at all.

Death and maturity

Nominee KYC, bank details for payout, a cancelled cheque with the account number and IFSC printed on it.

/redact-pii is built for exactly this shape of problem: it does not need to recognise the document, only the identifiers printed on it — Aadhaar, VID, PAN, passport, voter EPIC, driving licence, GSTIN, IFSC, phone and email.

Before it leaves your building

To a TPA or surveyor. A separate organisation with separate retention. Redact first.
To a reinsurer. Often outside India. Redaction before transfer removes most of the cross-border question rather than arguing about it.
To an intermediary portal. Agents and brokers download customer documents to their own machines.
Into the archive. Policies are retained for decades; whatever is unmasked stays unmasked for all of it.

The intermediary problem

Insurance is sold through people who are not employees: agents, brokers, bancassurance partners, aggregators and POSP networks. Each of them handles customer identity documents on their own devices, and none of them is inside your security perimeter.

Onboarding a customer

The agent photographs the Aadhaar and PAN on a personal phone and uploads through a portal. The original stays in the phone's gallery indefinitely.

Portal downloads

Intermediaries download customer documents for servicing. Every download is a copy you cannot recall.

Renewal and endorsement

Documents are re-shared years later, by which point the agent may no longer represent you at all.

Mask at upload and the portal has nothing unmasked to serve back. It is the only control that works when the endpoint is a phone belonging to someone you do not employ.

Retention, and why insurance is the hard case

Policies outlive systems. A term policy issued today may be claimed against in thirty years, through two core-system migrations. Documents get carried forward each time, with whatever was on them.
Claims reopen. A closed file is not a finished file. Documents come back into circulation years later for a dispute or an ombudsman referral.
Nominees are third parties. A death claim brings in identity documents for people who never had a relationship with you and never consented to anything.
Group policies multiply everything. One corporate client is thousands of member documents arriving as a batch, usually as a spreadsheet and a folder of scans.

The batch endpoints exist for that last case: a folder in, a ZIP out, and a manifest naming every document where nothing was found.

Questions we get asked

Can it redact identifiers on medical documents?

Yes. Redaction is identifier-driven rather than document-driven, so a discharge summary or a hospital bill is handled without a parser for that form. Note it targets identity and financial identifiers, not clinical content.

Does it detect driving licence numbers?

Yes, along with voter EPIC, passport, GSTIN and IFSC. Motor claim files are the usual place a licence number sits unredacted because most tools only look for Aadhaar.

We share files with a reinsurer abroad. Does that help?

Redacting before transfer means the identifiers never cross the border. Our own processing is entirely in Mumbai.

Can we process group policy member documents in bulk?

Yes. The batch endpoints take many documents per call and return a ZIP with a manifest giving per-document status. For mixed document types use /bulk/anonymise, which does not need to know what each file is.

Our agents upload from personal phones. Does masking help?

It helps with what your systems then hold and serve back, which is the part you control. It cannot reach the copy in the agent's camera roll — no API can. Masking at upload at least means the portal has nothing unmasked to hand out again.

Talk to us about your document volume

Tell us how many documents a month you process and what your peak looks like. We will size a plan, provision a key with a test quota, and answer a security questionnaire if you need one.

Contact sales Enterprise overview