Datapavan
See what the apps on your Android phone can reach and how much they send, and change it in Android's own settings. Everything runs on the phone. No internet access, no account, no root.
Status: pre-alpha. Nothing has been released yet.
What it checks
- Every installed app: where it came from, its sensitive permissions, and the special access that lets an app read the screen or act for you.
- Trackers and SDKs inside each app's code, matched on the phone.
- VPN, proxy and circumvention apps, against their developers' official signing keys, so that a modified copy shows.
- The phone itself: debugging, certificate authorities you installed, the security patch and the boot state.
- How much data each app sent and received, and which apps you have not opened for months but still hold access.
It looks for known names in an app's code, so a renamed or hidden SDK is missed: finding nothing is not proof that nothing is there.
What it helps you do
A short plan, the changes that remove the most risk first. Each one opens the right Android screen, where you decide. A journal on the phone keeps what you changed, so that you can undo it. It leaves out the apps it recognises as essential.
What it never does
No analytics, no crash reports, no accounts, and the app contacts no server. Datapavan itself sends nothing anywhere. Genuine Datapavan has no internet access and never asks for it. A copy that asks for it is not genuine.
Get it
There is nothing to download yet. With the first release:
- GitHub Releases: the signed APK, its SHA-256 and the signed release notes.
- F-Droid and IzzyOnDroid.
- Obtainium: add
https://github.com/visadahyu/datapavan.
Check your copy
Every genuine copy is signed with one key. Its certificate's SHA-256 fingerprint is:
FA:6A:24:04:2A:BC:AC:8B:
D0:09:01:10:F7:04:FF:EF:
E7:DA:D3:AD:F5:DB:38:FB:
07:38:90:AB:4C:B1:FA:84
Compare it with a tool other than Datapavan itself, since a modified copy can show any text: for
example AppVerifier on the phone, or apksigner verify --print-certs on a computer. The
same fingerprint is in the README and in every release's signed notes.
Security and privacy
Report a vulnerability privately through GitHub's private vulnerability reporting. See the security policy and the privacy notes. This page sets no cookies and loads nothing from other servers.