Mediora Privacy Policy

Mediora is a free social-media video downloader app. Regular mobile downloads do not require a Mediora account. Optional Mediora Connect uses Sign in with Google to send source links from a browser to phones you choose to link. The app and backend process the data described below to perform downloads, enforce quotas, manage Connect, provide support, and keep the service reliable.

Last updated: 25 October 2026

Who runs this

Developer & publisher: Morph Haven / Orvixa Bilişim Teknoloji Tic. Ltd. Şti. — morphaven@outlook.com
App: Mediora — Social Media Video Downloader
Android package name: app.mediora.android
iOS bundle ID: app.mediora.ios
Category: Tools / Social
Jurisdiction: Republic of Turkey

What we process

Mediora's regular mobile features can be used without a Mediora account. Connect is optional and processes Google identity information as explained below. Support requests may also contain the contact information you choose to provide. The app processes the following data so it can work:

Pseudonymous install ID

On current Android builds, the install ID is normally a salted hash derived on the device from Android's ANDROID_ID; the raw ANDROID_ID is not sent to our backend. Older installations may retain a previously generated UUID, and a random UUID is used if ANDROID_ID is unavailable. The derived ID may remain the same after reinstalling the app. Mobile API requests use the install ID for per-install quotas, Premium checks, feedback limits and abuse prevention. Analytics, feedback and entitlement records use further hashed versions. These identifiers are pseudonymous, not anonymous: they can link activity to the same installation.

Request IP address

Standard server access logs and rate limits may process your IP address. We may derive an approximate country from proxy headers or a GeoIP database for abuse prevention, proxy routing, and aggregate operational analytics. We do not use IP addresses for ad targeting or precise location profiling.

URLs you paste

Supported links may be resolved on your device. When server assistance is used, the source link is sent to our backend so it can fetch media metadata and return available formats. URLs and metadata may be kept in a short TTL cache so repeat requests are faster. Persistent extraction analytics store platform, country, Premium state, proxy usage, success/failure, and hashed install ID; source links are excluded except for optional failed-link diagnostics on Android versions offering that option (see Android download diagnostics).

Optional Mediora Connect

Connect uses a Google identity credential to verify your account. This credential may include your Google account identifier, name, email address and profile picture information. The server verifies it and retains a hash of the stable Google account identifier; it does not store the credential, name, email address or profile picture in Connect account records. Google handles sign-in under Google's privacy policy. Connect does not request your Google password or access to Gmail, Drive or contacts, and does not use Google identity information for advertising.

Connect stores linked phone identifiers and labels, hashed device/session credentials, pairing requests, submitted source links, queue status, timestamps and retry/quota receipts. These support authentication, account management, delivery to your chosen phone and prevention of unauthorised or duplicate actions. Google account and phone identifiers remain pseudonymous personal data even when hashed. The Connect queue does not upload saved photos or videos. Adding a link does not start a download: open Mediora on the phone, choose Start and select the media to save. Connect transfers require the app to remain in the foreground.

Pairing requests expire after 10 minutes and browser sessions after 24 hours. Queue links/history and send retry records become eligible for deletion after 30 days and are cleaned in bounded batches on subsequent Connect writes. Inactive accounts may retain expired records longer until another write or account deletion. Active phone links remain until unlinking or account deletion. Expired credentials cannot be used even if their records have not yet been physically removed. See Delete your Connect account.

In-app browsing and website sessions

The Android in-app browser renders HTTPS pages on your device. The websites you visit, their sign-in providers and their embedded services may receive ordinary browser traffic under their own policies. Website cookies and site storage stay in the app’s WebView storage on your device; Mediora does not upload website account cookies to its backend. We do not automatically clear website sessions when you leave a page or close the browser. You can clear cookies/site data explicitly; the website, cookie expiry, Android data clearing or uninstalling can also end a session. This local browsing storage is separate from the optional Connect browser sessions described above.

