# Terms of Service

**Effective date:** 2026-07-28  
**Operator:** SQLGuard Inc / DoggyBagg (“Operator,” “we,” “us”)  
**Contact:** hello@doggybagg.cc  
**Service:** SQLGuard (`https://sqlguard.io`, always-on `https://sqlguard-io.fly.dev`) — Execution Certificate Firewall for agent SQL authorization.

These Terms of Service (“Terms”) govern access to and use of SQLGuard APIs, MCP endpoints, websites, documentation, and related software (the “Service”). By accessing or using the Service—including via autonomous agents, scripts, wallets, MCP clients, or marketplace discovery—you agree to these Terms, the [Privacy Policy](/privacy), [AUP](/aup), [Disclaimer](/disclaimer), and [Refunds](/refunds) policy.

**Contract formation:** An unpaid `402` challenge is an offer. Completing Exact USDC settlement and retrying a paid route constitutes acceptance and purchase of the listed SKU. Calling MCP `initialize` / `sqlguard_handshake` or reading discovery docs does not waive these Terms.

## 1. Who we are

SQLGuard is operated by SQLGuard Inc / DoggyBagg, reachable at hello@doggybagg.cc. The Service is prepaid software tooling for attested SQL validation and authorize-before-mutate workflows. It is **not** a bank, custodian, exchange, law firm, insurer, auditor, or managed database provider.

## 2. Eligibility and agency

You represent that you have authority to bind the entity or agent system using the Service. If you operate an autonomous agent, **you remain fully responsible** for its actions, spends, Intent Mandates, certificates, and any production SQL it executes after verify/gate. “The agent did it” is not a defense.

## 3. The Service (what it is / is not)

SQLGuard may:

- sell prepaid credits and one-shot products via **x402 Exact** USDC on Base (`eip155:8453`) to the configured seller pay-to;
- evaluate proposed SQL against policy and an isolated sandbox (PGlite/Postgres);
- issue **Ed25519 Execution Certificates** (including Session slots and Mandate Bind artifacts);
- offer free tips (`/v1/probe`) and a free portable authorize check (`/v1/gate`).

SQLGuard does **not**:

- execute production database writes on your behalf on the public host (see §3.1);
- guarantee that a PASS certificate means SQL is safe, correct, legal, or compliant with your contracts or schemas;
- verify that any human actually authorized an Intent Mandate you submit;
- custody user funds beyond protocol-level settlement to the seller wallet;
- provide legal, tax, accounting, compliance, or security advice.

### 3.1 Executor fail-closed

`POST /v1/execute` is **optional** and **disabled by default** on the public host (`GET /health` → `executor.enabled`). You (or your agent runtime) hold the database URL and execute mutating SQL yourself **only after** a verified PASS (and/or successful `/v1/gate`). Payment for a certificate is **not** a production write grant.

### 3.2 Product SKUs (ABMP)

Live catalog controls prices (`GET /v1/catalog`). Current product families include:

| Product | Role |
|---------|------|
| Instant Cert (`POST /v1/cert`) | One Exact settle → one Ed25519 cert |
| Mandate Bind (`POST /v1/bind`) | Intent Mandate text hashed into signed cert (`mandate_hash`) |
| Session Cert (`POST /v1/session`) | One Exact settle → TTL window with N cert slots |
| Prepaid bundles (`/v1/credits/buy/*`) | Credits for `/v1/validate` |
| Free probe / GATE | Tip or portable check — **not** a paid warranty |

Unused Session slots expire at TTL with **no refund**. Slot burns (including FAIL certs) are final per [Refunds](/refunds).

### 3.3 Mandates and BIND

Mandate text is **user-supplied**. The Operator does **not** authenticate the human, review Intent Mandates for legal sufficiency, or warrant that SQL is within any real-world authorization. `mandate_hash` / `mandate_kind: abmp_intent` are cryptographic bindings of the bytes you sent—not legal approval, KYC, or a duty of care to third parties.

## 4. Accounts, agent IDs, and keys

You identify sessions using agent/wallet identifiers you control (e.g. `X-SQLGuard-Agent`). You are responsible for safeguarding private keys, payment authorizations, MCP credentials, and any secrets. The Operator never asks for your private keys. Do not share agent ids that hold credits.

