How It Works
The session lifecycle
From the moment a Host creates a session to the moment it expires, every step is designed around one principle: the verification happens, the identity does not.
The Privnote model applied to video
Privnote's genius is that it decouples the act of communication from the act of identity. You do not need an account to read a Privnote. You do not need to install anything. The link is the session. When it is gone, it is gone.
VideoVerify.Me applies this same philosophy to live video. When a Host creates a session, the platform generates a unique, encrypted URL. This URL encodes the session parameters and a cryptographic token. It does not encode anything about the Host's real identity.
videoverify.me/s/x7k2mQpLnR tells the recipient nothing except that they have been invited to a session.Step by step
Host Creates a Session
The Host logs into their VideoVerify.Me account and creates a new session. They set two parameters: the session expiry time (the window within which the Guest must join) and optionally a session label for their own reference — for example, "Rick from Hinge, Tuesday." The platform generates the encrypted URL.
Host Shares the Link
The Host pastes the URL into whatever messaging channel they are using on the dating platform. VideoVerify.Me does not need to integrate with any dating platform. It is platform-agnostic by design, which is also what makes it broadly applicable. The link looks like: videoverify.me/s/x7k2mQpLnR — opaque, unguessable, non-sequential.
Guest Joins
The Guest clicks the link before the expiry time. Their browser opens the VideoVerify.Me session page. They are prompted to allow camera and microphone access. No account creation, no sign-up, no personal information collected. The session URL is their only credential.
The Session Runs
Host and Guest are connected. They can communicate via live video and audio, or via an in-session text chat if either party prefers not to use audio. Either party can mute their microphone or disable their camera at any point. The session interface is minimal and purpose-built: no distractions, no social features, just the verification call.
Session Ends
The session ends when either party closes it, or when the Host-defined duration limit is reached. After the session ends, the URL is invalidated. If the Guest attempts to reload the page, they see a session-expired message. No video, no audio, and no chat content is retained on the platform's servers.
Expiry Without Use
If the Guest never joins before the expiry time, the URL silently expires. The Host sees the session marked as expired in their dashboard. No notification is sent to the Guest, preserving the no-identity-for-Guests principle.
In-session controls
The in-session experience is deliberately minimal. VideoVerify.Me is not trying to be a social network or a communication hub. It is a single-purpose trust instrument, and the UI reflects that.
Mute microphone
Either party can mute at any time without ending the session.
Disable camera
Either party can turn off their video feed without disconnecting.
Text chat panel
In-session text chat for those who prefer not to use audio. Clears when the session ends.
End session
Either party can end the session. The URL is immediately invalidated.
There are no reactions, no virtual backgrounds, no filters, and no other social features. These would dilute the purpose of the tool and potentially be used to obscure identity during the call.