Manual media discovery, probing and saving run on the device. Account cookies are not forwarded to the native download verifier or our server, so a signed-in page does not guarantee that its protected media can be saved. Download diagnostics and any source-link sharing follow the choices and retention rules described in this policy. Mediora is independent, not affiliated with Google, YouTube or visited websites. YouTube videos, including embeds on other websites, and protected/DRM streams are not supported. Only save media you own or are permitted to download.

Feedback and support reports

If you submit a bug report from the app, Mediora stores your platform selection, optional URL, app version, description, timestamp, and a short salted hash of your install ID in a feedback log. If support notifications are enabled, the same report may be sent to Morph Haven's configured email or Discord notification channel.

Purchases and entitlement status

Premium purchases are handled by Google Play Billing or Apple App Store / StoreKit. We never see your card details. The backend may store hashed purchase tokens or signed transaction identifiers, product ID, platform, subscription state, expiry time, update time, and hashed install ID so Premium can be verified server-side.

Download history (on your phone)

Recent downloads (platform, title, date, local file path, and save status) are kept in your device's local storage. Android uses Room; iOS uses SwiftData. The local history database is not uploaded. Separately, Android may report limited terminal download diagnostics: hashed install ID, approximate country, platform, app version, transfer method, success/failure, a normalised reason, timestamp and known transferred-byte counts. These reports exclude media files, titles, filenames, local paths and direct media URLs; source links are included only through the optional failed-link sharing described in Android download diagnostics. Reports are subject to bounded backend retention and deletion. Clear local history in-app where available; downloaded files are separate from history records.

Android download diagnostics

To prevent a diagnostic request already accepted before deletion from recreating erased records, the server keeps a deletion marker containing only the hashed installation ID, a random value and the deletion time. This marker becomes eligible for removal after 30 days and is cleared in bounded maintenance batches; a maintenance delay can extend physical retention. No source link or event payload is kept in this marker. An installation-independent timestamp remains after cleanup to reject older, delayed requests.

Versions with reliable diagnostic delivery keep a small, bounded local queue while a report is waiting to be sent. The queue is limited to 256 records of up to 4 KB each. Reports older than 24 hours are no longer sent and are removed during local maintenance; Android power restrictions or an inactive app can delay physical cleanup. Failed source links are included only with the optional permission below. Turning sharing off invalidates previously queued links, including if sharing is later turned on again. “Delete my data” clears pending diagnostics. A random delivery identifier prevents retries from being counted as separate reports.

Android may automatically send technical diagnostics for resolution and save operations to investigate download errors and keep the service reliable. On versions supporting attempt diagnostics, these may include a random attempt UUID, bounded step durations, platform, app version, result and a bounded error code or reason, alongside the technical fields listed above. The UUID and hashed install ID connect recorded steps from the same installation. Automatic technical reporting is independent of the optional source-link setting below.

On Android versions offering Settings → “Share failed links”, the option is off by default. If you enable it, Mediora may additionally receive the original source link only for a final failed resolution or a failed/corrupt save, for troubleshooting. Successful operations, cancellations and intermediate resolver failures that later recover do not share source links through this feature. Older clients without the option do not send source URLs in these diagnostics.

Before a diagnostic source link is shared or stored, tracking and token parameters and fragments are removed; only supported content-identifying query parameters may remain. Authentication links, URLs containing credentials, and direct media/CDN links are rejected. A supported hostname does not establish that the linked content is public.

Shared failed links expire after seven days in active diagnostics. Expired links are hidden from diagnostic views and removed in bounded maintenance batches; technical records without source links may be retained longer under their existing rules. Restricted operational backups may contain older records as described in Backup. Turning the setting off stops future source-link sharing. To delete existing diagnostic records associated with your installation, use Android Settings → Delete my data; see Data retention and deletion.

Optional Android crash reports

