DATA SOURCE POLICY
Open data, visible provenance, no invented product claims.
GlowBling's public catalogue is intentionally strict: sparse product and ingredient records are removed before publication. Missing fields stay missing, and product images are not automatically reused simply because database records are open.
Open Beauty Facts
Primary upstream product corpus for barcodes, brand labels, source category tags and on-pack ingredient declarations. Product/brand/composition data is reused under ODbL 1.0 with attribution and share-alike.
View sourceINCIDB
Normalization and sample layer used for GlowBling's initial catalogue import. The free sample contains 200 products, their brands, referenced ingredients, composition links and an ingredient-name resolution audit trail.
View sourceEuropean Commission CosIng
Reference source for cosmetic ingredient identity and regulatory-context fields where the INCIDB record is CosIng-matched. CosIng is informative and has no legal value by itself.
View sourceImages are a separate rights check
GlowBling does not assume that open database rights grant permission to reuse every associated product photograph. When image rights are not independently verified, the catalogue uses a branded fallback visual.
What “source verified” means here
It means the record passed GlowBling's strict provenance and completeness gate. Products need identifiable source data, barcode, specific category, a meaningful ingredient declaration and multiple detailed ingredient links. Imported ingredients need a CosIng match, recorded functions, additional reference detail and repeated product coverage. It does not imply regulatory approval, efficacy or personal suitability.
Internal implementation details are documented in DATA_SOURCE_POLICY.md. Catalogue import and validation can be rerun with npm run data:import and npm run data:validate.