TERMS AND CONDITIONS

Last Updated: February 7, 2026

1. ACCEPTANCE OF TERMS

By accessing or using OpenClaw Cloud's OpenClaw VPS deployment service (the "Service"), you agree to be bound by these Terms and Conditions. If you do not agree, do not use the Service.

2. DESCRIPTION OF SERVICE

The Service provides fully managed OpenClaw deployment infrastructure. You provide your API keys from third-party AI providers (OpenAI, Anthropic, etc.), and we handle all VPS provisioning, configuration, and infrastructure management. The Service is provided "AS IS" and "AS AVAILABLE" without any warranties of any kind.

CRITICAL: We manage the infrastructure, but YOU are responsible for all costs, usage, and security of your third-party API accounts.

3. SOFTWARE DEFECTS, BUGS, AND KNOWN ISSUES

3.1 CRITICAL ACKNOWLEDGMENT: THIS SOFTWARE WILL HAVE BUGS

YOU EXPLICITLY ACKNOWLEDGE AND AGREE THAT:

The Service WILL contain bugs, defects, errors, and vulnerabilities, including but not limited to:

• Security vulnerabilities that could expose your API keys
• Configuration errors that could cause runaway API costs
• Memory leaks that could crash your deployments
• Logic errors that could cause incorrect behavior
• Race conditions that could corrupt data
• Integration bugs with OpenClaw software
• Compatibility issues with AI provider APIs
• Infrastructure provisioning failures
• Monitoring and alerting failures
• Billing or usage tracking errors
• Authentication or authorization bypasses
• Data corruption or loss bugs
• Performance degradation issues
• Resource exhaustion problems
• Deployment failures or partial deployments
• Network connectivity issues
• Database or storage failures
• Backup and recovery failures
• API rate limiting errors
• Timeout and retry logic failures

3.2 No Testing Guarantees

WE MAKE NO REPRESENTATIONS THAT:

• The Service has been adequately tested
• All bugs have been identified or fixed
• Security vulnerabilities have been discovered or patched
• The Service is production-ready or stable
• Code reviews have been conducted
• Security audits have been performed
• Load testing has been completed
• Disaster recovery has been tested
• Edge cases have been handled
• Error handling is comprehensive

3.3 Production Use at Your Own Risk

THE SERVICE MAY NOT BE SUITABLE FOR PRODUCTION USE. By using the Service, you acknowledge:

• Critical bugs may exist in production
• The Service may fail catastrophically at any time
• Data loss or corruption may occur without warning
• Security breaches may happen despite our efforts
• Performance may degrade unexpectedly
• Features may break without notice
• Updates may introduce new bugs
• We may deploy untested code to production
• Rollbacks may fail or be unavailable

3.4 Specific Known Risk Areas

WE SPECIFICALLY WARN YOU ABOUT:

API Key Security:

• Keys may be logged in plain text
• Keys may be stored insecurely
• Keys may be exposed in error messages
• Keys may be leaked through system vulnerabilities
• Encryption may be improperly implemented
• Access controls may be bypassable

Cost Control:

• Rate limiting may fail or be bypassed
• Usage monitoring may be inaccurate or delayed
• Alerts may not fire when expected
• Spending caps may not be enforced
• Billing calculations may be incorrect
• Cost estimates may be wildly inaccurate

Infrastructure Stability:

• Deployments may fail mid-process
• Services may crash unexpectedly
• Auto-restart may not work
• Health checks may give false positives
• Load balancing may be misconfigured
• Scaling may fail or cause outages

Data Integrity:

• Data may be corrupted or lost
• Backups may fail silently
• Recovery processes may not work
• Data migrations may fail
• Database transactions may be lost
• File systems may become corrupted

3.5 Zero Obligation to Fix Bugs

WE HAVE ABSOLUTELY NO OBLIGATION TO:

• Fix any bugs, ever
• Provide security patches
• Address vulnerabilities
• Respond to bug reports
• Investigate issues
• Improve the Service
• Maintain backward compatibility
• Provide workarounds
• Update dependencies
• Fix critical security issues

Even if a bug causes you catastrophic financial losses, we are under NO obligation to fix it.

3.6 Beta/Alpha Software Warning

THE SERVICE SHOULD BE CONSIDERED PERPETUAL BETA/ALPHA SOFTWARE:

• Features are experimental and may not work
• We may introduce breaking changes at any time
• Stability is not guaranteed
• Reliability is not assured
• Best practices may not be followed
• Industry standards may not be met

4. USER RESPONSIBILITIES

4.1 You Are Solely Responsible For:

