Mixpanel · Mixpanel Terms of Use · View original document ↗

Beta Services Disclaimer and Confidentiality Obligation

Medium severity Medium confidence Explicitdocumentlanguage Unique · 0 of 352 platforms
Get alerted the next time Mixpanel changes these terms. Get same-day alerts →
Share 𝕏 Share in Share 🔒 PDF
Monitor governance changes for Mixpanel Monitor emails you the same day this changes. The archive stays free.
Get same-day alerts →

Get the weekly research letter

Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean. No account.

Document Record

What it is

Beta services are provided without warranty, SLA, support, or indemnification, Mixpanel accepts no liability for harm arising from them, and Customers are prohibited from publicly disclosing information about beta services, including their existence, without Mixpanel's written consent.

This analysis describes what Mixpanel's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology

ConductAtlas Analysis

Why it matters (compliance & governance perspective)

This provision establishes that beta services carry no contractual protections while simultaneously imposing a confidentiality obligation on Customer that extends to disclosing even the existence of a beta service, creating an asymmetric obligation structure.

Interpretive note: The interaction between the beta confidentiality obligation covering the existence of a service and GDPR transparency requirements is jurisdiction-dependent and may require case-by-case legal evaluation.

Recent Activity

This document changed recently

Medium Jun 5, 2026

The updated terms remove a contractual protection that previously prohibited Mixpanel from treating individually identifiable data as Usage Data. Under the revised language, Mixpanel may now classify data that identifies or is attributable to specific individuals as Usage Data, potentially making such data subject to uses and disclosures beyond what the Customer Content exclusion permits. This broadens the category of data Mixpanel may process and analyze under the Usage Data definition. The terms do not provide a mechanism to opt out of this reclassification.

View change record →
Medium May 9, 2026

The updated terms establish an automatic 7% fee increase mechanism that takes effect upon each subscription renewal. Previously, subscription fees remained fixed for the duration of the subscription term, with new pricing becoming effective only at the start of a new subscription term and only if the parties agreed in writing. Under the revised language, fees will now automatically escalate by 7% upon commencement of each renewal term unless the parties expressly agree otherwise in writing. This shifts the default pricing behavior from fixed-term rates to automatic annual escalation.

View change record →

Consumer impact (what this means for users)

Under this clause, customers who use beta services accept all risk associated with those services without warranty, SLA, or indemnification protections, and are contractually prohibited from discussing or disclosing beta services publicly without Mixpanel's written approval.

Cross-platform context

See how other platforms handle Beta Services Disclaimer and Confidentiality Obligation and similar clauses.

Compare across platforms →

Monitoring

Mixpanel has changed this document before.

Receive same-day alerts, structured change summaries, and monitoring for up to 20 platforms.

Get Monitor Or create a free account →
▸ View Original Clause Language DOCUMENT RECORD
"
Beta Services are provided on an "as-is" and "as available" basis without any warranty, support, maintenance, storage, service-level agreement or indemnity obligation of any kind and are not considered "Application Services" hereunder, even if displayed in the user interface; provided, however, that all restrictions herein, Mixpanel's reservation of rights and Customer's obligations concerning the Application Services shall apply equally to Customer's use of Beta Services. Mixpanel will have no liability for any harm or damage arising out of or in connection with a Beta Service. Beta Services may be considered Confidential Information of Mixpanel, if so denoted or communicated by Mixpanel to Customer. Customer will not disclose (including, but not limited to, in a press release or public statement) any information about, involving or regarding Beta Services (including the existence of), except as agreed by Mixpanel in writing.

Excerpt from Mixpanel's Terms of Use

ConductAtlas Analysis

Institutional analysis (regulatory & governance intelligence)

(1) REGULATORY LANDSCAPE: Non-disclosure obligations covering the existence of a commercial product or service may interact with consumer protection disclosure requirements in certain jurisdictions, particularly where the beta service involves processing of end user Personal Information. GDPR requires transparency about processing activities, which may create tension with confidentiality obligations that prevent disclosure of processing tools. (2) GOVERNANCE EXPOSURE: Medium. The combination of no-liability beta service access and a prohibition on disclosing even the existence of the beta creates an asymmetric risk profile: customers bear operational and data risk from beta use but cannot publicly reference the service. Organizations using beta features for production-adjacent workloads should document this risk. (3) JURISDICTION FLAGS: The confidentiality obligation covering existence of a beta service may interact with GDPR transparency requirements if the beta service processes Personal Information and the organization's privacy notice is required to accurately describe processing tools. EU-based organizations should evaluate whether this confidentiality obligation conflicts with their data protection transparency obligations. (4) CONTRACT AND VENDOR IMPLICATIONS: Procurement and communications teams should be informed that participation in Mixpanel beta programs creates a written consent requirement before any public reference, press release, or case study mentioning the beta. Violations could constitute a contract breach. (5) COMPLIANCE CONSIDERATIONS: Data protection officers should assess whether any beta services processing Personal Information require disclosure in privacy notices and whether Mixpanel's confidentiality requirement is compatible with those transparency obligations.

Full institutional analysis
Regulatory citations, enforcement risk, and due diligence action items.
Start Insight · $19.99/mo Start with Monitor · $4.99/mo

Provision details

Document information
Document
Mixpanel Terms of Use
Entity
Mixpanel
Document last updated
May 5, 2026
Tracking information
First tracked
July 9, 2026
Last verified
July 9, 2026
Record ID
CA-P-014566
Document ID
CA-D-00703
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
ac40e76378ab5a69d6cee99d3fc6738f3abd11e8fba371a9c34e6c6da068df82
Analysis generated
July 9, 2026 05:53 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: Mixpanel
Document: Mixpanel Terms of Use
Record ID: CA-P-014566
Captured: 2026-07-09 05:53:56 UTC
SHA-256: ac40e76378ab5a69…
URL: https://conductatlas.com/platform/mixpanel/mixpanel-terms-of-use/provision/CA-P-014566/beta-services-disclaimer-and-confidentiality-obligation/
Accessed: July 24, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Medium
Categories

Other risks in this policy

Governance intelligence across arbitration, AI governance, data rights, indemnification, and retention
Provision-level monitoring, governance timelines, and regulatory mapping built from archived source documents and historical version tracking.
Start Insight · $19.99/mo Start with Monitor · $4.99/mo

Frequently Asked Questions

What does Mixpanel's Beta Services Disclaimer and Confidentiality Obligation clause do?

This provision establishes that beta services carry no contractual protections while simultaneously imposing a confidentiality obligation on Customer that extends to disclosing even the existence of a beta service, creating an asymmetric obligation structure.

How does this clause affect you?

Under this clause, customers who use beta services accept all risk associated with those services without warranty, SLA, or indemnification protections, and are contractually prohibited from discussing or disclosing beta services publicly without Mixpanel's written approval.

Is ConductAtlas affiliated with Mixpanel?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Mixpanel.