Security

Encrypted by default. Isolated by design.

Visitor management holds names, photos, IDs and citizenship answers. Here's how LobbyPulse protects them.

Encrypted at the field level

Names, emails, phone numbers, photos and IDs are encrypted with AES-256 before they reach the database, with separate keys for every customer.

Isolated per customer

Every workspace is walled off at the database level, so one customer can never see another's data.

Single sign-on only

Staff sign in with Microsoft Entra ID or Google Workspace and your MFA. LobbyPulse has no passwords to steal.

Outbound-only connector

The Edge connector never opens a port, and it only grants the doors you allow.

Tamper-evident audit log

Every sensitive action is recorded in a hash-chained log you can stream to your SIEM.

You control retention

Automatically purge ID images, photos and old visits on the schedule your policy requires.

Encryption

Personal fields are encrypted with AES-256-GCM before they are written to the database, using data keys unique to each customer. Those keys are wrapped by a master key held in a hardware security module. Searching for a returning visitor works on keyed hashes, not plaintext. Enterprise customers can bring their own key and revoke our access to their data at any time.

Isolation

Every customer has its own workspace, and the database enforces that boundary on every query, so a bug in one screen can't show another customer's visitors. Each workspace has its own address, and sign-in sessions can't be shared between workspaces.

Your doors stay yours

The LobbyPulse Edge connector runs on your network and only makes outbound connections. Your UniFi credentials never leave your building, and you decide which doors LobbyPulse may grant. The cloud can't open anything you haven't allowed.

Federal customers

LobbyPulse does not store CUI. It supports the CMMC physical protection practices for escorting visitors and keeping physical access logs, and we provide a customer responsibility matrix for your System Security Plan. GCC High workspaces are planned on Microsoft Azure Government, with production access limited to U.S. persons.

Report a vulnerability

Email [email protected]. We acknowledge reports within 3–5 business days.

Questions from your security team?

We're happy to walk through architecture, data flows and our customer responsibility matrix.