Developers
Deployment is a configuration task, not an integration project. Nothing about your model choice, prompt stack or agent framework has to change.
REST
Encryption happens in the client SDK before the request is formed. The payload below is already ciphertext by the time it reaches us.
from clspp import Client client = Client(tenant="acme-eu", region="eu-west-1") # Encrypted client-side; the service receives ciphertext only. client.record( actor = "a.mehta@acme.com", surface = "chatgpt.com", model = "gpt-5.2", prompt = prompt_text, response = response_text, labels = ["credit-ops", "customer-data"], ) # → {"id": "rec_8f21c0", "chain": "e7c1a9", "region": "eu-west-1"}
Model Context Protocol
Works in Claude Desktop, Cursor and Cline. Tool calls, results and the context an agent retrieves are all recorded as entries.
{
"mcpServers": {
"clspp": {
"command": "npx",
"args": ["-y", "@clspp/mcp"],
"env": {
"CLSPP_TENANT": "acme-eu",
"CLSPP_REGION": "eu-west-1"
}
}
}
} Rollout
Force-install by Chrome or Edge group policy, or through Intune and Jamf. Users see a status indicator and nothing else.
Point CLS++ at your own KMS or HSM so key material never depends on us. Ten minutes with your platform team.
Nominate the jurisdiction per tenant. Every subsequent export carries the residency attestation with it.