Terms of Service

1. Beta status and service changes

The Service is a capped beta offered on a best-efforts basis. We may change or withdraw features, pricing, supported workload/model/runtime pairs, rate limits, provider lanes, and throughput. Unless a separate signed order says otherwise, there is no service-level agreement and no promise of capacity, latency, output quality, model availability, or successful completion. The catalog and quote in effect when a request is accepted control that request; a roadmap, benchmark, test, or registry entry is not an offer or capacity promise.

2. Accounts

You must be at least 18, legally able to enter these terms, based in the United States, and provide accurate account, billing, role, and location information. You are responsible for authorized users, activity under your account, and keeping credentials and API keys secret. Notify us immediately at contact@commoncompute.ai if you suspect compromise. We may request information needed for identity, payment, tax, sanctions, export, age, or location controls before enabling a feature or releasing funds.

3. Customer billing (prepaid credits)

• Billing draws against prepaid credit. You keep a payment card on file with our payments processor (Stripe) and use it to buy credit; each completed job is then drawn from that credit balance. The minimum credit purchase is US$10.00.
• Prices are quoted before every job and do not change mid-execution. Failed jobs are not billed, and retries are free. Charges are rounded up to the nearest whole cent, so one cent is the smallest amount we can bill. If we split a single job across several machines you are charged once for that job, not once per piece; items you submit together in a batch are billed individually. Work that records no measured usage is not billed at all.
• You must have a valid card on file and a positive credit balance to submit jobs. Credit is held against work in progress and drawn when it completes. We do not store full card numbers; card data is held by Stripe.
• Credit buys compute on this platform. It is not a deposit, does not earn interest, and is not redeemable for cash. Unused credit remains available on your account.
• Disputed charges must be raised within 60 days of the transaction. We reserve the right to suspend accounts with active chargebacks pending resolution.

For when refunds apply — including automatic non-billing of failed jobs — see the full Refund Policy.

3a. Provider classification

The current Provider Agreement is published for electronic acceptance. A newly enrolled computer is registered but remains out of dispatch until its account accepts the current version. Fleet-wide enrollment enforcement remains off during the transition and will be activated only after acceptance coverage is reviewed.

Providers are independent contractors, not employees, partners, joint venturers, or agents of Common Compute LLC. Providers control their own equipment, schedule, and methods of providing compute capacity.

4. Provider earnings and payouts

• Providers receive between 80% and 100% of the customer job price they complete, depending on the terms of their provider agreement:
• Standard providers (default): 80% per settled job. The platform take is a flat 20% of the customer job price, the same on every workload — it does not vary by job type.
• Grant recipients (founding fleet, early joiners): receive the percentage specified in their acceptance email, honored for the duration stated at grant time. Providers who join before October 1, 2026 receive a permanent 100% share — it does not expire. Accounts created on or after that date receive the standard rate above.
• Grants take precedence over the default take rate. If you hold a grant, it applies to the jobs you complete regardless of the standard rates above.
• Providers are paid per successfully completed task at the rates shown in the provider dashboard, which may change with 14 days’ notice. Changes to a grant’s terms are governed by the grant itself.
• Earnings accrue at job completion and pay out weekly via Stripe Connect. Stripe deposits to your linked bank account on its standard payout schedule (~2 business days) after each weekly payout. Accrued earnings are held only until the next weekly payout run.
• Tax reporting (e.g., Form 1099-K or 1099-NEC where applicable thresholds are met) is facilitated through Stripe Connect. Providers are solely responsible for their own income tax filings.
• Tasks that are fraudulent, produce manifestly wrong results, or violate Section 5 are not eligible for payout and may be clawed back.

5. Acceptable use

The Acceptable Use Policy is incorporated into these terms. Among other restrictions, you agree not to submit workloads or operate a provider in order to:

• Produce content that sexually exploits minors, or that depicts non-consensual intimate imagery.
• Generate content intended to harass, defame, or incite violence against a person or group.
• Develop, train, or operate malware, spyware, credential stealers, or offensive security tooling without written authorization.
• Mine cryptocurrency, run proof-of-work, or resell raw compute capacity.
• Evade export controls or sanctions, or process data from OFAC-embargoed jurisdictions.
• Attempt to de-anonymize, probe, or exfiltrate data from other tenants, providers, or our infrastructure.

