Privacy Policy

Last Updated: October 2026 • Package: com.encrypz.vault

1. Zero-Knowledge Architecture & Native Device Encryption

Encrypz is engineered on a zero-knowledge architecture. All cryptographic encryption and decryption operations occur locally on your Android device using native cryptographic APIs (Java/Android native crypto). Files are encrypted locally using AES-256-GCM, and cryptographic keys are derived using PBKDF2-HMAC-SHA256 (600,000 iterations for new accounts). Encryption does not run in a browser; it runs entirely within the native mobile sandbox before data ever leaves your hardware.

2. Backend Services & Data Stored in MongoDB

While encrypted file storage is handled directly by your personal cloud provider (Google Drive), account registration, session authentication, and encrypted vault state synchronization require our dedicated .NET backend service and MongoDB database.

We believe in absolute transparency regarding what information is stored on our servers versus what never leaves your device:

Stored in MongoDB

Backend Storage
  • Google Identity: OAuth identifier and basic profile details used solely for federated authentication and account sign-in.
  • Email Address: Account identifier used for login verification and essential security notifications.
  • Password-Proof Hashes: Client-derived verifier hashes used to prove password ownership upon login without transmitting or exposing your actual password.
  • Cryptographic Salts: High-entropy randomized salts generated for your account and utilized in PBKDF2 key derivation.
  • Encrypted Vault Key: Your master vault key, encrypted locally on your Android device before upload. It is stored as ciphertext; our servers cannot decrypt or read it.

NEVER Stored in MongoDB

Zero Access
  • Plaintext Passwords / PINs: Your master password and six-digit PIN never touch our network in unhashed/plaintext form.
  • File Contents: Unencrypted files, photos, videos, and documents are never sent to, proxied by, or stored in our MongoDB backend.
  • Plaintext Filenames: File and directory names are encrypted locally on your device prior to cloud transfer.
  • Decryption Keys: The keys needed to decrypt your vault key or your files exist solely in device memory during an active, unlocked vault session.

3. Cloud Providers & Direct File Transfers

Encrypz currently integrates with Google Drive via official Google OAuth 2.0 authorization. File uploads and downloads stream directly between your Android device and your personal Google Drive storage. Our backend servers do not relay, proxy, or inspect your file transfers. Your files are encrypted with AES-256-GCM and encrypted filenames before uploading.

4. In-Memory Processing & Memory Caps

The Android client currently reads files directly into memory for local cryptographic processing, operating with a 15 MiB file size cap. Files larger than this memory cap cannot currently be processed or may be truncated. Streaming chunked encryption for arbitrarily large files is planned for future updates.

5. Vault Security: PINs, Immediate Locking & Photo Sorting

Vault authentication is secured via a six-digit PIN or master password (biometric authentication is not currently implemented). For physical security and privacy, Encrypz implements immediate locking: whenever the app is minimized, closed, or switched away from the foreground, the vault locks instantly and memory keys are purged. In addition, the vault automatically parses media creation dates to sort encrypted photos chronologically without revealing metadata to cloud providers.

6. Vault Restoration & Zero-Knowledge Responsibilities

Because Encrypz enforces strict zero-knowledge principles, restoring your vault on a new or reset device requires two mandatory credentials: (1) your registered Google account / email, and (2) your master password or six-digit PIN. Your password-derived key is required to decrypt the vault key stored in MongoDB. If you lose your master password or PIN, Encrypz cannot recover your keys or decrypt your data.

7. Data Collection & Analytics

We do not track your IP address, use tracking cookies, or bundle third-party advertising or analytics SDKs that track your usage. We collect only the minimum data necessary to maintain your account authentication.

8. Open Source Transparency

Encrypz is open-source under package name com.encrypz.vault on GitHub. We welcome independent security researchers and users to audit our cryptographic implementation and verify all privacy claims.

Support Our Project

Encrypz is completely free and open-source. If you find it useful, consider supporting our development.