Skip to main content
Customers, prospects, and compliance reviewers usually start here. It is the short version: where tenant data lives, who can open it, and what AI features do with prompts. Hosting detail and the defensive stack are shared under NDA, not on this page.

​
Platform posture

  • Customer data is stored and processed in professionally managed cloud infrastructure.
  • Traffic to Keldyn services uses HTTPS.
  • Production and non-production environments are separated.
For a vendor questionnaire, ask your Keldyn representative or use the pack in your published Trust Center.

​
Authentication and access control

  • Users sign in with authenticated sessions; SSO is available where configured.
  • Optional multi-factor authentication.
  • Team roles and permissions control who can see and change governance data.
  • Machine and AI-agent clients authenticate separately from interactive users.
  • Trust Center gated resources use access grants; published Trust Center content is intentionally public.

​
Data protection

  • Data is encrypted in transit and at rest.
  • Integration credentials are stored encrypted.
  • Passwords are hashed; platform secrets are not exposed to end users.

​
AI data handling

Keldyn uses generative AI for governance workflows (for example questionnaires, architecture assistance, control suggestions, and document help). A prompt can contain confidential governance content. Treat prompts and outputs as confidential business data under your organization’s policies.

​
Logging and auditability

Significant use-case and organization actions are written to an audit trail a reviewer can read. Access to personal data is logged.

​
Reporting a security issue

A suspected vulnerability or an active incident goes to Report a bug or security issue. That page has the address and the first-response times.

​
Knowledgebase

Indexed organisational documents use the same encryption and team isolation as the rest of the product, with tighter collection rules. You pick a folder, space, page set, or channel. Connectors are read-only. Otter audio is never fetched. Sharing rules from the source do not come with the file. Anyone who can open Knowledgebase can read what you connected. Details are on Knowledgebase privacy.