Support · Together AI

Will it last?

Ownership levelPartialnone·limited·partial·substantial·fullAnalytical input B · 75.2/100

This page is a projection of the one entry record, the Transparency factor that Support covers. The full verdict is set by all four factors together, floor-weighted so the weakest caps the whole.

Which domain expands which factor

AssessUse & modify + Transparency
ImplementData control + Doesn't fail you
UseDoesn't fail you
SupportTransparency

Security disclosure & trust centre

Together's security documentation and its SOC 2 Type II announcement (both read this session) act as the trust surface, covering encryption, audit logging, MFA/RBAC and a described incident-response plan. A dedicated vulnerability-disclosure process - a published security.txt, advisory feed, or bug-bounty - was not surfaced this session, so for coordinated disclosure plan to go through the documented support/privacy contacts rather than a standing security channel.

Support & community channels

Support comprises product documentation plus commercial support on the Scale and Enterprise tiers. The breadth of community channels (Discord/forum) and the response commitments attached to each paid tier were not detailed in the sources read this session, so confirm the support SLA that comes with your tier during onboarding.

How this scores

The ownership factor this domain covers, drawn from the one entry record.

TransparencyAre the binding terms published, legible and independently checkable?

Moderate

The retention/no-training/ownership terms were actually read this session in the binding Privacy Policy and Terms of Service - a real improvement over a marketing page - but they are Together's own self-attestation, not independently audited, and no sub-processor list is published.

How this scores

Not a scored AOI dimension. For a hosted provider, transparency is whether the binding terms are published, legible and were actually read - the read/unverified evidence below, not a certification. A strong rating here must trace to a retrieved binding document.

What this means for adoptionYou own your workloads here in the ways that matter most: the Terms leave you owning your inputs and outputs, ZDR-by-default with no-training keeps them yours, and the open-weight catalogue on an OpenAI-compatible API is a clean portable exit. But overall ownership is partial, not substantial: the no-retention posture is Together's own self-attestation rather than independently audited, and the US HQ with DPA-confirmed North America default routing carries standing CLOUD Act exposure even for EU-hosted workloads, so data-control is moderate rather than strong. Pin the EU region on a paid tier if residency matters, and teams needing an audited no-retention guarantee should contract it in the DPA rather than rely on the default terms.

Sources

The same evidence records as the entry sheet. Read means the text was verified; unverified means it is known to exist but not yet read.

Privacy Policyread2026-07-25

Privacy Policy: inputs and outputs are not stored by default (zero data retention); under ZDR content is not stored, retained, or used for model training or product improvement except as needed to provide the Services; temporary caching may be used for performance; training on data is opt-in and off by default, controlled by an org-admin Privacy & Security setting.

Documentationread2026-07-25

Privacy and security docs: HIPAA-aligned data encryption in transit and at rest, audit logging and business associate agreements; layered security architecture with MFA/RBAC, continuous monitoring and regular vulnerability assessments; ZDR restated.

Vendor announcementread2026-07-25

SOC 2 Type II announcement: achieved via an independent, multi-month audit validating access management, data encryption, incident response and change management; regular penetration testing.

Documentationread2026-07-25

EU data centres and dedicated model deployment - dedicated endpoints on targeted data centres including EU locations (Sweden GPU capacity) - are available only on Scale and Enterprise tier plans.

Vendor announcementunverified2026-07-25

Serverless per-token pricing page (live rates not read from source this session): gpt-oss-120B ~$0.15/$0.60, Qwen3-235B ~$0.20/$0.60, DeepSeek-V3 ~$1.25/M - approximate and move frequently.

Documentationread2026-07-25

OpenAI-compatibility docs: an OpenAI-compatible /v1 REST API at api.together.ai/v1, used by pointing an existing OpenAI client at Together's base URL and API key (TOGETHER_API_KEY), with chat/completions, streaming, tool use and structured outputs across the open-weight catalogue.

Terms of serviceread2026-07-25

Terms of Service: as between you and Company you exclusively own all right, title and interest in Your Content and Output, granting Company only a limited license to operate them to provide the Services; Together does not use your data to train its models without your explicit opt-in and consent; the Company owns Company IP and Usage Data.

Third-party analysisread2026-07-25

Independent third-party price/performance analysis of Together AI corroborates the approximate serverless rates and shows the same open-weight models served across many providers (portability).

Data Processing Addendumread2026-07-25

Data Processing Addendum: Together (US) Inc.