ANONYM is an offline-first Android privacy scheduler. Your phone leaves an unbroken record of where it has been, because its radios never stop announcing it. ANONYM cuts that record into pieces: on intervals you define, it switches Wi-Fi, mobile data, airplane mode, Bluetooth and location off and back on, so the continuous trail becomes a series of gaps you control. It also reboots the device on a timer, shows you what is actually being transmitted, and — under duress — locks the phone behind a password nobody can force out of you. Everything runs on the device: ANONYM has no internet permission at all.
Open source. Licensed under the GNU General Public License v3.0 — free to use, study, modify and redistribute under the same terms. See LICENSE.
💸 You spent this whole page worrying about who is tracking you, and the one party you have successfully given nothing to is the person who built the countermeasure. Ko-fi: ko-fi.com/eversorhn PayPal: paypal.me/FAMarco Bitcoin:
bc1qv92c3eyeqvhgfnez7spfd7v2aytkhpshsl65yv
Author / copyright: © 2026 eVersor-HN. This is the official distribution repository — get ANONYM only from here: https://github.com/eVersor-HN/ANONYM
ANONYM has no account, no telemetry, no analytics and no cloud component. It cannot phone home, because it never requests network access. The only privileged actions it takes are the documented system commands it runs on your behalf.
Be clear-eyed about the boundaries, because they matter more than the marketing:
- Mobile data off is not modem off. The modem stays registered with your carrier, so the network still knows your approximate location and can page the device. Only airplane mode — or removing the SIM — powers it down. Use airplane mode as the main switch when you want the device dark, and the individual toggles to cut traffic and save battery.
- Airplane mode can be bypassed. Android lets Wi-Fi, and on some systems mobile data, run on top of airplane mode. ANONYM warns you when that is happening.
- Gaps, not silence. When a window reopens, queued traffic flushes at once. The goal is to break the continuous trail, not to reach zero emissions.
- Software, not a hardware kill switch. No app can guarantee nothing is transmitted. For high-risk situations, use a Faraday bag or remove the SIM.
- ANONYM controls radios, not individual apps. Pair it with a firewall if you want per-app control while staying online.
- Open the Releases page and download the latest APK asset.
- Verify it is the genuine original (see below) before installing it.
- On your phone, open the APK and allow installing from this source if prompted ("Install unknown apps"). ANONYM is sideloaded — it is not on the Play Store.
- Open Setup and grant root or Shizuku access.
ANONYM has no auto-update, by design — it has no network access. Download the newest signed APK and install it over the old one; the signing key is unchanged, so it updates in place and keeps your rules. Settings → Updates opens the releases page for you.
Coming from FA (v0.3.5 or older)? The app was renamed to ANONYM and its application id changed, so Android treats the new build as a separate app: it installs alongside FA instead of updating it, and your rules do not carry over. Set your rules up again in ANONYM, then uninstall FA — and disarm the panic-lock in FA first, since uninstalling it while armed leaves the rotated password in place with nothing left to restore it.
Every official release publishes the SHA-256 checksum of the APK. Comparing the checksum of your download against the published value proves the file is the unmodified original and was not tampered with.
v0.3.5 — FindAnonymity-0.3.5.apk:
d51617f1f5a0203d46c744a220710b7c1c6eb13891fbf297f8175a3a68a17416
The authoritative value for each release is published in that release's notes.
Check it:
# Windows (PowerShell)
Get-FileHash .\FindAnonymity-0.3.5.apk -Algorithm SHA256# macOS # Linux
shasum -a 256 FindAnonymity-0.3.5.apk sha256sum FindAnonymity-0.3.5.apkThe printed hash must match the value above (case-insensitive). If it does not match, do not
install the file — it is not the genuine ANONYM build. The APK is signed with the release key
d35bd3c4f93c781853bfe7ae1d55dc64b477dbf6929dba908d19589730dc442a; Android will refuse any later
update that is not signed with the same key.
Control Wi-Fi, mobile data, airplane mode, Bluetooth and location independently, or set all of them at once. Each radio runs a repeating cycle (on 1 minute every 3 minutes, or any span from seconds to years) or a clock schedule — on and off times on the weekdays you pick, including windows that cross midnight such as 22:00 → 06:00. Always on, always off and unmanaged are there too, so ANONYM only touches what you tell it to.
Rules are enforced against wall-clock time from a fixed anchor, so a delayed wake-up never compounds: the next switch happens when it was due, not when the last one finished.
Reboot on an interval to clear volatile state and return the device to its Before-First-Unlock posture, where the encryption keys are not in memory and the data is far harder to extract. Useful on its own, and the reason a stolen-but-unlocked phone can lock itself again without you touching it.
Forced reboot is a per-rule option: normally the reboot is driven by ANONYM's foreground service, so stopping ANONYM from the notification cancels it — convenient for you, but a thief could do the same. With Force reboot on, it runs from a detached privileged daemon that survives ANONYM being stopped or killed. Root re-arms it on every boot; under Shizuku it fires once, since Shizuku is not running that early.
An optional watcher notices rapid power-button presses — say five within three seconds — and instantly replaces your lock-screen password with a long random string you have backed up externally, then locks the device. Under coercion you press a button and lock yourself out; the phone can no longer be unlocked on demand. It keeps working even if ANONYM's own process is killed, and is restored after a reboot.
Arming is deliberately hard to do by accident: two typed confirmations, and ANONYM verifies your current lock-screen credential first, so it refuses to arm into a state where the rotation would silently fail.
A live view of what the device is actually sending: byte rates with a 60-second history, the real state of every radio, and the established outbound connections. It flags the two things people usually miss — traffic leaving while Wi-Fi and mobile data are both off, and airplane mode being bypassed because Wi-Fi or data were switched back on top of it.
Live countdown to the next change in the app and in the notification, stop automation straight from the notification, 15 languages with full right-to-left support, and a cold cyberpunk-corpo terminal interface.
- Android 12 (API 31) or newer.
- A privileged backend: root (Magisk, KernelSU) or Shizuku.
| Capability | Root | Shizuku |
|---|---|---|
| Wi-Fi, data, airplane mode, Bluetooth, location | ✅ | ✅ |
| Timed reboots | ✅ | ✅ |
| Panic-lock | ✅ |
Root enables everything and is the recommended backend for the panic-lock: the watcher runs as a detached root daemon and ANONYM re-arms it after a reboot. Under Shizuku (paired via Wireless Debugging, or root-mode Sui) the connectivity and reboot automation work fully, but the panic-lock is experimental — changing the lock-screen password from a shell-uid process is not dependable on every device, and protection ends at reboot with no auto re-arm. Test on a spare device first.
- No plaintext credentials at rest. While the panic-lock is armed, the watcher holds its two secrets in memory only; the on-disk copies are shredded and unlinked the moment it starts.
- Restoring protection after a reboot. A reboot — including ANONYM's own scheduled one — ends the watcher, so ANONYM restores it at boot from Keystore-encrypted, device-bound, app-private copies of the credentials, which are cleared on disarm. If they are missing or privileged access is unavailable, ANONYM does not touch your password: it disarms and tells you, rather than leaving you believing you are still protected.
- A stale credential cannot lock you out. If a panic had already rotated your password, the stored credential no longer matches, so a later trigger simply does nothing until you reconfigure.
- Real lockout risk remains. The panic-lock sets a genuinely random password. If you lose your external backup of it, you can be permanently locked out of your device, including possible data loss. Test on a spare device before arming it on your daily phone.
- The next password is generated with
SecureRandom. - Backup and device-transfer extraction are disabled, so the stored credentials never leave the device through a system backup.
- Some manufacturers restrict background apps beyond Android's own limits. If automation stops unexpectedly, allow ANONYM to autostart in your system settings.
Requires a JDK 17+ toolchain and the Android SDK (API 36).
git clone https://github.com/eVersor-HN/ANONYM.git
cd ANONYM
./gradlew assembleDebugThe installable debug APK lands in app/build/outputs/apk/debug/.
For a signed release build, create a gitignored keystore.properties in the project root pointing at
your own keystore, then run ./gradlew assembleRelease:
storeFile=keystore/your-release.jks
storePassword=…
keyAlias=…
keyPassword=…Without keystore.properties the release build stays unsigned.
GNU General Public License v3.0 © 2026 eVersor-HN. Full user-visible history is in CHANGELOG.md.