Our Security practices
Keres AI answers your customers and handles their data every day. This page states the practices we follow, and is plain about what we do not have. For the short version, see Trust & Security.
01Encryption in transit
- Traffic between callers, our systems and the tools we write to is encrypted in transit.
02Access controls
- Principle of least privilege — only the people who run your account can see it.
- Access ends when a person’s role no longer needs it.
03Data handling
- We do not train third-party AI models on client data.
- Data retention is configured per engagement — we keep only what is necessary for the service to function.
- Data can be exported or deleted on request within 15 business days.
04Compliance
Keres AI does not hold a SOC 2 report or HIPAA certification and does not sign Business Associate Agreements (BAAs) today. If your business has regulatory requirements, tell us before you sign so we can say plainly whether Keres fits.
05Responsible disclosure
If you believe you’ve found a security vulnerability in our systems or a client deployment we operate, please report it to ops@keresai.com (see also security.txt). We work with reporters to validate and resolve issues, and we do not pursue legal action against good-faith researchers who follow responsible disclosure.
06Questions
Have specific security or compliance requirements? Email ops@keresai.com and we’ll tell you honestly whether Keres fits.