Privacy
This page covers two things: the website seanimemobile.com and the Android app Seanime Mobile. The short version: neither tracks you, and I don't run a server that receives anything from you.
Last updated: 17 November 2026
- 0 cookies
- 0 trackers and analytics
- 0 ads or ad IDs
- 0 servers of mine
Who is responsible
Nick Schäfer, Canton of Basel-Landschaft, Switzerland. Email: info@seanimemobile.com. I build Seanime Mobile and this website in my spare time, as a private person. More in the imprint.
Questions about your data go to that address. Bug reports can also go to the issue tracker on GitHub, but issues are public, so please don't put personal details in them.
Part 1 · The website
No cookies, no banner
The website sets no cookies, its own or anyone else's. There is no analytics tool, no advertising, no embedded video player, no font or script from another server, no newsletter and no contact form. A rule the site sends to your browser (its Content Security Policy) blocks every connection except to the site itself and to GitHub's API.
There is no consent banner because there is nothing to agree to. The few entries below are saved only when you use the feature they belong to.
What stays in your browser
sm-setuplocalStorage · until you delete it- Your progress in the five setup steps: which ones you ticked and which one is open. Saved when you use the checklist. Start over empties it.
sm-themelocalStorage · until you delete it- The colour theme you picked. Saved only when you choose one, removed when you go back to the default theme.
sm-ghsessionStorage · 30 minutes, gone when the tab closes- A copy of GitHub's public release data (version, date, size, download count, stars, checksum, release notes), so a reload doesn't ask GitHub again.
These entries never leave your device and I can't read them. To remove them, clear the site data for seanimemobile.com in your browser. If your browser blocks storage, the page still works; it just forgets. The page reads your browser's user agent only on your device, to guess whether you're on Android, a computer or an iPhone; it is not sent anywhere.
What GitHub sees
When the start page loads, your browser asks api.github.com twice for public data about the project: the list of releases and the star count. That's where the version, the download link and the checksum come from. The requests carry no cookies and no login.
GitHub receives your IP address, your browser's details, the time, and the fact that the request came from seanimemobile.com. The APK isn't stored on this website: the download button links to the release file on GitHub, so the download is between you and GitHub. GitHub is a US company; how it handles data is in the GitHub General Privacy Statement.
Purpose: showing current release data and a working download link. The other pages (this one, help, imprint) don't contact GitHub.
Hosting at Cloudflare
The website is a set of static files on Cloudflare Pages. To deliver a page, Cloudflare processes your IP address and the technical details of the request (address, time, browser) and keeps server logs to run and protect its network. For these logs Cloudflare works on my behalf as a processor, under its data processing addendum. Cloudflare has servers worldwide, including in the United States.
I haven't switched on any visitor analytics, and I don't look at data about single visitors. Cloudflare's own rules: Cloudflare Privacy Policy.
If you write to me
Mail to info@seanimemobile.com is forwarded by Cloudflare's email routing to my personal mailbox. Cloudflare and my mail provider handle the message (sender, subject, content) to deliver it. I use it only to answer you and delete it when the matter is done, unless the law requires me to keep it.
Links and the marketplace address
The site links to other websites, such as GitHub, AniList, Obtainium and Seanime. Nothing goes to them until you click; after that, their rules apply.
Step 4 of the setup shows the address of a community marketplace as text and as a QR code. The website only displays that address. It never requests it.
Part 2 · The app
The short version
- No telemetry, no crash reports, no analytics, no advertising and no advertising ID. The code contains no such library.
- I run no server for the app and receive no data from it. Every connection goes straight from your device to the service named below.
- Notifications are planned on the device. There is no push service.
- The app's own logs hide tokens and passwords.
The code is public on GitHub, so all of this can be checked.
What stays on your device
- Your AniList token, a debrid key and the Nakama password, if you add them: in Android's encrypted storage.
- Settings, appearance and the order of Home, in a database inside the app.
- Watch positions and history, copies of your AniList lists and changes that are waiting to go out.
- The local account's lists, if you use it.
- Extensions and their settings, playlists, local files you scanned and their scan reports.
- Downloads: episodes, chapters and torrent data in the app's own folder, and a downloaded update until it is installed.
- Cookies of sources: some sources sit behind a Cloudflare check. A hidden browser inside the app passes it and keeps those sites' cookies. It never gets your token.
Android's cloud backup is switched off for the app. Uninstalling the app deletes all of the above.
Settings → App → Backup writes a file to the place you choose. It holds settings, watch positions, waiting AniList changes, extension settings, playlists and local lists. It never holds your AniList token, a debrid key, a password, or your downloads. The file is not encrypted, so keep it somewhere safe.
Where the app connects
Each of these services sees your IP address and the request. What they do with it is up to them.
| Service | What goes there | When |
|---|---|---|
| AniList | Requests for your lists and the catalogue. Signed in: your token and your list changes (progress, status, score). The widgets ask for your public list by user name. | While you use the app; a background check about once an hour |
| AniList sign-in | Opens AniList's login page in your browser | When you sign in |
| GitHub | Asks for the newest release; downloads the update. Installs it only if the checksum matches. | When the app starts |
| api.ani.zip | The AniList ID of an anime, for episode details | When you open an anime page |
| api.aniskip.com | The anime's MyAnimeList ID and the episode number, to skip opening and ending | When an episode plays |
| Extension servers | Whatever the installed extension asks for: search words, titles, episodes, chapters | When you stream, read or search |
| Marketplace | Loads the list of extensions: the official Seanime marketplace on GitHub, or the one you entered. Installed extensions are checked for updates at their own address. | When you open the marketplace or check for updates |
| Image servers | Cover art and pages, from AniList and from your sources | When they are shown |
| Debrid services | Real-Debrid, AllDebrid, TorBox or Premiumize: your key and the links | Only if you add a key |
| Torrent network | Peers and trackers see your IP address. While a torrent runs, the app also uploads parts of it to others, as BitTorrent does. | When a torrent runs; on mobile data the app asks first |
| Your TV (DLNA) | Looks for TVs in your Wi-Fi; the TV then fetches the episode from the app | When you cast |
| Google Cast | Uses Google Play services; what they send to Google is Google's matter | When you cast with Google Cast |
| Nakama | Your own Seanime on a PC, with the password you set | Only if you set it up |
Trailers, AniList and MyAnimeList pages open in your browser, not in the app. Plain HTTP is allowed, because your TV, Nakama on your PC and some sources don't speak HTTPS.
Extensions and sources
The app delivers no content. Extensions come from marketplaces run by other people, and they decide which sites the app contacts. Each extension runs in its own sandbox with limits on memory and time, and reaches the network only through the app. It still sees what you search for and what you open with it. Sources may contain material for adults only. Install only extensions you trust.
Permissions
| Permission | What for |
|---|---|
| Internet, network state | Everything online. The network state tells the app when you are on mobile data (for the Wi-Fi-only switch and the torrent question). |
| Install unknown apps | Installing its own updates from GitHub. Android asks you once. |
| All files access | Scanning a folder of your own anime files for the local library. Only needed for that. |
| Storage (older Android) | Reading and saving files on older Android versions |
| Notifications | New episodes and chapters, download progress |
| Foreground service, wake lock | Downloads, torrents and playback keep running when the screen is off |
| Run after restart | Planned notifications come back after the phone restarts |
| Wi-Fi multicast | Finding TVs for DLNA |
| Audio settings | The player's sound |
The app doesn't ask for the camera, the microphone, your location, contacts, phone or calendar. Some libraries bring permissions along that the app doesn't need; the app removes those (microphone, drawing over other apps, system settings, activity recognition).
Part 3 · Your rights
Law and rights
Swiss data protection law (the revised FADP, in German revDSG) applies. If you are in the EU or the EEA, the GDPR gives you similar rights: to learn what is stored about you, to have it corrected or deleted, to restrict or object to its use, and to get it in a portable form.
The processing by GitHub and Cloudflare described above is needed to show the website and its release data. Under the GDPR it rests on the legitimate interest in running a working website (Art. 6(1)(f)). Data goes to the United States and other countries where these companies run servers.
In practice I hold no personal data about you: no database, no accounts, no logs of mine. Mail is the exception. To use your rights, write to info@seanimemobile.com.
Complaints
In Switzerland the supervisory authority is the Federal Data Protection and Information Commissioner, FDPIC (EDÖB). In the EU it is the data protection authority of your country; the European Data Protection Board lists them.
Changes
When the website or the app changes in a way that matters here, this page changes with it and the date at the top is updated.