Private Keys
Encrypted Private Key Input Field
Crypto private keys entered in web forms are the highest-value target. SmartField encrypts them with AES-256-GCM + RSA-2048. Zero exposure to JavaScript, clipboard, or screen capture.
The Problem
Private Keys 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 private keys in plaintext
The Solution
<smart-field type="password" encrypt-key="/api/sf-key"
placeholder="Enter private keys"></smart-field>
Now the same attack returns AES-256-GCM encrypted data. The private keys never exist as plaintext in the browser.
What the User Sees
The user types normally. The screen shows animated cipher characters: ΣΩΔψξλμπ
The real private keys 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 private keys in plaintext, server-side only
Frequently Asked Questions
How does SmartField encrypt private keys?+
SmartField generates a new AES-256 key and IV for every encryption. Private Keys 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 private keys?+
No. Hotjar records DOM content. SmartField stores private keys 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