The service
BrokerOS is a relationship operating system for real estate brokerages. It provides governed recruiting, onboarding, retention, reporting, delivery, and administration workflows through an authenticated application and configured communications.
Features depend on the customer's package, authorized data sources, provider connections, user permissions, and current product support. A connected source or provider record does not by itself make a feature active.
Customer agreement, billing, and cancellation
Package, price, billing cadence, subscription term, support responsibilities, service commitments, and cancellation rights are stated in the applicable order form, customer agreement, or other signed commercial document. That document controls if it conflicts with these general terms.
BrokerOS does not activate a production audience merely because an account was created or a payment method was provided. Source authorization, owner and audience configuration, exact preview, provider readiness, and an authorized activation remain separate requirements.
Accounts, roles, and access
Users are responsible for protecting their credentials and for activity performed through their accounts. Brokerage administrators are responsible for maintaining accurate users, recipients, roles, scopes, source access, and delegated connections.
A report recipient may receive configured communication without holding an application account. Receiving an email does not grant access to the brokerage workspace or its data.
BrokerOS may suspend access when needed to protect a customer, another user, the service, or a legal obligation. BrokerOS support does not receive ambient customer access; support sessions are explicit, limited, and audited.
Customer data and source permission
As between the customer and BrokerOS, the customer retains its rights in customer-provided data and configured reports. The customer grants BrokerOS the limited rights needed to host, process, secure, transform, display, and deliver that data as necessary to provide the service.
Customers must follow applicable MLS, RESO, brokerage-system, privacy, employment, marketing, and recipient-consent obligations. BrokerOS may refuse or disable a source, audience, workflow, or requested action that is unsupported, unauthorized, unsafe, or inconsistent with those obligations.
The Privacy Policy explains how BrokerOS handles customer and connected-account information.
Reports, recipients, and provider actions
Drafting, previewing, testing, publishing, scheduling, provider acceptance, delivery, and recipient engagement are different states. A report sends automatically only after an authorized user activates a valid version and its required source, audience, owner, schedule, and provider configuration remain available.
Users are responsible for reviewing configured audiences and approving content or delegated messages when the product requires approval. Provider acceptance does not guarantee delivery, reading, response, or a business outcome.
Calendar events, delegated email, document-signing packages, and similar provider actions occur only through the connected account and permission boundary configured for that purpose.
Jet and assisted work
Jet can answer questions, prepare work, and use permitted tools within the user's brokerage, role, scope, page, package, and source boundary. Assisted output may be incomplete or incorrect and should be reviewed before it is used for a material decision or external communication.
Tool availability does not remove authorization, confirmation, audit, or source-freshness requirements. BrokerOS does not represent an observed listing event, link selection, model suggestion, or generated draft as proof that a human action or business outcome occurred.
Acceptable use
Users may not:
- access another customer, user, source, report, recipient, or provider connection without authorization;
- circumvent permissions, tenant boundaries, rate limits, security controls, suppressions, or delivery safeguards;
- upload malicious code, interfere with the service, probe for vulnerabilities without permission, or use BrokerOS for unlawful surveillance;
- use data or communications in violation of an MLS agreement, privacy law, marketing rule, intellectual-property right, or recipient preference;
- misrepresent generated or source-derived information as verified human action, legal advice, financial advice, or guaranteed business performance; or
- copy, resell, or reverse engineer the service except where applicable law expressly permits it.
Availability and product changes
BrokerOS works to execute valid configured workflows reliably, but sources, networks, recipients, and third-party providers can fail or change. The service may be unavailable during maintenance, incident response, provider interruption, or a source outage.
BrokerOS may change or discontinue features. Material changes that reduce a contracted service will be handled under the applicable customer agreement. A failed or stale source may pause an affected workflow rather than send unsupported content.
Third-party services and source information
BrokerOS depends on services such as MLS or RESO feeds, customer systems, hosting, email delivery, Google Workspace, Microsoft 365, model providers, and document-signing providers. Their terms, availability, and data can affect BrokerOS behavior.
Market, production, roster, license, listing, open-house, and related information is only as current and complete as the identified source. Users remain responsible for confirming information before relying on it for legal, compliance, compensation, employment, or other consequential decisions.
BrokerOS ownership and feedback
BrokerOS and its licensors retain all rights in the service, software, design, documentation, templates, and methods, excluding customer data and third-party source material. No rights are granted except the limited right to use the service under the applicable agreement.
Feedback may be used to improve BrokerOS without obligation, provided that BrokerOS does not identify the customer or disclose confidential customer information without permission.
Warranties and limitation of liability
Except for commitments stated in a signed customer agreement, BrokerOS is provided "as is" and "as available." To the maximum extent permitted by law, BrokerOS disclaims implied warranties, including merchantability, fitness for a particular purpose, and non-infringement.
BrokerOS does not guarantee uninterrupted operation, complete source data, delivery to every recipient, or a particular recruiting, retention, onboarding, or financial result.
To the maximum extent permitted by law, BrokerOS is not liable for indirect, incidental, special, consequential, exemplary, or punitive damages. Unless a signed customer agreement states otherwise, total liability arising from the service will not exceed the fees paid for BrokerOS during the twelve months preceding the event giving rise to the claim.
Suspension, termination, and data handling
Access may end or be suspended according to the customer agreement, for material breach, for nonpayment when applicable, or when continued operation creates a security, legal, or provider risk.
After termination, customer access and active provider connections may be disabled. Export, deletion, retention, and transition obligations follow the customer agreement, the Privacy Policy, and applicable law. Historical artifacts or audit evidence may be retained where needed for accountability or legal obligations.
Changes, governing law, and contact
BrokerOS may update these terms. Material changes will be posted here and communicated to active customers when appropriate. Continued use after an effective update constitutes acceptance except where a customer agreement or applicable law requires a different process.
Unless a signed customer agreement states otherwise, these terms are governed by Michigan law, without regard to conflict-of-law rules, and disputes will be brought in state or federal courts located in Michigan.
Questions about these terms can be sent to jonathan@getbrokeros.ai.
Last updated / July 20, 2026