The awkward question
If a warning appears when you install Pinehold, that is expected, and pretending otherwise would be the actual red flag. This section explains what triggers it and how to check the claim rather than take my word for it.
Android is not accusing Pinehold of anything. It is flagging a combination of capabilities. Device Owner, accessibility, drawing over other apps and reading usage stats are exactly the four things spyware needs — and exactly the four things any blocker strong enough to survive a determined 11pm needs too. Android cannot read intent from a sideloaded file, so it warns about every app holding that set. The warning is about what the app could do, not what it does.
No account for Free or Pro, no backend for blocking, no analytics SDK, no ad SDK, no automatic crash reporting. Not "we don’t collect much" — the app sends nothing by itself. A problem report goes out only when you send it, through an app you pick, and the update check runs only when you ask. The Keeper sends only what you ask it to check, to the AI you chose.
The INTERNET permission exists so the built-in browser and text search can load pages you open. Those requests go from your phone to that site. None come here.
The SHA-256 of both builds is published below. Hash what you downloaded and compare — that proves the file is the one described here and was not altered on the way.
The honest limit of all this: everything above is a claim I am making, and a determined liar would make the same claims. What is checkable is checkable — the permission list below matches the manifest, the checksums match the files, and Play Protect will scan it and tell you itself. What isn’t, isn’t. That is the real state of trusting any sideloaded app, including this one.
Privacy
An app that asks for device owner rights should be able to account for itself line by line. This is the full list from the manifest, not a summary.
| Permission | What it lets Pinehold do | What it can never do | Status |
|---|---|---|---|
DEVICE_ADMIN / Device Owner | The enforcement itself: hiding apps, suspending them, lock task mode, disabling Safe Boot and uninstall. | Read your messages, files or accounts. Device policy controls apps and settings, not content. | Core |
PACKAGE_USAGE_STATS | Knowing which app is in the foreground, and computing your daily limits and local analytics. | See inside an app. It reports which app is in front and for how long, never what you did there. | Core |
QUERY_ALL_PACKAGES | Listing the apps you own so you can pick which ones to block. Never leaves the phone. | Send the list anywhere. There is no network call that carries it. | Core |
FOREGROUND_SERVICE | Keeping the watcher alive so an 8pm schedule fires without the app being open. | Run invisibly. Android requires the permanent notification you can see. | Core |
RECEIVE_BOOT_COMPLETED | Re-applying your policy after a restart, so rebooting isn’t a bypass. | Do anything at boot except re-apply the rules you already set. | Core |
INTERNET | Loading pages in the built-in browser and text search. No telemetry, no accounts. The one request of its own is the update check, and only when you ask for it. | Contact a Pinehold server, because there is not one. It loads the pages you open and nothing else. | Core |
SYSTEM_ALERT_WINDOW | Drawing the block screen over a blocked app fast enough that you don’t see the feed first. | Capture what is underneath. It draws over the screen; it cannot read it. | Core |
| Accessibility service | The keyword guard reading on-screen text to catch a phrase inside another app. | Log or transmit what it reads. Text is matched against your phrases in memory and dropped. | Optional |
| Notification access | Dismissing notifications from blocked apps so they don’t pile up. | Read notifications from apps you have not blocked, or send their contents anywhere. | Optional |
ACCESS_COARSE_LOCATION | Place rules. Read as a last-known fix when a rule is evaluated, never as a continuous stream. | Track you. It asks for a rough last-known fix only while evaluating a place rule, and stores no history. | Optional |
| Camera (via the system camera app) | Photo proof for Earn Mode. Pinehold has no camera permission of its own; it hands one file to your camera app and takes it straight back. | Open the camera by itself. Pinehold holds no camera permission; the photo is deleted after checking. | Optional |
READ_MEDIA_VIDEO | Playing videos you saved to the delayed library. Only files you pick. | Touch media you did not pick, or upload any of it. | Optional |
Swipe for more
There is nothing to sign up for and nowhere for your data to go. Rules, tasks and history sit in local storage on the phone.
Export the whole setup as one document you keep. That’s the backup, and it’s also the proof that nothing is hidden from you.
No analytics, no ads, nothing phoning home. Crash reports stay on the phone until you choose to send one. The dependency list is media playback and the Android support libraries.
Every claim above is about the shipped releases. These are the SHA-256 checksums for v2.3 (Android) and the Windows PC installer, so you can confirm nothing was swapped or altered in transit. On macOS or Linux run shasum -a 256 <file>; on Windows, certutil -hashfile <file> SHA256.
| File | SHA-256 |
|---|---|
Pinehold-v2.3.apk |
4e163527195d4372505d547bccf04487f7c677c2ff9276c11f40fcf560503d4a |
Pinehold-Setup.exe |
155ff564987ff5f5f1ad987134b0664e8c83c6db403b6259bf22159cf11510bb |
Swipe for more
Both are signed with the same key, so your phone will refuse an update that did not come from me.