Privacy policy

1.No account, no advertising

Nexora needs no account or sign-up. It has no advertising and does not send your viewing activity to us. Usage statistics and crash reports (Google Analytics for Firebase and Firebase Crashlytics) are each off unless you allow them, and even then they never include what you watch.

2.Where your data is

Your sources, channels, favourites, My list, watch history, reminders, downloads and settings are stored on your device, not with Nexora. So are a temporary cache for peer-to-peer playback and records of how well each source played (used to pick the copy that plays). If Android backup is on, Android also keeps your settings (not passwords, the parental PIN, the peer-to-peer choice or add-on secrets) in your own Google account backup. When you move to a new phone with Android's device-to-device transfer, your sources and their links move too (links can contain sign-in details); the parental PIN, add-on secrets and your usage statistics choice do not. Your usage statistics and crash reports choice is never backed up or moved: Nexora asks again on a new device, and both stay off until you allow them. A backup file you save is not encrypted and can contain sign-in details, so keep it private. Removing the app removes what is on the device, except pictures you saved to your gallery.

3.The services you add

Nexora connects to the playlists, guides, add-ons and servers you add, and to the addresses they name for streams, pictures and subtitles. Each of them sees your network address and the requests the app makes, under its own privacy policy. A home media server you sign in to (Jellyfin or Emby) also receives your device's name, a random ID Nexora creates for this installation, and what you play from it, as those servers expect. Nexora (the developer) does not receive any of these requests.

4.Matching titles with your add-ons

To show a film or series from one source together with the same title elsewhere, and to fill in pictures, cast and episode lists, Nexora sends the title's name (and year, when known) to the catalog add-ons you turned on. When a video plays, subtitle add-ons you turned on receive its file name, size and a fingerprint (hash) of the file, so they can find matching subtitles. Suggestions, More like this and cast pages ask your add-ons for genres and people's names. Nothing else about you is sent, and add-ons you did not turn on receive nothing.

5.Peer-to-peer playback and downloads

Peer-to-peer is off until you turn it on. While a torrent streams — in Nexora, or in the app you chose with “Play with” (Nexora Pro) — and afterwards, if you turn on “Continue sharing after playback”, your device downloads pieces of it from other people and shares the pieces it has with them. To find those people, Nexora uses the torrent network (DHT), the trackers the torrent names and, when it names fewer than five, a few public trackers; they and the other people in the swarm can see your network address and what you are sharing. A download you start works the same way while it runs and stops sharing when it finishes; the file stays in Nexora's storage on this device until you delete it. A notification shows whenever Nexora downloads or shares.

6.Your phone and TV

Pairing, sync, typing on your phone for the TV and backups between your own phone and TV go directly between the two devices on your network, encrypted, with no Nexora server in between. After pairing, the phone keeps the TV up to date by itself for 10 minutes; with Nexora Pro it keeps syncing while Nexora is open; without Pro, Sync now sends changes and the phone checks the TV for requests while Nexora is open. What syncs: your sources and guide links, favourites, My list, hidden items, groups, reminders, watch history and Continue watching, playback and appearance settings, and the names of your add-ons (never add-on links, home media server passwords or the parental PIN); parental rules only if you choose them. Text you type on the phone for a TV field (which can be a password) goes only to that TV. While a phone is paired, the TV listens on your home network and announces its name there so the phone can find it; turn off “Phones on this network can connect” in the TV's Devices settings to stop this. The TV's optional “Back up or restore in a browser” page is not encrypted: it opens only with a one-time code for 10 minutes; use it only on your own network.

7.Casting and other apps

When you cast, Nexora sends the stream's address and its title to the TV or speaker you choose on your network. “Open in another app” gives the stream's address to the app you choose. What those devices and apps do with it is up to them. Nexora never installs other apps, and add-ons run no code on your device: Nexora only reads what they send.

8.Crash records and reports you send

If the app crashes, it keeps a short crash record on this device. Report a problem prepares a message that you send yourself, from an editable email draft to Nexora support or, if email is unavailable, your share sheet: the app version, device maker and model, Android version, how many sources of each type you have, and the code lines of recent crashes — never links, names, passwords or what you watch. Report this add-on adds the add-on's name, ID, address host, version and the list it came from. Nothing else is sent unless you allow crash reports (section 10): then Firebase Crashlytics also sends crash reports to Google. With that setting on, choosing Report a problem also queues a diagnostic report as described in section 10. The editable share-sheet message is not sent to Firebase.

9.Purchases