Android versions offering Settings → Privacy → Crash reports use Google Firebase Crashlytics only with a separate optional choice, off by default. Usage measurement, personalized ads and failed-link sharing do not grant this choice. You can use the app without enabling crash reports. Existing users are not automatically opted in when the SDK is added.

With crash reporting enabled, Crashlytics processes stack traces, crash/ANR diagnostics, app and OS versions, device characteristics, timestamps and pseudonymous installation/session identifiers. Native crash reports are included. We do not set a Crashlytics user ID. Bounded custom save-failure reports contain a platform, transfer type, outcome and technical error code; we do not attach the source link, filename, clipboard, account, purchase token or the original network exception to these custom reports. Automatically captured crash traces can contain exception messages and technical runtime details; this is not a claim that SDK reports are anonymous. Google Analytics breadcrumbs follow the separate usage-measurement choice.

Turning the choice off immediately stops Mediora's additional save-failure callbacks and asks the SDK to disable collection and delete unsent reports. The SDK's automatic collection change takes full effect on the next app run. When automatic collection is disabled, the SDK can retain crash information locally on the device; it must not be treated as a guarantee that the SDK creates no local files. Deleting app data revokes the local preference. These actions cannot recall reports Google has already received. Test crash reports use a separate development Firebase project. See Crashlytics data collection controls and Firebase privacy information.

Ads and the advertising ID

Ad-supported builds show banner, interstitial, and rewarded ads via Google AdMob. On Android, AdMob may use the Android Advertising ID (AAID). On iOS, AdMob may use Apple's advertising identifier (IDFA) only where App Tracking Transparency and consent choices allow it.

On Android, the Google Mobile Ads SDK also collects and shares IP addresses (which may be used to estimate approximate location), product interactions such as app launches, taps and video views, technical diagnostic information, and device/account identifiers for advertising, analytics and fraud prevention, as described in Google's SDK disclosure. The failed-link sharing setting controls Mediora's optional diagnostic source links; advertising consent and identifier controls are separate.

To stop it on Android: Phone Settings → Privacy → Ads → Reset / Delete Advertising ID.
To control it on iOS: iOS Settings → Privacy & Security → Tracking.
To turn off personalized ads: AdMob shows a GDPR/UMP consent screen where required; you can decline personalization there. On iOS, Mediora starts the consent/ad flow only after you choose a rewarded ad action.
Premium subscription removes Mediora's ads. It does not remove Android permission declarations or change a separate usage-measurement choice. Websites opened in the in-app browser follow their own advertising practices.

Optional Android usage measurement

Android versions offering Settings → Usage measurement use Google Analytics for Firebase only after a separate opt-in. This option is off by default and does not enable personalized ads or failed-link sharing. The app remains usable when it is off. You can withdraw the choice at any time in Settings.

With this choice enabled, Google Analytics processes app interactions, app/OS and device information, installation/referral metadata, approximate location derived by Google, timestamps and an app-instance identifier. The app-instance identifier is pseudonymous, not anonymous. Mediora records bounded ad format/placement, load/show outcomes and SDK error codes; ad value/currency/precision; and final save outcomes with broad size/time bands and platform/transfer type. The SDK may also produce standard session and ad-revenue events, and purchase/subscription events containing product identifiers, product names and prices. We do not set an Analytics user ID or enable Google signals. Test measurements use a separate development project.

We do not attach pasted or visited links, titles, filenames, clipboard content, cookies, credentials, email addresses, social usernames, Mediora installation IDs, purchase tokens or diagnostic attempt/save IDs to these events. Analytics advertising-ID collection, automatic screen reporting, advertising storage, advertising user data and personalization signals are disabled in this initial integration. AdMob's existing advertising disclosures remain separate.

Turning usage measurement off stops subsequent app measurement callbacks and requests a local Analytics data/instance reset. Deleting app data also revokes this preference and resets local measurement state. These actions do not guarantee deletion of events already received by Google. Those records follow the Analytics property's retention settings and Google's processing rules; contact us for assistance with a data-rights request. The Mediora install ID alone cannot identify an Analytics app instance because we do not send that ID to Google Analytics. See Google's Analytics data disclosure and Firebase privacy information.

