Encrypt files locally in your browser and bind access to verified identity. Only the right face can decrypt—no passwords, no OTPs.
Demo simulates face matching. Replace with Axiam's biometric SDK for production.
Choose any document, photo, or video. Output is a single
.facelock
container.
Use the same face photo used at enrollment to unlock the encrypted file.
Bind encryption keys to verified identity. Only the right face can decrypt.
Files encrypt locally in the browser using the Web Crypto API.
Secure PDFs, images, Videos and any binary file. Image preview after decryption.
No passwords or OTPs in the flow—reduce credential theft exposure.
Download a single .fenc bundle with salt + IV + ciphertext for transport.
Swap the simulated scan for a certified face verification SDK in production.
FaceLock Encrypt is a biometric encryption system that uses facial verification to lock and unlock sensitive files—whether documents, photos, or videos. It replaces passwords and keys with verified identity, ensuring only the authorized user can decrypt the content.
• Enrollment: A user creates a secure facial template (encrypted, not stored as raw image).
• Encryption: A Data Encryption Key (DEK) is generated and used to encrypt the file (AES-GCM or
similar). The DEK itself is then sealed (wrapped) with a key derived from the user’s face
template.
• Decryption: When the authorized user re-authenticates, the face-derived key unseals the DEK,
allowing file decryption.
• Documents: Word, PDF, spreadsheets, text files, etc.
• Photos/Images: JPEG, PNG, TIFF, RAW, etc.
• Videos: MP4, MOV, AVI, MKV, and more.
Any digital file can be encrypted, but FaceLock provides tailored previews and workflows for
commonly used formats.
Yes. Even if encrypted files are copied, emailed, or uploaded to the cloud, they cannot be opened without the correct face match. Unauthorized users only see ciphertext, not the original content.
FaceLock uses liveness detection to detect blinking, head movement, and depth cues. Spoof attempts with printed photos, masks, or pre-recorded videos will fail.
Absolutely. FaceLock never stores raw facial images. Instead, it creates encrypted mathematical templates. All templates are secured with end-to-end encryption and cannot be reverse-engineered back into a photo.
Yes. Once installed, FaceLock can operate offline. Files can be encrypted/decrypted without an internet connection, though centralized audit logging and enterprise policy enforcement may require connectivity.
The system adjusts for moderate changes in appearance. For poor lighting, it prompts the user to improve conditions. If recognition consistently fails, an admin recovery policy (e.g., secondary approval) can be used.
Yes. It supports integration with Active Directory, SAML, OAuth 2.0, and existing document management systems. Files can remain under enterprise compliance while adding biometric security.
• Stops data leaks by binding encryption to identity.
• Eliminates passwords, keys, and tokens for file protection.
• Provides audit trails of file access attempts.
• Works across documents, photos, and videos with the same workflow.
• Reduces IT overhead in managing cryptographic keys.