Marketplace terms.

01Scope of the Marketplace

These Marketplace Terms of Use (the "Terms") govern the Message.com Marketplace, including the public listings at /integrations and the in-app marketplace inside the Message dashboard (collectively, the "Marketplace").

The Terms bind two groups. Marketplace Partners are the developers and companies that submit apps for listing. Customers are the Message workspaces that install and run those apps. Each group is bound to the extent the relevant section applies.

The Terms supplement the Developer Terms, the main Terms of Service, the Acceptable Use Policy, and (when a Partner's app processes personal data) the Data Processing Addendum. If a conflict exists, these Terms control with respect to the Marketplace.

02Listing requirements

To be listed, your app must satisfy each of these baseline requirements at submission and throughout its time on the Marketplace:

• Working software. A live, installable build that connects to a Message workspace and performs the function described in the listing. No mockups, no "coming soon" listings.
• Real screenshots. Screenshots taken from the running product, not Figma frames. Mark mock data clearly if you cannot use a live customer's data.
• Working contact information. A monitored support email and a security email that you respond to within the windows below.
• Security questionnaire. Complete the Marketplace security questionnaire honestly. Material misstatements are grounds for immediate de-listing.
• Accessibility. Conform to WCAG 2.2 AA for any user-facing surface, including embedded views inside the Message dashboard. Document any known gaps in your listing.
• Privacy notice. A privacy notice covering any personal data your app processes, including which categories you collect, your legal basis, and how a customer can request deletion.
• Versioning. A clear changelog, semantic version numbers, and a published deprecation policy if your app exposes an API of its own.

03Approval process

Every submission is reviewed by a Message engineer and a Message product reviewer. Typical turnaround is five business days from submission to approval, rejection, or a request for changes.

We may install your app into a sandbox workspace to verify behavior, OAuth flow, webhook signatures, and error paths. We may ask for source links, security policies, or a screen share. Re-submissions after rejection are reviewed within three business days where the changes are scoped to the items we flagged.

Approval is at our discretion. We do not guarantee a slot, a category placement, or featured placement. We may rank, sort, and surface listings in the way that we believe best serves Customers.

04Supported pricing models

The Marketplace supports the following pricing models for Partner apps:

• Free. No charge to the Customer. No revenue share.
• Freemium. A free tier and one or more paid tiers. Each paid tier follows the rules below.
• Paid one-time. A single charge at install or at activation.
• Subscription. Recurring monthly or annual fee.
• Per-conversation or usage-based. Metered by an event count the app reports through the Marketplace billing API.

Trial periods, money-back guarantees, and discount codes are allowed; document them in the listing. Hidden fees, dark-pattern upsells, and pricing that changes after install without notice are not allowed.

05Revenue share

Where the Customer is billed through Message's checkout (we collect the money and remit to you), the revenue share is 15 percent for paid one-time, subscription, and usage-based listings. We deduct payment processing fees from the gross before applying the share. Payouts are issued monthly net 30 from month close, with the same minimum and method options as the Partner Program Terms.

Where the Customer is billed by the Partner directly through your own checkout (the "bring your own billing" path), the revenue share is zero. You collect and you remit any taxes you owe; we provide the listing and the install flow at no charge in that case.

A Partner may move a listing between the two billing modes at most once per quarter, with 30 days' notice to existing subscribers. We will email affected Customers about the change.

06Tax handling

For apps billed through the Message checkout (the 15 percent revenue-share path), Message acts as a marketplace facilitator for US sales tax. We will calculate, collect, and remit US state and local sales tax where we are required to do so, including under marketplace facilitator laws. The Partner remains responsible for federal, income, foreign, and any tax outside of the US sales-tax remit.

For apps billed through the Partner's own checkout, the Partner is the merchant of record and is solely responsible for all sales, use, VAT, GST, and similar transaction taxes worldwide. We do not collect, withhold, or remit any tax on those transactions.

Partners must keep tax forms and registration numbers current in the partner portal. We may withhold payouts if a required form (W-9, W-8, VAT number where applicable) is missing or invalid.

07Ongoing Partner obligations

Once listed, the Partner agrees to keep the app safe, working, and supported:

• Security disclosures. Notify Message at [email protected] within 24 hours of becoming aware of any security incident that may affect Customers.
• Vulnerability fixes. Patch confirmed vulnerabilities within 30 days of disclosure, or 7 days for critical severity. Coordinate the timing of any public disclosure with Message.
• Customer support. Respond to a Customer support ticket within one business day. Resolution times depend on the issue; first-touch response within 1 business day is the floor.
• Uptime. Maintain at least 99.9 percent monthly availability of any backend service your app depends on. Publish a status page or report monthly uptime to Customers on request.
• Changelog. Keep a public changelog. Communicate breaking changes at least 30 days in advance, longer where Customers' workflows depend on the surface you are changing.
• Data minimisation. Request only the OAuth scopes and webhooks your app actually needs. If you reduce scope in a release, drop the request; if you expand scope, prompt for re-consent.

08Branding and how you describe the integration

In your listing copy, in your own marketing, and inside the app UI, describe the integration accurately. The required phrasing is "Built for Message" (or in localised form an equivalent phrase). Do not use "Made by Message," "Official Message app," or "Powered by Message" unless we have agreed to that phrasing in writing.

You may use the Message logo and name only under the Brand Identity Policy linked from /legal. Do not modify the marks, do not combine them with your own to create a lockup, and do not register a domain that contains "message" or a confusingly similar string.

If your app is a finalist or winner in any Marketplace program (Featured App, App of the Year), you may use the matching badge for as long as the designation is current.

09Content guidelines

The Marketplace does not list apps that:

• Compete with Message's core surfaces in a way that materially duplicates them inside the Marketplace, including a competing unified inbox, a competing AI chat agent that does not extend our AI, a competing phone or call routing layer, or a competing knowledge-base authoring stack. We welcome apps that integrate with these surfaces; we do not list apps that replace them.
• Exfiltrate Customer Data outside the scope the Customer authorised, including covert sharing with affiliates, brokers, or model trainers.
• Embed advertising, retargeting pixels, or third-party trackers without explicit Customer consent surfaced in the install flow.
• Implement dark patterns, fake urgency, or deceptive trial-to-paid conversions.
• Violate the Acceptable Use Policy, including spam, fraud, illegal-content moderation evasion, or sanctioned-region distribution.

We may add categories to this list as the Marketplace evolves. Material changes will be notified to listed Partners at least 30 days before they take effect.

10De-listing and appeals

We may de-list an app for any of the following reasons:

• Confirmed security incident affecting Customers.
• Repeated abuse complaints from Customers (three or more substantiated complaints in a 90-day window).
• The integration is broken (errors above a published threshold, OAuth flow failing, webhook delivery failing) and the Partner has not fixed it within 14 days of notice.
• Repeated SLA misses on support response or uptime.
• Violation of these Terms, the AUP, or the Developer Terms.
• The Partner's legal status changes such that they would no longer qualify under section 2.

We will give the Partner written notice of the de-listing, the reason, and (for non-security causes) a 14-day window to cure. Customers with the app installed will be notified and given a path to export their data and migrate.

The Partner may appeal a de-listing by emailing [email protected] within 14 days of the notice. An appeal is reviewed by an officer not involved in the de-listing decision and is decided within 14 days of receipt. Security-driven de-listings are not paused during the appeal.

11Disputes between Customers and Partners

When a Customer and a Partner disagree (a refund request, a feature dispute, a data-handling complaint), they should first try to resolve it directly. Most Marketplace disputes are billing-related and can be settled in a single email between the two parties.

If the parties cannot resolve it, either side may escalate to Message at [email protected]with the subject "Marketplace dispute." We will read both sides, ask for evidence, and propose a resolution within 10 business days. Our resolution is binding only with respect to the Marketplace surface (whether the app stays listed, whether we issue a goodwill refund where we processed the payment, whether installs continue). It does not adjudicate the underlying commercial contract between the Partner and the Customer.

We reserve the final right to remove an app from the Marketplace, refund Customers we billed, or freeze a Partner's payouts pending the outcome of the dispute.

12Liability between Message and the Partner

The Partner is responsible for the app: its security, its correctness, its compliance, the legality of what it does inside a Customer's workspace, and any losses caused by it. Message is responsible for the Marketplace surface: the discovery, install, billing, OAuth, and webhook plumbing we operate. Each party indemnifies the other for losses caused by its own area of responsibility.

Neither party is liable to the other for consequential, incidental, special, or punitive damages, or for lost profits or lost goodwill. Each party's total liability for any single claim arising out of these Terms is limited to the greater of (a) the revenue share paid or owed for the 12 months preceding the claim, or (b) USD 5,000. These caps do not apply to indemnification for IP infringement or for breaches of confidentiality, security, or the AUP.

Nothing in this section limits liability that cannot be excluded under applicable law (death, personal injury, fraud, willful misconduct).

13Intellectual property

The Partner retains all rights in the app's code, logo, copy, and trade dress. Message retains all rights in the Marketplace surface, the platform APIs, and the Message marks. Each party grants the other only the licenses needed to make the Marketplace work: the Partner grants Message a license to display, install, and operate the listing; Message grants the Partner a license to use the platform APIs and the Marketplace install flow as documented.

Customer Data is the Customer's; neither the Partner nor Message gains ownership of Customer Data through the install. Aggregated, de-identified statistics about Marketplace activity (install counts, popular categories) may be published by either party in their own marketing.

14Governing law and dispute resolution

These Terms are governed by the laws of the State of Texas. The parties consent to the exclusive personal jurisdiction of the state and federal courts in Harris County, Texas, for any matter not subject to arbitration.

Disputes that the parties cannot resolve in 30 days will be finally settled by binding arbitration administered by the American Arbitration Association under its Commercial Arbitration Rules, with a seat in Houston, Texas. Either party may seek injunctive relief from a court to protect IP, confidential information, Customer Data, or platform security without first arbitrating. Class actions and consolidated proceedings are not permitted.

Notices to Message go to [email protected] with a hard copy to Message.com LLC, 363 N Sam Houston Pkwy E Ste 125, Houston, TX 77060, United States. Notices to a Partner go to the email on file in the partner portal.