Zorqelio / Security and operational boundaries

How Zorqelio protects workflow access

Workspace and account access are required for private customer resources. Browser sessions use Secure, HttpOnly, SameSite cookies. API tokens are stored as hashes; passwords use the application's salted password-hashing implementation.

Authorize agents narrowly

Workflow keys bind a single workflow and policy, with inspect/evaluate/execute permissions, an expiry and a lifetime request budget. Owners can revoke them in the dashboard. Destination credentials stay in the trusted integration service. Existing broad workspace keys should not be given to untrusted agents.

Guard boundaries

The SDK checks the submitted payload and claims a short-lived, single-use permission. It does not prove factual truth, stop code bypassing the guard, or guarantee exactly-once execution in an unrelated destination. Use durable business-operation idempotency and reconcile unknown outcomes.

Operational evidence

Automated tests cover authorization, workspace isolation, quotas, replay prevention and destination idempotency. These tests are not a security certification or a measured uptime guarantee. Service status reports a point-in-time response; no independent uptime history or contractual SLA is advertised.

To connect compatible assistants without sharing broad credentials, review the MCP client setup examples and guarded handoff guide.

Data handling and retention · Service terms and limits