Zeroware
← Home
Legal

Agreements & policies

⚠️ These are starting templates for a Zeroware engagement. They are not legal advice — have your counsel review and adapt them before relying on them.

Master Service Agreement

Version 1.0-2026-07

This Master Service Agreement (“Agreement”) is between Zeroware (“Zeroware”, “we”) and the customer identified at sign-up (“Client”, “you”), effective on the date you accept it (“Effective Date”).

1. Services

Zeroware provides a governance and integrity layer (“Services”) that scores workloads on entropy and drift, gates wasteful or off-specification requests, self-heals on breach, and produces a tamper-evident audit trail. The Services run inside Client’s own cloud environment (“bring-your-own-cloud”). Zeroware governs on integrity signals only and does not access Client’s underlying data (see the Data Processing Addendum).

2. Fees & Payment

  • Value-share model. Fees are anchored to measured reductions in Client’s cloud spend. Client keeps the majority of savings; Zeroware’s fee is a fraction of the savings actually delivered, scoped to Client’s estate.
  • Onboarding down payment. A one-time onboarding down payment, sized to Client’s estate, is due before the ingress key is issued; it is applied to Client’s first invoice. Amounts at or below the card limit are paid by card; larger amounts are paid by bank wire.
  • Value-share bands. As delivered savings exceed 50% and 75%, a transparent value-share applies to the base fee, disclosed on Client’s dashboard.
  • Taxes. Fees are exclusive of applicable taxes.

3. Term & Termination

This Agreement begins on the Effective Date and continues until terminated. Either party may terminate for material breach not cured within 30 days’ notice. On termination, Client may remove the Zeroware kernel from its cloud at any time; accrued fees remain payable.

4. Client Data; Zero Access

Client retains all right, title, and interest in Client Data. Zeroware never inspects, copies, stores, or transmits Client Data; it processes only integrity signals and content fingerprints as described in the DPA. Zeroware is not a processor of Client Data.

5. Confidentiality

Each party will protect the other’s confidential information with reasonable care and use it only to perform under this Agreement.

6. Intellectual Property

Zeroware retains all right, title, and interest in the Services, the governance kernel, and all related technology and IP. No rights are granted except the limited right to use the Services during the term. Client retains all rights in Client Data.

7. Warranties & Disclaimers

Zeroware will perform the Services in a professional manner. EXCEPT AS EXPRESSLY STATED, THE SERVICES ARE PROVIDED “AS IS” WITHOUT WARRANTIES OF ANY KIND. Savings figures are estimates measured against Client’s baseline and are not guaranteed.

8. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, NEITHER PARTY IS LIABLE FOR INDIRECT OR CONSEQUENTIAL DAMAGES. EACH PARTY’S TOTAL LIABILITY IS LIMITED TO THE FEES PAID BY CLIENT IN THE 12 MONTHS BEFORE THE CLAIM.

9. Indemnification

Each party will defend and indemnify the other against third-party claims arising from its breach of this Agreement or violation of law.

10. Governing Law

This Agreement is governed by the laws of the State of [___], excluding conflict-of-laws rules. Disputes will be resolved in the state or federal courts located in [___].

11. General

This Agreement is the entire agreement between the parties and supersedes prior understandings. If any provision is unenforceable, the rest remains in effect. Neither party may assign without the other’s consent, except to a successor in interest.

Terms of Service

1. Acceptance

By creating an account or using getzeroware.com and the Services, you agree to these Terms and to the Master Service Agreement.

2. Accounts

You are responsible for the accuracy of your account information and for safeguarding your credentials, API keys, and two-factor device. Notify us promptly of any unauthorized use.

3. Acceptable Use

  • No unlawful, infringing, or abusive use.
  • No attempt to reverse-engineer, decompile, or circumvent the Services or their security.
  • No interference with or overloading of the platform.

4. API Keys

Ingress keys authenticate your traffic and must be kept secret. You are responsible for activity under your keys. Keys may be rotated or revoked.

5. Changes

We may update these Terms; material changes will be notified. Continued use constitutes acceptance.

6. Termination

We may suspend or terminate access for breach of these Terms. Sections that by their nature survive termination will survive.

Privacy Policy

1. What we collect

  • Account information: your work email, company name, and an estimate of your monthly cloud spend.
  • Integrity signals: from governed estates, we receive derived metrics and content fingerprints (e.g., entropy, drift, health scores, and hashes) — never your files, payloads, keystrokes, or raw data.
  • Usage & security data: log-ins, IP address at sign-up (for agreement records), and audit metadata.

2. What we do NOT collect

We do not access, copy, or store the contents of your workloads or data. The governance kernel runs inside your own cloud and scores signals, not content.

3. How we use it

To provide and secure the Services, compute savings and billing, communicate with you, and meet legal obligations. We do not sell personal information.

4. Security

Encryption in transit and at rest, tamper-evident audit logging, least-privilege access, and two-factor authentication for accounts.

5. Retention & your rights

We retain account and audit records for as long as your account is active and as required by law. You may request access, correction, or deletion of your personal information at hello@getzeroware.com.

6. Sub-processors

We use infrastructure providers (e.g., AWS) to operate the platform. Your governed data remains in your own cloud.

Data Processing Addendum

This Addendum forms part of the Agreement and governs any processing of personal data in connection with the Services.

1. Roles & scope

The Services are architected so that Zeroware does not access Client Data. Zeroware runs inside Client’s cloud boundary and processes only integrity signals and fingerprints (metadata), not the content of Client’s data. Accordingly, Zeroware acts as a processor solely with respect to limited account and integrity metadata, and is not a processor of Client’s underlying data.

2. Data location

Client Data never leaves Client’s own cloud environment. Zeroware does not transfer, export, or store Client Data.

3. Security measures

  • Encryption in transit and at rest for metadata Zeroware holds.
  • Tamper-evident, hash-chained audit of governance decisions.
  • Access controls, least privilege, and MFA.
  • Automatic rollback to last known-good state on integrity breach.

4. Sub-processors

Zeroware uses AWS to host account/metadata services. Client Data is not shared with sub-processors because it is never accessed.

5. Breach notification

Zeroware will notify Client without undue delay after becoming aware of a personal-data breach affecting metadata it processes.

6. Assistance & deletion

Zeroware will reasonably assist Client with data-subject requests and, on termination, delete or return account/metadata it holds, subject to legal retention.

© 2026 Zeroware · getzeroware.comHomeGet started