AI & data standards

Infrastructure data, built for public trust.

CYVL captures roads, sidewalks, and public assets. Faces and license plates are blurred before delivery, and customer outputs contain condition data, inventories, and geospatial layers.

Serving · public agenciesPrivacy-first
Residents walking into a brick city hall with the American flag flying out front

Trust & data privacy

Built for infrastructure, with clear privacy limits.

Faces and license plates are blurred before delivery. CYVL models focus on public assets and condition, with no biometric identifiers or owner-record lookups.

Before delivery

Identifiers are removed

Faces and license plates are blurred before imagery reaches the customer platform.

Purpose-limited AI

Models focus on public assets

CYVL models identify infrastructure condition and assets without biometric templates or owner-record lookups.

Procurement-ready

Cities can adopt the standard

The Municipal Infrastructure Data Privacy Standard can be added directly to procurement requirements.

The standard

The Municipal Infrastructure Data Privacy Standard.

Five requirements cities can use when evaluating any vendor that collects roadway imagery.

The five commitments

01

Faces and license plates are blurred before delivery.

The process runs before imagery enters the customer platform or any deliverable.

02

License plates are not matched to owner records.

CYVL does not connect plate numbers to motor vehicle databases.

03

Captured imagery is not used to create biometric identifiers.

No facial-recognition templates, gait analysis, or similar identifiers are derived.

04

Customer deliverables contain infrastructure data.

Outputs include condition data, asset inventories, and geospatial layers.

05

Collection follows the federal Driver's Privacy Protection Act.

DPPA requirements are built into the system architecture and operating process.

Why this matters

Roadway imagery can reveal the condition of pavement, signs, sidewalks, and other public assets without preserving identifying details about residents.

CYVL meets all five commitments today. Cities can use this language in procurement to set the same expectations for any infrastructure-data vendor.

American-made

Built in America, end to end.

CYVL's sensors, cloud infrastructure, and engineering operations are U.S.-based. Its LiDAR and cameras are approved for U.S. government use.

The American supply chain

01

Sensors built and assembled in the United States.

CYVL sensor rigs are produced domestically.

02

LiDAR and cameras approved for U.S. government use.

Field hardware meets the requirements CYVL serves in government deployments.

03

On-device software developed in the United States.

CYVL develops the software that runs on each sensor.

04

Data stored on U.S.-based cloud infrastructure.

Customer captures are uploaded to cloud infrastructure located in the United States.

05

Engineering operations based in Boston, Massachusetts.

CYVL's hardware and software teams work from the Boston area.

Why this matters

A U.S.-based supply chain gives agencies a clearer answer on hardware provenance, data residency, support, and long-term accountability.