Terms of Use - unsandbox.com

1. Service Description

unsandbox.com provides secure code execution environments accessible via API. The service offers:

Executions: Synchronous or asynchronous code execution across 42+ programming languages, destroyed after processing by default
Sessions: Long-running interactive environments with terminal multiplexer support
Services: Persistent containers with freeze/unfreeze capability to manage concurrency allocation
Snapshots: Point-in-time backups of services or sessions that preserve complete state for later restoration
Environment Vault: Encrypted storage for environment variables and secrets, injected into services at runtime
Service Domains: Each service receives a public URL (*.on.unsandbox.com) and can optionally use custom domains via CNAME
Resource Scaling: Services support configurable vCPU (1-8 cores), each vCPU provides 2GB RAM

Rate limits and concurrency are configurable based on pricing tier.

2. Acceptable Use

You agree to use the service only for lawful purposes. Prohibited activities include:

Attempting to circumvent rate limits or security measures
Unauthorized access attempts to underlying infrastructure
Executing code that generates illegal content or facilitates illegal activities
Cryptocurrency mining or resource-intensive operations beyond tier limits
Denial of service attacks or deliberate service disruption
Storing or processing illegal content
Reverse engineering or attempting to extract service internals

3. API Keys & Payment

API Key Structure:

Each purchase creates a public key (unsb-pk-...) and secret key (unsb-sk-...) pair
Keys cannot be rotated - both expire together based on tier duration
If keys are lost or compromised, you must purchase a new key pair
You are responsible for securing your keys - we cannot recover lost keys

Payment Terms:

Payments accepted via Stripe (credit/debit cards) and cryptocurrency (Bitcoin, Litecoin, Monero, Dogecoin)
All sales are final - no refunds or chargebacks after key delivery
All payments are non-refundable once API key is generated and delivered
Cryptocurrency payments are final after required confirmations
Keys can be funded/extended at any time before or after expiration

Cryptocurrency Quote Refund Policy (9%% Restocking Fee):

Refund Address Required: You must provide a valid refund address when creating a quote. Refunds cannot be processed without one
Expired Quote Payments: If you send payment after a quote expires (1 hour), you will receive a 91%% refund with a 9%% restocking fee deducted
Underpayments: Partial payments that expire before full amount is received will be refunded at 91%% of the amount sent
Overpayments: Excess amounts beyond the quoted price will be refunded at 91%% (9%% restocking fee on the excess only)
Refund Timing: Refunds are processed automatically after incoming payments receive required confirmations (10 for XMR, 6 for DOGE)
Minimum Refund Threshold: Refunds below $0.069 USD value are not economically viable and will not be processed
No Refund After Key Delivery: Once a payment is confirmed and an API key is generated, no refunds are possible

4. Service Limits & Guarantees

Rate Limits:

Freeloader (Tier -1): 1 execution per 42 seconds, 1 concurrent
Paid tiers (1-32): RPM = tier × 7, concurrency increases every 4 tiers
Example - Tier 1: 7 RPM, 1 concurrent ($7/month)
Example - Tier 13: 91 RPM, 4 concurrent ($91/month)
Example - Tier 32: 224 RPM, 8 concurrent ($224/month)

Service Level:

Service provided "as-is" with reasonable uptime expectations
No formal SLA - we make best efforts for availability
Scheduled maintenance will be announced when possible
We reserve right to modify or discontinue features with notice

5. Execution Environment

Executions:

Executions can be synchronous (wait for result) or asynchronous (poll for result)
Containers are destroyed after processing by default - no persistent state
Code executes in isolated containers with resource limits
Network access may be restricted or filtered
Execution time limits apply per tier
File system access is temporary and ephemeral

Interactive Sessions:

Sessions provide long-running interactive environments with terminal multiplexer support
Sessions persist state between commands within their allocated time
Session limits and durations vary by pricing tier
Sessions may be terminated due to inactivity or resource limits

Services:

Services are persistent containers that can run background applications
Services can be frozen to release concurrency allocation while preserving state
Frozen services do not count against your concurrency limit
Services can be unfrozen on demand to resume operation
Service availability and limits depend on your pricing tier
All data within a service persists until you explicitly destroy it
You are responsible for managing data stored within your services

Snapshots:

Snapshots capture the complete state of a service or session at a specific point in time
Snapshots include all files, installed packages, environment variables, and application state
Snapshots can be used to restore services or sessions to a previous state
Snapshots remain stored until you explicitly delete them
Snapshot storage limits depend on your pricing tier
Creating snapshots of services with sensitive data stores that data in the snapshot
You are responsible for managing and deleting snapshots containing sensitive information

Environment Vault:

Services support encrypted environment variable storage via the Environment Vault
Vault contents are encrypted at rest and injected into the service container at runtime
You are responsible for managing secrets stored in the vault
Vault contents are included in snapshots of the service
Deleting a vault or destroying a service permanently removes the stored secrets

Service Domains:

Each service receives a public URL under *.on.unsandbox.com accessible from the internet
You may configure custom domains (e.g., www.example.com) by pointing a CNAME record to your service URL
TLS certificates for custom domains are provisioned automatically
You are responsible for all content served through your service domain
Services exposed via public domains are subject to the same acceptable use policies
We reserve the right to revoke domain access for services that violate these terms