• ALL API costs incurred on your OpenAI, Anthropic, or other AI provider accounts
• Monitoring your API usage and spending limits CONTINUOUSLY AND IN REAL-TIME
• Setting spending caps on your API provider accounts BEFORE FIRST USE
• Security and confidentiality of your API keys
• Revoking/rotating API keys if compromised
• All content generated through your API usage
• Compliance with all AI provider Terms of Service
• Compliance with all applicable laws and regulations
• Monitoring the Service for bugs, errors, unusual behavior, and failures
• Testing the Service thoroughly before any production use
• Implementing your own independent monitoring systems
• Any runaway costs from API calls
• Verifying that the Service is functioning as expected
• Maintaining access to your API provider dashboards
• Any legal issues arising from content generated via your APIs
• Creating and maintaining independent backups
• Implementing your own rate limiting and cost controls
• Regularly auditing logs and system behavior
• Assuming all features may be broken or buggy
• Planning for catastrophic failures

4.2 Bug Discovery and Monitoring Obligations

YOU MUST:

• Actively monitor the Service for bugs and defects YOURSELF
• NOT rely on us to detect, report, or notify you of ANY issues
• Implement your own comprehensive testing and validation
• Assume bugs exist in ALL features until proven otherwise
• Create fallback systems and contingency plans for when things break
• Monitor API usage independently of any tools we provide
• Verify billing and usage data accuracy yourself
• Test disaster recovery procedures regularly
• NOT assume any feature works correctly, ever
• Treat all Service functionality as potentially unreliable and buggy
• Build your own monitoring dashboards and alerts
• Log all API calls and costs independently
• Have manual override capabilities for all critical functions

4.3 API Key Acknowledgments and Risks

YOU UNDERSTAND AND AGREE THAT:

• We store your API keys to operate the Service
• API keys WILL be exposed in logs, errors, debugging output, and system breaches
• Bugs in our code WILL leak your API keys at some point
• Security vulnerabilities WILL expose your keys to potential attackers
• We may accidentally commit your keys to version control
• Error messages WILL include your keys
• Our logging systems WILL capture your keys in plain text
• Database dumps may contain your keys
• System administrators WILL have access to your keys
• We make ABSOLUTELY NO guarantee of API key security
• Compromised API keys could result in UNLIMITED CHARGES to your accounts (potentially millions of dollars)
• You MUST use API keys with strict spending limits SET BEFORE FIRST USE
• You MUST monitor your API provider billing MULTIPLE TIMES DAILY
• We are NOT responsible for any charges on your API accounts, NO MATTER HOW THEY OCCUR
• You should treat giving us your API keys as equivalent to giving us unrestricted access to charge your credit card

4.4 Prohibited Uses

You may NOT use the Service to:

• Deploy illegal content or services
• Violate AI provider Terms of Service
• Generate illegal, harmful, or malicious content
• Exceed rate limits or abuse AI provider services
• Share access with unauthorized third parties
• Violate intellectual property rights
• Conduct illegal activities of any kind
• Rely on the Service for mission-critical operations without multiple independent safeguards
• Use the Service without comprehensive testing and validation
• Deploy to production without extensive safety measures

4.5 Independent Verification Mandatory

YOU MUST INDEPENDENTLY:

