Security
Security at Intelligence Cloud
How to report a vulnerability or a security incident, and how to send secrets to Tresic.
Section 1
Vulnerability disclosure policy
| Topic | Policy |
|---|---|
| How to report | Email security@tresic.cloud about any vulnerability in Intelligence Cloud, its API or the SDKs. |
| What to include | What is affected, the steps to reproduce it, what an attacker could do with it, and how to reach you. Don't include other people's data. |
| Our response | We acknowledge your report within 3 business days, keep you informed while we fix it, and tell you when it is resolved. |
| Good-faith research | We will not pursue good-faith security research that follows this policy, as long as you avoid privacy violations, destruction of data and disruption of the service, and you don't access or keep other customers' data. If you reach data that isn't yours, stop, and tell us. |
Research that follows this policy does not breach the API and SDK Terms.
Section 2
Security contacts
| You need to | Go to |
|---|---|
| Report a suspected security incident, or exposed conversation data, a password, a key or a webhook address | security@tresic.cloud, straight away, copying your Tresic contact or your provider. Rotate what was exposed. |
| Send Tresic a key, password or client secret | security@tresic.cloud, by secure transfer only: a password manager share, a one-time secret link, or encrypted email |
| Request an access log: who read a customer's conversations, in the app or through the API, and who changed its configuration | security@tresic.cloud. Logs are kept for the customer's retention period. |
| Request security documentation: certifications, penetration test summary, data location, subprocessors, BAA | security@tresic.cloud |
How integrations must protect conversation data and credentials is set out in Conversation data protection.
Creo Solutions, Inc. d/b/a Tresic
© 2026 Creo Solutions, Inc. d/b/a Tresic · API and SDK Terms · Other names are trademarks of their respective owners.