Customer Terms of Service

These Customer Terms of Service (the “Terms”) govern access to and use of the Olive compute platform (the “Platform” or “Services”) provided by Olive Compute, Inc., a Delaware corporation having an address at 131 Continental Dr, Suite 305, Newark, DE 19713 (“Olive,” the “Company,” “we,” or “us”), and you, the person or entity using the Platform (the “Customer,” “you”). These Terms form a binding contract between Olive and the Customer.

By creating an account, submitting a job, or otherwise using the Services, you agree to these Terms. If you accept on behalf of an organization, you represent that you are authorized to bind it.

1. How Olive works (please read)

Olive sends your compute jobs to run on computers that other people own and operate (our “Device Owners”), routing them through our systems and running them inside an isolated space (a “sandbox”) on a Device Owner’s machine.

Olive runs short-lived, batch jobs. It is not a storage service. You submit a job, it runs once, and you retrieve the results. Olive does not keep your work for you to return to later, and there is no way to pause a job and resume it from where you left off. You should treat your inputs and results like a document in another application, such as Microsoft Word or Excel. Our advice is to save your own copies on your own systems so that you can come back to your work if you are not finished.

2. Acceptable use

You must use the Platform in compliance with all applicable laws. You may not submit, deploy, or run jobs that involve:

• Illegal activity, content whose creation or distribution violates applicable law, or acts of moral turpitude (conduct that gravely violates accepted standards of honesty or morality, such as fraud or exploitation);
• Malware, viruses, spyware, or code designed to damage, hijack, surveil, or exfiltrate from host environments;
• Unauthorized cryptocurrency mining;
• Attempts to break out of, bypass, or evade the sandbox (the isolated space in which your job runs), network isolation, signing, or verification systems;
• Mass surveillance, weapons targeting, or other high-risk military applications;
• Non-consensual sexual content, child sexual abuse material, or deepfakes depicting real individuals without consent;
• Content that depicts cruelty to animals or their mistreatment or abuse; or
• High-stakes automated decisions affecting people’s legal rights, safety, finances, or access to essential services without appropriate human oversight.

You are responsible for what you run. Olive does not proactively monitor the content of your jobs, and by design often cannot see it. The responsibility for keeping your use lawful and within these rules is yours. Olive reserves the right, but is not obligated, to investigate suspected violations, review job metadata, suspend or terminate access, preserve information, and cooperate with valid legal process. We act on credible reports and on legal requirements.

3. What you may submit (“Permitted Data”)

Because your job runs on computers operated by independent third parties who could, in principle, see it, you may submit only Permitted Data.

The simple test: if you would not be comfortable with an unknown member of the public seeing this data, do not submit it.

More formally, data is not Permitted Data if disclosing it to an unknown third party could harm you or anyone else, or would breach any legal, contractual, regulatory, or professional duty of confidentiality you owe.

Examples of what you may not submit (not a complete list):

• Anything you have a duty to keep confidential — for example, attorney–client privileged material, client or matter files, data covered by an NDA, trade secrets, or third-party data you handle under a data-processing or similar agreement.
• Sensitive or regulated personal data about people — health/medical data, financial-account or payment-card data, government IDs, biometric data, precise location, data about minors, student education records protected under FERPA (the Family Educational Rights and Privacy Act), or GDPR special-category data (health, biometrics, race/ethnicity, religion, sexual orientation, political views, union membership).
  (Note: Data that has been fully de-identified, so that no individual — including a minor — can be recognized, is treated differently; if your use case depends on this, such as education or research, confirm your approach with your own advisers.)
• Secrets and credentials — passwords, API keys, private keys, access tokens.
• Anything export-controlled, classified, or otherwise legally restricted from disclosure.

A note for confidential businesses.If your work is inherently confidential — for example, a law firm’s client matters, a healthcare provider’s patient records, or a school’s student records — that work is not appropriate for this network, no matter how careful you are. You can still use Olive for tasks involving only non-confidential or public information (for example, running a model over published court opinions or public datasets). For confidential workloads, the planned confidential-compute tier is the intended path.

You decide, and you are responsible. Only you know what obligations attach to your data, and Olive cannot see your content to check it. By submitting data, you represent and warrant that it is Permitted Data and that you have the right to process it on third-party machines. If you are unsure, do not submit it.

4. How your data is handled — what we protect, and what we do not protect

What we protect:

• Isolation. Your standard inference or compute job runs in a sandbox on the Device Owner’s machine — an isolated space that cannot reach the rest of that computer, its files, or its local network. When that job finishes, the sandbox and its contents are deleted. Training and other checkpointed workloads are currently gated off in private beta and would have separate retention terms before enablement.
• Integrity. We confirm your job ran correctly and was not tampered with, using cryptographically signed job files (Ed25519 signatures) and by re-running a sample of work on independent machines.

What we cannot promise: Because your job runs on a computer Olive does not own or control, we cannot promise that the owner of that computer is technically unable to view the data your job processes while it runs. To reduce this risk, Device Owners are contractually prohibitedfrom accessing your job’s contents, and Olive uses automated detection — including decoy jobs and sampled re-execution — to catch and remove bad actors. These measures deter and detect misuse but cannot make it physically impossible, which is why Olive today is built for non-confidential work (Section 3).

