Isolated instances, clear data handling, and BYOK control.
OpenClawAi.run is an online OpenClaw tool that asks you to bring your own model key and data. That only works if the security model is explicit. This page explains how instances are isolated, how credentials are stored, what data we keep, and what happens when you delete an instance.
Core promise
Each user gets a dedicated OpenClaw instance. Only authenticated access can reach that instance, and you can delete it at any time. Credentials are stored inside the instance, not shared across users, and deletions are permanent.
Scope of this policy
This security and privacy overview applies to the OpenClawAi.run website, the hosted OpenClaw instances, the console, and the API surface that supports those features. Public demo experiences are covered only when they are connected to your account.
If you require a formal data processing agreement or additional compliance documentation, contact support@openclawai.run before running production data.
Threats we actively mitigate
Security is easier to trust when the risk model is explicit. The hosted OpenClaw instance is designed to reduce the following common risks.
Unauthorized instance access
Instances are isolated and accessed through authenticated gateways, not open public ports.
Cross-user data exposure
Each runtime is separated so one user cannot read another user's files or credentials.
Credential leakage
BYOK credentials remain inside the instance and can be deleted instantly through the console.
Abuse of resources
Resource limits and auto-pause reduce the impact of mining, scanning, or abusive workloads.
Unbounded retention
Deletion removes instance data, and inactive instances are removed after one month.
Opaque incident handling
Status updates and incident timelines keep you informed when issues occur.
Isolation and access control
The most important security feature is isolation. Each OpenClawAi.run user receives a dedicated instance, and access is mediated through authenticated gateways.
Dedicated instance boundaries
Instances do not share file systems or runtime environments. This reduces cross-tenant exposure and keeps experiments separate, even if multiple users run similar workflows.
Authenticated access only
Access to instances is protected by authentication. Knowing a URL alone is not sufficient to reach an instance, and session checks verify the requesting user.
When combined, these controls ensure that the online OpenClaw tool is safe for BYOK usage and private workflows.
Data handling and retention
We collect the minimum data required to operate the service. User content stays in the instance unless you explicitly export it. Access logs are limited and used for security and reliability.
| Data type | Purpose | Retention |
|---|---|---|
| Account email | Account creation and support | While your account is active |
| Instance metadata | Lifecycle tracking and status display | Until instance deletion |
| Access logs | Security and troubleshooting | Limited retention window |
| Conversation or task data | Only inside your instance | Removed when the instance is deleted |
If you need a specific retention guarantee, contact support. We aim to keep retention minimal and aligned with the principle of least data.
BYOK credentials and deletion
BYOK is central to OpenClawAi.run. You control your model keys, and we design storage to keep them confined to your instance.
Where keys are stored
Model keys are stored inside the instance only. They are not shared across users and can be removed at any time through the console.
How to delete keys
You can delete credentials from the console or delete the entire instance. Deletion is permanent and cannot be undone.
OAuth support is not available in the current beta. We will document any new credential methods clearly before they launch.
Lifecycle controls you can trust
Auto-pause protects shared resources without hiding what happens. When an instance is idle, it pauses. If it remains inactive for one month, it is removed and cannot be recovered. These rules are visible in the console and reiterated in the docs so you are never surprised.
If you need longer retention or custom controls, contact support to discuss enterprise arrangements.
Abuse prevention and fair use
OpenClawAi.run is a free beta, so we enforce fair use rules to protect the community. Prohibited behavior includes abuse, scanning, mining, or attempts to bypass isolation boundaries.
Resource limits
Quotas on runtime, concurrency, and idle time keep the platform stable for everyone.
Enforcement
Accounts that violate policies may be paused or removed to protect platform integrity.
If you discover a vulnerability, report it to support@openclawai.run. We will respond as quickly as possible and coordinate a responsible disclosure process.
Security FAQ
Can someone access my instance if they know the URL?
No. Access requires authentication and session validation.
Do you store my data after I delete an instance?
No. Deletion removes instance data and cannot be undone.
Do you use my data to train models?
No. We do not use your content to train models.
Can I export data from an instance?
Export is not supported in the current beta. Contact support if you need export functionality.
Security is part of the product
We believe a hosted OpenClaw instance should be safe by default, clear in its promises, and explicit about limits. If you have questions, we are happy to walk through the details.