StreetLens is built around public incident datasets, but public availability does not erase the need for restraint.
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.
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.
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.
The administrator area uses a secure HTTP-only, SameSite session cookie. Passwords and session secrets remain server-side. Failed login attempts are rate-limited.
My StreetLens uses the Sites sign-in service to identify the signed-in viewer. StreetLens stores a one-way account key, saved-item identifiers, followed cities, and save dates so a private watchlist can work across sessions. StreetLens does not store the viewer's sign-in password.
Removing a saved item or followed city deletes that association from the active library. Account-specific pages are excluded from search indexing.
The StreetLens video desk uses privacy-enhanced YouTube embeds. YouTube may receive device, network, and interaction information when a visitor loads a thumbnail, starts a video, or opens YouTube. Video titles, dates, and publishers remain attributed to their original channels.
StreetLens uses Google AdSense to serve and measure advertising. Google and other third-party vendors may place or read cookies, use web beacons, process IP addresses, or use other identifiers as a result of ad serving on this site. Advertising cookies may be used to show ads based on a visitor's prior visits to StreetLens or other websites.
Learn how Google uses data when you use sites that use its services ↗.
Visitors can manage or opt out of personalized Google advertising through Google Ads Settings ↗. Where required, StreetLens uses Google's consent and privacy messages so visitors can make region-appropriate choices before personalized advertising is served.
StreetLens does not sell information submitted through correction requests or the protected administration area.
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.