Skip to content

SecurePoint platform

One platform to screen visitors, review matches and keep the record.

The kiosk, Host Hub, screening, the review queue and the audit log work from the same visit record. When an assessor asks what happened, what the front desk saw, what screening found and who decided are in one place.

Pictured: a review screen for a held visitor, from a demo organization with fictional visitors.

An adjudication case for a demo visitor on hold at the front desk: a 91% possible match on the OFAC SDN list, a count of the details that are the same, similar, different or cannot be compared, the visitor and the demo list entry compared field by field, and the four decisions Not a Match, Approve Visit, Deny Access and Send for Senior Review.
Named sanctions and watch lists
OFAC, BIS, UN, UK, EU and more. Each list refreshes on its own schedule.
No badge until the checks clear
Pending reviews, missing NDAs and incomplete screening stop the print.
Append-only audit trail
SHA-256 hash-chained. Application users can't edit or delete it.
10-year decision records
Screening and review records can't be deleted for 10 years.
Unlimited visitor screenings
Visitor plans are priced per site.
Hosted in U.S. regions
The application runs on Vercel and the database on Supabase, both in U.S. West regions.

One visit, start to finish.

A host invites a visitor, the kiosk checks them in, a possible match waits for a reviewer, and the decisions stay on record.

The front desk sees who is on site, and who is held.

The front desk dashboard shows who is on site, who is expected and who is held for review. Visitors check in at the kiosk by QR code, ID scan or by hand, or staff check them in at the desk.

The SecurePoint front desk roster for a demo organization, with three visitors marked On hold: security review. Each row tells the desk the visitor is not checked in, not to issue a badge, and that compliance will decide.

The badge waits for the evidence.

Each site's security profile sets what a visit needs: host approval, ID capture, an NDA or safety briefing, an escort. Until those are on the visit and screening has cleared, the badge does not print.

Only a staff role allowed to override can print past a missing step, and it takes a written reason. A required escort can't be skipped that way.

A SecurePoint Visitor visit record listing what is still missing before a badge: NDA, Safety Briefing and ID Front, with Headshot and ID Back marked optional

The decisions land in the audit log.

Check-ins, host approvals, screening decisions, badge prints and check-outs go to an append-only, hash-chained audit log that application users cannot edit or delete, with a verifier that checks the chain.

Export an evidence pack for the date range and sites an assessor asks about. It exports with SHA-256 checksums.

Rows in the SecurePoint audit ledger, each with a timestamp, the action recorded and its target

What's in the platform, and how it's sold.

The core modules come with every Visitor plan. What each plan includes is on the pricing page.

SecurePoint platform modules and how each is offered
ModuleAvailabilityWhat it does
Kiosk and front deskCoreCheck-in by QR code, ID scan or by hand, at the kiosk or the desk, with host alerts by email, and by text on plans with SMS.
Host HubCoreHosts invite their own visitors and follow each visit, signing in with a password or a work Microsoft account.
Sanctions screeningCoreEach visitor, and the company they list, is checked against named lists. A possible match holds the visit for a person.
Adjudication queueCorePossible matches wait in a review queue with SLA tracking, and every decision carries a reason.
Audit logCoreAn append-only, hash-chained audit log that application users cannot edit or delete, with a verifier that checks the chain.
Evidence packsAdd-onPacks organized for CMMC Level 2, DFARS 252.204-7012 and ITAR/EAR reviews, exported with SHA-256 checksums. The CMMC Level 2 evidence pack is an add-on on every plan.
Workforce and vendor screeningAdd-onRe-screens employees, contractors and vendors on the interval you set. An add-on on Defense Front Desk, included in Enterprise Compliance.
Third-Party Integrity MonitorControlled pilotRoster reviews against restricted-party lists, enforcement sources and news. Turned on per organization, not part of every plan.
Screening APIOn approvalScreen names and companies from your own systems. SecurePoint turns it on for your organization and issues the keys.

For your security review.

Each line says whether a control is built into the product, documented, or still planned. No control is independently audited yet.

Security and procurement facts, with status
AreaStatusWhat it means
Sign-in and accessBuilt inMicrosoft Entra ID single sign-on on every plan, MFA enforced by organization policy, and role-based permissions.
Hosting and dataBuilt inThe application runs on Vercel and the database on Supabase, both in U.S. West regions. Each organization's data is separated by row-level security.
Audit trailBuilt inAppend-only audit log, SHA-256 hash-chained, with an integrity check every day.
Record retentionBuilt inScreening and review records can't be deleted for 10 years.
SubprocessorsPublishedNamed list with purposes. The AI providers that summarize screened names and read ID text at browser kiosks both run until an administrator turns them off.
Incident responseDocumentedA written runbook with named roles. Breach notification terms are in the DPA.
SOC 2 Type IINot certifiedControls are mapped to the Trust Services Criteria. The Q3 2027 target is not a commitment.
Penetration testPlannedNo third-party test has been performed yet. Internal security review is ongoing.
  • Kiosk

    Self check-in on an iPad or Android tablet, or in a browser.

  • Host Hub

    Hosts invite their own visitors and follow each visit.

  • Screening

    The lists, how matching works, and where screening stops.

  • Adjudication queue

    How reviewers work possible matches, with SLA tracking.

  • Audit logs and evidence

    The audit trail and the evidence packs an assessor receives.

  • Integrations

    What connects today, what is in development, and what is not offered.

See it with a visit you run every week.

Bring a sample visit. We'll walk through check-in, a held match, the decision and the evidence pack.

Frequently asked questions

Is visitor data separated between organizations?
Yes. Each organization's data is separated by row-level security in the database, and the organization comes from trusted server-side context rather than anything the browser supplies.
Can the audit trail be edited or deleted?
Not by application users. It's an append-only, hash-chained audit log that application users cannot edit or delete, with a verifier that checks the chain. Screening and review records can't be deleted for 10 years.
What happens if screening cannot complete?
The visit holds rather than passes. A screen that cannot run, or a possible match that has not been decided, does not become an approval by default.
Where is the data held?
The application runs on Vercel and the database on Supabase, both in U.S. West regions, and each organization's data is separated by row-level security. AI providers and messaging services are named separately on the subprocessors page.
Does SecurePoint make us compliant?
No. SecurePoint supports your compliance program: it screens visitors, records the decisions and produces the evidence. It doesn't certify your program, and it doesn't file with any agency on your behalf.