Privacy

Minimize personal data. Preserve source context.

StreetLens is built around public incident datasets, but public availability does not erase the need for restraint.

01

Public incident records

StreetLens does not automatically display victim names, ages, race, sex, ethnicity, private contact information, apartment or unit numbers, or other sensitive demographic profiling fields.

Map points are slightly generalized for display. Agency block labels are retained only when they are already public.

02

Curated people and media

A selected incident may include a verified mini Casefile with a public name, role, portrait, booking photo, or non-graphic contextual image. These additions are manually reviewed, source-attributed, rights-documented, and published separately from the automatic city-data feed.

Draft and review-stage Casefile material remains in the protected administrator workflow. StreetLens does not use face recognition, scrape private profiles, or automatically match a photograph to a map location.

03

Correction requests

A correction request may include an optional email address, subject, related page URL, and message. It is stored in the site database so the request can be reviewed. Do not submit private personal information.

04

Administration

The administrator area uses a secure HTTP-only, SameSite session cookie. Passwords and session secrets remain server-side. Failed login attempts are rate-limited.

05

Analytics readiness

The application emits first-party interaction events that can later be connected to an analytics provider. This preview does not hard-code an external analytics service or sell visitor data.

06

External links

Official-source pages and TopTrendReportTV links open on third-party sites with their own privacy practices. StreetLens cannot control those services after you leave this site.