Zeroth Technology, Inc.

Verify who you're really talking to — biometric verification of the person inside your video call.

Vero helps you verify that the person in your video call is live and present. Click the Vero icon on your meeting tab, select the person to verify, and ask them to join from the free Vero iPhone app. Their phone displays a one-time light pattern. Vero reads that pattern from the meeting video and checks the face and signed session response. Works with browser-based calls such as Zoom Web, Google Meet and Microsoft Teams. Face analysis runs locally in your browser. Nothing runs until you click the icon. No account or enrollment is required. Privacy and optional Testing Testing and High Data both start off. Standard-session face data is transient. High Data alone shares the presenter's image and detailed scan directly with the verifier for that session and does not save those artifacts in Firebase. The verifier can request Testing, which automatically turns on High Data. Before collection, the presenter signs consent for 1 hour, 1 day or 1 week. Consent can cover Testing sessions they join with the same signing key during that period, including sessions with other verifiers. Every session still needs fresh private authorization. Consent does not collect between sessions. Testing can save video of the selected meeting region, face images, detailed scans and diagnostic logs in Zeroth Attest's Firebase storage for debugging, testing and improving Vero detection. The selected region can include other people or visible content. The exact signed consent, public signing key, disclosure versions and dates are published as a public EAS attestation on Base. Anyone can retrieve and link that consent activity. No video, image, scan, recording identifier, session identifier, name or email is included in that attestation. Public consent history remains permanently after expiry, withdrawal or deletion of private training data. Collection stays off until publication confirms. Expiry or withdrawal stops future collection and pending uploads. In iOS Settings, the presenter can inspect and withdraw consent and delete saved private training data using the same signing key. Local stopping, service withdrawal and public revocation are shown separately; public revocation can remain pending. Private deletion does not erase public EAS history. Retained private data follows the privacy policy's retention schedule and can be deleted earlier through Settings. Minimal hashed-key controls prevent delayed uploads from restoring deleted data. Vero is a patent-pending protocol by Zeroth Attest, Inc. Learn more: https://vero.technology Privacy and Testing terms: https://vero.technology/privacy#testing-mode