Social Security Numbers
Encrypted Social Security Number Input
SSNs are the most targeted personal identifier. SmartField encrypts 9-digit SSNs with AES-256-GCM, enforces format validation, and blocks all extraction attempts.
The Problem
Social Security Numbers entered in a standard HTML input are immediately accessible to any JavaScript on the page:
// Any script, extension, or tracker:
document.querySelector('input').value
// Your social security numbers in plaintext
The Solution
<smart-field type="password" encrypt-key="/api/sf-key"
placeholder="Enter social security numbers"></smart-field>
Now the same attack returns AES-256-GCM encrypted data. The social security numbers never exist as plaintext in the browser.
What the User Sees
The user types normally. The screen shows animated cipher characters: ΣΩΔψξλμπ
The real social security numbers are stored in a WeakMap (invisible to JavaScript) and encrypted with AES-256-GCM (unreadable without the server key).
Server-Side Decryption
// Node.js
const sf = require('@smartfield-dev/server');
await sf.init();
const data = await sf.decrypt(req.body.field);
// Your social security numbers in plaintext, server-side only
Frequently Asked Questions
How does SmartField encrypt social security numbers?+
SmartField generates a new AES-256 key and IV for every encryption. Social Security Numbers are encrypted before they exist in the DOM. The AES key is wrapped with RSA-2048. Only your server can decrypt.
Can trackers like Hotjar capture social security numbers?+
No. Hotjar records DOM content. SmartField stores social security numbers in a WeakMap inside a closed Shadow DOM. Hotjar only captures cipher characters.
What server languages are supported?+
SmartField provides SDKs for Node.js, Python, Java, Go, PHP, and Ruby. All tested and verified.
Related Pages