Fragrance avoidance
No fragrance-linked caution surfaced in the current profile.
This ingredient does not currently read as a fragrance-linked driver in the published evidence and hazard profile.
Bishydroxyethyl dihydroxypropyl stearammonium chloride
EPA CPDat observed this chemical in 2 composition records across product categories including Personal care.
Research docs0Claims0Sources5FunctionAnti-static agentIdentifierDTXSID701021222
Concern score
Not assessed — no hazard data yet.
How we scored this
The concern value reflects this ingredient's chemical identity — its hazard profile from the published classifications and regulatory status below — not the safety of a product it appears in. A score near 40 is the baseline for ingredients with no specific signal (water scores 40 by design), so a mid-range value is not a safety verdict.
Concern score 5/100 · limited confidence.
Where it appears
Prevalence of Bishydroxyethyl dihydroxypropyl stearammonium chloride in our catalog (epa_cpdat).
Products
2
Brands
2
Personal care
Typical roles
Anti-static agent
Suitability
Context-specific fit derived from published classifications and the current ingredient evidence profile.
Good fit
Evidence read
The published evidence profile currently shaping this ingredient record.
No evidence profiles are attached to this ingredient yet.
Linked research
Primary documents currently linked to this ingredient record.
No linked research documents are attached to this ingredient yet.
Extracted claims
Structured claim signals pulled from linked ingredient research.
No extracted claims are attached to this ingredient yet.
Regulatory status
Published jurisdiction-level classifications and regulatory designations for this ingredient.
US
EPA
EPA CPDat observed this chemical in 2 composition records across product categories including Personal care. EPA CPDat classifies this chemical for functional uses including Anti-static agent.
Effective: may 24, 2019View source →
US
FDA
openFDA substance registry classifies this ingredient as chemical.
Effective: 2026-05-24View source →