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.

Kimss orchestrates inference through customer-configured model endpoints, including Microsoft Azure AI Foundry and OpenAI-compatible providers when connected. Kimss does not use your prompts or completions to train or fine-tune Kimss-owned foundation models, and does not repurpose your content as a Kimss product training dataset. How Microsoft processes data for the underlying Azure AI services is governed by Microsoft’s published product terms and data processing documentation; customers should review those materials with their counsel as part of vendor due diligence.

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.

Partner referrals

If you arrive via a creator /go link, Kimss sets an HttpOnly kimss_ref cookie (90 days) so a first-time individual signup can receive a longer no-card Production trial and so the creator can be attributed if you later subscribe. We store the creator handle on the new account record, and we log hashed (not raw) IP and user-agent for click counting. Click logs are retained for 180 days. Creators see counts only, never your name or email.

Cookies and similar technologies

The public site uses a first-party consent banner. Strictly necessary cookies (session, partner portal, and storing your consent choice) run so the site works. Analytics cookies (Google Analytics 4 and PostHog, when configured) and marketing cookies stay off unless you opt in. Details, durations, and how to change your choice are in the Cookie Policy.

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.