Miro AI
Miro · Productivity · NL · miro.com/ai/
services/miro-ai.yamlVendor data-handling terms
“If your use of Miro's Service is not through a subscription to a Miro enterprise plan (e.g. if you are on a free, starter, business, or equivalent plan), and Miro seeks to use your Input and Output for improving its AI Features, including for training or fine tuning underlying models, Miro will provide you with reasonable means to object to such use. / Miro uses technology of third party providers in order to make the AI Features available to you.”
“If your use of Miro's Service is subject to a Master Cloud Agreement, for example, because you are on Miro's Enterprise Plan, Miro will obtain your consent prior to using your Input and Output for improving its AI Features, including for training or fine tuning underlying models. You may withdraw your consent at any time during your Agreement term.”
The addendum addresses ownership and training use of input and output but gives no retention period for AI prompts or outputs.
The addendum names third-party providers via a separate provider list and states no processing region for AI features.
Domains and endpoints
observed means seen in Unseen deployments; vendor-documented means listed by the vendor. Vendors do not publish complete lists.
| Host | Role | Source |
|---|---|---|
| miro.com | app | vendor-documented |
| api.miro.com | api | vendor-documented |
Assessment
Reasoning: The AI features inside Miro boards. Non-enterprise plans allow Miro to train on board content unless the customer objects; enterprise plans are consent-only. Third-party model providers are used, with region and retention left to the wider agreement.
Flags: Non-enterprise plans train unless objected · Third-party model providers · Retention and region not stated in the addendum · Assessed 2026-09-16. The assessment is Unseen's; the terms above are the vendor's.
Changelog
- 2026-09-16Documented. Training terms verified against the Miro AI Features Addendum; retention and region not stated there.
- 2026-09-16Added with vendor-documented domains.
Corrections
Pull request on GitHub, or the form below. Changes are reviewed and recorded in the changelog.