Klime handles your team's work and connects to the tools that run your business, so protecting your data is core to how we build. This page summarizes how we keep it safe.
Encryption
Data is encrypted in transit with TLS and at rest using strong, industry-standard encryption. Credentials and connection tokens are stored encrypted.
Human approval by design
Agents in Klime ask before they act. Actions that change your connected tools wait for a person to approve them, which keeps automation from making changes without oversight and gives you a clear record of who approved what.
Least-privilege access to your tools
When you connect a tool, Klime requests only the access the features you use need, and you can disconnect a tool at any time. Connection tokens are scoped to your organization and stored encrypted.
Access controls
Access to production systems is limited to the people who need it, protected by strong authentication, and logged. Permissions inside Klime follow the roles and access your team already has in its connected tools.
Isolation
Each organization's data is logically separated, and every request is scoped to the organization that owns the data.
Monitoring and resilience
We monitor our systems for problems and unusual activity, and we back up data so we can recover it. We test our ability to restore from those backups.
Our vendors
We work with established hosting and AI providers, and we hold them to contractual security and data-protection commitments. Our AI providers do not use content sent through their APIs to train their models.
Responsible disclosure
Found a security issue? Email hello@klime.com with the details and steps to reproduce, and give us reasonable time to fix it before sharing it publicly. We are grateful for reports that help keep Klime safe and will work with you in good faith.
Contact
For any security question, reach us at hello@klime.com.