---
title: "Terms of Service"
version: 2026-10-18.1
effective: 2026-10-18
reviewed_by: null
canonical: https://brdg2b.ai/legal/terms
---

# Terms of Service

> **Draft pending review by counsel — not yet in force.**

Version 2026-10-18.1, effective 2026-10-18. Bridge to Brands is a product of RunOps Inc.

## In short

- You confirm you can bind your business and that it holds valid dealer accounts with every brand you connect.
- Bridge to Brands acts on your instructions. Anything done with your sessions, API keys or connected AI agents is your action.
- Orders are your contracts with the brand. Submitted orders are binding and cost money; you control caps, confirmation and who may submit.
- We store your portal passwords encrypted and use them only to run the service; you remain responsible for each brand's dealer terms.
- Usage is metered but not billed until you accept a published rate card. Liability is capped; you indemnify us for orders and misuse.
- Bridge to Brands is a product of RunOps Inc.

## 1. Who we are and what these Terms cover

1.1 Bridge to Brands ("**the Service**", "**we**", "**us**") is a product of **RunOps Inc.**, a [STATE] corporation with its principal office at [ADDRESS] ("**RunOps**"). Notices to us go to [NOTICE EMAIL].

1.2 These Terms of Service ("**Terms**") form a contract between RunOps and the business that creates a Bridge to Brands account (the "**Retailer**", "**you**"). They govern the web application at app.brdg2b.ai, the REST API at api.brdg2b.ai, the MCP server at mcp.brdg2b.ai and any related documentation.

1.3 The following documents are part of these Terms: the [Order Authorisation Acknowledgement](/legal/order-authorisation), the [Acceptable Use Policy](/legal/acceptable-use), the [Privacy Policy](/legal/privacy) and the [Data Processing Addendum](/legal/dpa). If they conflict, the order of precedence is: the Data Processing Addendum (for personal data only), these Terms, the Order Authorisation Acknowledgement, the Acceptable Use Policy.

## 2. Definitions

- "**Account**": the Retailer's workspace in the Service, also called a tenant.
- "**Owner**": a User with the owner role on the Account.
- "**User**": a person the Retailer has invited to the Account.
- "**Brand**": a manufacturer or vendor that sells to the Retailer at wholesale through a dealer portal.
- "**Dealer Portal**": a Brand's (or its platform's) password-protected business-to-business website.
- "**Portal Credentials**": the username, password and related secrets the Retailer uses to sign in to a Dealer Portal.
- "**API Key**": a secret issued by the Service that lets software act on the Account, with the scopes the Retailer chooses.
- "**AI Agent**": any software, including third-party AI systems such as Claude or ChatGPT, that the Retailer connects to the Service through an API Key or an OAuth grant.
- "**Stage**": to place an order into a Brand's Dealer Portal as an unsubmitted basket or draft.
- "**Submit**": to complete the Dealer Portal's order-placement step so that the Brand receives a purchase order.
- "**Order**": any order the Service Stages or Submits for the Account.
- "**Caps**": the per-order and per-day unit, line and dollar limits set on the Account.

## 3. Authority to bind the Retailer

3.1 The person who accepts these Terms represents and warrants that they are authorised to bind the Retailer to them.

3.2 The Retailer represents and warrants that, for every Brand it connects, it holds a valid dealer account with that Brand, it is entitled to use the Portal Credentials it provides, and its use of that Dealer Portal through the Service is permitted by its agreement with the Brand.

3.3 The Retailer is responsible for its Users and for keeping the list of Users, their roles and their access current.

## 4. Bridge to Brands acts as instructed agent

4.1 The Service acts on the Retailer's instructions, given through its Users, its API Keys and the AI Agents it connects, to read from and write to the Retailer's own Dealer Portal accounts.

4.2 Any action taken with a valid session, API Key or OAuth grant for the Account is the Retailer's action. We do not decide what to order, for whom, or when.

4.3 We do not act for any Brand. We are not the Brand's agent, distributor or reseller.

## 5. Orders are the Retailer's contracts with Brands

5.1 Every Order, whether Staged or Submitted, is a purchase order from the Retailer to the Brand, governed by the Retailer's dealer terms with that Brand.

5.2 RunOps is not a party to any Order. We do not sell goods, take title, collect payment for goods, or guarantee that a Brand will accept an Order or honour any price, availability, delivery date, allocation, return or cancellation.

