Mantle Open the web app

Privacy notice

Last updated

Mantle has no telemetry or analytics, and it works without an account. This page says what the apps, the optional Mantle account and this website do with your data.

Who runs Mantle

Mantle is a free, open-source project published under the name sotherdev, under the MIT licence (LICENSE). For a privacy question or request, write to privacy@mantlevid.com.

Without an account

The Windows, Android and web apps keep your library, settings, watch history and plugin settings on your device. In the web app they are kept in your browser's storage. Without an account, none of it goes to a server of Mantle's.

The keys and sign-ins that plugins keep, and your Mantle account’s sign-in and key, are stored on your device too, encrypted. In the Windows app (and the server build) they are encrypted under a key kept in the data folder, beside them. That is what lets the folder move to another computer or a thumb drive as it is, and it means that anyone who has the folder, or a copy of it, has them. In the Android app the key is held by the Android Keystore, so the keys and sign-ins cannot be read from a copy of the app’s files (the rest of what the app keeps there, your library and history, is not encrypted). In a browser they are encrypted under a key the browser keeps for the page, which protects against a dump of what the browser stores, but not against script running in the page or someone with the browser’s whole profile.

What the apps contact

Any service an app contacts sees your IP address and the request itself. Without an account, the apps contact these on their own:

  • Metadata. Once a metadata plugin is on, Home asks its service for its shelves, and the apps ask it about the titles on screen: cards in Home, search, your library and history. In the background they also describe the titles in your library, history and progress: when the app starts, once an hour, and when titles are added, again once a day for a series or a week for a film.
  • Stremio-style addons. At start, and when you check for updates, the app reads each addon's manifest again from its host.
  • Media servers. A media-server plugin reads its libraries when the app starts, when you sign in or out, and as its shelves are shown.
  • Calendar. Opening the Calendar sends the series in your library, by their ids, to the calendar's service.
  • Debrid Ready shelf. On Home, a debrid plugin asks your account for its list of torrents, at most every 20 seconds. The names of up to 30 releases are then looked up in a catalog plugin to find their titles.
  • The update check. The Windows, Android and web apps look for a newer version when they start and once a day after. Each look is two requests, for https://app.mantlevid.com/releases.json, a file that lists Mantle's releases, and for https://app.mantlevid.com/releases.json.sig, its signature, which Mantle checks to know the list is Mantle's. In the Windows and Android apps the request says it comes from Mantle/<version> (+https://mantlevid.com), so the host can see which version asks. In the web app your browser sends its usual headers. The request carries nothing about your library or profiles. To turn it off, or to read another feed, use Settings → Data and storage → About. A new version is downloaded only when you choose to update, from the release on CodeFloe, and the app checks it against the release's SHA-256 sum before it installs it.
  • Trailers. When you play a trailer, the app shows YouTube's player (youtube-nocookie.com) inside the page. YouTube receives the request and handles it under its own policy.
  • Pictures and streams. Posters, backdrops and subtitles are fetched from the address a plugin's provider gives, and videos play from the service that provides them. Those services see your request. No server of Mantle's sits in between.

The apps and this website use fonts that come with them, and ask no one else for fonts.

Plugins

Everything beyond Mantle's core is a plugin, and plugins are how Mantle reaches other services: your Jellyfin server, Real-Debrid, TorBox, Trakt, OpenSubtitles, The Movie Database, Cinemeta, Stremio addons and others. A plugin can reach only the hosts it declares, and only if you allow it the network. You can refuse the network for a plugin when you install it, and change that later in its details. A plugin may declare that its service can send it on to other addresses, as a Stremio addon's does, or where the pictures and subtitles it passes on may come from.

Each service's own privacy policy applies to what you send it. A plugin sends what its service needs to answer, including the shelves and lists it shows on its own: a search you typed, the title you opened, or the key or sign-in you gave the plugin. In the Windows and Android apps, a plugin's requests say by default that they come from Mantle and which version. In the web app your browser sends its own headers.

If you add a plugin repository, or install a plugin from a link, Mantle reads it from the address you gave.

Logs and telemetry

