How Client-Side Security Works

Technical explanation of client-side WebAssembly, HTML5 Canvas, and PDF.js in-memory processing. Learn why your government ID never touches a remote server on AadharHub.

How Client-Side Security Works

Why WebAssembly, HTML5 Canvas, and client-side cryptography guarantee that your Aadhaar and government cards never leave your device.

1. In-Memory File Read

When you select a PDF, the HTML5 File API loads the document directly into your browser’s volatile RAM as a local ArrayBuffer.

2. In-Browser WASM Engine

PDF rendering, cropping, and decryption are executed locally using PDF-lib and Canvas. No API endpoints receive your data.

3. Direct Blob Export

The formatted 300 DPI PDF is generated directly as a client-side Blob URL and downloaded to your hard drive.

AadharHub vs. Traditional Cloud Converters

AadharHub: never uploads to a server (0% uploads), zero database logging of your Aadhaar number, works offline after load, and processes instantly with no upload wait. Generic cloud tools: upload 100% of your file to the cloud, store data in temp files, fail without a server connection, and are slow because they require upload and download.

Verify for Yourself: The F12 Network Test

You do not have to take our word for it. Press F12 (or right click and Inspect) in Chrome, Edge, or Firefox, open the Network tab and select the Fetch/XHR filter, then upload your e-Aadhaar or PAN PDF and crop it. Result: zero outbound POST or upload requests are made. The entire conversion happens locally in your browser memory.

AadharHub is an independent web utility and is NOT affiliated with, endorsed by, or sponsored by the Unique Identification Authority of India (UIDAI), Ministry of Electronics & IT (MeitY), or the Government of India. "Aadhaar" is a registered trademark of UIDAI. All document operations occur strictly client-side in your local browser — no file is ever uploaded to a server.