Nexora Pro is bought through Google Play, which handles the payment; Nexora never sees your card or payment details. The app learns from Google Play which plan you have (monthly, yearly or Lifetime), whether it is active and whether a free trial is offered to you, and it keeps on this device only the time Google Play last confirmed Pro (so viewing stays unlimited for up to 3 days if Google Play cannot be reached).

10.Usage statistics and crash reports (Google Firebase)

Nexora asks once, on first start, whether you allow usage statistics and crash reports: you can allow both, choose each one yourself, or choose Not now; later, Settings → Storage & privacy has one switch for each ("Share usage statistics", "Send crash reports"). Each is off until you allow it (opt-in); accepting the terms is not that permission, and developer debug builds never collect. When you allow them, Nexora uses two Google services, each only for the choice you turned on.

Google Analytics for Firebase: Nexora sends only which features and screens are used (for example "search used" or "a movie started"), which switches are turned on or off, a session-length range and whether it is a phone or a TV; Firebase adds an app-instance ID (a random ID for this installation of Nexora, not your advertising ID), device and app information (such as device model, Android version, app version and language), its standard app events (such as first open, session start and a Nexora Pro purchase made through Google Play) and an approximate location (such as country, region and city) that Google derives from your IP address. For Nexora Pro it also sends, without any other detail: that the free daily viewing ran out (live TV or on demand), that the Nexora Pro page was opened and from where (the limit, Settings, the Home banner or elsewhere), and which plan a purchase was started or completed with (monthly, yearly or lifetime, with or without a free trial). To help fix problems it also sends coarse playback-quality ranges and outcomes as fixed words only: how long a video took to start (for example "under 3 seconds"), how often it paused to buffer, the type of a playback error (for example "network" or "decoder"), and whether a sync, a purchase step or an add-on install worked.

Firebase Crashlytics: when the app crashes or stops responding, it sends a crash report with the stack trace and technical details of the error, device and app information and a Crashlytics installation ID; crash reports are not anonymous and can include technical details of what the app was doing. Nexora adds fixed facts that help find the cause — phone or TV, debug or release build, Free or Pro, whether the device has little memory, the network type, the language, the screen shown, the player's state, the kind of source playing (for example "playlist" or "add-on") and roughly how many add-ons are installed — and, only if you also allow usage statistics, the recent usage events above. It also sends reports of errors the app handled (for example a playback, sync or purchase error): the error type and the code lines only, never the error's message, at most ten per session. When you choose Report a problem with crash sharing on, Nexora also records a diagnostic report: these same app and device facts, ranges for the number of sources and local crash records, the kind of latest local exit (crash, unresponsive app or native crash), and the latest handled error’s type and code lines if available. These explicit reports are limited to three per app session. Turning crash sharing off clears the handled-error detail retained for this purpose. Firebase determines when queued reports upload; the text you can edit in the share sheet is never sent to Firebase.

Nexora never sends what you watch, titles, links, add-on or source names, searches, error messages or anything you type, and never uses your advertising ID or Android ID; ad personalisation and Google signals are off. Google processes this data for us as a service provider; Analytics data is kept for 2 months and crash reports for up to 90 days.

To opt out, turn a switch off: collection stops at once; turning statistics off resets the analytics data on your device (including the app-instance ID), and turning crash reports off deletes crash reports not yet sent. To ask us to delete data already collected, e-mail greate43.sk.dev@gmail.com.

11.Scanning a pairing code

On a phone, scanning the TV's pairing code inside Nexora uses Google's code scanner from Google Play services. It reads the code on your phone; Google may receive diagnostics about the scanner, such as the device model, app version, performance and a per-installation identifier, under Google's privacy policy. Nexora receives nothing from it beyond what pairing needs. The code is also a link to Nexora's website, so your phone's own camera can open it; if it opens in a browser, the website's host (GitHub) sees your network address, but the pairing code itself is never sent to the website.

12.Nexora's add-on lists and Nexora Public Domain

To show Add-ons, the app downloads Nexora's public add-on lists from Nexora's website when you open Add-ons and about every 6 hours. The request carries no account, identifier or anything about what you watch or install; like any website, the host (GitHub) sees your network address. The app uses a downloaded list only if its signature checks out against a key built into the app and it is newer than the copy the app already has; otherwise it keeps what it has, and a copy bundled in the app is the fallback when you are offline. Nexora does not learn which add-ons you install, update or remove: the app contacts an add-on's own server (section 3) only when you add, refresh or use that add-on, and it shows you a preview before it installs or updates one. To tell you about updates, the app also downloads a small public file with Nexora's newest and minimum version from the same website when it opens or comes back to the front, and asks Google Play whether a newer Nexora build is available for your device; nothing about you is in that request either. Nexora Public Domain, the add-on Nexora makes, is served from the same website, and its films play from the Internet Archive, which sees your network address under its own privacy policy.

