Is Talpatra Scan really offline? Here's how to check for yourself

Every document scanner app claims to respect your privacy. Almost none of them let you check. Talpatra Scan makes one specific, technical, falsifiable claim — it never requests Android’s INTERNET permission — and this post walks through what that claim actually means and exactly how to verify it against the APK, not against a paragraph of marketing copy.

Short answer: Talpatra Scan’s APK does not declare android.permission.INTERNET, so the operating system will not let it open a network socket under any circumstance, and that fact is checkable in minutes with free tools — you don’t have to trust us.

What does “no internet permission” actually mean on Android?

Every Android app ships a manifest that declares, ahead of time, every permission it might ever use. This isn’t optional or lazy — it’s how the platform works. An app can’t request network access on the fly the way a desktop program might; if INTERNET isn’t in the manifest at build time, the OS enforces that the app has no path to open a socket, full stop, regardless of what the code tries to do at runtime.

INTERNET is also worth knowing about because of how Android classifies it. Permissions like camera, location, and contacts are “dangerous” — they trigger a runtime prompt you have to tap through, and Settings keeps a visible toggle for each. INTERNET is classified as “normal,” granted silently at install time with no prompt, because Google’s threat model treats network access as low risk compared to reading your contacts. That’s exactly why it’s worth checking independently rather than assuming: a normal permission is easy for a developer to add without anyone noticing, and easy for a user to never see mentioned anywhere in the UI.

How do I check this myself?

Here’s the part most privacy pages skip, so it’s worth being precise: opening Settings > Apps > Talpatra Scan > Permissions on a stock Android phone will not reliably show you whether the app holds INTERNET. That screen is built to surface the dangerous, runtime-prompted permissions you granted interactively — camera, storage, and so on. Normal, install-time permissions like INTERNET don’t consistently show up there across devices and Android versions. Some Android 13+ phones expose an advanced “See all permissions” view that does list it, but that view isn’t standardized across manufacturers, so treat it as a bonus check, not the method you rely on.

The two methods that actually work inspect the APK’s manifest directly:

Method 1 — Android’s own tooling. Download the signed APK from the GitHub Releases page, then run:

aapt dump permissions app-release.apk

(apkanalyzer works the same way if you have the Android SDK command-line tools installed instead.) The output lists every permission the app declares, by name. Look for android.permission.INTERNET. It won’t be there.

Method 2 — an independent auditor. If you’d rather not install SDK tooling, upload the same APK to Exodus Privacy, a nonprofit that scans Android apps for embedded trackers and lists every declared permission. It isn’t run by us and has no reason to take our side. Run Talpatra Scan’s APK through it and you’ll see zero trackers and a permission list with no INTERNET entry.

Both methods read the manifest — or a third party’s scan of the manifest — directly. Neither one asks you to trust a sentence on this website.

What stops this from silently changing in a future update?

A no-internet claim is only worth something if it can’t quietly regress the next time the app is updated. Talpatra Scan’s build process is set up so the app simply cannot compile with the INTERNET permission present. If that permission ever ends up in the final package — through a mistake, or pulled in transitively by some third-party library — the build fails outright and nothing gets released. It isn’t a manual checklist item a developer might forget to tick; it’s a hard stop built into how every release is produced.

That distinction matters. A “we checked once and it was fine” promise is a snapshot. A build that refuses to compile with the permission present is a guarantee that holds for every version, by construction, every time — including versions that haven’t shipped yet.

How is this different from apps that say “offline” in their marketing?

“Offline scanning” is a common line in scanner-app marketing, and it doesn’t always mean what it sounds like. A 2026-09 comparative review of Adobe Scan, Kaagaz Scanner, and Doc Scanner (Lufick) found real gaps between the claim and the app:

Adobe Scan is the clearest case of a mismatch — it auto-uploads scans to Adobe Document Cloud with no documented off switch, and its OCR runs server-side, not on-device. It has never claimed to be offline, but it’s worth naming because “AI scanning” marketing can read as private when the processing is actually happening on a server.

Kaagaz’s privacy policy states scanning works completely offline and documents stay on-device unless you opt into cloud sync. That may well be true for the scanning step specifically. But the app itself ships ads plus Branch, Firebase, and Google Analytics SDKs, and its “Kaagaz AI” feature routes through OpenAI’s API. Its Play Store data-safety disclosure lists location and other personal-info categories shared with third parties. So even where the core scan-to-PDF flow stays local, the app around it is still a networked app, holding the INTERNET permission and phoning home for ads and analytics.

Doc Scanner (Lufick) makes a similar vendor claim — “no internet required for the app to function” — while holding the INTERNET permission and bundling AdMob, Firebase Analytics, Crashlytics, and Facebook Ads. Its privacy policy still references a deprecated SDK (Fabric), a small sign the document hasn’t been kept current with what’s actually in the build.

The pattern across all three: a policy document says documents stay local, but nothing about the app itself prevents it from holding network access or shipping trackers alongside that local-storage behavior. There’s no public teardown confirming any of their runtime network behavior — the offline claims rest on vendor statements, not on an inspectable build artifact. That’s the gap Talpatra Scan is built to close: instead of a policy promising your documents won’t be uploaded, the app is not capable of making a network request in the first place, and that’s something you can go verify on the actual APK right now.