Home / Security

Security and data privacy

Lenders handle Aadhaar, PAN and bank data. LendOCR is designed to keep as little of it as possible, for as short a time as possible.

Documents are not stored

On the extract, batch and read APIs, files are processed in memory and dropped. They are never written to disk or logs.

Background jobs are encrypted

Queued files are encrypted with AES-256-GCM and deleted as soon as they are processed. Results stay encrypted for 24 hours, then are erased, or sooner on request.

Aadhaar is always masked

The Aadhaar number is checked with its Verhoeff checksum and only ever returned as XXXX XXXX 1234.

API keys are hashed

We store only a keyed hash of each key, never the key itself. Keys can be limited by scope, revoked instantly and rotated without downtime.

Signed webhooks

Webhooks are signed with HMAC-SHA256 and a timestamp, carry no document data, and only go to public https addresses.

Logs without personal data

Logs and metrics record request ids, timings and counts, never document content or extracted values.

Your own servers

Banks and NBFCs that must keep data in-house can run the same software in their own data centre or cloud account.

Limits and abuse protection

Per-key rate limits and monthly quotas, file-type checks by content, size and page limits.

These controls are designed to support your obligations under the Digital Personal Data Protection Act, 2023 and UIDAI's Aadhaar guidelines. Ask us for our data processing terms.