5.3 Availability, prices and delivery windows shown by the Service are read from the Dealer Portal at the time stated (`as_of`) and may change before an Order is placed.

## 6. Financial consequences of submitted orders

6.1 **Orders Submitted through the Service create binding financial obligations between the Retailer and the Brand.** They may result in invoices, shipments, minimums, freight charges and restocking or cancellation fees under the Brand's terms.

6.2 The Retailer controls, and is responsible for: the Caps on its Account; whether each Brand is set to stage only, submit with human confirmation, or submit; which Users may confirm; which API Keys carry the `orders:submit` scope; and which AI Agents it connects.

6.3 The Retailer is responsible for every Order placed with its sessions, API Keys or Portal Credentials, including Orders placed by AI Agents it connected, whether or not a person reviewed them first.

6.4 Submitting is available only for Brands whose submit path we have verified on a live account, and only where the Retailer has enabled it. Where the outcome of a Submit cannot be determined, the Service marks the Order "submit unknown", does not retry it, and checks the Dealer Portal's order history; until that check resolves, the Retailer should treat the Order as possibly placed. The [Order Authorisation Acknowledgement](/legal/order-authorisation) sets this out in plain terms and is accepted separately.

## 7. Dealer-portal credentials

7.1 The Retailer authorises RunOps to store its Portal Credentials in encrypted form and to use them solely to provide the Service to the Retailer.

7.2 Portal Credentials are entered only in the web application. They are never readable through an API Key, an OAuth grant or an AI Agent, and are decrypted only by the component that signs in to the Dealer Portal.

7.3 The Retailer is responsible for complying with each Brand's dealer and portal terms, including any terms about automated access. We may suspend or remove a connection at any time if a Brand objects to it, if the Dealer Portal reports the account as misused, or if we believe the connection breaches a Brand's terms.

7.4 The Retailer must tell us promptly if Portal Credentials change or are compromised, and may disconnect a Brand at any time.

## 8. API keys and the MCP server

8.1 API Keys are confidential. The Retailer must not share them outside its business, embed them in public code, or let anyone use them in breach of the Acceptable Use Policy.

8.2 Rate limits, scopes and other technical limits described in the documentation apply and are part of the Service. Portal pacing is set by us and cannot be changed by the Retailer.

## 9. AI agents

9.1 AI Agents are third-party systems. Their output, recommendations and decisions are not ours, and we do not warrant them.

9.2 The Retailer is responsible for reviewing what its AI Agents do. The confirmation step, Caps, scopes and kill switches exist so the Retailer can keep a person in control; the Retailer decides how to use them.

9.3 Content returned from Dealer Portals is data, not instructions. We mark it as such for AI Agents, but we cannot prevent a third-party AI system from misreading it.

## 10. Fees

10.1 Usage is metered from the first day (searches, results, Orders, lines and units, per API Key).

10.2 No fees are charged until we publish a rate card and the Retailer accepts it. We will give at least 30 days' notice before any pricing takes effect or changes.

10.3 Fees for goods ordered from Brands are owed to the Brand under the Retailer's dealer terms, not to RunOps.

## 11. Availability and beta

11.1 The Service is provided on a best-effort basis during its beta period. There is no service-level agreement until we publish one.

11.2 Dealer Portals are operated by Brands and their platforms. Their outages, changes, rate limits and errors are outside our control; the Service reports them (for example `portal_down` or `portal_changed`) rather than guaranteeing around them.

## 12. Warranties and disclaimers

12.1 Each party warrants that it will comply with laws that apply to it in connection with the Service.

12.2 Except as stated in these Terms, the Service is provided "as is" and "as available". To the extent the law allows, RunOps disclaims all other warranties, express or implied, including merchantability, fitness for a particular purpose, non-infringement, and accuracy of data read from Dealer Portals.

## 13. Limitation of liability

13.1 **Exclusion of consequential damages.** To the extent the law allows, neither party is liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, revenue, goodwill or data, however caused.

13.2 **Cap.** To the extent the law allows, RunOps' total liability arising out of or relating to these Terms in any 12-month period is limited to the greater of (a) the fees the Retailer paid RunOps in the 12 months before the event giving rise to the claim and (b) [FIXED AMOUNT] US dollars while the Service is free.

