Alexandre Family Creamery

Active WDID 2 01NEC006559 San Leandro, Alameda County Region 2 · San Francisco Bay

At a glance

Permit Evidence: SMARTS record
Active Industrial
No Exposure Certification (NEC) · Permits and applications
Location Evidence: facility-reported
San Leandro, Alameda County
Region 2 · San Francisco Bay · Location · Statewide map
Receiving water
Not reported
No identification to check. Details
Identified receiving water on the 2026 303(d) list
Not established
Shown only when the reported receiving water is identified and corroborated.
2026 Integrated Report waters within 1.0 km Evidence: geographic proximity
None
Monitoring results Evidence: facility-reported
None in the current exports
Compliance and enforcement records Evidence: SMARTS record
0 inspections · 2 violation records · 3 enforcement actions
Counts as published in SMARTS; not a compliance determination · Details
SMARTS TMDL records Evidence: SMARTS-reported
0 records
TMDL records

Each label shows where a statement comes from. How to read the labels.

Overview and location

Reported facility location HUC12 watershed Corroborated receiving water 2026 Integrated Report waterbodies nearby

Open this facility on the statewide map

Reported location Evidence: facility-reported

Coordinates
37.69563, -122.16316
Precision
5 decimal places
Shared point
No
Matches application record
same

Facility location as reported by the discharger in SMARTS; not a discharge point or outfall.

Facility address
14710 Wicks Blvd, San Leandro 94577
Regional Water Board
2 — San Francisco Bay

HUC12 watershed Evidence: spatial

  • Sausal Creek-Frontal San Francisco Bay Estuaries HUC12 180500040805

The facility's reported location lies within this HUC12 watershed (spatial derivation); it is not a discharge location.

Permits and applications Evidence: SMARTS record

Current permit record

Permit type
Industrial
Application type
No Exposure Certification (NEC)
Status
Active
Operator
Alexandre Family Creamery LLC
Primary industry (SIC)
2026-Fluid Milk
Application ID
519558
NOI processed
Apr 22, 2020
Last certified
Oct 21, 2025
Facility size
21600 SqFt
Impervious area
0 %

Retrieved from SMARTS Oct 20, 2026. Verify against SMARTS before relying on it.

Permit history

Storm water applications for this WDID, newest first
ApplicationTypeStatusProcessedTerminatedCertified
519558 IndustrialActiveApr 22, 2020 —Oct 21, 2025

Every storm water application SMARTS records for this WDID, newest first (1).

Receiving water

Reported by the facility Evidence: facility-reported
—
Discharges directly / indirectly
— / — (as answered in the permit application)

No receiving-water text was reported for this permit.

Impaired waters and TMDLs

Two kinds of information, kept apart: 2026 Integrated Report waterbodies near the reported location (geographic proximity only), and TMDL records that SMARTS lists for this facility. Neither establishes where the facility discharges; see Receiving water for the facility's own statement.

Nearby waterbodies Evidence: geographic proximity

Spatial proximity only; discharge pathway not established. Being near a waterbody does not mean the facility discharges to it.

No 2026 Integrated Report waterbody lies within the proximity threshold of the reported location.

SMARTS TMDL records Evidence: SMARTS-reported

No TMDL records for this facility in the SMARTS TMDL export.

Reported monitoring results Evidence: facility-reported

Numeric Action Level (NAL) screening is being independently validated and is not shown. Nothing on this page states whether a result exceeded a NAL.

No industrial monitoring results for this permit are in the current exports.

Compliance and enforcement records Evidence: SMARTS record

These are records as the State Water Board publishes them in SMARTS, with the source's own types and statuses. They are not a compliance determination or rating. A record listed here is not proof of a violation beyond what the source states, and the absence of records does not establish compliance.

Compliance and enforcement records by type
Record typeRecordsAs publishedDatesRetrievedList
Violations2 2 Violation · 0 Potential (preliminary) · 0 Dismissed Oct 02, 2021 – Oct 02, 2025 Oct 21, 2026 All violations
Enforcement actions3 3 issued · 0 draft · 0 withdrawn, rescinded or superseded Oct 18, 2021 – Oct 17, 2025 Oct 21, 2026 All actions
Inspections0inspections, not findings — Oct 21, 2026
Annual reports0certified reports (contents not shown) — Oct 21, 2026
Water-quality-based corrective action reports0reports, by parameter — Oct 21, 2026

Each record type is counted by its own SMARTS identifier. A violation and the enforcement action that cites it are two records in two lists; they are never added together.

Chronological record history (5 records, newest first)
Compliance and enforcement records, newest first
DateRecordIDType or purposeStatus as publishedDetail
Oct 17, 2025 Enforcement actions 464059 NOV (Notice of Violation) Active
Oct 02, 2025 Violations 898575 Failure to meet NEC criteria ViolationReport
Jan 03, 2022 Enforcement actions 445232 NOV (Notice of Violation) Historical
Oct 18, 2021 Enforcement actions 442380 NOV (Notice of Violation) Historical
Oct 02, 2021 Violations 878487 Failure to meet NEC criteria ViolationInternal Report

Sources and provenance

Sources behind this page
InformationSourceRetrieved or published
Permit, location, receiving-water textSMARTS Industrial Application Specific DataOct 20, 2026
Permit historySMARTS Storm Water ApplicationsOct 20, 2026
Monitoring resultsSMARTS Industrial Parameter DataOct 20, 2026
Watershed Boundary Dataset HU2 GeoPackages 15, 16, 18 (WBDHU12)USGS2026-10-22
2026 California Integrated Report, Appendix A: 2026 303(d) List (final)SWRCB2026-10-22
Final_2026_Rivers_and_Streams + Final_2026_Lakes_and_Reservoirs (FeatureServer 0)SWRCB GIS2026-10-22
SMARTS TMDL requirementsSMARTS2026-10-21

Relationships computed 2026-10-22 with methods facility_huc12/1, proximity/1, receiving_water/2, tmdl_reference/1, waterbody_huc12_ovl/1, waterbody_huc12_pub/1; proximity threshold 1.0 km.

How to read the evidence labels

Records are shown as published and are not compliance determinations. How geographic context is derived.