Privacy Policy
Mirivo is provided by Alper Biçer. This policy describes data handling in the iOS app and on this support website.
Updated:
Screen and app audio
Screen sharing begins with the iOS system confirmation. Video and app audio are processed on your device and transmitted to the selected compatible display. Mirivo does not upload them to a developer server or create an audio or video recording. Media fragments are held in bounded temporary memory and removed when the session ends. Mirivo does not record the microphone. Personal information and notifications visible on the screen may be included in the broadcast. You can stop it at any time using the iOS broadcast control.
Local connection
Screen broadcasts use a hard-to-guess, per-session access address. Local transmission may use HTTP; this is not a promise of end-to-end encryption. The access address is excluded from logs and exported diagnostic reports. Access is revoked when sharing stops.
Sources and credentials
Source names and types are stored in the app’s local storage. Stream URLs, usernames and passwords are stored in iOS Keychain with device-only accessibility. Importing a playlist file saves a copy, which may include stream URLs and credentials, in the app’s protected device storage. Provider-reported account expiry and the last check time are also stored on the device. Your chosen source server receives your IP address, requested content and any necessary credentials when you connect; its own policies apply. HTTP sources do not encrypt transport. Prefer HTTPS when available.
Library cache
To open the library quickly and show the previous list without a connection, channel/movie/series titles, groups, stream and artwork URLs and provider-supplied descriptions may be cached in encrypted files on the device. The encryption key is stored in device-only Keychain; the cache is excluded from device backup. An old list can remain until replaced or the source is edited or deleted. Removing a source deletes its imported playlist copy, cache and account-check information.
Viewing history and favorites
The title, group, stream URL, descriptive metadata, playback position and last watched time of the most recent online item and up to 30 unfinished movies or series are kept in this device’s Keychain. Episodes of the same series share one continuation record. Favorite items or series also retain their title, source association, stream/artwork URLs and descriptive metadata in device-only Keychain. Remove continuation records from the list and favorites using the heart button. Editing a source clears its continuation records; changing its type, URL or credentials also clears its favorites. Deleting a source clears both. Mirivo does not copy these records to a developer server or provide iCloud synchronization.
Content information and artwork
Movie, series and episode information may be requested from your chosen provider’s API, sending the content identifier and necessary account details to that provider. Posters and covers are loaded from the server specified by the playlist or provider response; that server receives your IP address and requested image URL. Images are held in bounded device memory. Descriptive information may also be retained in the library cache, continuation records or favorites. These requests do not pass through a Mirivo server.
Offline downloads
Eligible movie/episode downloads you start are fetched directly from the content provider to your device. The provider receives your IP address, requested content and any credentials required by the connection. iOS may continue a download in the background. The media file, title, group, source association, download status and local file path are stored on the device; the download list stores a hash of the stream URL rather than the URL itself. You can cancel a download or delete it from Downloads. Removing a source does not automatically remove downloaded files; delete those separately. Mirivo does not upload downloads to a developer server.
Personal media you select
Media you choose through the system photo or file picker is processed on your device for playback and sharing. A temporary copy of the selected file may be created. You initiate transmission to a compatible TV or receiver; Mirivo does not upload this media to a developer server.
Live captions
When enabled on a supported device and language, live captions use Apple’s on-device speech models. Initial setup may download a language model from Apple. Mirivo does not send speech or generated text to a server or create a persistent transcript. Captions are composited into the video and temporary text is cleared on stop. Recognition may be inaccurate.
Preferences and diagnostics
Language, quality, audio and caption preferences stay on the device. Technical logs retain up to 10 recent sessions within a total 5 MiB budget. They contain structured states, error codes, timing, media counters and connection types. Screen content, audio, captions, source URLs, tokens, IPTV accounts, passwords and device names are excluded. Reports are not sent automatically; you select the recipient in the system share sheet. Mirivo uses no advertising SDK.
TV connections with Google Cast
When you connect to a TV with Google Cast, Google’s SDK may process technical diagnostics and performance data for service reliability and functionality, and derive general location from that data. Cast analytics logging and automatic discovery are disabled in Mirivo. TV discovery starts when you open the connection picker. Other SDK diagnostics may still be processed. The selected media link and playback information are shared with the TV/receiver; the content provider’s and Google Cast’s policies apply.
Updates and notifications
When Firebase is configured, the app checks its version policy through Remote Config. Firebase installation identifiers and technical connection information may be processed for this service. Notifications are registered only after you enable them in Settings and allow them in iOS. For public announcements, Firebase Cloud Messaging processes a notification token and topic subscription; this mode does not create an anonymous user account or a developer-operated token database. Turning notifications off unregisters the device and removes the topic subscription when the server can be reached; offline changes are retried on the next connection. Removing a topic subscription does not delete the Firebase installation identity. A release configured for per-device registration additionally uses anonymous Firebase Authentication and App Check to process a token, app version, language and registration time. In that mode, opting out deletes token and version/language metadata; a minimal revision record may remain to prevent delayed requests from reversing the choice. Private registry entries not refreshed for 180 days are excluded from sends and queued for deletion under the enabled retention policy. Screen content, audio, personal media, source addresses and passwords are not sent to these services. No advertising tracking is used. Firebase may also process installation and technical diagnostic data for security and functionality.
Trial-ending reminder
For a verified free trial set to renew, a local reminder is scheduled on the device 48 hours before expiry when your preference and iOS permission allow it. The preference, notification identifier and a record representing trial expiry/renewal details are stored locally. This does not require an FCM token or public-announcement subscription. Disabling the preference removes the pending reminder. Cancellation and expiry changes are applied when the app next checks subscription status; changes made while it is closed may not be reflected immediately. Delivery depends on iOS settings. Manage cancellation yourself in the App Store.
Optional usage analytics
The Usage analytics preference in Settings is off by default. If you enable it, Firebase Analytics processes app sessions, fixed screen names, app/OS versions and technical usage statistics to improve the product. Fixed categories measure source-save results and types, playback starts/errors, general display connection types, Pro screen views, and purchase and restore outcomes. Saving a source does not verify provider availability. Custom events do not include prices, transaction identifiers, or source/content identifiers. A random analytics identifier is assigned to each installation. General location may be derived from masked IP addresses, and StoreKit purchase and subscription events may include product ID, name and price. Payment card details are not part of those events. Media, source names/addresses, search text, credentials and user-entered content are not included in analytics events. Advertising identifiers (IDFA), vendor identifiers (IDFV), ad personalization and ad network measurement are disabled. The Firebase Auth identity is not assigned as an Analytics user ID. Turning the preference off stops subsequent analytics collection and resets the local analytics identifier; this alone does not delete data previously sent to the server.
Optional error reports
Share error reports is separate from Usage analytics and is off by default. If enabled, Firebase Crashlytics processes crash stack traces, app/OS versions, technical device information, random installation/session identifiers and limited technical error codes to diagnose problems. If you also permit usage analytics, Analytics events may appear as breadcrumbs in a report. Mirivo does not add media, source names/URLs, search text, credentials or a custom user ID to reports. Automatic Crashlytics uploads remain disabled; reports from the previous session are sent or deleted after checking consent again at the next launch. Reports from sessions without consent are not sent. Turning consent off prevents subsequent sends; re-enabling within the same session resumes error sharing at the next launch. The SDK may still create local crash files while consent is off. Turning consent off does not recall reports already sent or being sent. This is separate from the local diagnostic report whose recipient you choose yourself.
App Store reviews
The first-use date, up to three successful-use days, and the last review-request date/version stay on your device to choose an appropriate time to request Apple’s review prompt. These counters do not require analytics consent and are not sent to a server. Apple controls whether the prompt appears; Mirivo does not learn whether you submitted a rating or what rating you gave. You can also use the link in Settings to write an App Store review.
Purchases
Apple App Store handles payment and subscriptions. Mirivo does not receive payment card details. Access is determined from locally verified StoreKit transactions. When RevenueCat is configured, it processes a random app user identifier, purchase and subscription records and technical connection information to verify purchases, prevent fraud, manage Pro access and provide purchase analytics. Sources, credentials, screen content, audio and captions are not sent to RevenueCat.
Support and this website
If you email support, your email address, message and any attachments you choose to send are used to respond. You do not need to send screen recordings, stream passwords or personal content. Messages are retained as needed to resolve the request and meet applicable obligations. This static website has no ads, analytics cookies, forms or tracking scripts. When hosted on Netlify, Netlify may process technical connection details, including IP addresses, to serve and secure the website under its own privacy policy.
Deletion and choices
Settings lets you clear diagnostics and delete all sources with saved credentials, library caches, continuation records and favorites. Individual sources can also be removed. Delete downloaded media separately from Downloads. Use these controls before uninstalling; iOS Keychain entries can survive app removal. No Mirivo account is required and local data is not backed up to a Mirivo account. You can turn off usage analytics and notification preferences in Settings. Contact us below regarding support information you sent or applicable access, correction and deletion rights. Transaction and technical records held by Apple or service providers remain subject to their purposes, retention policies and legal obligations; uninstalling does not automatically delete them.
Contact and updates
Publisher and data controller: Alper Biçer. Contact: alperrbicer@gmail.com. We update this policy when data handling changes; the current date appears on this page.
Apple Privacy ↗ · Firebase Privacy ↗ · Google Privacy ↗ · RevenueCat Privacy ↗ · Netlify Privacy ↗