Facial verification (simulated) AES‑GCM client‑side crypto Zero-Password

Lock documents, photos, and videos to a face.

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.

Encrypt with Face

Choose any document, photo, or video. Output is a single .facelock container.

No file chosen
preview
No file chosen
Encrypted Output
    Download .facelock
    Decrypt with Face

    Use the same face photo used at enrollment to unlock the encrypted file.

    No file chosen
    No file chosen
    Decrypted Output
    Download Decrypted

    Why facial encryption?

    Face‑Locked Access

    Bind encryption keys to verified identity. Only the right face can decrypt.

    Client‑Side AES‑GCM

    Files encrypt locally in the browser using the Web Crypto API.

    Documents, Photos & Videos

    Secure PDFs, images, Videos and any binary file. Image preview after decryption.

    Phishing‑Resistant

    No passwords or OTPs in the flow—reduce credential theft exposure.

    Shareable Packages

    Download a single .fenc bundle with salt + IV + ciphertext for transport.

    Pluggable Biometric

    Swap the simulated scan for a certified face verification SDK in production.

    How it fits together

    Reference Architecture

    FAQ: FaceLock Encrypt for Documents, Photos, and Videos

    What is FaceLock Encrypt?

    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.

    How does FaceLock Encrypt work?

    • 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.

    What types of files can FaceLock Encrypt protect?

    • 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.

    Can FaceLock prevent file sharing or leaks?

    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.

    What happens if someone tries to spoof my face with a photo or video?

    FaceLock uses liveness detection to detect blinking, head movement, and depth cues. Spoof attempts with printed photos, masks, or pre-recorded videos will fail.

    Is my biometric data safe?

    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.

    Can I use FaceLock Encrypt offline?

    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.

    What happens if lighting is poor or my face changes (e.g., beard, glasses)?

    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.

    Can FaceLock Encrypt be integrated with enterprise tools?

    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.

    What are the benefits for organizations?

    • 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.