Third parties

Sign in with Google — verifies optional Connect accounts. Google processes sign-in, while Mediora retains the pseudonymous account key and Connect records described above. Google privacy policy: policies.google.com/privacy.
Google Play Billing — handles Android Premium subscriptions where available. Payment is collected by Google; we never see your card details. The subscription record lives in your Google Play account. The app and backend verify whether the subscription is active and store only the entitlement state needed to unlock Premium.
- Cancel: the in-app "Manage subscription" button takes you straight to Play Store → Profile → Payments and subscriptions → Mediora. After cancelling you stay Premium until the end of the billing period.
- Refund: Refund eligibility and processing follow Google Play's refund policy and applicable consumer rights; a refund is not guaranteed merely because 48 hours have not elapsed. You can also contact morphaven@outlook.com for assistance.
Apple App Store / StoreKit — handles iOS Premium subscriptions where available. Payment is collected by Apple; we never see your card details. The app and backend verify signed transaction status needed to unlock Premium.
- Cancel: iOS Settings → Apple Account → Subscriptions → Mediora.
- Refund: Apple handles App Store refund requests through reportaproblem.apple.com.
Google AdMob — for ad delivery under Google's privacy policy and the disclosures above. In addition to aggregate reports, the SDK can provide per-impression estimated ad value to the app. When optional usage measurement is enabled, the bounded ad-value event described above can be sent to Analytics. An impression value is not the user's identity or a guarantee of final revenue.
Google Analytics for Firebase — optional usage/ad measurement in Android versions offering that choice, under the separate opt-in and limits above. This is distinct from our existing backend operational diagnostics.
Cloudflare Turnstile — used on the website to block bot signups. Generates a short-lived token similar to a CAPTCHA. Doesn't collect email or user info. Cloudflare privacy policy: cloudflare.com/privacypolicy.
Mediora backend — runs the actual video metadata extraction (yt-dlp based) behind morphaven.com/mediora/api and related infrastructure. It receives your URL, fetches a response from the target platform, and returns it to you. It also stores pseudonymous analytics, feedback, quota/reward state, and Premium entitlement cache records as described above.

Platform content

Mediora itself hosts no video content. It fetches publicly available content published by TikTok, Instagram, Twitter/X, Pinterest, Reddit, Facebook, Twitch, and Bilibili at the user's request. Copyright in any downloaded content belongs to the original publisher; you are responsible for using it only for personal use or other purposes the publisher has explicitly permitted.

Data sharing and sale

No personal data is sold to third parties. We don't share user profiles with ad networks or data brokers. The advertising ID that AdMob uses for targeting falls under Google's own policy — you can reset or delete it from Android settings, and you can control iOS tracking permission from iOS Privacy & Security settings.

Backup

Android cloud backup: OFF. allowBackup=false — your download history and settings are not included in Google Drive backups.
Android device-to-device transfer: ON. Android's Setup Wizard can copy directly from your old phone to a new one without going through the cloud.
iOS backup: iOS may include app-local data in encrypted device or iCloud backups according to your Apple backup settings. Downloaded files remain local to your device storage unless you share or move them yourself.
Operational server backups: restricted backups used for recovery may contain older records. If an older backup is restored, confirmed account deletions must be reapplied before the restored account data is used.

Data retention and deletion

To remove your in-app history:

"Settings → Clear history" wipes recent downloads where available.
Uninstalling removes app-local history and preferences; files saved outside the app's private storage remain.

