Privacy Policy — Kryptic
- Effective date: 13 August 2026
- Application: Kryptic (Android)
- Publisher: Asadullahil Galib
- Contact: agalib216@gmail.com
1. Overview
Kryptic encrypts and decrypts files entirely on your device. We do not collect, store, transmit, process, or share any personal data, usage analytics, telemetry, or file contents. There is no server, no account, and no network component.
This is not a promise about what the app chooses to do. Kryptic does not request Android's internet permission, so the operating system will not permit the app to open a network connection at all. See §3.
2. Information collection and use
- Personal information — Kryptic does not collect any personally identifiable information: no name, email address, IP address, device identifier, or location.
- File contents — files you encrypt or decrypt remain in your device's local storage or the app's temporary cache. They are never uploaded anywhere.
- Passphrases — your passphrase is never stored, logged, or transmitted. It is held in memory only for the duration of an operation and used to derive an encryption key via PBKDF2-HMAC-SHA256. Because the app has no network access and no persistent storage for secrets, a passphrase cannot leave your device.
- Biometric data — app-lock authentication is handled entirely by the operating system's
BiometricPromptAPI. Kryptic receives only a success or failure result. It never accesses, receives, or stores biometric data of any kind. - Advertising — Kryptic contains no advertising and does not access the Android advertising ID.
3. Network access
Kryptic requests no network permissions. android.permission.INTERNET is not declared in the app manifest and is not contributed by any library the app depends on, so the application is technically incapable of making network requests. It operates fully offline.
This is verified against the merged manifest — the one Android actually enforces, after every dependency has had the chance to add permissions to it — rather than against the manifest as written in the source tree.
4. Device storage and permissions
Kryptic uses the Android Storage Access Framework (SAF), so you explicitly choose each input file and each output location. The app requests no storage permissions and can only access the files you select.
Temporary copies may be written to the app's private cache directory while an operation completes or when sharing a file with another app. These are removed when the operation is dismissed, and — if the Auto-Purge Temporary Cache setting is enabled — automatically after five minutes.
The complete list of permissions Kryptic requests:
| Permission | Why |
|---|---|
android.permission.USE_BIOMETRIC | The optional App Lock, which asks the operating system to verify your device screen lock |
android.permission.USE_FINGERPRINT | Added automatically by the AndroidX biometric library for compatibility with Android 9 and earlier; it is the deprecated predecessor of the permission above and serves the same App Lock |
5. Data deletion
Kryptic stores no data on any server, so there is nothing for us to delete and no deletion request to make. Removing the app from your device removes its cache and any app-private data. Files you saved to your own chosen locations remain under your control.
6. Children
Kryptic is not directed at children and collects no data from anyone, including children.
7. Changes to this policy
Material changes will be reflected here with an updated effective date, and in the app's release notes. The current version of this policy is published at the URL given on the app's Google Play listing.
8. Contact
Questions about this policy, or about the app: agalib216@gmail.com.