Clarity at every
trust boundary.

Presence is the unified 4SI environment for identity, physical Keys, objects, products, access, partners and trust operations. This Private Beta demonstrates the intended experience without claiming a production verification result.

Presence is invitation-only. On the first visit, open the one-time activation link issued by an authorized administrator and create a passkey on your device. On later visits, use that passkey from the Presence sign-in page.

Start in the Personal Trust Center. The recommended-next-step card guides identity, Key, recovery and privacy setup. Use the workspace switcher to explore enterprise, issuer, partner, developer, assurance and internal operations views.

Not in the current protected deployment. Account entry uses an invited, origin-bound passkey. Object-assisted entry and Presence Key authentication remain separate planned access methods until their controls have been validated for production use.

The Beta treats other enrolled objects as hard negatives. Presence isolates and size-normalizes the object, creates compact local pattern codes, accumulates evidence across clear live frames and requires the target to beat the closest saved lookalike by a safety margin. Enroll every similar object and capture its most distinctive patterned sides for the strongest test.

The Key is the person-facing physical trust reference. The Layer binds trust to a real object. The Suite translates a verified event into permit, deny, record or escalation decisions in connected systems.

Yes. Open any item in Personal → Scan history to go directly to its saved object. From there you can test recognition, add views, return to the object library or delete the object and its local images.

It is a real protected account for the private Presence environment, but it does not by itself establish a regulated identity, certified verification result or entitlement outside the explicitly authorized workspace.

Identity, session and account records used by the connected deployment are stored server-side under access controls. Some interface preferences and prototype records may remain in the browser. Individual modules identify their own data boundary, and users should not enter sensitive data unless the relevant workflow explicitly permits it.

No. Workspace switching only changes the interface. A production deployment must enforce tenant, role, purpose, environment and retention boundaries on the server.

Open the account menu and choose Reset Beta data. This clears locally created records and restores the included Beta account.

Aster is the guide inside Presence. It explains 4SI concepts and navigation from a bounded knowledge base. When Gemini is configured, responses are AI-generated and visibly labeled.

No. Aster cannot authenticate a person or object, approve access, determine compliance or replace qualified legal, security or professional advice.

Do not enter passwords, API keys, biometric data, government identifiers, health information, payment data, confidential business information or other sensitive material.