• Verify ALL API charges and usage (don't trust our dashboards)
• Monitor infrastructure health with your own tools
• Check for security incidents using external monitoring
• Validate data integrity with independent checksums
• Test backup and recovery monthly at minimum
• Audit system logs with your own analysis tools
• Review access patterns for anomalies
• Confirm proper configuration using third-party validation
• NEVER rely solely on our monitoring, alerts, or reporting
• Maintain completely separate logging and monitoring infrastructure
• Have independent API usage tracking
• Set up external uptime monitoring
• Implement your own security scanning

5. DISCLAIMER OF WARRANTIES

5.1 NO WARRANTIES WHATSOEVER

THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO: MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, FITNESS FOR ANY PURPOSE, NON-INFRINGEMENT, ACCURACY OR RELIABILITY, UNINTERRUPTED OR ERROR-FREE OPERATION, SECURITY OR FREEDOM FROM VIRUSES OR ATTACKS, AVAILABILITY OR UPTIME, DATA INTEGRITY OR PRESERVATION, API KEY SECURITY OR CONFIDENTIALITY, INFRASTRUCTURE RELIABILITY, CORRECTNESS OF CODE OR LOGIC, ABSENCE OF BUGS OR DEFECTS, PROPER IMPLEMENTATION, COMPLIANCE WITH STANDARDS, QUALITY OR WORKMANSHIP.

WE DISCLAIM ALL WARRANTIES. IF IT CAN BE WARRANTED, WE DISCLAIM IT.

5.2 No Guarantee of Results or Functionality

We make ABSOLUTELY NO guarantee that the Service will meet ANY of your requirements, will actually work at all, that infrastructure will remain operational, that your API keys will remain secure, that API costs will be reasonable, that the Service will be compatible with AI providers, that OpenClaw will function properly, that data will be preserved, that third-party services will function properly, that you will receive ANY notice of issues, that spending limits will prevent runaway costs, that features will work as described, that updates won't break existing functionality, that the Service will remain available, that backups will work, that security measures will be effective, that monitoring will detect issues, that alerts will fire when they should, that documentation is accurate, or that anything will work correctly.

5.3 Infrastructure Disclaimer

We manage infrastructure on your behalf, but: we do NOT guarantee uptime or availability of ANY KIND. Infrastructure WILL fail at unexpected times. We are NOT responsible for infrastructure outages. We do NOT guarantee data backups or recovery. Configuration errors WILL occur. Security vulnerabilities WILL exist. Servers WILL crash without warning. Network issues WILL cause downtime. Storage WILL fail or become corrupted. Databases WILL become inconsistent or corrupt. Everything is unreliable and may break at any time.

5.4 API Integration Disclaimer

Regarding AI provider integrations: we do NOT guarantee API compatibility AT ALL. APIs MAY change without notice and break everything. Rate limits MAY be imposed, bypassed, or fail. Costs MAY vary wildly and unpredictably. We do NOT monitor your API spending reliably. We CANNOT prevent unauthorized API usage. API requests MAY fail silently. Retry logic MAY cause duplicate charges. Timeout handling MAY be buggy or missing. Error handling MAY be incomplete or incorrect.

5.5 Monitoring and Alerting Disclaimer

CRITICAL: DO NOT RELY ON OUR MONITORING OR ALERTS. Monitoring systems WILL have blind spots and bugs. Alerts WILL fail to fire when they should. Alert thresholds MAY be incorrectly configured. Notification delivery MAY fail or be delayed. Metrics MAY be inaccurate or missing. Logs MAY not capture critical events. Dashboards MAY show incorrect information. You MUST implement your own independent monitoring.

5.6 Security Disclaimer

WE MAKE NO SECURITY GUARANTEES: Security measures MAY be ineffective or improperly implemented. Encryption MAY be weak, broken, or missing. Access controls MAY be bypassable. Authentication MAY fail or be compromised. We may have CRITICAL security holes at any time.

5.7 Data Handling Disclaimer

Data MAY be lost at any time without warning. Backups MAY fail, be corrupted, or be unrestorable. Data MAY become corrupted during operation. Data consistency IS NOT guaranteed. Data MAY be exposed to unauthorized parties. Assume all your data will eventually be lost or compromised.

6. LIMITATION OF LIABILITY

6.1 Maximum Liability Cap

TO THE MAXIMUM EXTENT PERMITTED BY LAW, ANDURYL LIMITED AND ITS OFFICERS, DIRECTORS, EMPLOYEES, AGENTS, AND AFFILIATES SHALL NOT BE LIABLE FOR:

A) INDIRECT DAMAGES: Loss of profits, revenue, or business opportunities; loss of data or information; loss of goodwill or reputation; business interruption; cost of substitute services; any indirect, incidental, special, consequential, or punitive damages.

B) API-RELATED COSTS (CRITICAL): ANY AND ALL charges incurred on your AI provider accounts (OpenAI, Anthropic, etc.), regardless of amount. Runaway API costs from bugs, software defects, attacks, or misconfigurations. ANY API costs, regardless of who or what caused them.

C) BUG-RELATED DAMAGES: Any losses caused by software bugs, security vulnerabilities, configuration errors, data corruption, service outages, failed backups, or any code defects whatsoever.

D) SECURITY BREACH DAMAGES: Any losses from API key exposure, unauthorized access, data breaches, hacking, or any security incident.

E) DIRECT DAMAGES CAP: Even if we are found liable for direct damages, our total liability shall not exceed the LESSER of: the amount you paid us in the 12 months preceding the claim, OR $100 USD.

THIS $100 MAXIMUM LIABILITY CAP APPLIES EVEN IF: API charges reach millions of dollars, we had gross negligence, we had willful misconduct, we knew about the bugs and didn't fix them, the damages were entirely our fault, you lose your entire business, or you go bankrupt from API charges.

6.2 Exclusions Apply Regardless Of

