How LiveLock Works

Works like Slack or Microsoft Teams onboarding — enter each person's work email and they receive an invite link. No IT department required.

Each person installs LiveLock on their phone or laptop. Their device is cryptographically registered — this is the "something you have" factor that AI cannot replicate.

A short video selfie, SMS confirmation, and optional PIN ties their real identity to their registered device. This is the anchor that makes the challenge words meaningful.

Only admin-approved members can send or receive verification requests. The result is a closed, verified team roster — like a corporate contact book where every entry has been identity-verified.

Examples: approving a wire transfer, granting system access, signing a contract, authorizing a personnel change. Any action that cannot be undone.

In Model A, Sarah manually opens LiveLock before the action. She selects who to verify with (e.g. Marcus, CEO) and what the action is (e.g. Wire Transfer — $180,000).

The request travels through LiveLock's encrypted channel — completely separate from email, phone, or any channel an attacker might control. A deepfake on a video call cannot intercept this.

The session is time-limited and one-time. The challenge words are generated fresh for every session and expire immediately after use.

The requester always speaks first. This lets the approver verify the requester's identity before they see or approve anything. Marcus confirms he heard the correct word.

Now Sarah verifies Marcus — confirming she is not talking to a man-in-the-middle or a deepfake impersonating her CEO. Neither party trusts the other until both rounds are complete.

The session is cryptographically signed with both parties' device keys and a timestamp. This creates a tamper-evident record that both parties were present and consented.

With both identities confirmed, Sarah can now send the wire, grant the access, or sign the document — with full confidence she spoke to the real Marcus.

The log records: who verified, who approved, what action was authorized, what challenge words were used, the exact timestamp, and both device IDs. This is your compliance and forensic record.