Lockstone 1.1.1 · version code 11
Check it yourself
Lockstone does not ask Android for permission to use the internet. You don't have to take our word for it. Here is the full permission list, how to check it on your own phone, and what it does and doesn't prove.
Every permission Lockstone 1.1.1 asks for
This list was read from the actual release build (Lockstone 1.1.1, version code 11), not from our source code or a store form.
| Permission | Why |
|---|---|
android.permission.CAMERA | The in-app camera and scanner, and break-in photos if you turn them on. Android asks you before the camera is used; you can say no. |
android.permission.USE_BIOMETRIC | Optional fingerprint or face unlock. Lockstone never sees your fingerprint; Android only tells it "yes" or "no". |
android.permission.USE_FINGERPRINT | The older name for the same thing, added by Android's own biometric library for older phones. |
com.android.vending.BILLING | Lets Lockstone ask the Google Play Store app on your phone to handle a Pro purchase. |
com.raglandcontracting.lockstone.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION | A private permission Android's build tools add automatically. It only lets Lockstone talk to itself, so other apps can't send it internal messages. |
Not on the list: INTERNET, ACCESS_NETWORK_STATE, AD_ID. Also no storage, location, contacts, microphone or phone permissions.
The raw output from the build (for the technical crowd)
$ aapt2 dump badging base.apk
package: name='com.raglandcontracting.lockstone' versionCode='11' versionName='1.1.1'
targetSdkVersion:'36'
$ aapt2 dump permissions base.apk
package: com.raglandcontracting.lockstone
uses-permission: name='android.permission.CAMERA'
uses-permission: name='android.permission.USE_BIOMETRIC'
uses-permission: name='android.permission.USE_FINGERPRINT'
uses-permission: name='com.android.vending.BILLING'
permission: com.raglandcontracting.lockstone.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION
uses-permission: name='com.raglandcontracting.lockstone.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION'
$ # search the merged manifest for network permissions
none of INTERNET / ACCESS_NETWORK_STATE / AD_ID
Some of the libraries we use (Google's video player and Play Billing) normally add INTERNET and ACCESS_NETWORK_STATE on their own. We strip both out of the final build on purpose, and our automated tests check that they stay out.
How to check on your own phone
1. In Google Play, before you install
Open the Lockstone listing, tap About this app, and scroll to App permissions (tap See more). An app with internet access shows "full network access" there. Lockstone won't.
2. In your phone's Settings, after you install
Go to Settings > Apps > Lockstone > Permissions. You'll see Camera, and that's it. On many phones the ⋮ menu on that screen has All permissions, which also lists the "other app capabilities" like network access. Menu names vary a little by phone maker.
Why the extra step: Android treats internet access as an install-time permission, so it never pops up a question and doesn't show on the main Permissions screen for any app. That's why the Play listing or the "All permissions" view is the place to look.
3. With a computer: the exact proof
This reads the permissions straight out of the Lockstone files installed on your phone. You need a computer with Android's platform tools (adb) and build tools (aapt2), and USB debugging turned on in Developer options.
- Find the installed APKs. Google Play installs an app as a base APK and sometimes extra "split" APKs:
Each line of output is one file, for exampleadb shell pm path com.raglandcontracting.lockstonepackage:/data/app/…/base.apk. - Pull every APK it lists to your computer (use the exact paths printed, without
package:):adb pull /data/app/…/base.apk adb pull /data/app/…/split_config.arm64_v8a.apk - Dump the permissions of each file:
aapt2 dump permissions base.apk aapt2 dump permissions split_config.arm64_v8a.apk - Look for
android.permission.INTERNET. In Lockstone it isn't in any of them. You should see only the permissions in the table above.
Shortcut: adb shell dumpsys package com.raglandcontracting.lockstone | grep permission lists what Android actually granted the installed app.
What this proves: the copy of Lockstone on your phone, the one Google Play delivered, can't open a network connection, because Android only lets an app use the network if it declared INTERNET. No library inside it can reach a server either. What it doesn't prove: that the encryption is correct, that the Play Store app (which handles purchases with its own internet access) or Google Play services (used by optional automatic recovery) are offline, or that files you export, share or back up to a cloud folder stay on your phone. It also only covers the version you checked; run it again after updates. The details are below.
What "no internet permission" proves
- Lockstone's own code can't open a network connection. Android blocks it at the system level, no matter what the app tries.
- There are no ads, analytics or tracking libraries talking to a server from inside Lockstone, because they would need that permission too.
- We have no Lockstone server and no Lockstone account. There is nowhere for the app to send your files, and nothing on our side to hack.
What it doesn't prove
- Google Play still handles purchases. When you buy Pro, the Play Store app does the work, under Google's own policies and with its own internet access. Lockstone only asks it "is this person Pro?"
- Your backups go where you send them. If you pick a Google Drive folder, the Drive app uploads the file. The file is encrypted inside Lockstone before it's saved, but it does leave your phone through Drive.
- Optional automatic recovery uses Google. If you leave it on, your vault's recovery key is saved in your Google backup through Google Play services, end-to-end encrypted with your phone's screen lock. You can turn it off.
- Sharing and exporting are your call. If you share or export a file out of the vault, it becomes a normal file and the app you send it to decides what happens next.
- It doesn't make the encryption perfect. No network access is one layer. Lockstone also encrypts files on your phone (AES-256-GCM, with keys protected by the Android Keystore). We publish exactly how it works on the security page.
- It can't protect a phone that's already compromised. If someone has full control of your phone or knows your pattern, no app can stop them.
- It applies to this version. This page describes Lockstone 1.1.1. Every future version can be checked the same way, and we'll update this page when the list changes.
Found something that doesn't match this page? Email lockstone.support@proton.me. We'll answer, and credit you publicly if you'd like.
