The Terms of Service operate alongside a Master Cloud Agreement, AI Features Addendum, Customer Data Processing Addendum, Developer Terms of Use, Marketplace Terms of Use, and other supplemental instruments, creating a layered contractual structure where different documents may govern different user types and use cases.
This analysis describes what Miro'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
This provision establishes that the operative contractual terms for any given user depend on which agreement tier applies to their account type and usage pattern. Enterprise customers may be governed by the Master Cloud Agreement rather than the consumer Terms of Service, and the applicable rights and obligations may differ materially between tiers.
This new provision suggests a reorganization toward a more complex multi-document framework, potentially making the full contractual obligations less transparent to users.
View full change record →Users accessing Miro through different account types, including free, paid, enterprise, or developer accounts, are subject to different combinations of the applicable legal documents. The agreement structures these as distinct instruments, and the terms applicable to a given user depend on their account type and the features they access.
How other platforms handle this
Welcome to Hinge, operated by MTCH Technology Services Limited ("MTCH Technology") for users located in the European Union ("EU"), European Economic Area ("EEA"), the United Kingdom ("UK"), or Switzerland, and operated by Hinge, Inc. for all other users. As used in this Agreement, the terms "Hinge,"...
X's Terms of Service for users outside the European Union, EFTA States, or the United Kingdom (including in the United States) have been updated. X's Terms of Service for users in the European Union, EFTA States or the United Kingdom remain unchanged.
If you live in the Designated Countries, the laws of Ireland govern all claims related to LinkedIn's provision of the Services, but this shall not deprive you of the mandatory consumer protections under the law of the country to which we direct your Services where you have habitual residence. With r...
Monitoring
Miro has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
(1) REGULATORY LANDSCAPE: The multi-document structure creates compliance complexity under GDPR, CCPA, and the EU AI Act, as different documents may address data processing, AI, and developer activities under separate terms. Each document may independently engage applicable regulatory frameworks. (2) GOVERNANCE EXPOSURE: Medium. The layered structure means compliance teams must review multiple documents to establish a complete picture of obligations; gaps between documents or ambiguous scope language could create unaddressed compliance areas. (3) JURISDICTION FLAGS: Enterprise customers in EU/EEA jurisdictions should confirm whether the Master Cloud Agreement or consumer Terms of Service governs their account, as GDPR Article 28 obligations may be addressed differently across tiers. Developer accounts subject to the Developer Terms of Use face additional considerations around API data access and third-party integrations. (4) CONTRACT AND VENDOR IMPLICATIONS: Procurement teams should identify which agreement tier governs their engagement and ensure all supplemental documents are reviewed. Conflict of terms provisions, if any, should be located to determine which document prevails in case of inconsistency. (5) COMPLIANCE CONSIDERATIONS: A full compliance review should map which user populations are governed by which documents and ensure that data processing, AI use, and developer activities are each covered by an applicable instrument. Annual legal review of all supplemental documents is advisable given that terms may be updated independently.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 1 platform + weekly digest. Monitor: 25 platforms + same-day alerts. No credit card required.
Compliance Governance Intelligence
Need to monitor specific governance provisions?
Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
This provision establishes that the operative contractual terms for any given user depend on which agreement tier applies to their account type and usage pattern. Enterprise customers may be governed by the Master Cloud Agreement rather than the consumer Terms of Service, and the applicable rights and obligations may differ materially between tiers.
Users accessing Miro through different account types, including free, paid, enterprise, or developer accounts, are subject to different combinations of the applicable legal documents. The agreement structures these as distinct instruments, and the terms applicable to a given user depend on their account type and the features they access.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Miro.