Privacy Policy

How Kimss AI handles information

This Privacy Policy explains the categories of information Kimss AI may process, how that information is used, and the safeguards applied to protect it.

Last updated: April 30, 2026

Data Collection

Kimss AI collects information needed to provide, secure, and improve the service. This may include account identifiers, authentication details from supported identity providers, workspace configuration, billing and subscription records, product usage events, support communications, and technical logs.

When users interact with AI agents or connected tools, Kimss AI may process prompts, responses, files, metadata, and operational telemetry necessary to deliver those features. Customers remain responsible for the data they choose to submit to the platform.

Usage

Information is used for professional service operations, including:

  • Providing access to Kimss AI features, workspaces, agents, and account settings.
  • Authenticating users, enforcing permissions, and maintaining session security.
  • Measuring usage for billing, subscription management, reliability, and support.
  • Improving product performance, troubleshooting issues, and preventing misuse.
  • Complying with legal, contractual, security, and operational obligations.

Security Measures

Kimss AI applies administrative, technical, and organizational safeguards designed to protect information against unauthorized access, disclosure, alteration, or loss. These safeguards may include encrypted transport, access controls, identity provider integration, audit logging, usage monitoring, and secure infrastructure practices.

No system can be guaranteed to be completely secure. Kimss AI reviews and improves its security practices over time and encourages customers to configure identity, access, and workspace permissions according to their own security requirements.

Contact Information

For privacy questions, data requests, or security-related concerns, contact Kimss AI through the product support channel at /app/support. Requests should include enough context for the team to identify the relevant account, workspace, or communication.