IDSENTRA™
Request a consultation
Architecture & trust boundaries

Separate the public surface, operational authority, and commercial control plane.

IDSENTRA is designed so identity and case operations remain in the protected operational boundary while licensing and release management remain commercially separate. The public website sits outside both.

Review security & trustDeployment model
Three authority zones

Clear ownership reduces accidental data crossover.

01

Public website

Low-trust product education, evaluation resources, trust documentation, and contact conversion. No operational authority.

02

IDSENTRA-CORE

Protected operational authority for verification, watchlists, alerts, cases, evidence, occupancy, reporting, users, settings, and regulated integrations.

03

IDSENTRA-DISTRO

Commercial control plane for customers, sites, deployment identity, signed licensing, entitlements, releases, activation, and privacy-minimized fleet health.

Operational flow

Identity events become controlled, auditable response.

  1. 01Verify identity
  2. 02Screen intelligence
  3. 03Assess match
  4. 04Coordinate response
  5. 05Preserve evidence
  6. 06Report & audit
Data rule

Operational patron data does not belong in distribution telemetry.

Deployment health is intentionally privacy-minimized. Patron searches, self-exclusion records, SSNs, dates of birth, contact data, images, PDFs, passwords, tokens, cookies, provider payloads, and other operational PII are outside the IDSENTRA-DISTRO telemetry contract.

Open enterprise evaluation guide →