RAgencyOS · Legal

Master Services Agreement

Effective
May 31, 2026
Last revised
May 31, 2026
Version
2026.05.31
Issued by
RAgencyOS, ragencyos.com
Who needs this

Most customers use the Service under the standard Terms of Service and Data Processing Addendum, no signature required, just accept-by-use. Larger agencies whose procurement teams require a counter-signed Master Services Agreement (MSA) can request one here. The MSA contains the same substance as our standard terms, in a format your procurement team can sign and file.

1.What's in an MSA with RAgencyOS

An executed MSA covers the same substance as our public documents:

  • Definitions and the description of the Service (mirrors Terms §1).
  • Subscription term, renewal, and termination rights.
  • Fees, payment terms, taxes, and late-fee mechanics.
  • Customer Data ownership and license grant (Terms §3).
  • Customer responsibilities and warranties (Terms §4).
  • Acceptable use, by reference to the AUP.
  • Data processing terms, by attachment of the DPA.
  • Confidentiality (mutual).
  • Intellectual property, including a feedback license.
  • Service-level commitment, where applicable (see below).
  • Disclaimer of warranties.
  • Limitation of liability and the standard carve-outs.
  • Indemnification (mutual, with the standard procedures).
  • Insurance covenant, we carry commercial general liability and technology errors-and-omissions / cyber liability insurance at policy limits appropriate to a SaaS of our stage.
  • Force majeure.
  • Governing law and venue.
  • Notices, assignment, severability, and the standard general provisions.

2.Service-level commitment (custom)

Our public Terms of Service do not include a contractual uptime SLA. An executed MSA can include a target SLA, typically 99.5% monthly uptime, calculated on standard industry assumptions and with the standard exclusions for scheduled maintenance, beta features, force majeure, and Customer-caused issues. Remediation for missed SLA is typically a prorated service credit against the next billing period, capped at a single month’s subscription fee.

3.What an MSA does NOT change

An MSA is the same product on a different paper. We do not modify the following for an MSA customer:

  • Our technical security posture (described at /security).
  • Our subprocessor list (at /subprocessors) or the 15-day change-notification window.
  • Our breach-notification commitment of 72 hours from confirmation.
  • Our compliance status (no SOC-2, no HIPAA BAA, see Trust Center).
  • The strict no-resale, no-AI-training, and no-cross-context-advertising commitments in the Terms and Privacy Policy.

We do not offer source-code escrow, exclusive support tiers, or contractual rights to dictate our product roadmap. Requests for those typically belong in an enterprise contract at materially higher volume.

4.Requesting an MSA

To request a counter-signed MSA, email support@ragencyos.comwith subject “MSA request” and include:

  • Your agency’s legal name and state of formation.
  • The name of the authorized signatory.
  • Your expected number of users (so we can size the subscription).
  • Any redlines or specific terms your procurement team requires (we’ll review and respond).

We aim to turn around a signature-ready MSA within 5 business days for customers requesting our standard terms. Custom redlines are reviewed case-by-case; expect 5–10 additional business days for substantive changes.

5.Contact

MSA requests, redline questions, procurement inquiries:

This document is provided in good faith and reflects RAgencyOS’s current practices as of the effective date shown above. It does not constitute legal advice. For questions, please contact support@ragencyos.com.

— RAgencyOS