Security and privacy by design — for an add-on that never stands between your people and the door.
GateStride touches how people get into your building and the record of who left. This page sets out how it is built, where your data lives, what it can and cannot do on your existing system, and how to report a problem. It is written for IT managers, security leads and the integrators who advise them.

- On-site architecture
- Keys & unlock
- Offline
- No relay, your VPN
- Your existing system
- Audit
- Privacy
- Life safety
- Disclosure
Center and door nodes run in your building. No GateStride cloud.
Created in the secure element; the door sees only a signature.
Device credentials and non-biometric person detection.
Runs entirely on your premises
Every part of GateStride runs on your own site: the center in your comms room and an off-the-shelf small node at each door, connected to your access-control system with your own credentials. GateStride offers no hosted or cloud service, so no GateStride server holds your door controls, your people or your access logs. Your data stays in your building, under your network policies, backups and retention rules.
Keys never leave the phone
Each phone, watch or tablet creates its credential key inside its hardware secure element: StrongBox on Android, the Secure Enclave on iOS. The private key never leaves the device. When a phone approaches, the door node issues a single-use challenge over Bluetooth; the phone signs it; the node verifies the signature against that person’s public key and the door’s own rules. The door only ever sees a signature.
Because the decision is made at the door, the center is not in the real-time unlock path. A slowdown or outage on the center does not hold up the moment of entry.
It keeps working offline
If GateStride itself goes down, your doors don’t. Your existing access control keeps working exactly as it did before GateStride was added: cards and fobs still open doors, request-to-exit and fire release are unchanged, and the system keeps its own event log. GateStride only adds to it; it is never in the existing system’s own unlock or egress path.
Door nodes hold a cached, signed set of credentials. If the network or the center is unavailable, the door still verifies phones from that cache and refuses anything it cannot verify. When the connection returns, the node resyncs. Free egress never depends on GateStride; it stays with your certified system.
No relay: remote access goes over your own VPN
Your doors never depend on our servers, and there is no GateStride relay to break into. Many cloud access-control products route remote unlocks and admin changes through the vendor’s servers. That is convenient, but it puts one system in the middle of every customer’s doors: if it is compromised, all of them are exposed at once, and if it is down, remote control stops everywhere.
GateStride is built the other way. Each office runs its own GateStride on site, and nothing about your doors passes through GateStride’s network. When an administrator needs to manage a site from somewhere else — add a new hire, revoke a leaver, check who is still inside — they connect to that office over your company’s own VPN, under your own network policies and logins, just as they would reach any other system in the building.
- No shared target. There is no central GateStride service that could open many customers’ doors, because it does not exist.
- You control the way in. Remote access uses the VPN you choose and manage, with your own accounts, multi-factor rules and logs.
- One office at a time. A company with several offices runs GateStride at each one and manages each over the VPN, with its own who’s-inside list.
- No VPN yet? Many business routers include one. Your integrator can set it up as part of the installation.
Least privilege on your existing system
GateStride connects to your access-control software through a dedicated operator account that you or your integrator create, with only the permissions it needs to read events and call the system’s own unlock. Because it is a separate account, you can see exactly what it is allowed to do and disable it at any time.
The credentials for that account are encrypted at rest and are never returned through the interface. Operators can set and test them; nobody can read them back.
One integration account acting for many people depends on your vendor’s licence terms. Some vendors license per cardholder or per connection; we check your licence with you before you commit.
A record that can’t be quietly changed
Security-relevant events are written to a hash-chained audit log: each entry seals the one before it, so any edit, deletion or reordering of history is detectable on verification. It tells you the record has been tampered with; it does not stop someone with control of the machine from trying, which is why the center belongs in a room you control.
Privacy by default
By default GateStride identifies devices and credentials and uses non-biometric person detection for occupancy and exit tracking, so there is no biometric data to collect, store or govern. The person detection is a microwave radar presence sensor in each door node: it notices that someone is at the door and counts people passing, produces no images and cannot tell who anyone is (how radar presence works). Facial recognition is optional, off by default, and offered only where it is legally compliant and the customer chooses to enable it. If you enable it, biometric privacy laws such as Illinois’ BIPA, Texas’ CUBI and Washington’s biometric statute may apply, and compliance is your responsibility.
| Default | Optional | |
|---|---|---|
| How people are identified | Enrolled phone, watch or tablet | Facial recognition, if enabled |
| Occupancy and exits | Device credentials + non-biometric person detection | — |
| Biometric data | None | Only if you enable face; your compliance |
| Status | On | Off by default |
See the privacy notice (draft, pending legal review).
You own your data
Access logs, occupancy and attendance records are created and stored by systems running on your premises, so they are yours. You decide who in your organisation can see them, how long to keep them and when to delete them. Attendance can be exported to CSV for your own records.
Life safety
GateStride is not a life-safety system. It does not provide, certify or override free egress, request-to-exit or fire release; those stay with your certified access-control and fire systems. Installing it needs no re-wiring, no new panels and no re-certification of the life-safety path. Exit tracking and roll call help with accountability during an evacuation, but they are not a substitute for certified egress, your evacuation plan or your fire systems.
General information, not legal, privacy or life-safety advice. Requirements vary by jurisdiction; confirm with your authority having jurisdiction and your counsel.
Early access
GateStride is in early access. Kantech EntraPass is GateStride Verified, our own test program rather than a manufacturer certification; LenelS2 OnGuard and Brivo are in development; Honeywell, Software House and HID are planned. We do not claim third-party security certifications. If your security review needs more detail than this page gives, ask us.
Responsible disclosure
If you believe you have found a security vulnerability in GateStride or this website, please tell us. Email [email protected] with a description, the steps to reproduce it and the impact you expect. We will acknowledge your report, keep you updated and credit you if you wish.
- Test only against systems you own or are authorised to test. Never against a customer’s doors or data.
- Do not access, change or delete other people’s data, and do not degrade service.
- Give us reasonable time to fix the issue before making it public.
Our machine-readable contact file is at /.well-known/security.txt (RFC 9116).
Questions
- Does GateStride store our data in the cloud?
- No. The GateStride center and the door nodes run on your premises, connected to your access system with your own credentials. GateStride offers no hosted or cloud service, so access logs stay in your building.
- Can we manage GateStride when we are not in the office?
- Yes, over your company’s own VPN. GateStride runs on site and does not relay anything through its own network, so an administrator connects to the office the same way they reach other internal systems. Each office is managed separately, with its own who’s-inside list.
- Can someone copy a phone credential?
- The private key is created inside the phone’s secure element (StrongBox on Android, the Secure Enclave on iOS) and never leaves it. The door node only ever sees a signature over a one-time challenge, not the key.
- What can GateStride do on our existing access system?
- It uses one dedicated operator account that you create and own, with only the permissions it needs. Those credentials are encrypted at rest and never returned through the interface, and you can disable the account at any time.
- Does GateStride use facial recognition?
- Not by default. GateStride uses device credentials and non-biometric person detection. Facial recognition is optional, off by default, and offered only where it is legally compliant and the customer chooses to enable it; compliance then rests with the customer.
- Who owns the access logs?
- You do. The logs are created and stored on your premises by systems you operate.
- How do I report a security vulnerability?
- Email [email protected] with details and steps to reproduce. Our security.txt file is at https://gatestride.com/.well-known/security.txt.
Bring your security questions
We will walk your IT or security team through the architecture on your own system.
Kantech, EntraPass, LenelS2, OnGuard, Brivo, Honeywell, Software House, HID, Android and iOS are trademarks of their respective owners. GateStride is independent and not affiliated with or endorsed by them.