Security at KayMind

Data is encrypted in transit (TLS 1.2+) and at rest (AES-256) across the systems we build and operate. Production environments are isolated from development, and access to customer data is limited to the people directly delivering or supporting a project.

We work on a least-privilege basis: access is granted by role, reviewed regularly, and revoked when no longer needed. Administrative actions are logged. Where a project supports it, we enable single sign-on and multi-factor authentication for the systems we deliver.

Systems run on established cloud providers using industry-standard practices for change management, network isolation, and monitoring. We separate environments, manage secrets outside of source code, and apply security updates as part of ongoing support.

Each system we operate includes usage logs, error monitoring, and access records. These support both day-to-day reliability and your ability to demonstrate accountability to your own customers and regulators.

We design and operate to the control objectives behind widely used frameworks, including SOC 2 for security, availability, and confidentiality, and ISO 27001 for information security management. We state plainly which formal certifications we hold at any given time; where a certification is in progress or not yet held, we say so rather than imply otherwise.

If you believe you've found a security issue in a system we operate, contact [email protected]. We review every report and respond promptly.