klink.cloud

The platform runs on Amazon Web Services in the region the customer selects, so data residency is a deployment choice rather than a support ticket.

Traffic between customers, agents and the platform is carried over TLS 1.2 or higher.

Stored data, including recordings and transcripts, is encrypted with AES-256.

Privileged access to encryption keys is limited to named operators with a business need.

Production runs in private subnets with security groups restricting inbound access to what each tier requires.

Infrastructure changes are applied through reviewed configuration rather than by hand on a console.

Access to production infrastructure requires a second factor in addition to a password.

Infrastructure health and availability are monitored, with alerts routed to an on-call owner.

Enterprise customers can authenticate their agents through their own identity provider.

Every tenant assigns permissions by role, so an agent sees only the queues and records their role allows.

Each tenant's data is separated so that one customer cannot address another customer's records.

Administrative changes are recorded on a timeline a customer can review.

An independent third party tests the platform, and findings are tracked to remediation.

Third party packages are scanned against known vulnerability databases.

Changes reach production through review by an engineer other than the author.

Customers with stricter requirements can run the platform in an environment they control.

The policy set governing the ISMS is reviewed and approved at least once a year.

Staff complete security training when they join and each year after.

Checks are carried out on hire where local law permits.

Staff and contractors sign confidentiality agreements before handling customer data.

Staff and contractors acknowledge the code of conduct.

Access is reviewed on role change and revoked on departure.

Company assets are inventoried, and disposal is documented.

A documented plan covers detection, triage, escalation and customer notification.

Business continuity and disaster recovery plans are exercised and the result recorded.

Risks to the ISMS are assessed at least annually and treated.

Suppliers with access to data are assessed before engagement and reviewed periodically.

Backups are taken on a schedule, and restoration is tested rather than assumed.

Production releases follow a documented change process.

The ISMS is audited internally against the standard.

Every model provider with access to conversation content is published in the sub-processor list.

Data sent through the providers' business APIs is excluded from model training under their published terms.

A tenant that has not enabled Kai sends no conversation content to a model provider.

The request sent to a model carries the conversation content required to answer it and the knowledge base the customer published, not the whole account.

Kai escalates to a human rather than acting where a configured confidence threshold is not met.

Customers who cannot send data to an external model provider can run a private deployment.

Customer data is held in the region selected at onboarding rather than a single global location.

Customers requiring EU residency are hosted on OVHcloud, under European jurisdiction.

US customers are hosted in AWS US regions, and their data remains in the United States.

Customers requiring data to stay in Singapore can be hosted there.

Transfers outside the region of collection are covered by the data processing agreement, including standard contractual clauses where they apply.

The platform can run inside infrastructure the customer controls, so regulated data never leaves it.

Data is classified so that handling requirements follow its sensitivity.

Each class of data has a defined retention period rather than being kept indefinitely.

Data is deleted on request and at contract end, following the published instructions.

A DPA covering processor obligations is available to every customer.

Parties with access to customer data are listed publicly and kept current.

Access, correction and erasure requests are handled within statutory deadlines.