Privacy and data
Collect less. Explain more.
Coodra should use the data needed to rank decisions, avoid unnecessary collection, and keep private retail context out of public or analytics surfaces.
Collect less. Explain more.
Coodra needs retail data to rank useful decisions. That does not mean every interaction, field, or answer belongs in analytics, logs, or public docs. The safest useful product keeps private retailer context inside the product boundary.
Analytics boundary
Category
Treatment
Public page views
Can be measured after consent to improve the website.
Dashboard flow events
Use categorical events, such as page changed or detail opened.
Retailer operating data
Do not send product names, SKUs, inventory values, margins, or Ask Coodra message text to analytics.
Credentials and secrets
Never collect in analytics, logs, docs, screenshots, or chat.
AI data boundary
The AI should use the minimum useful context to explain recommendations and improve ranking. Review feedback can make future decisions better, but it should not become public proof, a secret store, or a hidden permission system.