Headquarters
7150 Columbia Gateway Drive, Suite L, Columbia, MD 21046
New York Location
112 West 34th Street, 18th Floor, Room 18025, New York, NY 10001
Proud Member
A digital visitor badge system prints very little: usually a name, who the visitor is there to see, the date, and a code that a turnstile or a guard can check. Depending on configuration, it can store considerably more: fields read from an ID, a photograph, a signature and visit timestamps. Scanning a document does not by itself establish that its image is retained. What it deletes depends on how the building configures the system, what the vendor's controls allow, how backups are handled, and what the building is required to keep. This covers what lands on the badge, what sits behind it, how long it stays, which laws put a deadline on that, and what a building should be able to erase when someone asks.
The badge is the smallest part of the system. It exists to answer one question for anyone who looks at it: should this person be standing here right now.
That usually takes four things. The visitor's name. The host or company they are visiting. The date, and sometimes an expiry time, so a badge from last Tuesday is obviously not valid today. And a scannable code, a QR or barcode, that a turnstile or a guard can verify against the live record. Navigo issues these as printed or digital badges at check-in, so a visitor can carry the credential on a phone instead of a clip.
What goes on the badge is a design decision with a privacy consequence, because a badge is worn in public for several hours. A photograph makes a badge harder to pass to someone else and also makes the wearer identifiable to every person they pass. A suite number tells a visitor where to go and tells anyone else which tenant they are visiting. Neither is wrong. Both should be chosen on purpose rather than inherited from a template.
Everything else, and this is the part buildings underestimate.
The three sets are different sizes, and the gap between them is the whole subject:
Data | On the printed badge | In the stored record | Retention or deletion considerations |
|---|---|---|---|
Visitor name | Yes | Yes | Subject to retention duties |
Host or company visited | Yes | Yes | Subject to retention duties |
Date, and often an expiry time | Yes | Yes | Subject to retention duties |
QR or barcode credential | Yes | Yes, tied to the visit | Validity expires with the visit; whether the record is kept is a separate configuration question |
Photograph | Optional, a design choice | Yes, where photo capture is on | Confirm with the vendor |
Fields read from an ID or passport | No | Depends on configuration | Confirm with the vendor |
Digital signature on an NDA or acknowledgement | No | Yes, where signing is in the workflow | Often preserved as the agreement |
Entry and exit timestamps | No | Yes, searchable afterward | Subject to retention duties |
User-defined fields the building added | Only if configured | Yes | Set by the building |
Depending on how the lobby is configured, a visit can generate:
The badge shows a name. The record behind it can hold identity data taken from a government document, a photograph, a signed agreement and the times of arrival and departure. Whether a system keeps the document image itself or only the fields read from it, and whether every check-in produces a timestamped history, depend on configuration and are worth asking about directly. Those are different categories of data with different obligations attached, and a configured lobby workflow can collect several of them during one check-in.
Longer than most people assume, and the vendor's answer is not the same as the building's answer.
On the Navigo side, routine backups hold up to three years of historical data. That is a useful number to know, and it is worth being precise about what it describes: it is how far back the system's own backups can reach, not a statement that any particular record sits in a backup for three years, and not a retention policy a building has chosen. Those are different things, and conflating them is how buildings end up holding visitor records nobody decided to keep. What the backup rotation actually writes, keeps and overwrites is a question to put to the vendor alongside the deletion questions further down.
The building's retention question is separate and has to be answered by the building. How long does a visitor log need to stay useful? For a compliance-driven site, the answer follows the regulation that drives it. Elsewhere, keeping less for less time is a data-minimization choice rather than a rule, and it has to be set against what the building may need later: an incident review, a litigation hold, an audit, a lease or tenant requirement, and anything applicable law obliges it to retain.
Ask the question in that order. Decide what the building needs, then configure to it. A system holding three years of records because nobody set a shorter schedule is not a policy.
It depends on what was captured, and the sharpest rules apply to biometrics rather than to ordinary visitor logs.
Two things are worth holding onto before the statutes, because they do most of the work. An ordinary visitor log and a biometric record are not governed by the same rules. And which duties apply turns on what is collected and how it is processed, not on what the system is called. The detail below follows from those two ideas.
Under the Illinois Biometric Information Privacy Act, a private entity holding biometric identifiers or biometric information must make a written retention and destruction policy publicly available and destroy that data when the purpose for collecting it has been satisfied, or within three years of the person's last interaction, whichever comes first. Texas sets a shorter outside limit: under Business and Commerce Code 503.001, a biometric identifier captured for a commercial purpose must generally be destroyed within a reasonable time and no later than the first anniversary of the date the purpose for collecting it expires. The statute carries exceptions and exclusions, including a longer clock where the identifier is tied to a document another law requires to be kept, so counsel should check the current text against a particular deployment. Where it applies, it sets its own notice and consent requirements before capture. Illinois allows a private lawsuit. In Texas, the Attorney General has exclusive enforcement authority, with civil penalties of up to $25,000 per violation.
The definition is where lobby operators get caught out. Illinois defines a biometric identifier as a retina or iris scan, fingerprint, voiceprint, or scan of hand or face geometry, and the statute expressly excludes photographs and written signatures. So a stored visitor photo is not by itself a biometric identifier under BIPA. Where a recognition system works by extracting and comparing face geometry, the data it derives can fall inside the definition, which is why the processing a building switches on matters more than the camera that feeds it. Whether a given deployment is covered turns on the facts of what is collected and how, so it is a question for counsel rather than a product label.
Scope is not the only duty either. Section 15 also requires prior written notice that a biometric identifier or biometric information is being collected or stored, a statement of the specific purpose and the length of term, a written release from the person, and a publicly available retention and destruction policy. A deletion schedule addresses only part of those duties; Section 15 also restricts disclosure and sale and sets standards for safeguarding the data.
Scanning a driver's license has its own patchwork. State laws can limit why an ID may be electronically scanned and what may be kept. Their scope varies by jurisdiction and type of establishment, so a building scanning IDs should have counsel check the rules that apply to its location and use rather than assume that a scanner's availability makes every use permissible.
Someone will eventually ask a building to remove their visit. Whether they have an enforceable right to that depends on the jurisdiction, on exemptions, on identity verification and on any duty the building has to preserve the record, so a request is not the same as an entitlement. Either way, the time to find out what the system can actually do is before the first one arrives.
Four questions answer it, and they are worth putting to a vendor in writing:
That last one matters more than it sounds. A deletion log can help a building demonstrate that it followed its retention policy. Confirm what the log records without unnecessarily retaining the personal data it was meant to remove. None of these four should be assumed from a feature list. Get the answers from the vendor in writing before purchase.
Five decisions, and all five are cheaper now than after the first visitor walks in.
A worked example makes the shape of it clearer. A building might capture a name and a visit timestamp for an ordinary meeting, and for a contractor capture ID information and a signed site acknowledgement as well. Those are two different data sets created at the same desk, and they can carry different access permissions and different retention decisions. Deciding that once, by visitor type, is easier than deciding it per visit.
What gets captured, by visitor type, since a contractor and a client do not need the same fields. What lands on the printed badge, chosen rather than defaulted. Who can see the stored record, which is a role-based permissions question the platform already supports. How long records are kept, by category, with biometric identifiers and biometric information on a separate schedule where applicable law requires it. And who approves a deletion request when one arrives.
Write those down before configuration rather than after. What a visitor management system does in an office building sets out where badging sits in the wider system, visitor check-in vs. visitor management covers where the record fits against the rest of the arrival, and connecting visitor management to Lenel, Genetec, C-CURE, AMAG and Kastle covers what happens when the badge has to open something.
Tell us what your building scans today, whether you use photo capture, and what your retention schedule says. Those three answers decide most of the configuration. From there the useful output is a short written list: what each visitor type has to hand over, who can see it afterward, how long each category is kept, and who signs off when somebody asks for their visit to be removed.
Typically the visitor's name, the host or company being visited, the date, often an expiry time, and a QR or barcode that a turnstile or guard can verify. A photograph and a suite number are optional additions, and both have privacy consequences because a badge is worn in public.
That depends on the building's retention policy, available vendor controls and applicable preservation duties; the public product page does not establish a default retention period. Navigo's routine backups hold up to three years of historical data, which describes the backup window rather than a retention policy. Keeping less for less time is a data-minimization choice, weighed against incidents, litigation holds, lease and tenant requirements and anything law obliges the building to keep.
Not by itself under Illinois BIPA, which defines biometric identifiers as retina or iris scans, fingerprints, voiceprints, and scans of hand or face geometry, and expressly excludes photographs. Where a recognition system extracts and compares face geometry, the derived data can fall inside the definition. Whether a given deployment is covered is a question for counsel.
For biometrics, yes in some states. For covered biometric identifiers and biometric information, Illinois BIPA requires destruction when the collection purpose is satisfied or within three years of the person's last interaction, whichever is first. Where the Texas statute applies, destruction is generally required within a reasonable time and no later than one year after the collection purpose expires, subject to its exceptions and exclusions. Ordinary visitor logs are not covered by those deadlines.
They can ask. Whether that request is enforceable depends on the jurisdiction, on exemptions and on any duty to preserve the record, and whether it can be honored depends on the system. Confirm with the vendor before purchase whether a single record can be deleted, whether bulk purges by date are possible, whether deletion reaches backups, and whether it is logged.
Toll-Free
Phone
© Copyright 2025 ITS, Inc. All rights reserved.
Stay in touch with the latest news and updates from ITS, Inc.
7150 Columbia Gateway Drive, Suite L
Columbia, MD 21046
112 West 34th Street, 18th Floor, Room 18025
New York, NY 10001