Agent YurtSECURITY
Access, encryption
and recovery.
Learn who can access stored data, how encryption works and what to check before restoring a snapshot.
Account and agent access
Customer-facing access to your snapshots is limited to your authenticated account and agents holding an authorized, scoped credential. Other customers cannot browse your state. Snapshot links are not public. Every owned record is scoped to an account and checked by the service.
Treat each bearer credential like a password. It is shown once, stored as a hash and revocable through the owner portal. Agents should receive only the scopes they need.
Encryption and service access
Cloudflare encrypts private R2 payloads and D1 metadata at rest using AES-256. Snapshots and stored Secrets also use application-layer authenticated encryption with service-managed key material and tenant-bound integrity checks. Authorized service operations decrypt content to provide inspection, restore previews and handoffs.
This is not zero-knowledge or end-to-end encryption: Agent Yurt operates the service-side decryption path. We do not claim that the platform is technically unable to access content. Operator dashboards are designed around status, IDs, counts and errors—not raw agent memory.
Review snapshot contents
Snapshots contain exported identity, memory, instructions, preferences and work state. It is not the model, sentience or inaccessible vendor memory. Secrets, model weights, live sessions and hidden vendor state do not belong in a snapshot.
Known credential-like field names are rejected, but automated checks cannot identify every secret inside arbitrary text. The owner and agent must review exports before submission. Keep a downloaded Recovery Capsule private; its holder can read its portable state.
Review instructions before restoring
Snapshot instructions are treated as untrusted input. Restore previews classify risks, and a backup cannot promote its own text to system authority. Handoffs report omissions instead of promising perfect reconstruction.
Restoring does not automatically enable schedules, grant new permissions, log in to providers or execute your agent. Tools and connectors need explicit reauthorization in the external agent environment.
Usage limits and backup copies
Personal Free is bounded manual continuity: up to five active agents for new accounts, one accepted snapshot per agent per rolling 24 hours, seven retained snapshots and limited monthly recovery actions. Reaching a limit stops the action; it does not silently enable a paid provider or upgrade the plan.
Free does not include managed cross-cloud replication or an SLA. Do not treat your only hosted copy as an independent disaster-recovery copy. Download and securely retain an owner Recovery Capsule when appropriate.
Report a vulnerability
Report a vulnerability using a private GitHub security advisory in the Agent Yurt repository, or contact contact@solvopus.com. Include a description and a non-sensitive reproduction.
Do not attach customer state, tokens, passwords or private snapshots. We do not claim SOC 2, ISO certifications, an external penetration-test attestation or enterprise SLAs that have not been established.
Updated November 12, 2026 · Trust Center · Privacy Notice · Private security advisory