Security and data
Identity, permissions, encryption, hosting and the audit record.
Skilder sits between your agents and your internal systems, so it holds credentials and sees what agents do with them. This page states how both are handled.
Identity
| Caller | How it authenticates |
|---|---|
| Agent | OAuth 2.1 against Skilder, with dynamic client registration. The token is bound to one user and one workspace. |
| Person in the web app | Email and password, an emailed sign-in code, or a Google, GitHub or Microsoft sign-in. Passwords are hashed with peppered scrypt. |
| Runtime | Its own key, set in its environment. |
Permissions
Two workspace roles, admin and member, decide what a person may do. Users and permissions lists the split.
Two properties make it enforceable rather than advisory:
- Every permission check runs through one gate in the control plane, against one shared map from role to permission. No feature keeps its own copy of that map.
- A workspace role is read from the database on every request, never from the caller's token. Revoking a role takes effect on the next call, and a stolen token carries no permissions of its own.
Encryption
- In transit: TLS.
- At rest: the credentials marked secret on an MCP server, stored OAuth tokens and AI provider keys are encrypted with AES-256-GCM. The key lives in the control plane's environment, not in the database next to the ciphertext it protects.
Hosting and residency
Skilder hosts the platform in Switzerland. Personal data is processed primarily in Switzerland and the European Economic Area, with named exceptions.
The privacy policy states the retention periods and the transfer safeguards. The subprocessor list names every provider, what it processes and where.
Your content and AI models
Skilder does not train models on your content, your skills, your prompts or your tool outputs. Its providers are not permitted to either. Training requires separate written consent.
Separately from training, execution traces are processed to operate and improve the service. The privacy policy states how to opt out.
The audit record
Skilder records tool calls. Each record carries the caller, arguments, result, status, timing, and the role and skill it ran under. A very large argument or result is stored truncated. Calls are grouped into sessions when session tracking is on.
Members see their own activity. Admins see the whole workspace. Activity is where you read it.
Change control
A role or skill an agent can learn is a published version. Editing one creates a draft, and agents keep loading the published version until you publish again. See Publish and version.