Mantle has no telemetry, analytics, tracking or crash reporting. Nothing sends your usage, or your log, to anyone.

The Windows and Android apps keep a log file on your device, in mantle-data/logs (on Android, in the app's own storage): mantle.log, and mantle-previous.log once the first passes 1 MB. It records what happened in the app, such as what a plugin did, why a request failed and which titles you played, so that a problem can be found. It stays on your device unless you copy it somewhere yourself. The web app keeps no log file.

Mantle Together

Mantle Together is an optional account for your household. It keeps your profiles in step across your devices, and lets profiles be friends, share lists and watch together. The Mantle Together guide explains each part.

Until you sign in, or ask to join the account from another device, the apps do not contact the account service. The exception is a watch party: joining one connects your device to the service, with or without an account.

Where it runs

The service runs on Supabase, a hosted database and sign-in provider. Sign-in emails are sent through Resend, from noreply@mantlevid.com. Both handle your email address under their own privacy policies.

Signing in

You sign in with your email address. Mantle emails you a code that works for an hour, and you type it into the app. You can also give the account a password and sign in with that instead.

What the service can read

The service keeps what it needs to sync. It can see:

  • your email address;
  • which profiles and devices the account has, what kind of device each is that signed in with your email (Android, Windows, web and so on), which profile a device holds alone, when each was added, and when a device was last seen;
  • how many items each profile and shared list keeps, how large each is, the order they were written in, and when the account last changed;
  • which profiles are friends, and whom a profile has blocked;
  • which profiles share each list, and what each can do, and which of them wrote each thing kept in it;
  • whether each device is known to hold the account's key, and a fingerprint of a secret that only the key gives, so it can tell such a device from one that has only your email (the fingerprint cannot be turned back into the key);
  • whom the host of a watch party invited by name, and when.
  • when you ask for a sign-in code: for fifteen minutes, a scrambled form of your email address and of the network address you asked from (hashes with a salt that is made again every hour), so that an account can be made for the address; and, for each new account, a scrambled form of the network address it was made from, for the hour, so that one network cannot make accounts without end. A salt is kept for an hour after it is replaced, for the tickets asked with it, so a hash can last two hours at most, and none can be matched to an address once its salt is gone.

A device that joins without your email gets a sign-in of its own with no email address.

What it cannot read

Everything a synced profile keeps is encrypted on your device before it is sent, with AES-256-GCM and keys your devices make. That covers its name and picture, library, lists, favourites, watch progress, history, recent searches and settings. It also covers the household's plugins and their settings, the keys you typed into plugins' settings, such as a TorBox API key or a Jellyfin password, and the sign-ins that sync (Trakt's, Nuvio's and Stremio's). The Real-Debrid sign-in does not sync. The service cannot read a shared list's titles and notes, the devices' names, or anything played or said in a watch party.

The account's key reaches the service only sealed: with your recovery code, which is how the code brings your profiles back, and to a device you are approving, for that device alone to open. The service can tell when an item is written again, but not what the item is.

A device that holds every profile of the account can open all of them, and change what the household shares, such as its plugins and what they may do. A device that holds one profile can read what the household shares and write none of it, writes its own profile, and reaches no other. Approve Every profile only for a device you trust.

What the people you share with see

Friends are made between profiles by invite alone: there is no directory and no search. A friend sees your profile's name and picture. So does anyone who has a friend invite's link, code or QR code, before they accept it: it shows who made it, so give it only to the person you mean. The people in a shared list see its name, its rules, its titles and their order, the notes on them, and who shares it. Everyone in a watch party sees what is playing and where, a fingerprint of the source the host plays it from (someone with the same release can tell it is that one; it says nothing else), the chat and the reactions, and each member's name, colour and icon. Anyone who has a party's code, link or QR code can join it, so share it only with people you want there.

How long it is kept

The service has no cleanup that removes account data over time, except for these short-lived items. A request, an invite or a party that has run out can no longer be used or read, and is removed by the service's cleanup, which runs when someone next asks to join, makes an invite or starts a party (at most once a minute). On a quiet service that can be later than the times below:

  • A device's request to join the account lasts 15 minutes.
  • A friend invite lasts a week.
  • A watch party's invitations go when the party ends, and any left behind are removed after twelve hours.
  • A device that asked to join without your email, and was never approved, is removed after a day.
  • An account that was never used (it asked for a sign-in code and no more: it has no device, profile or sign-in) is removed after a day.
  • The scrambled network and email addresses go when the first sign-in code is asked for after their time (a ticket after fifteen minutes, or when it makes its account; the network's count after the hour, and two at most), and are never used after: on a quiet service they stay until then.
  • A device that signed in with your email and never got the account’s key is taken out, and signed out, once it has not been seen, nor asked for the key, nor renewed its sign-in, for a day. One that is open says it is there. This starts two weeks after the account service takes the change: until then none is taken out.
  • A device whose sign-in has ended is taken off the account's list of devices.
  • An account you delete is deleted 7 days after you ask, by a cleanup that runs every minute (below).

When you delete something that syncs, the service keeps an encrypted marker that it was deleted, so that your other devices hear of it. The marker goes when its profile is taken out of the account or the account is deleted.

A title you take out of a list that syncs stays in that list's encrypted record, with when it was taken out, until the list has been changed more than 90 days after, so that a device that syncs within 90 days of the list's changes does not bring it back; if the list is not changed again it stays for good, until the list, its profile or the account is deleted. Only your devices can read it. What the service sees of the record, its size, is larger by it.

Supabase and Resend may keep their own records, such as backups or logs, under their own policies. Deleting the account does not reach those.

Deleting the account

A profile that manages the account, on a device that holds every profile, can delete it: Settings → Account → Delete the account. It is deleted 7 days after you ask, within a few minutes of that time (the service's cleanup runs every minute). Until then the service keeps what it has and accepts nothing new from the account's own devices, every device signed in says when, and a profile that manages the account can keep it (Keep the account). Then everything the service keeps goes: the account's email address and sign-in, its profiles' synced data, their friendships, shared lists and parties, and its devices. Every device is signed out, and its profiles stay on it, as profiles of that device alone. This cannot be undone.

Short of that, you can sign a device out, take a device out of the account, take a profile out of the account (which deletes what the service keeps of it), or stop a profile syncing on a device.

This website

mantlevid.com and app.mantlevid.com are static sites, served by CodeFloe Pages. CodeFloe may keep standard server logs under its own policy. Mantle's downloads and source code are on CodeFloe too, and a link to them leaves this site for CodeFloe's.

This website stores one thing in your browser: if you pick a theme, its name, under mantle-theme in the browser's local storage, so that the next page shows it. It stays in your browser and is not sent anywhere. The pages set no cookies, use no analytics or tracking scripts, and load nothing from other sites: their fonts, pictures, styles and scripts are their own. The page reads your browser's user agent to show your system's download first, and does nothing else with it.

The web app at app.mantlevid.com keeps your data in your browser's storage, as described above. Its files are served by the host, but your data never reaches the host. It stays in the browser until you clear the site's data, or until the browser clears it itself when the disk runs low, which it may do unless it has agreed to keep it (Settings → Data and storage → Keeping your data says whether it has).

Your choices

  • You do not need an account. In the first run, press Skip on the Account step.
  • You can turn off the update check in Settings → Data and storage → About.
  • You choose which plugins are on, and can refuse a plugin the network.
  • Export in Settings → Data and storage saves your library, lists and watch history as one file. Share your setup, in the same place, saves your plugins, settings and lists as a code or a file.
  • To delete data: Clear history on the History page clears your watch history, and Delete profile removes a profile with its library, lists, progress, history and settings. Deleting the mantle-data folder removes the profiles, settings and plugins the desktop app keeps (downloaded files are separate, in your download folders). Clearing the site's data in your browser removes everything the web app keeps, and uninstalling the Android app deletes its data. Deleting a Mantle account is described above.
  • For anything else, write to privacy@mantlevid.com.

Changes

When this page changes, the date at the top changes. The page's text is home/privacy.md in the repository on CodeFloe, and the repository's history keeps every version of it.