Front Gate FAQ — system capabilities (Crest public form)
This is a public record hosted on the source's public portal. Open or verify it at the source below; the file hash was checked against the capture manifest. This site has not necessarily content-reviewed the full text yet.
Relevant excerpt / transcription (labeled)
Describes LPR, RFID, PIN, fob, directory, Swiftlane, facial recognition, cloud facial-photo upload, live video, still images, and an activity feed.
Source location: See source link
Source identity
- Title
- Front Gate FAQ — system capabilities (Crest public form)
- Record date
- April 27, 2026
- Publisher / source
- Crest Management (public portal)
- Source type
- Public form / FAQ
- File type
- application/pdf
- Pages
- —
- Published
- August 27, 2026
- Archive record ID
- front-gate-faq
Summary
A 12-page Crest description of the gate system: rear and standard license-plate readers, RFID, PINs, fobs, a resident directory, the Swiftlane app, optional facial recognition, cloud-hosted facial photos, live/still camera images, visitor PINs, and an activity feature recording incoming calls and PIN use. It also states the entrance should not be considered “security” or “secure.”
What this establishes
- What the vendor/management describe the system as capable of.
What this does not establish
- Actual current configuration, whether facial recognition is enabled for any resident, or that the system is unlawful. Capability is not proof of use.
Why it matters
Capability disclosures warrant precise public answers on ownership, data categories, retention, access, exports, facial-template treatment, law-enforcement access, and deletion at contract termination.
Related records
Open questions — records still needed
- Gate/Swiftlane contracts, privacy notices, settings, retention schedules, access logs, deletion provisions.
Known limitations
Describes capability and expected use, not verified configuration.
Integrity information
- Original filename
- Front Gate FAQ.pdf
- File size / extent
- —
- SHA-256
- D0E7C0AA902CE877070845C8EC47F64EBF3D7D44FFB95BC4135851ED6B7E5972
- Complete or excerpted
- Excerpt / partial (original retained privately)
- Redaction status
- No credentials, PINs, or access instructions republished.
“Verified” refers to file provenance or capture integrity; it does not mean every statement inside the record is true.
Corrections and responses
No corrections or responses have been published for this record yet. Verified corrections and any full Board, management, vendor, or named-person response will be dated and linked here.
Request a correction for this recordRevision history
- August 27, 2026Record created for first public release.
Last reviewed: August 27, 2026