Match, don't record
Non-matches produce no record, ever. Surveillance of the innocent isn't a setting — it's absent.
Finds stolen cars and AMBER-alert vehicles. Destroys everything else on the camera in seconds. Your city holds the keys — we can't read the data.
Conventional plate readers photograph everyone and upload it to a vendor's cloud. Havenlight decides what matters on the camera — before any record exists. Watch:
Each plate is read in volatile memory and checked against signed alert lists stored on the camera: NCIC stolen vehicles, AMBER/Silver alerts, your case-flagged plates.
Almost every vehicle. Erased on the camera in seconds — never transmitted, never stored. Only hourly traffic totals survive.
Re-read for accuracy, encrypted to your keys, delivered in seconds. An officer confirms plate, state, and alert freshness before anyone gets stopped.
Yes. Every plate reader — ours or anyone's — only sees vehicles that pass its cameras, and the catches happen live, the instant a flagged car crosses one. Recording everyone doesn't add eyes; it only adds storage. Watch the same traffic go through both systems:
Stolen cars, AMBER alerts, flagged suspect vehicles — they're caught the moment they pass any camera, in real time. That instant is where this technology earns its keep, and both architectures share it equally.
A city has a handful of arterial routes, and a moving vehicle can't avoid them. Coverage is set by placement and density — and with no bulk video to haul, the same budget buys a tighter net of cameras.
When a witness or doorbell camera produces a suspect plate, flag it — every camera hunts that vehicle from then on, tied to the case. No archive of everyone required.
The archive of everyone isn't where the catches come from.
It's only where the risk lives.
Privacy engineering isn't a tax on police work — it's what makes hits trustworthy, stops defensible, and evidence admissible.
Every alert is a verified hit, re-read before it fires. Photo, plate, state, and direction of travel hit the MDT in seconds — no "vehicle of interest" spam.
Hits go to the units covering that zone and your crime center — not every login in three counties.
Detective flags a plate against an RMS-validated case; a different supervisor approves; fleet-wide in minutes. Case closes, flag dies.
Image, confirmation record, cryptographic chain of custody — court-ready. The audit trail that satisfies your council defeats suppression arguments.
CAD push, RMS validation, NCIC sync. Only confirmed, case-bound matches ever enter CAD or RMS. Solar + LTE: no trenching, under an hour per pole.
Departments elsewhere are losing cameras to council votes. Our governance model turns a 5–4 kill into a 7–2 approval — and keeps it funded.
Solar-powered, self-contained, installs on existing poles in under an hour. Everything that matters happens inside the shell — so there's very little to trust.
| Recognition | On-device plate reading and matching — no cloud inference |
| Power | 28 W solar wing, 14-day battery reserve |
| Connectivity | Constant-rate encrypted LTE heartbeat — traffic looks identical with or without a match. Never bulk video |
| Security | Secure element; signed, reproducible firmware; remote attestation. Watchlists stored on-device as keyed hashes — a stolen camera reveals nothing, not even who was being looked for |
| Audio | No microphone — nothing to subpoena |
| Encryption | Matches encrypted to agency-held keys; Havenlight can't decrypt |
| Audit | Annual public security audit, full report published |
Enforceable terms with penalties owed to your city — and architecture a vendor can't quietly change.
Non-matches produce no record, ever. Surveillance of the innocent isn't a setting — it's absent.
Everything lives in your cloud tenant or on-prem, encrypted to keys you hold. We can't query it.
All activity lands on a tamper-evident ledger. Aggregates publish to your public portal automatically.
Case-scoped grants between named agencies, expiring in 30 days. No network. Immigration and reproductive-health surveillance rejected at the API.
Public vote to deploy, annual renewal vote, 30-day no-fault termination — standard in every contract.
An alert is a lead, not probable cause. Officers confirm plate, state, and validity before acting.
We fund and draft the laws — warrant rules, retention caps, audits — that bind the whole industry, us included.
| Dimension | Havenlight | Networked ALPR |
|---|---|---|
| Non-matching vehicles | Destroyed in seconds | Stored for weeks, searchable |
| Data custody | Your tenant, your keys | Vendor's cloud, vendor's control |
| Cross-agency search | Bilateral, case-scoped, expiring | De facto national network |
| Query accountability | Purpose codes + case numbers, enforced at the API | Free-text "reason" fields |
| Vendor access | None — cryptographically | Full |
| Retention ceiling | Seconds; 72 h investigative tier; 30-day hard cap | 30 days to years, extendable |
| Community control | Public vote, annual renewal, resident dashboard | Residents learn from the news |
| Business model | Hardware + flat fee; public pricing | The database is the moat |
Trust claims are cheap; repositories aren't. Everything that touches your data is open source — and reproducible builds with remote attestation prove the code running on the pole is the code anyone can read.
The on-device pipeline: read, match, erase. Reproducibly built; attestation verifies the running image byte-for-byte.
The agency backend: alerting, policy engine, evidence packaging. Deploys in your tenant, not ours.
The tamper-evident audit chain and the public transparency portal it generates.
Independent audit tooling — verify attestation and ledger integrity without trusting us.
Your auditor — or any resident — can inspect the exact code, and attestation proves it's what's deployed. No "trust us" step anywhere.
Open code means researchers find problems before adversaries do. Our vulnerability-disclosure program pays for what they find.
If Havenlight ever disappears — or disappoints — your city isn't stranded. The full stack can be run, audited, and maintained without us.
Repositories publish with the first production release, alongside the annual public security audit.
The public portal shows delayed, aggregated stats — never live case activity. Your oversight board streams the full ledger in real time. And it cuts both ways: the same chain clears your officers when an accusation lands.
Hash-chained, written in the same transaction as the query. No off switch — for anyone. No plate numbers in the chain.
Your oversight board reads the full chain in real time. Suspects can't watch investigations; auditors can.
New camera, new sharing agreement, new setting — public notice first. Nothing arrives by quiet update.
We publish our threat model; no one else in this market does. Tap any scenario for the countermeasure. Misuse caught by an automatic flag is a personnel matter — misuse caught by a journalist ends the program.
Flat and all-inclusive. No per-search fees, no bundle games, never a business model that needs your residents' data.
Volume pricing for 25+ cameras is in our public standard contract. Every agency starts with a 90-day pilot — real cameras, real alerts, council materials included. If a competitor quotes lower, ask to see their data-use terms next to ours.
A privacy company that opposes privacy law is a surveillance company with better branding. We draft and fund rules that bind the whole industry — including us: warrant requirements, retention caps, purpose limits, mandatory audits, a private right of action.
Statutes take years; purchasing rules take a vote. Our model procurement ordinance fits on a page and names no vendor — it just makes the dragnet un-purchasable while keeping real alerting. Residents: hand it to your council.
Real-time alerts handle most of it. For look-backs, an optional 72-hour tier exists — it takes a case number, two approvals, and usually a court order. After 72 hours the key is destroyed and the data is gone for good.
The missing features are the ones cities get sued over. And with no bulk video to store, match-only is cheaper to run.
Your data is encrypted with keys we don't have — there's nothing for a future owner to monetize. And the commitments are contract terms your city can enforce with penalties.
No. Non-matches no longer exist, and matches live in your tenant under your keys. Nothing is shared unless your agency shares it, case by case.
The camera re-reads every hit, then a human confirms it before any stop. Unconfirmed matches erase themselves in 24 hours, and error rates are published quarterly.
Ask your council to adopt our one-page procurement standard. It keeps real alerting and makes the dragnet un-purchasable. Message us for the text.
A live demo, the standard contract, or the model ordinance for your council. We publish everything — that's rather the point.
Expect an answer within 12 hours.