Resource Scaling:

Services can be configured with 1 to 8 vCPUs, each vCPU providing 2GB of RAM
Resource allocation is set at service creation and can be changed via resize
Higher resource allocations may be subject to availability on pool nodes

6. Content & Ownership

Your Code:

You retain all ownership of code you submit for execution
We receive a limited license to execute and store your code as needed to provide the service
Standard execution code and outputs are not permanently stored
You are responsible for any code you execute

Service and Snapshot Data:

You retain ownership of all data stored within your services and snapshots
Data stored in services persists until you destroy the service
Snapshot data persists until you delete the snapshot
We do not access, review, or use your service or snapshot data except as needed for service operation
You are solely responsible for ensuring you have rights to store any data in services or snapshots
Upon service destruction or snapshot deletion, data is permanently removed and cannot be recovered

7. Privacy & Data

Data Collection:

IP addresses collected for rate limiting and abuse prevention
Email addresses optional - only for support and key delivery
Execution requests processed and discarded (not logged permanently)
Payment data stored only for transaction processing
See Privacy Policy for complete details

Persistent Data (Services and Snapshots):

Service data is stored for the lifetime of the service
Snapshot data is stored until you explicitly delete the snapshot
You control when services and snapshots are deleted
Upon API key expiration, services and snapshots may be retained for a grace period
After the grace period, inactive services and snapshots may be automatically deleted
We recommend exporting important data before API key expiration

8. Partner & Agent Access

Third-party partners and AI agents may interact with the service on behalf of end users:

Partners can create API keys and invoices on behalf of their users via authenticated API endpoints
Partner access requires separate HMAC authentication credentials
Partners are responsible for ensuring their users comply with these Terms of Use
AI agents may autonomously provision keys, create services, and execute code using the API
The API key holder is responsible for all actions taken with their key, whether by human or automated agent

9. Sudo Protection & Audit Log

Sudo OTP Confirmation:

Destructive operations (deleting services, sessions, snapshots, images, and unlocking resources) may require email confirmation when sudo protection is enabled
When triggered, a one-time code is sent to the email address registered with your API key
Each OTP is bound to the specific destructive action requested and cannot be reused for a different operation
You may disable sudo protection from the console settings page at your own risk

Contacts & Team Access:

API key owners can invite additional contacts to share operational access
Contacts are assigned roles: owner (full control including contact management), operator (receives sudo OTP codes for destructive operations), or reader (view-only access)
When sudo is triggered, all contacts with operator or owner role receive unique one-time codes
Any single valid code from any authorized contact is sufficient to confirm the operation
The last owner contact cannot be removed or demoted to prevent lockout
You are responsible for managing who has contact access to your API key

Audit Log:

All destructive operations are logged in an immutable audit trail regardless of whether sudo protection is enabled
You acknowledge that your API key identifier, IP address, and operation details are recorded for every destructive action
When a contact verifies a sudo OTP, the specific contact email is attributed in the audit entry
Audit log entries cannot be modified or deleted

Anonymous Mode:

API keys without an associated email address operate in anonymous mode without sudo protection
Destructive operations in anonymous mode proceed without OTP confirmation
You can claim an API key by adding an email address from the console settings page

API Key Security:

You are responsible for the security of your API key credentials
If sudo protection is enabled, a one-time code will be sent to the registered email before destructive operations proceed
Sudo protection is a safeguard, not a guarantee - you remain responsible for key security

10. Account Suspension

We reserve the right to suspend or terminate API keys for:

Violation of these Terms of Use
Abusive behavior or excessive resource consumption
Fraudulent payment or chargebacks
Illegal activities or content generation
Security threats to service or other users
Storing prohibited content in services or snapshots

Suspended keys forfeit remaining time - no refunds for violations. Upon suspension or termination, all associated services and snapshots may be immediately destroyed without prior notice.

11. Disclaimers & Liability

Service Disclaimers:

Service provided "AS-IS" without warranties of any kind
No guarantee of code execution accuracy or reliability
We take no liability for any damages, losses, or issues arising from service use
Not liable for data loss, execution errors, or service interruptions
Not responsible for content generated by user code
Not liable for financial losses, business interruption, or consequential damages
Use of this service is entirely at your own risk

Services and Snapshots Disclaimers:

Services and snapshots are provided without guarantees of availability or durability
We are not liable for loss of data stored in services or snapshots
Infrastructure failures, security incidents, or other events may result in data loss
You are responsible for maintaining your own backups of critical data
Snapshots are not a substitute for proper backup procedures
We make no guarantee that services or snapshots will be recoverable after any failure

12. Open Source

Parts of unsandbox.com infrastructure may be open-sourced. Code available at our Git repository is provided under respective open source licenses. Community contributions are welcome.

13. Modifications

We reserve the right to modify these Terms of Use at any time. Continued use of the service after modifications constitutes acceptance. Major changes will be announced via service notifications.

14. Governing Law

These terms are governed by the laws of the United States. Any disputes shall be resolved in accordance with US jurisdiction.