Trust, Privacy, and Responsible Use
What not to enter into the tool
Cogliva is built for strategy diagnosis, not for storing sensitive or regulated data. A few simple boundaries protect you and your clients.
Avoid sensitive personal data
- Identifiable personal data about individuals beyond what is necessary.
- Special-category data such as health, financial, or biometric records.
- Credentials, passwords, API keys, or other secrets.
Avoid regulated or confidential records
Do not enter regulated records, privileged legal material, or confidential client documents that are governed by specific handling obligations. Describe the situation in general terms instead.
Describe, don't dump
You rarely need raw sensitive data to get a useful diagnosis. Summarise the relevant context — patterns, constraints, and challenges — rather than pasting source documents.
When in doubt, leave it out
If you are unsure whether something is appropriate to enter, omit it or generalise it. The quality of the diagnosis depends on clear context, not on sensitive specifics.
How to use this in Cogliva
- Summarise sensitive context rather than entering raw records.
- Strip identifiers and secrets before entering anything.