Security
Found a security problem in the app or on this website? Tell me privately first, so it can be fixed before anyone else can use it.
Last updated: 17 November 2026
How to report it
Use one of these two private channels:
- Report a vulnerability on GitHub (private security advisory, needs a GitHub account)
- Email: info@seanimemobile.com
Please don't open a public issue for a security problem. Write in English or German.
What helps
- What the problem is and what an attacker could do with it.
- Where it is: the page address, or the app version and the screen.
- Steps to reproduce it, and screenshots or a short recording if you have them.
What happens next
Seanime Mobile is a private project run by one person in his free time. I read every report and answer as soon as I can, usually within a week. Once the problem is confirmed, I fix it, release a new version and, if you like, name you in the release notes. There is no paid bug bounty.
Please give me time to ship the fix before you talk about the problem in public.
In scope
- The Seanime Mobile app, latest release from GitHub Releases.
- This website, seanimemobile.com.
- The release files published on GitHub.
Not in scope
- Third-party extensions, marketplaces and the sites they load. Report those to their authors.
- Seanime by 5rahim itself: report to the Seanime project.
- AniList, GitHub, Cloudflare and other services the app or site talks to.
- Attacks on other people's devices or accounts, denial of service, spam and social engineering. Please only test with your own device and your own data.
How this website protects you
- It is a static site: no login, no forms, no database, no cookies, no tracking.
- It only runs its own scripts. A strict Content-Security-Policy blocks code from anywhere else, and the site can't be embedded in other pages.
- It is only served over HTTPS.
- The only outside request is to the GitHub API, for the release data. The download button only ever points to the official GitHub releases of this project.
To make sure your download wasn't changed on the way, compare its SHA-256 checksum with the one GitHub publishes: how to check the checksum.
For machines
The same contact details in the standard format (RFC 9116): security.txt.