Warden uses root permission to enable/disable components & de-bloat. Use at your own risk!
- Detects Trackers & Loggers across whole device
- Allows to disable all trackers/loggers
- Advance profile based app de-bloater
How does it work?
Warden has a static curated list of known trackers (Exodus Privacy) , each app's dex file is read to retrieve the class names, these class names are then matched with the signatures of known trackers & loggers to find them.
A list of currently known trackers & loggers can be found here & here
Loggers in the context of Warden means all utilities which are used to log user activity on an app or logcat in general. Not all loggers are evil.
But few logging tools like ACRA, xLog are very powerful tools that can send user data to devs without user's consent.
De-Bloater (Requires Root)
Warden provides a profile based de-bloater where a profile is created in a format specified as in this sample scripts
You need to place this profile/your custom profile at `ExternalStorage/Warden/Profiles` to make them appear in app.
De-Bloater is an experimental feature, will improve it over time.
Default action for debloating is 'disable' you can configure it to 'uninstall' or 'hide' from settings.
Nuke it! (Requires Root)
Nuke it! is another experimental feature that scans all apps on the device and disables all know tracker components automatically.
It also gives an option to export components names per-app basis.
Components here means: Activities, Services, Providers & Receivers
Warden uses `su pm` to manage the components.
Warden, App for all devices (see above for details)
Source Code: https://gitlab.com/AuroraOSS/AppWarden
Current Stable Version: 1.0.1
Stable Release Date: 2020-06-24
Last Updated 2020-06-23