Server-side pseudonymous analytics, feedback and operational records are cleaned in bounded maintenance batches according to their retention rules. Purchase ownership, balances, transactions, refund evidence and abuse-prevention records needed to protect payments are retained under their existing rules. Android Settings → Delete my data removes local history/preferences and matching non-financial backend data, including that phone's Connect linkage and jobs; partial server failures are reported by the app. Saved media files and paid purchase evidence are preserved, and this does not cancel a store subscription or reset purchase rights. To request assistance deleting matching backend records, email morphaven@outlook.com and include the install ID shown in the app settings where needed to locate its hashed records.

Delete your Connect account

Open Mediora Connect, sign in with the Google account used for Connect, open Account settings, choose Delete Connect account and confirm. You can do this in a browser without installing or reinstalling the app. On Android, the portal is also reachable from Settings → Connect.

Account deletion removes all linked phones, pending re-pair requests for currently linked phones, source links, queue history, retry/quota receipts and browser sessions from the active Connect database. It preserves files saved on your phone, your Google account and existing purchase/payment evidence; subscription cancellation is separate. Deleting one phone's data or unlinking one phone does not delete a Connect account shared with other phones. Restricted operational backups may still contain earlier records as described above.

If you cannot sign in, request help at morphaven@outlook.com. Ownership must be verified before account deletion; an email address alone is not sufficient because Connect does not store your Google email address. Do not send passwords, pairing codes or session credentials.

Security

The local database lives in the platform app sandbox. Android uses app-private storage; iOS uses the app container.
All network traffic is TLS-encrypted; cleartext HTTP is rejected.
Release builds go through R8/ProGuard minification and obfuscation before reaching Play Store.
Play Billing purchase tokens are signed and verified on Google's side.
App Store transactions are signed by Apple and must be verified server-side before iOS Premium is trusted.
Backend SSRF protection: the server only fetches URLs whose host belongs to a small whitelist (TikTok, Instagram, Twitter, Pinterest, Reddit, Facebook, Twitch, Bilibili); HTTP redirects are not followed.

Permissions

The Android permissions Mediora requests, with reasons:

INTERNET, ACCESS_NETWORK_STATE — fetch video metadata and watch download status (required).
POST_NOTIFICATIONS (Android 13+) — requested when you enable notification-dependent features, such as the quick shortcut or download progress.
FOREGROUND_SERVICE, FOREGROUND_SERVICE_DATA_SYNC — keep long downloads running in the background.
com.google.android.gms.permission.AD_ID — declared for AdMob's permitted advertising-identifier use, subject to consent, Android identifier controls and ad-serving configuration. Premium removes Mediora's ads; it does not remove this permission from the installed package. Firebase Analytics advertising-ID collection is disabled separately.

The iOS permissions Mediora requests, with reasons:

Photo Library Add access — only to save downloaded media to Photos when you choose that action.
Tracking permission — requested only if an ad-supported iOS build needs App Tracking Transparency for personalized ads.

Mediora does not request location, contacts, camera, or microphone access.

Children

Mediora is not directed at children under 13. We do not knowingly collect data from anyone under 13. Ad requests are configured conservatively for age-appropriate delivery: Android may use Google's under-age/age-treatment controls where applicable, and the iOS client sets Google Mobile Ads age treatment and maximum ad content rating to the teen level before loading ads.

Your KVKK / GDPR rights

Under the Turkish Personal Data Protection Law (KVKK, no. 6698) and equivalent rights for GDPR users:

The right to know whether your data is being processed — Mediora processes pseudonymous app data as described above.
The right to request information if it has been processed.
The right to request correction or deletion.
The right to know whether data has been transferred to third parties — AdMob (Google), Play Billing (Google), Apple App Store / StoreKit (Apple), Cloudflare Turnstile (Cloudflare).
The right to object to outcomes derived from automated processing.

Send any data-rights request to morphaven@outlook.com.

Changes

This policy may be updated over time. Material changes are surfaced in the app and reflected in the "Last updated" date above. Mediora release notes can also be tracked from the Play Store or App Store listing page, depending on your platform.

Contact

For any privacy question: morphaven@outlook.com