Note that this is a property of running on distributed third-party hardware — a deliberate design choice for this tier, not a temporary limitation of the beta. For work that needs guaranteed secrecy, a separate confidential-compute tier on specialized, hardware-secured machines is planned but not available, and these Terms do not promise it.

Data processing roles. Where your Job Content includes personal data, you are the controller and Olive acts as a processor. A Data Processing Addendum (DPA), including applicable Standard Contractual Clauses, will be made available on request and, once executed, is incorporated by reference.

5. Billing

• Simulated during beta. The Platform is in private beta. All prices, cost estimates, and ledgers are simulated. No charges are collected and no payments are due during beta.
• Transition to live billing. We may introduce live billing in U.S. dollars. We will give you at least 30 days’ notice by email or in-product notice before live billing begins, and live billing will be governed by the then-current pricing and any updated agreement.
• Metering. Once live, you will be billed based on metered consumption (for example, CPU/GPU time, memory, and data transfer).
• Failed jobs. Once live, billing is intended to apply to completed jobs. Credits or refunds for failed jobs (for example, node failure or failed verification) will be handled on a case-by-case basis.

6. Service Level Agreement (SLA)

A Service Level Agreement (“SLA”) is a commitment about how available and reliable a service will be.

• During beta. The Services, APIs, and dashboards are provided “as is” and “as available.” We do not make availability, performance, or uptime commitments during the private beta, and we do not offer service credits during this period.
• At production. If and when we move to production billing, we intend to publish service-level targets (for example, availability, job-success, and latency), together with any associated credits, in a production agreement. Those commitments will apply once published.

7. Confidentiality and the peer-execution model

• Acknowledgment. Because jobs run on third-party machines, you acknowledge that your code, data, prompts, and containers will be distributed to and run on hardware the Company does not control.
• Safeguards (in plain terms). The protections that apply are: each job runs in an isolated sandbox that cannot reach the host’s files or network; job files and results are cryptographically signed so tampering is detectable; a sample of jobs is re-run on independent machines to verify results; and Device Owners are contractually barred from accessing job contents, backed by automated detection.
• Scope of waiver. To the maximum extent permitted by law, you agree not to bring confidentiality-breach claims against the Company or Device Owners arising solely from execution of your job on peer devices, provided the Company has applied the safeguards above.
• Your representation. You represent that all data and models you upload are Permitted Data (Section 3) and that you have the rights to use and process them.
• Olive’s duties to you. Separately, the Company will protect your account credentials, API keys, and non-public business information that you share with us directly (as distinct from Job Content run on peer devices).

8. Upstream model licenses

If you run third-party or open-weight models made available on the Platform, you are solely responsible for complying with the license that applies to each model you use, including any attribution, notice, redistribution, or use-based conditions it imposes. The license that applies to each model is identified on our models page at olivecompute.com/models.

Where a model you run is offered under a license that includes use-based conditions or a prohibited-use policy (for example, certain community or custom licenses that are not standard permissive open-source licenses such as Apache 2.0 or MIT), those conditions and policies apply to your use of that model and are incorporated into these Terms by reference. You must not use the Platform in violation of any applicable model license.

9. Indemnification and limitation of liability

• Indemnification.You agree to indemnify and hold harmless the Company and its officers, directors, employees, and agents from third-party claims, damages, and reasonable expenses (including attorneys’ fees) arising from your own misconduct — specifically: (a) your breach of the Acceptable Use rules (Section 2); (b) your violation of third-party intellectual-property or privacy rights; or (c) your submission of data that is not Permitted Data (Section 3). (This is intentionally limited to harms you cause through misuse, not a general indemnity for using a beta service.)
• Limitation of liability. TO THE MAXIMUM EXTENT PERMITTED BY LAW, THE COMPANY WILL NOT BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR LOST PROFITS, DATA, OR USE. THE COMPANY’S TOTAL AGGREGATE LIABILITY WILL NOT EXCEED THE GREATER OF $100 OR THE TOTAL FEES YOU HAVE PAID THE COMPANY IN THE PRIOR 6 MONTHS.
• Savings clause. Nothing in these Terms limits liability that cannot be limited under applicable law (for example, for gross negligence or willful misconduct), or removes mandatory protections you have as a consumer under your local law.

10. Disputes and governing law

• Governing law. These Terms are governed by the laws of the State of Delaware, without regard to its conflict-of-laws rules, regardless of where you reside.
• Consumer savings clause. Nothing here removes protections you have under the mandatory consumer-protection or data-protection laws of your home country, state, or region (for example, for consumers in the EU, UK, or California). Where those laws give you rights these Terms cannot lawfully waive, those rights apply.
• Informal resolution first. Before starting a formal proceeding, contact us at support@olivecompute.com and give us 30 days to resolve the dispute informally.

MANDATORY BINDING INDIVIDUAL ARBITRATION AND CLASS ACTION WAIVER

