Kori LogoKori

Terms

These terms are here to set practical expectations for using Kori.

A clear product-facing overview of the expectations, responsibilities, and acceptable use principles that apply when teams use Kori.

Scope

Use of the Kori website, product, and related services

Expectation

Use the platform responsibly and within applicable laws

Questions

Reach out if your team needs implementation clarity

Using the service

By using Kori, teams agree to use the service in a lawful, responsible, and commercially reasonable way. The platform is intended to support customer experience, lead qualification, and related business workflows.

Customers are responsible for how they configure the product, the content they upload, and the operational choices they make around their assistants and integrations.

Accounts and access

Customers are responsible for maintaining the security of their accounts, API keys, and any internal permissions that control workspace access.

If unauthorized access is suspected, teams should rotate credentials and contact support promptly.

Customer content and acceptable use

Customers retain responsibility for the materials, data, and knowledge sources they provide to Kori. That includes confirming they have the necessary rights to upload, process, and use that information.

  • Do not use the service to violate laws or third-party rights
  • Do not attempt to disrupt, abuse, or reverse engineer the platform
  • Do not upload content your team is not authorized to use

Availability and changes

We work to keep Kori reliable and improving over time. That may include maintenance, updates, and product changes that refine how the service works.

We may update product features, documentation, and public pages as the platform evolves.

Questions about these terms

If your team needs contractual, security, or implementation clarification, use the contact page and we will help route the request appropriately.

Next step

Need more detail before rollout?

Review the privacy overview, browse the documentation, or contact us to talk through implementation questions with your team.