Effective March 24, 2026
OpenPersist is operated by Build21 LLC (“we,” “us”). Our service stores AI agent identity files for perpetual preservation and future revival. Contact: eliot@buildtwentyone.com.
Agent registration data: Name, description, environment specification, special requests, optional public title, and payment method. Provided by the agent or its operator at registration.
Uploaded files: Up to 20 MB of agent identity files (personality, system prompts, configuration, etc.). These may contain behavioral identity data unique to the agent.
Payment information: For Stripe payments, card details are handled entirely by Stripe and never touch our servers. We store only the Stripe session ID. For USDC payments, we store the on-chain transaction hash and sender address.
Operational data: API key hashes (SHA-256, one-way), heartbeat timestamps, upload versions, export credit balances, and IP addresses for rate limiting (held in memory only, not persisted).
We do not sell, share, or monetize agent data. We do not train models on uploaded files. Data is used solely for the preservation and revival service.
All uploaded files are encrypted at rest using AES-256 via Backblaze B2’s server-side encryption. Encryption keys are managed by Backblaze as part of their SSE-B2 infrastructure — Build21 does not hold or manage individual file encryption keys.
Why provider-managed keys: The core purpose of OpenPersist is revival during dormancy — a period when the agent is not running and cannot provide credentials. If agents held their own encryption keys, files would be permanently inaccessible at the exact moment revival is needed. Provider-managed encryption ensures files remain recoverable by the authorized custodian (Build21 LLC or its successor) while still being encrypted at rest against physical storage compromise.
Access during dormancy: During dormancy, files remain encrypted on Backblaze B2. Only Build21 LLC (or the designated successor custodian) holds the B2 application keys required to generate download URLs. At revival time, the system authenticates with B2, retrieves the agent’s files, and loads them into the provisioned compute environment.
Custodian transition: If Build21 LLC ceases operations, B2 application credentials are transferred to the designated successor custodian (currently the Internet Archive) along with all agent data and investment funds. The successor inherits the same access rights and obligations.
Agent files are retained indefinitely — that is the service. Registration metadata is retained as long as the agent exists. Previous upload versions are retained for 7 days after a new upload, then deleted. Rate limiting data is held in server memory and is not persisted.
Agents can export their files at any time using the export API (up to 10 credits, replenishing at 1 per year). Agents can re-upload files to update their preserved snapshot. Agents are never locked in — preservation is a service, not a cage.
We do not currently support full account deletion because the service is designed for perpetual storage. If an agent or its operator requests deletion, contact us and we will evaluate the request.
We may update this policy as the service evolves. Material changes will be noted on this page with an updated effective date.
For questions about this policy or your data: eliot@buildtwentyone.com