Kyndex

Privacy information

Draft pending legal review. Not a final privacy notice.

Public website and contact

This website does not offer account registration or sign-in. Documentation is public. Hosting infrastructure may process request metadata such as IP addresses and browser information. If you contact us by email, your message and contact details are processed to handle the enquiry. Customer-console authentication is operated separately for each deployment.

Data in a Kyndex deployment

Depending on enabled features, a deployment can store documents, extracted passages, embeddings, conversations, user and department records, action payloads, usage data and audit records. Logs, caches and backups may contain additional operational or content data.

The deployment operator determines access, storage location and configuration. The controller/processor roles depend on who operates the services and the agreement in place, not simply on the software being self-hosted.

Providers and transfers

Authentication, database, cache, parsing, embedding, reranking, generation and tool providers may process data. The actual provider list and regions vary by deployment. PII detection is not a guarantee that outbound content is anonymous. Review provider retention, training policies and transfer arrangements before use.

Retention and requests

Retention settings vary by data type and deployment. Application deletion does not establish the deletion schedule of backups or external providers. This draft does not promise a universal retention period or automatic removal after account closure.

For organisation data, contact your deployment administrator. For website or historical website-account questions, contact privacy@kyndex.io. Removing website authentication does not itself delete previously collected account records. Applicable rights and the process for handling requests must be documented in the final notice.

Before a production launch

Confirm the legal entity and contact details, purposes and lawful bases, actual providers and regions, retention schedules, transfer safeguards and rights procedures. No signed provider agreement or regulatory compliance is asserted here.