Built for sites that take security seriously.

Every crossing is an auditable record.

Plate, photo, and a short clip, encrypted, retained on your schedule, visible only to the people you authorize, and logged whenever anyone opens it.

Your gate, your data, not a surveillance network.

Some plate readers feed a shared network that pools and trades vehicle sightings across cities, which is exactly what's driving the public and legal backlash against them. GateGuardX is the opposite: a plate is matched against your own allowlist, on your site, the gate opens, and the record stays yours, retained on your schedule, visible only to the people you authorize, and never pooled into a shared network.

It's a deliberate design choice: your access data exists to run your gate, not to populate someone else's database. That keeps your exposure low, and the trust of the people who pass through your gate intact.

From critical infrastructure to privacy-sensitive communities.

• Regulated & critical infrastructure, energy, utilities, transportation, and industrial sites under compliance mandates.
• Government & defense contractors, CUI handling aligned to NIST SP 800-171, with GovCloud hosting on request.
• Privacy-sensitive communities, HOAs and residential sites that want controlled access without a surveillance network.
• Multi-site enterprises, one security policy, role-based access, and audit-ready exports across the portfolio.

The default settings cover what most procurement audits ask for.

• AES-256 at rest, TLS 1.2+ in transit
• Certificate-based device auth
• Signed firmware + secure boot
• Audit logs on every action
• Role-based access control
• Plate-data retention controls

Where is our data stored?

On-site by default, recognition and gate control run on the local edge device, and plate data stays at your site. The cloud is optional, used only for the features you enable; private-cloud and AWS GovCloud / Azure Government hosting are available on request.

Can it run without the cloud?

Yes. Plate reading and gate control run locally, so gates keep opening from a saved copy of your approved list even with no connection, and records upload once it's back. The internet is never required to open a gate. The one exception: the optional Conversational AI voice agent (beta) uses cloud-based speech processing when you turn it on, and if that's unreachable, the gate simply falls back to your keypad, intercom, or remotes.

Do you sell or share access data?

Never. A plate is matched against your own allowlist, on your site, and the record stays yours, it is never pooled into a shared vehicle-sighting network. Your access data exists to run your gate, nothing else.

Who can see plate data, and how long is it kept?

Only the people you authorize, under role-based access with MFA, and every view is logged. Retention is configurable per site, and deletion and data-subject requests run through the CCPA / GDPR DSAR workflow.

Are the cameras NDAA-compliant?

Yes, the LPR cameras supplied in our kit are NDAA-compliant. If a deployment reuses your existing cameras, we verify their NDAA status during the compatibility check, required for Section 889-covered sites. Firmware is signed with secure boot and devices authenticate with certificates, so only trusted hardware joins your network.

Can we get a DPA and your security documentation?

Yes. A DPA is available, along with our control summary and framework alignment (NIST CSF, SP 800-53 / 800-171). We'll share the full security package and work through your security questionnaire under NDA during evaluation.