The form of action, whether we were advised of the possibility, whether the remedy fails of its essential purpose, the amount of API charges incurred, whether damages were foreseeable, our own negligence, whether we knew about bugs, whether we failed to implement basic security, whether we failed to test code, whether we deployed broken code, whether we violated industry standards, whether we were reckless, or how catastrophic your losses are.

6.3 Third-Party Actions and Costs

We are ABSOLUTELY NOT responsible for: actions or failures of AI providers, billing or charges from AI providers FOR ANY REASON, security breaches, data loss from any cause, service outages, performance issues, API provider policy changes, account suspensions, third-party security vulnerabilities, supply chain attacks, infrastructure provider failures, network or connectivity issues, DDoS attacks or abuse.

7. INDEMNIFICATION

You agree to indemnify, defend, and hold harmless Anduryl Limited and its officers, directors, employees, agents, and affiliates from and against any and all claims, damages, obligations, losses, liabilities, costs, and expenses (including attorney's fees) arising from: your use of the Service, your violation of these Terms, your violation of any law, ANY API charges on your accounts, claims from AI providers, unauthorized usage of your API keys, data breaches, exposure of your API keys, any third-party claims related to your use.

THIS MEANS: If someone sues us because of your API charges, you pay our legal fees and any damages.

8. NO SUPPORT OR MAINTENANCE

We provide the Service on a self-service basis. We are under NO obligation to: provide technical support, maintain or update the Service, fix bugs or errors, respond to inquiries, monitor your deployments, or ensure Service availability. Any support provided is at our sole discretion and does not create any ongoing obligation.

9. THIRD-PARTY SERVICES AND API PROVIDERS

Your use of AI provider services is subject to their respective terms and conditions. We are NOT responsible for any costs, billing, service performance, security, or access issues related to AI providers. OpenClaw is third-party open-source software; we do NOT develop or maintain it and disclaim all liability related to OpenClaw software. We use third-party infrastructure providers and are NOT responsible for infrastructure outages, data loss, security breaches, or hardware failures.

10. API KEY SECURITY AND HANDLING

BY PROVIDING YOUR API KEYS, YOU ACKNOWLEDGE: We store your API keys in our systems to operate the Service. Despite reasonable security measures, WE CANNOT AND DO NOT GUARANTEE that your API keys will remain secure. Your API keys may be exposed through system breaches, infrastructure vulnerabilities, insider threats, software bugs, backup processes, legal demands, third-party breaches, or network interception.

Financial Risk: Compromised API keys could result in UNLIMITED charges to your accounts. We are NOT responsible for any API charges, regardless of cause. API costs can escalate to thousands or millions of dollars very quickly. We will NOT reimburse you for any API charges.

You MUST: Set maximum spending limits on ALL API provider accounts, enable billing alerts, monitor API usage daily, rotate API keys regularly, use API keys with minimum necessary permissions, and immediately revoke keys if suspicious activity is detected.

11. DATA AND PRIVACY

Any data processed through your API usage is subject to the AI provider's terms. We do NOT guarantee data confidentiality or privacy. We may have access to data passing through our infrastructure. We are NOT responsible for data breaches or exposure. We may log or store data for system operation. We may delete data at any time without notice. We may retain data indefinitely for system operation. You are responsible for maintaining your own backups.

12. SERVICE MODIFICATIONS AND TERMINATION

We may at any time: modify, suspend, or discontinue the Service, change pricing or features, terminate your access without notice or reason, delete your data and deployments, or modify these Terms. We shall have NO liability for any modification, suspension, or termination.

13. ASSUMPTION OF RISK

BY USING THE SERVICE, YOU ACKNOWLEDGE AND AGREE THAT: You understand the technical risks of managed infrastructure services. Infrastructure may fail at any time. Your API keys will be stored with inherent security risks. API key compromise could result in CATASTROPHIC financial losses. Bugs or misconfigurations could cause runaway API costs. You accept 100% financial responsibility for ALL API charges. System breaches may expose your API keys. The Service may be terminated at any time. Features may change or be removed without notice. You Accept ALL of These Risks.

14. COMPREHENSIVE FAILURE SCENARIOS

14.1 What WILL Go Wrong

Catastrophic API Cost Scenarios:

• Infinite Loop Bug: A bug creates an infinite retry loop, making millions of API calls. Cost: $50,000+.
• Rate Limit Bypass: Rate limiting fails, user makes 100,000 requests instead of 100. Cost: $25,000+.
• Leaked API Key: Your API key appears in our error logs and gets scraped by attackers. Cost: Unlimited.
• Failed Alert System: API costs are spiking but monitoring is broken and doesn't alert you for 3 days.
• Concurrent Request Bug: Race condition causes duplicate API calls. Your costs double or triple overnight.

Security Breach Scenarios:

• Plain Text Logging: We accidentally log your API key in plain text.
• SQL Injection: Attacker exploits SQL injection to dump all API keys.
• Misconfigured Storage: Backups containing your keys are publicly readable.
• Insider Threat: Employee copies all API keys before quitting.
• Third-Party Breach: Infrastructure provider gets hacked, your keys exposed.

14.2 Your Required Response Plan

BEFORE using the Service, you MUST have: external monitoring, manual kill switch (ability to revoke API keys in under 1 minute), budget alerts on AI provider side, hard spending caps on ALL API provider accounts, daily cost review process, alternative infrastructure ready, incident response plan, and cyber liability insurance if using for business.

14.3 Explicit Examples of Our Non-Liability

• Our bug causes infinite API loop. Your OpenAI bill: $87,000. Our liability: $0 (or max $100).
• We accidentally publish your API key to GitHub. Attackers rack up $340,000. Our liability: $0 (or max $100).
• Database corruption loses all your business data. Lost revenue: $2,000,000. Our liability: $0 (or max $100).
• Security breach exposes customer data, you face $5,000,000 lawsuit. Our liability: $0 (or max $100).
• Service down for 30 days during your critical period. Lost sales: $500,000. Our liability: $0 (or max $100).

15. RELEASE OF CLAIMS

You hereby RELEASE, WAIVE, AND DISCHARGE Anduryl Limited from any and all claims, demands, and damages of every kind and nature, known and unknown, arising out of or in any way connected with your use of the Service.

16. FORCE MAJEURE

We are not liable for any failure or delay in performance due to circumstances beyond our reasonable control, including acts of God, natural disasters, internet or infrastructure failures, third-party service outages, cyberattacks, government actions, or labor disputes.

17. GOVERNING LAW AND DISPUTES

These Terms shall be governed by the laws of Hong Kong, without regard to conflict of law provisions. Any disputes shall be resolved through binding arbitration in Hong Kong. You waive any right to a jury trial or class action. Any claim must be filed within ONE (1) YEAR of the event giving rise to the claim, or be forever barred.

18. SEVERABILITY

If any provision of these Terms is found to be unenforceable, the remaining provisions shall remain in full force and effect.

19. ENTIRE AGREEMENT

These Terms constitute the entire agreement between you and Anduryl Limited regarding the Service and supersede all prior agreements.

20. FINAL STARK WARNING

BEFORE YOU CLICK "I ACCEPT", UNDERSTAND THIS:

You are about to give your API keys (which are essentially credit cards with no limit) to a service that: has no professional security team, has not been security audited, WILL have bugs and vulnerabilities, makes ZERO guarantees about anything, takes ZERO responsibility for any costs you incur, could expose your keys at any moment, and limits liability to $100 even if you lose millions.

In plain English, you are agreeing that:

• Financial Risk: We can cause $1,000,000 in API charges through our bugs, and you can't sue us for more than $100.
• Security Risk: We can accidentally publish your API key on GitHub, and it's YOUR problem.
• Zero Support: We have no obligation to help you, ever, even in emergencies.
• No Monitoring: Our alerts may never work. You MUST monitor everything yourself.
• Data Loss: We can lose all your data tomorrow and owe you nothing.
• Bugs Everywhere: Assume EVERYTHING is broken until you verify otherwise.
• Your Responsibility: You are 100% responsible for EVERYTHING that happens.

Recommended Actions: Set HARD spending limits on every API provider account ($100 max recommended), set up billing alerts on the API provider side, review API costs daily, keep API key revocation process ready, have cyber liability insurance if this is for business.

21. ACCEPTANCE

BY USING THE SERVICE, YOU ACKNOWLEDGE THAT:

• You have read EVERY WORD of these Terms (all 22 sections)
• You understand these Terms COMPLETELY
• You agree to ALL disclaimers and limitations of liability
• You accept ALL risks associated with the Service
• You waive ALL claims against Anduryl Limited
• You understand we are NOT liable for API charges even if they reach millions
• You understand your API keys WILL be at risk of exposure
• You understand bugs and failures WILL occur
• You understand we have ZERO obligation to fix anything
• You understand our maximum liability is $100 no matter what happens
• You have set up independent monitoring and safeguards
• You have set spending limits on your API accounts BEFORE using this service
• You accept you might lose everything

22. CONTACT

For questions about these Terms: support@instantclaw.ai