Skip to main content
An initial security review of the Keldyn MCP server (“KC”) usually asks three things: what happens to data you send, whether the connection widens what your coding agent can reach, and who at Keldyn can see your account. Training, subprocessors, GDPR, the DPA, and attestations are on Compliance.

​
Key concerns

​
Could uploading data to KC leak my IP, PII, or cardholder data?

Tool inputs, and anything a persisted tool call writes back (evidence text, control status, findings), are protected the same way as data typed into the web app. Encrypted in transit and at rest. Scoped to your team’s access control, below. Never used to train models (Compliance). Keldyn does not process or store payment card data. If a control’s evidence relates to a payment flow, record an attestation or reference to it rather than pasting actual cardholder data into Keldyn.

​
Does connecting KC give my coding agent extra access?

No. MCP access and your coding agent’s access are two separate things. KC authenticates over OAuth as you, scoped to one team. That token only unlocks the Keldyn tools listed in the MCP server guide: read and write your Keldyn governance data. Connecting KC does not grant Cursor, Claude Code, or any other agent new access to your filesystem, shell, cloud accounts, or CI. Whatever that agent could already reach is unchanged, and Keldyn cannot see it.

​
Does KC read or write to my production or other sensitive environments?

No. KC reads and writes Keldyn governance data only: frameworks, controls, evidence, tasks, use cases, Trust Center configuration. It has no credentials for your source repositories, infrastructure, or production and staging environments, and it cannot reach them. Prompts such as collect-evidence and review-changes ask your coding agent to look at the local codebase and propose evidence. That scan runs on your own model. Nothing reaches Keldyn until the agent makes an explicit tool call, for example update-control, and you can review that call first. See Responsible use. The PR Review Bot is a different integration. It is the one flow where code leaves your environment. What is sent, where it goes, who can see it, and how long it is kept are on Data flow.

​
Encryption, in plain terms

  • In transit. The web app, the API, and KC all use HTTPS. Nothing moves between you and Keldyn in the clear.
  • At rest. The application database and uploaded files (evidence, documents) are encrypted at the storage layer. Passwords are hashed, never stored as plain text. Integration credentials and other long-lived secrets get another encryption layer on top of that.

​
Who at Keldyn can access your data, and when

Day to day, your data is scoped by team and role. There is no standing back door for Keldyn staff. The only way a Keldyn team member views your account is a deliberate “act as you” support flow:
  • Only platform admins using a Keldyn company account can start it.
  • It requires a stated reason and the admin re-authenticating (password, plus a one-time code if they have 2FA on).
  • The resulting access is single-use and expires almost immediately if unused, and it never grants more than the target user already had.
  • Every step is written to an audit trail that cannot be edited or deleted afterward: who, for whom, why, and when.
That non-routine access is sampled and reviewed monthly, and who has any standing access at all is reviewed on a quarterly cycle.

​
Retention and deletion

Your data stays for as long as the account or team does. Use cases, evidence, and documents can be edited or deleted in the product at any time. Deleting your account is self-service and permanent. It is treated as a GDPR right-to-erasure request. Personal data is removed. Uploaded files are queued for removal from storage shortly after. Data teammates still need, on a team you shared, is reassigned to another active member so it does not vanish under them. Audit logs are the exception. Records of who accessed or changed what stay as append-only history, separate from the data they describe, and are not deleted with the account.