ميرو — سياسة الخصوصية

Miro is developed by OSSUS / Mohammed Al-Jaf. Privacy and support contact: OSSUS official profile.

Information processed

We process your phone number, account and session identifiers, plan and subscription-request records, and technical installation information: a random installation identifier, device brand/model and OS, app version, language, time zone, last activity and notification-permission state. Installation data may be processed before sign-in. If available and permitted, a Firebase notification token is used to deliver messages and avoid duplicate delivery. Server requests include IP addresses and technical/security records. Connection-based country information may be used for regional prices; this does not require GPS access. For App Store or Google Play purchases, we process transaction identifiers, verification tokens, renewal, expiry and refund status to link access to your account and prevent purchase reuse. The store processes payment; Miro does not receive your card number or security code.

Screen and video content

Screen capture starts with operating-system permission. Miro does not upload captured screen content or local video files to its account servers. Display processing takes place on the device and connected display path. Session reports and preferences may be stored locally.

Purposes and service providers

Data supports account access, plans, verification, service notifications and Miro promotional notifications when permitted, device activity, troubleshooting and abuse prevention. We do not use the device advertising identifier for cross-app ad tracking or sell personal account data. Google Firebase and Apple APNs deliver notifications. OTPIQ delivers sign-in codes through WhatsApp or SMS when the fallback applies. These services receive information necessary for delivery, such as the phone number or notification token and technical request information. External stream/video providers may receive your IP and playback-request information when your device connects to their content, subject to their policies.

Protection and retention

Miro server connections use HTTPS and authenticated access controls. Account and plan records are kept while the service is used. Certain session/security records follow limited retention cycles; audit logs may be kept for up to one year. Deleted data may remain in encrypted backups until those backups are replaced through their backup cycle; backups are not used for marketing or normal daily operation.

Account deletion

Use Settings → Account → Delete account, or the Miro account deletion page without reinstalling the app. Identity verification is required. Deletion removes the account and associated installation records and invalidates sessions. Limited transaction identifiers detached from the phone number may be retained for refunds, fraud prevention and financial obligations. Deleting a Miro account does not cancel store renewal; cancel it through the store if desired. Keyed abuse-prevention counters may remain without the plain phone number or code to prevent quota resets and abuse. Administrator ownership must be transferred before deleting the administrator account; contact support for assistance.

Your choices

Manage notification permission in device settings, stop capture through operating-system controls and customize appearance/language in Miro. Miro is not specifically directed at children. Contact support if you believe a child's data was collected without appropriate authorization. This policy may be updated as the service changes; the update date is shown above.