13.Permissions

Nexora asks Android for: notifications (to show peer-to-peer sharing, downloads, imports and programme reminders), nearby Wi-Fi devices / local network access (only to find, pair and sync with your own phone or TV), and, on Android 10 and older, storage (only to save a picture you choose to save). It also uses permissions Android grants without asking: internet and network state (to load what you add), Wi-Fi state and multicast (to find your own phone or TV on your network) and keep-awake (so playback and background work such as imports and syncing are not cut short). Imports, backups and restores can run as a foreground service of the data-sync type, with a notification. Nexora does not use the camera permission (the pairing scanner is Google's), your location or your advertising ID, and it cannot install other apps.

14.This website

This website uses no cookies, analytics, tracking, advertising or third-party scripts and fonts. It is hosted on GitHub Pages; GitHub receives your network address and browser details to serve the pages, under GitHub's privacy statement.

15.Children

Nexora is meant for adults and is not directed at children; we do not knowingly collect data from them. The parental PIN stays on the device where it was set and is never synced or backed up; parental rules travel to your own paired device only if you choose them under “Choose what syncs”, and only to make that device stricter.

16.Who is responsible, and your rights

Who is responsible: Greatdev Studios, the developer of Nexora, is responsible for the data described here (the controller under the GDPR and UK GDPR). Contact: greate43.sk.dev@gmail.com.

Why we may use data: usage statistics and crash reports only with your consent (the "Help improve Nexora" page or the switch in Settings), which you can withdraw at any time by turning the switch off; this does not affect what was sent before. Nexora's add-on lists and this website: to provide them (legitimate interests). Messages, notices and add-on submissions you send: to answer them and to handle notices and submissions (legitimate interests, or an obligation under copyright law).

Who processes data for us: Google, through Google Analytics for Firebase and Firebase Crashlytics, for usage statistics and crash reports when you allow them (our processor under Google's Firebase data processing terms); GitHub, for this website and the add-on lists; Google, for the code scanner and Play Billing, under Google's own terms.

Transfers: the developer is in Australia. Google may store and process statistics and crash reports on its servers outside your country, including in the United States; e-mails are handled from Australia. Where the GDPR or UK GDPR applies, these transfers rely on the safeguards the law provides, such as the standard contractual clauses in Google's data processing terms.

Your rights: depending on where you live (for example under the GDPR, the UK GDPR, the Australian Privacy Act or Californian law), you may ask for access to, correction or deletion of personal data we hold about you, object to its use, or withdraw consent. Statistics and crash reports are linked only to random IDs for the installation (the app-instance ID and the Crashlytics installation ID), not to your name or e-mail address, so we usually cannot find records about one person; we will tell you if that is the case. You can complain to your data protection authority (for example the OAIC in Australia, the ICO in the United Kingdom, or the authority in your EU country). Nexora does not sell or share personal information for advertising: Google signals, ad personalisation and data sharing with other Google products are off.

17.When you contact Nexora, and how long data is kept

If you e-mail Nexora or send a notice, Nexora receives your e-mail address and what you write, and keeps them only as long as needed to deal with it, and no more than 2 years after the matter is closed. For a notice about an add-on, Nexora may share its content (not your e-mail address, unless you agree) with the add-on's developer. If you ask for an add-on to be added to Nexora's Community list, Nexora receives your e-mail address and what you send (the add-on's address and, if you give them, your name and contact details). Nexora keeps your e-mail address and contact details only as long as needed to deal with the request, and no more than 2 years after it is closed. The add-on's name, description, version and public address are published in Nexora's public list for as long as it is listed, so send only the add-on's public address, never a link that contains your own settings or sign-in details. GitHub issues are public: please do not post personal information there. If you allow usage statistics and crash reports (section 10), Google Analytics for Firebase keeps the statistics for us for 2 months and Firebase Crashlytics keeps crash reports for up to 90 days. Nexora (the developer) keeps no data about you on its own servers. Everything else Nexora stores is on your device: clear history and recent searches in Settings → Storage & privacy, delete downloads in Downloads, or remove the app to delete all of it. To ask Nexora to delete anything it holds about you, write to greate43.sk.dev@gmail.com.

18.Changes

Changes are published on this page with a new effective date. The app's Privacy policy links always open this page, so it is the current text.

19.Contact

Questions about this policy or your data: greate43.sk.dev@gmail.com. Nexora does not monitor what you watch.