Features

Aadhaar masking features.
And what's next.

30 capabilities, each labelled so you know what works today, what's available on request, and what's still planned.

Available 20 On request 2 Planned 7
29 features

Deployment

Where it runs, and how it reaches your documents.

4
Available

Inside DocVault

Built into DocVault document management. It can mask files automatically in chosen folders, at upload, as a workflow step, or as a bulk job over existing files.

On request

On your own servers

Run the engine as a container in your data centre or cloud, so images never leave your network. It runs on ordinary CPUs; no GPU is needed.

Plan on a server with at least 8 GB of memory.
Available

Bulk masking of archives

Inside DocVault, bulk jobs mask whole folders of files you already hold, including every stored version, and report each skipped file with the reason.

Available

Free online trial

Walk through the API flow your systems would use, on your own card, with no sign-up: a key, an upload, the status and the masked result, with access rules applied.

The masking engine

What happens to an image, and what it hides.

8
Available

First 8 digits hidden, last 4 kept

The first eight digits of the Aadhaar number are covered with a solid block. The last four stay readable, in the format of a masked Aadhaar.

Available

QR code masked

The QR code on the card carries personal details too, so it is found and covered completely.

Available

Card detection

A trained vision model finds the Aadhaar card in the image, including a card that is part of a larger photo or scan.

Available

Number recognition

Two text-recognition engines read the card and pick out the 12-digit number, printed horizontally or vertically.

Available

Rotation and skew correction

Sideways, upside-down and tilted photos are straightened before they are read.

Available

Already-masked cards left alone

A card that already shows a masked number is recognised and not masked a second time.

Available

No card, no change

An image with no Aadhaar number comes back byte-for-byte unchanged, and you're told so.

Available

Same format back

A JPEG comes back as a JPEG and a PNG as a PNG, with the rest of the image untouched.

Files

What you can send.

3
Available

JPG and PNG

Phone photos and scans, checked by their real content, not their name.

File size and resolution caps are set for your deployment.
On request

TIFF and PDF

The engine also handles TIFF images and PDF documents, page by page, when you run it yourself or inside DocVault.

A masked PDF page becomes an image, so its text can no longer be selected.
Available

Safe file handling

Empty, truncated and damaged files, and files pretending to be images, are refused before processing.

Privacy

What happens to your data.

4
Available

No image storage

Your image is held in memory only, never saved to disk or a database.

Available

Single-use results

Each masked result is released once, to the request that made it, then erased. Uncollected results are erased automatically after the time you set.

Available

No numbers or names stored

We never store the Aadhaar number (not even the last four), your file name, or anything read from the card.

Available

Audit log

Every request is logged with its time, source, file type and size, and outcome, never the image or anything read from it.

Service and API

How applications and people use it.

4
Available

Request–status–download API

Send an image, check its status, and collect the masked copy once, with a clear result: masked, no Aadhaar found, or a reason it was refused.

Available

Configurable access rules

Set the rules for your deployment: key expiry, images per key, requests per client in a time window, file size and resolution caps, and how long uncollected results are kept. Keys are tied to the client that requested them, and only a one-way hash of each key is stored.

Available

Queue with honest waits

A bounded queue in front of the engine. Callers see their place in line, and a full queue answers with how long to wait.

Available

No GPU needed

Runs on ordinary CPU servers. Tested on CPU-only hardware: an Intel Core i7 machine (4 cores, 8 threads, 32 GB of memory) and a 2-vCPU, 8 GB cloud server.

On the roadmap

Not available yet. Tell us which ones matter to you.

7
Planned

PDF and TIFF online

Multi-page PDFs and TIFFs through the online service, not only when self-hosted.

Planned

Production API accounts

Your own API credentials, higher limits, usage reporting and an SLA for your apps.

Planned

Batch masking

Send many images in one request and collect the results together.

Planned

Result notifications

A callback to your system when a result is ready, instead of checking its status.

Planned

Second-pass check

An extra check on every masked image, which flags any image where a full number might still be readable.

Planned

GPU-accelerated hosting

Faster masking on GPU servers for high volumes.

Planned

More document types

Exploring masking for other Indian ID documents.

Exploring, not committed.
See it on your documents

The fastest way
to understand it.

Book a demo on your own documents, or ask our sales team about pricing.