Together AI added two new sentences to its Terms of Service on May 21, 2026 that clarify payment clearing procedures for credits and prepaid balances. The updated terms now state that credits funded via ACH, wire transfer, or other delayed-settlement methods will not be available for use until the company has received and confirmed clearance of the underlying funds. The company is also not responsible for delays in service access resulting from payment processing time, or for failed, reversed, or returned payments.
The updated terms establish that prepaid credits funded via ACH, wire transfer, or other delayed-settlement payment methods will not be available for use until the company confirms receipt and clearance of the underlying funds. The terms also state that the company is not responsible for any service access delays that result from the time required for payments to clear, or for any failed, reversed, or returned payments. This means users who choose these payment methods should expect a processing delay before credits are usable.
The updated terms establish explicit timelines and liability allocation for delayed-settlement payment methods. Users paying via ACH or wire transfer should understand that credits will not be immediately available and that service interruptions during the clearing period are not company responsibility, affecting when prepaid balances can be used.
→ Review payment method options and select immediate-settlement methods if service access timing is critical.
→ Plan prepaid credit purchases to account for ACH and wire transfer clearing delays before needing service access.
→ Prepaid credits funded via ACH or wire transfer will not be available for use until the company confirms fund clearance.
→ Service access delays during payment processing are not company responsibility under the updated terms.
Credits via ACH, wire, or delayed-settlement methods are unavailable until fund clearance is confirmed.
Company is not responsible for service delays from payment processing time or for failed, reversed, or returned payments.
This change record describes what was added, removed, or modified in the document. Analysis reflects what the updated agreement states or permits. It does not constitute a legal determination about enforceability. Applicability may vary by jurisdiction. Methodology
Together AI added clarifying language around payment processing timelines and liability for delayed-settlement payment methods. This is a standard commercial practice for SaaS platforms handling ACH and wire transfers. The language allocates risk for payment processing delays and failed transactions to the user. No novel regulatory exposure appears created; the change aligns with typical merchant practices in the payments and SaaS sectors. Internal review is not required unless the organization's vendor management framework requires explicit documentation of payment clearing procedures.
Full compliance analysis
Obligation analysis, escalation trigger, board language, and recommended action.
Monitor: regulatory citations + obligations. Compliance: full compliance memo.
ConductAtlas provides verified policy intelligence sourced directly from platform documents. All analysis is intended to support, not replace, legal and compliance review. Record CA-C-002234.
This provision creates a separate Acceptable Use Policy framework and adds specific prohibitions on weapons, malware, and discrimination that were less explicit in the previous version's combined prohibited uses clause.
This comprehensive prohibited uses clause was replaced with a more limited Acceptable Use Policy reference, notably removing the explicit prohibition on circumventing safety measures and developing competing products.
Removed specific reference to JAMS arbitration rules and San Francisco location requirement, simplified language to lowercase, and expanded scope to include breach, termination, enforcement, interpretation and validity.
Expanded waiver language to explicitly prohibit private attorney general actions and representative proceedings, and clarified that this applies to all forums, not just court proceedings.
Removed $100 minimum liability floor, expanded liability exclusion to cover officers, directors, employees, agents, contractors, and licensors, explicitly excluded indirect/consequential/punitive damages, and broadened scope to cover contract, tort, and statutory claims.
Removed provision about user-initiated termination, added specific triggers for termination related to Agreement violations and Acceptable Use Policy breaches, and removed company liability waiver language.
Added explicit user ownership retention of content, removed sublicense rights and removed rights to process/transmit/display, and narrowed license scope to only providing and improving services rather than all distribution methods.
Added requirement to notify for material changes specifically, changed from discretionary notice to mandatory email or in-service notification, and made notice timing more explicit (prior to effectiveness).
Added "exclusive" jurisdiction language and explicitly limited court jurisdiction to situations permitted under the agreement (acknowledging arbitration clause takes precedence).
Changed "WITHOUT" to "on an AS IS basis", added warranty of TITLE to the exclusions, and removed "IMPLIED" modifier before warranties of merchantability and fitness.
2 provisions unchanged.
Cross-platform context
See how other platforms handle similar provisions across the ConductAtlas archive.
See the full side-by-side comparison of every sentence added, removed, and modified.
🔒 Full diff — MonitorTogether AI modified a single sentence in its Terms of Service on May 19, 2026, changing the section heading from …
Get alerted when this policy changes again — including what changed and why it matters.
Prefer a weekly summary instead?
Get the biggest policy changes across 352+ platforms every Sunday.