13.3 **Carve-outs.** The cap and exclusion do not apply to [CARVE-OUTS TO BE SPECIFIED BY COUNSEL, for example liability that cannot be limited by law, a party's indemnity obligations, or breach of confidentiality].

13.4 RunOps is not liable for the content, acceptance, price, fulfilment or cancellation of any Order, which are matters between the Retailer and the Brand.

## 14. Indemnity

14.1 The Retailer will defend and indemnify RunOps against third-party claims, and related losses and reasonable costs, arising from: (a) Orders placed with the Retailer's sessions, API Keys, Portal Credentials or AI Agents; (b) the Retailer's use of Portal Credentials, including any breach of a Brand's dealer or portal terms; (c) unlawful use of the Service or breach of the Acceptable Use Policy; and (d) consumer personal data the Retailer provides for drop-ship Orders without a lawful basis.

14.2 [RUNOPS INDEMNITY, IF ANY, TO BE SPECIFIED BY COUNSEL.]

## 15. Data protection

15.1 The [Privacy Policy](/legal/privacy) and the [Data Processing Addendum](/legal/dpa) are incorporated into these Terms.

15.2 For consumer personal data in drop-ship Orders, the Retailer is the controller and RunOps is its processor. Brands receive that data as independent controllers when an Order reaches them.

15.3 Retention follows the schedule in the Privacy Policy; in particular, sealed consumer drop-ship data is purged 90 days after the Order reaches a final state.

15.4 **Portal-window recordings.** When a User works in a Brand's Dealer Portal inside the Service (the "portal window"), RunOps may record the requests and responses exchanged between the Service and that Brand's own portal during the session. Passwords, session cookies, tokens and other credentials, and personal data (names, e-mail addresses, phone numbers, street addresses, card numbers and drop-ship consumer details) are removed before anything is stored. Recordings are used only to build and improve the Service's Brand integrations, are visible only to RunOps staff, are never shown to other customers or replayed against a Dealer Portal, and are deleted after 180 days. Recording starts only once the Owner has accepted the version of these Terms that contains this clause.

## 16. Suspension and termination

16.1 The Retailer may stop using the Service and close the Account at any time.

16.2 RunOps may suspend an API Key, a Brand connection or the Account immediately where needed to protect the Service, a Brand, the Retailer or third parties, including for suspected credential compromise, a breach of these Terms or the Acceptable Use Policy, a Brand objection, or non-payment once fees apply. We will tell the Owner what was suspended and why, unless the law prevents it.

16.3 Either party may terminate these Terms for convenience on [30] days' written notice, or immediately for the other party's material breach that is not cured within [15] days of notice.

16.4 On termination, access ends, API Keys and OAuth grants are revoked, and Portal Credentials are deleted. Sections 5, 6.3, 12 to 15, 17 and 18 survive.

## 17. Export of data

17.1 Before and for [30] days after termination, the Owner may export the Account's Orders, usage records and acceptance history in a machine-readable format. After that period we delete Account data, except records we must keep by law or for security, which we keep only as long as required.

## 18. Governing law and disputes

18.1 These Terms are governed by the laws of the State of [STATE], without regard to its conflict-of-laws rules.

18.2 Disputes will be resolved [IN THE STATE OR FEDERAL COURTS LOCATED IN [COUNTY, STATE] / BY BINDING ARBITRATION UNDER [RULES] — TO BE DECIDED BY COUNSEL], and each party consents to that venue.

## 19. Changes to these Terms

19.1 We may change these Terms. Each version carries a version string and effective date, and earlier versions are kept in the change log below.

19.2 For a material change we will notify the Owner at least [30] days in advance where reasonably possible and ask the Owner to accept the new version. Owners have a 14-day grace period after the effective date; after that, the Account cannot place Orders or make other changes through the app, the REST API or the MCP server until the new version is accepted.

## 20. Attribution and general terms

20.1 **Attribution.** Bridge to Brands is a product of RunOps Inc.

20.2 These Terms are the entire agreement on their subject. If a provision is unenforceable, the rest remains in effect. Neither party may assign these Terms without the other's consent, except RunOps may assign them to a successor to its business. Failure to enforce a provision is not a waiver. Neither party is liable for delays caused by events beyond its reasonable control.

## Change log

| Version | Effective | Change |
|---|---|---|
| 2026-10-18.1 | 2026-10-18 | Adds 15.4: portal-window sessions may be recorded, with credentials and personal data removed, to build and improve Brand integrations. Re-acceptance requested at the next sign-in. |
| 2026-10-16.1 | 2026-10-16 | First engineering draft, pending review by counsel. Reflects that the Service submits Orders where a Brand's submit path is verified and the Retailer enables it. |