Is Miro Search safe?
Miro Search sends usage analytics with a persistent anonymous ID and hashed Miro user or board IDs to Segment.
When you use the omnibox search feature, the extension creates or reuses a stored anonymous ID and posts Segment events such as search opened, results shown, suggestion selected, and board opened. For signed-in Miro users, those events can include MD5-hashed Miro user and board IDs, query length, and result counts. OAuth token exchange and refresh requests are sent to api.miro.com with the bundled app client secret.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
What it can do
Permissions this extension asks for, as declared in version 9.4. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Read and change your data on miro.com
https://miro.com/ and 1 more
Read and change your data on api.miro.com
https://api.miro.com/*
Read and change your data on ingest.sentry.io
https://*.ingest.sentry.io/*
Read and change your data on api.segment.io
https://api.segment.io/*
Store data in your browser
storage
Sign you in with your Google account
identity
Where it sends data
Destinations our analysis observed Miro Search contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.
- api.segment.io
Miro Search sends data to api.segment.io. 21 other extensions we have analysed send data here.
- api.miro.com
Miro Search sends data to api.miro.com. No other extension we have analysed sends data here.