## 5. Payments and credits

- SKUs are prepaid digital service units priced in USDC via x402 Exact on Base unless marked free.
- Settlement uses third-party facilitators (e.g. CDP / PayAI) and public blockchains. Confirmed on-chain transfers are **irreversible**.
- Credits are non-transferable, have no cash value, are not deposits, and are not securities.
- Refunds and re-credits: see [Refunds & Credits](/refunds). Except where required by law or as stated there, **USDC purchases are final**.
- Prices and SKUs may change; the live catalog and 402 challenge control the offer at purchase time.
- Operator/index wallets used for smoke tests do not create consumer warranties for third parties.

## 6. Acceptable use

You must not use the Service to attack or overload systems, bypass payment, launder funds, violate sanctions/AML/export laws, probe systems without authorization, submit illegal content (including CSAM), ship malware/exploits, or misrepresent certificates as warranties of production safety. See the [AUP](/aup).

## 7. Certificates and reliance

Execution Certificates attest a **sandbox run and policy check** under stated parameters (schema_hash, sql_hash, optional mandate_hash, TTL, status). Downstream systems that auto-apply SQL do so **at their own risk**. You must independently verify signature, expiry, hashes, business appropriateness, backups, and change-control **before** production mutation. Free `/v1/gate` is a technical check, not a professional sign-off.

## 8. Intellectual property and submissions

The Service, branding, and documentation are owned by the Operator or licensors. Open-source components remain under their licenses. You retain rights to SQL/DDL/mandate text you submit; you grant the Operator a limited license to process them solely to provide the Service. You warrant you have rights to submit that content. Copyright notices: [DMCA](/dmca).

## 9. Privacy and cookies

See [Privacy](/privacy) and [Cookies](/cookies). For platform customers needing a processor addendum: [DPA](/dpa).

## 10. Disclaimers

THE SERVICE IS PROVIDED “AS IS” AND “AS AVAILABLE” WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT. THE OPERATOR DOES NOT WARRANT UNINTERRUPTED OR ERROR-FREE OPERATION, CORRECTNESS OF POLICY/SANDBOX RESULTS, OR THAT CERTIFICATES PREVENT DATA LOSS, BREACH, OR LIABILITY.

## 11. Limitation of liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, THE OPERATOR’S TOTAL AGGREGATE LIABILITY ARISING OUT OF THE SERVICE SHALL NOT EXCEED THE GREATER OF (A) USDC AMOUNTS YOU PAID TO THE SERVICE FOR THE SPECIFIC SKU GIVING RISE TO THE CLAIM IN THE THIRTY (30) DAYS BEFORE THE CLAIM OR (B) TEN US DOLLARS (US$10). THE OPERATOR IS NOT LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR LOSS OF DATA, PROFITS, GOODWILL, OR BUSINESS INTERRUPTION—EVEN IF ADVISED OF THE POSSIBILITY.

## 12. Indemnity

You will defend, indemnify, and hold harmless the Operator and its officers from claims, damages, and costs (including reasonable attorneys’ fees) arising from your (or your agents’) use of the Service, payments, mandates, certificates, production SQL execution, content submissions, or violation of these Terms or law.

## 13. Export and sanctions

You may not use the Service if you are subject to US/OFAC sanctions or in a prohibited jurisdiction. You will not use the Service to violate export control or sanctions laws.

## 14. Termination

The Operator may suspend or terminate access for abuse, legal risk, non-payment, or operational reasons. You may stop using the Service at any time. Unused credits and Session slots may be forfeited on termination for cause or expiry as described in [Refunds](/refunds).

## 15. Changes

We may update these Terms by posting a revised version with a new effective date. Continued use after posting constitutes acceptance. Material payment changes appear in the live catalog/402 challenge.

## 16. Governing law; disputes

These Terms are governed by the laws of the State of Delaware and applicable United States federal law, excluding conflict-of-law rules. Exclusive venue for disputes is the state or federal courts located in Delaware, except where prohibited. You waive class actions to the extent permitted by law.

## 17. Contact

Legal / billing: hello@doggybagg.cc  
Security: [Security Policy](/security) · `/.well-known/security.txt`  
Legal index: [/legal](/legal)