Customers and providers must be based in the United States at this time and may not conceal location or identity to bypass that boundary. We may review workload metadata and provider telemetry to enforce this section and may review content where reasonably necessary to respond to abuse, security, rights, or legal reports. Violations may result in restriction, suspension, termination, content preservation or deletion, and a hold on unpaid earnings while we investigate. To report a concern, email contact@commoncompute.ai.

6. Data handling

Customer task inputs for terminal jobs become eligible for an early purge after a one-hour grace period. A separate sweep deletes stored task inputs and outputs after 30 days, and you can request deletion of an individual final job’s payloads earlier. An assigned provider machine receives the plaintext needed to execute the task but does not receive customer account information. Its operator controls that machine, so transport security, object-storage encryption, process isolation, contractual restrictions, and deletion controls do not make the plaintext technically inaccessible. See the Privacy Policy for the full data flow.

7. Intellectual property

You retain the rights you have in your inputs. You grant Common Compute, its infrastructure providers, and an assigned capacity provider a limited, non-exclusive license to host, transmit, cache, execute, transform, secure, meter, troubleshoot, and return your content solely to provide, protect, support, and account for the Service or comply with law. As between you and Common Compute, and to the extent the law and applicable model terms permit, you retain rights in output. Output may not be unique, accurate, non-infringing, or suitable for a purpose, and you are responsible for review and downstream use. We own the Common Compute software, SDKs, marks, documentation, and operational telemetry, subject to the Privacy Policy.

You agree not to:

• Reverse engineer, decompile, or disassemble the provider app, SDKs, or API, except to the extent applicable law makes this restriction unenforceable.
• Scrape, crawl, or systematically extract data from the service, or circumvent rate limits or access controls, other than through the documented SDK or API.
• Use access to the service — including as a provider — to build, train, or offer a competing distributed-compute or workload-routing product.
• Remove or obscure any proprietary or attribution notice on the software, SDKs, or documentation.

8. Warranty disclaimer

THE SERVICE IS PROVIDED “AS IS” AND “AS AVAILABLE”. WE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, AND NON-INFRINGEMENT. WE DO NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED OR ERROR-FREE, OR THAT INFERENCE OUTPUTS WILL BE ACCURATE FOR YOUR USE CASE.

9. Limitation of liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, OUR AGGREGATE LIABILITY ARISING OUT OF OR RELATING TO THESE TERMS OR THE SERVICE IS CAPPED AT THE GREATER OF (A) THE AMOUNT YOU PAID US FOR COMPUTE IN THE TWELVE MONTHS PRECEDING THE CLAIM, OR (B) US$100. WE ARE NOT LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES.

9a. Indemnification

Provider indemnifies Common Compute LLC against claims arising from Provider’s breach of these Terms or unlawful conduct. Common Compute LLC indemnifies Provider against intellectual-property infringement claims arising solely from Common Compute LLC’s platform infrastructure.

9b. Data-processing terms

A reviewed United States DPA framework is available to qualified business customers by separately signed order. It is not automatically incorporated into these terms and does not make provider-operated plaintext execution technically confidential. See the DPA status and framework before submitting data that requires processor terms or a specific routing boundary.

10. Termination

You may close your account at any time. We may suspend or terminate accounts for breach of these terms, abusive use, or prolonged inactivity with written notice. On termination, any legacy pre-paid credit balance remaining from before the move to real-time billing may be refunded on a pro-rata basis, less any processing fees.

11. Governing law and disputes

These terms are governed by the laws of the State of Utah, USA, without regard to conflicts of law. Disputes will be resolved by binding arbitration in Utah under the rules of the American Arbitration Association, except that either party may seek injunctive relief in court to protect intellectual property or confidential information.

12. Changes

We may update these terms. A substantive update receives a new dated version. Material changes will be announced by email to the address on your account at least 14 days before they take effect unless an urgent legal or security change requires faster action. Continued use after the effective date constitutes acceptance where permitted; we may require affirmative re-acceptance for a material change.

13. Contact

Questions, disclosure requests, or legal notices: contact@commoncompute.ai.

14. General

These terms, the Privacy Policy, Acceptable Use Policy, Refund Policy, any applicable Provider Agreement, and a signed order are the entire agreement for the Service. A role-specific agreement controls a direct conflict for that role. If a provision is unenforceable, it will be limited to the minimum extent needed and the rest remains effective. Failure to enforce a provision is not a waiver. You may not assign these terms without our written consent; we may assign them with a merger, financing, reorganization, or sale of the relevant business.