PLEASE READ THIS SECTION CAREFULLY. IT AFFECTS YOUR LEGAL RIGHTS, INCLUDING YOUR RIGHT TO FILE A LAWSUIT IN COURT, TO HAVE A JURY HEAR YOUR CLAIMS, AND TO PARTICIPATE IN A CLASS ACTION.

• 1. BINDING ARBITRATION. YOU AND OLIVE AGREE THAT ANY DISPUTE, CLAIM, OR CONTROVERSY ARISING OUT OF OR RELATING TO THESE TERMS, THE PLATFORM, OR THE RELATIONSHIP BETWEEN US — WHETHER BASED IN CONTRACT, TORT, STATUTE, FRAUD, MISREPRESENTATION, OR ANY OTHER LEGAL THEORY — SHALL BE RESOLVED EXCLUSIVELY THROUGH BINDING INDIVIDUAL ARBITRATION, RATHER THAN IN A COURT OF LAW, ADMINISTERED BY JAMS UNDER ITS COMPREHENSIVE ARBITRATION RULES & PROCEDURES (OR, WHERE THE AMOUNT IN DISPUTE QUALIFIES, ITS STREAMLINED ARBITRATION RULES & PROCEDURES) AND, FOR ANY CUSTOMER WHO IS AN INDIVIDUAL CONSUMER, THE JAMS CONSUMER ARBITRATION MINIMUM STANDARDS OF PROCEDURAL FAIRNESS, SEATED IN DELAWARE.
• 2. CLASS ACTION WAIVER. YOU AND OLIVE EXPLICITLY AGREE THAT ALL DISPUTES MUST BE ARBITRATED OR LITIGATED ON AN INDIVIDUAL BASIS AND NOT ON A CLASS, COLLECTIVE, COORDINATED, CONSOLIDATED, OR REPRESENTATIVE BASIS. BY AGREEING TO THESE TERMS, YOU HEREBY WAIVE THE RIGHT TO FILE A CLASS ACTION, TO PARTICIPATE AS A CLASS REPRESENTATIVE, OR TO PARTICIPATE AS A CLASS MEMBER IN ANY PURPORTED CLASS, MASS, CONSOLIDATED, OR REPRESENTATIVE PROCEEDING AGAINST OLIVE. THE ARBITRATOR MAY NOT CONSOLIDATE MORE THAN ONE PERSON’S CLAIMS, AND MAY NOT OTHERWISE PRESIDE OVER ANY FORM OF A REPRESENTATIVE OR CLASS PROCEEDING. THE ARBITRATOR MAY AWARD DECLARATORY OR INJUNCTIVE RELIEF ONLY IN FAVOR OF THE INDIVIDUAL PARTY SEEKING RELIEF AND ONLY TO THE EXTENT NECESSARY TO PROVIDE RELIEF WARRANTED BY THAT PARTY’S INDIVIDUAL CLAIM.
• 3. MASS ARBITRATION PROVISION. IF 25 OR MORE SIMILAR ARBITRATION DEMANDS ARE FILED AGAINST THE COMPANY BY THE SAME OR COORDINATED COUNSEL WITHIN A 90-DAY PERIOD, THE JAMS MASS ARBITRATION PROCEDURES AND GUIDELINES WILL APPLY, INCLUDING THEIR FLAT MASS-ARBITRATION FILING FEE AND CONSOLIDATED PROCESS ADMINISTRATOR PROCEDURES. THIS PROVISION IS INTENDED TO PREVENT A COORDINATED MASS FILING FROM IMPOSING CRUSHING UPFRONT PER-CASE FEES DESIGNED TO FORCE SETTLEMENT RATHER THAN RESOLVE CLAIMS ON THE MERITS.
• 4. Carve-outs. Either party may (a) bring an individual claim in small-claims court if it qualifies, and (b) seek injunctive or other equitable relief in court to protect its intellectual property or confidential information, without first arbitrating.

11. Termination, suspension, and offboarding

• By you. You may stop using the Services and close your account at any time.
• By us. We may suspend or terminate access, without liability, if: (a) you violate Section 2; (b) your activity poses a security risk to the Platform or others; or (c) you fail to pay live fees when due.
• Offboarding and grace period. Because Olive runs short-lived jobs and is not durable storage (Section 1), you should retrieve and keep your own copy of any results as you go. On termination, we retain your account record for a 90-day grace period before deletion or de-identification, so that you have time to reactivate, unless you ask us to delete sooner or the law requires longer retention (see the Privacy Policy). Stored job outputs have an independent 24-hour retrieval window and are not kept for the 90-day account grace period; standard-job inputs are purged when the job reaches a final state. Training and other checkpointed workloads are currently gated off and will have separate terms if enabled.

12. Changes to these Terms

We may update these Terms. We will post changes, update the effective date, and, for material changes, notify you by email or in-product notice. Continued use after changes take effect constitutes acceptance.

13. Contact

Olive Compute, Inc.
Email: support@olivecompute.com
Address: 131 Continental Dr, Suite 305, Newark, DE 19713