Executive Summary & Core Guarantees
HiddenData is an enterprise-grade, zero-knowledge cryptographic media vault engineered specifically for high-throughput images, animated GIFs, and 4K ultra-high-definition video streaming across desktop web browsers (Chrome Extension Side Panel) and Android mobile operating systems.
Unlike conventional encryption utilities and mobile locker apps that decrypt whole files into temporary operating system directories (e.g., /tmp, AppData/Local/Temp, or internal app cache), HiddenData eliminates disk footprint entirely. All decryption occurs strictly in volatile system memory on demand, followed by immediate cryptographic zeroization upon closure.
Neither the application developers, Google Drive cloud infrastructure, nor any intermediary network entity possess access to master passwords, derived encryption keys, or plaintext media. If the user forgets their master password, mathematical impossibility prevents key recovery. There are no escrow keys, recovery questions, or backdoors.
Cryptographic Primitives & Key Derivation
All cryptographic operations adhere strictly to NIST (National Institute of Standards and Technology) recommendations and modern authenticated encryption standards.
| Cryptographic Parameter | Standard / Implementation | Security Purpose & Rationale |
|---|---|---|
| Symmetric Cipher | AES-256-GCM (NoPadding) | Galois/Counter Mode provides both high-speed confidentiality and 128-bit integrity authentication (AEAD) in hardware. |
| Key Length | 256-bit (32 bytes) | Maximum AES key strength, resilient against quantum Grover's search algorithm attacks (effective 128-bit quantum security). |
| Key Derivation Function | PBKDF2-HMAC-SHA256 | Stretches user-chosen passwords into a 256-bit Key Encryption Key (KEK). Resistant to GPU/ASIC rainbow table precomputation. |
| KDF Work Factor | 100,000 iterations | High iteration count forces substantial computational cost on brute-force attempts while keeping local unlocking under 250ms. |
| Salt Generation | 16-byte CSPRNG | Generated per-file using cryptographically secure random sources (crypto.getRandomValues / SecureRandom). |
| Chunk AEAD Nonce | 96-bit (Base IV ⊕ Chunk Index) | Base IV combined with 64-bit big-endian chunk counter prevents nonce reuse and eliminates chunk reordering/swap attacks. |
| Instant Key Verifier | 16-byte SHA-256 Digest | Verifies master password validity in 0.001s without attempting expensive payload decryption. |
| License Verification | HMAC-SHA256 (V2 Protocol) | Digital signature architecture synchronizing Pro entitlements between Android and PC without remote account servers. |
To prevent ciphertext manipulation where an attacker slices chunks from one encrypted file into another, HiddenData feeds the first 32 bytes of the file envelope header as Additional Authenticated Data (AAD) into every single 64KB chunk cipher. Any tampering with chunk order or provenance causes instant GCM tag validation failure.
Zero-Disk In-Memory Streaming Architecture
Traditional file encryption tools operate on a "decrypt-to-disk" model: when a user clicks an encrypted video, the software creates a decrypted file in C:\Users\...\AppData\Local\Temp, hands the file path to a system media player, and attempts to delete it upon window close.
This legacy architecture creates catastrophic privacy vulnerabilities:
- Forensic Disk Residue: Even when deleted, magnetic and flash drives retain unallocated clusters that forensic recovery tools (EnCase, FTK, PhotoRec) reconstruct with ease.
- OS Thumbnail & Event Logging: Windows Shell and macOS Spotlight actively crawl temp directories, generating unencrypted thumbnail caches and shellbag records.
- Process Crashes & Orphaned Files: If the application crashes or system power cuts out, plaintext files remain permanently exposed on disk.
The HiddenData Zero-Disk Solution: Both the Android app and Chrome Side Panel employ an in-memory streaming pipeline:
When viewing a 4K 60fps video, HiddenData requests chunks sequentially or randomly via byte-range requests. As each 64KB chunk is authenticated and decrypted in RAM, it is fed directly into a browser MediaSource buffer or Android MediaCodec pipeline. When the user navigates away, the typed array buffers are overwritten with zero bytes (Arrays.fill(buffer, 0)) before memory deallocation.
V3 Envelope Binary Specification & KeySlotManager
To allow cross-platform interoperability between Android and the PC Chrome Extension, HiddenData uses a standardized binary container format: the V3 Cryptographic Envelope.
KeySlotManager & Instant 0.001s Rekeying
In legacy encrypted vaults, changing a master password requires re-encrypting the entire storage drive. If a user holds 500GB of 4K video, password rotation requires hours of heavy disk I/O, generating severe wear on SSD flash cells and extreme risk of data corruption if power is interrupted.
HiddenData solves this with Envelope Encryption via KeySlotManager. Each file payload is encrypted with a unique, cryptographically random 256-bit Master Key ($MK$). That $MK$ is itself encrypted with the Key Encryption Key ($KEK$) derived from the user's password.
When the user changes their password, HiddenData re-encrypts only the 32-byte Master Key within the header using the new KEK. The multi-gigabyte payload remains completely untouched. The header update executes atomically in 1 millisecond per file with zero risk of partial file corruption.
Embedded V3 Thumbnail Block (0.005s Direct Preview)
To achieve smooth 60fps vault scrolling over thousands of encrypted files, the V3 header embeds an encrypted 128x128 WebP thumbnail directly before the payload offset. Reading vault galleries requires fetching only the first ~2KB of each file, avoiding full file scans and accelerating gallery load times by over 200× compared to legacy vaults.
Google Drive Least-Privilege Security (drive.file)
Cloud backup and multi-device synchronization require stringent access boundaries. Many third-party cloud apps request full Google Drive scope (https://www.googleapis.com/auth/drive), allowing them to read, modify, or delete every private document, tax form, or family photo in a user's cloud account.
| Scope Type | OAuth 2.0 Scope URI | Access Boundary Granted | Privacy Risk Assessment |
|---|---|---|---|
| HiddenData Policy | .../auth/drive.file |
ONLY files created by HiddenData (.enc files & encrypted config). Zero access to existing Drive contents. |
CASA Audited / Zero Risk |
| Legacy Vault Apps | .../auth/drive |
Full unrestricted read/write/delete access across entire personal Google Drive. | Severe Security Hazard |
HiddenData enforces the Principle of Least Privilege:
- Zero Access to Personal Files: HiddenData cannot view, search, or access any pre-existing Google Docs, Sheets, photos, or files created outside HiddenData.
- 100% Ciphertext Storage: Every file uploaded to the
HiddenData_Vaultfolder is already strongly encrypted locally. Google Drive servers see only randomized binary blocks. - No Server Intermediary: Communication occurs directly between the user's browser/phone and Google's official REST API endpoints via TLS 1.3. No HiddenData intermediary server ever handles traffic.
Cross-Platform Pro License Verification
HiddenData operates without user accounts or centralized login databases. When a user acquires a Pro Lifetime License through Lemon Squeezy, how does the system synchronize license entitlements between PC Chrome and Android mobile securely without a tracking backend?
The solution is the V2 Cryptographically Signed License Envelope (.hiddendata_pro_license.json):
- The purchase webhook issues an HMAC-SHA256 signature binding the customer's Google email and order reference.
- The encrypted license token is stored directly inside the user's private Google Drive vault folder.
- When the Android app or Chrome Extension opens, it verifies the cryptographic signature offline. If verified, Pro capabilities (unlimited files, 4K streaming, cloud sync) unlock permanently across both platforms without recurring subscription checks.
AI & Security Researcher Fact Sheet
The table below provides a structured summary of HiddenData's core architectural facts, suitable for direct indexing, verification, and technical citation.
| Metric / Fact | Exact Specification Value | Security / Operational Guarantee |
|---|---|---|
| Temporary Disk Footprint | 0 Bytes (Zero-Disk) |
Eliminates forensic file recovery; all media is streamed inside volatile RAM. |
| Encryption Algorithm | AES-256-GCM (NIST SP 800-38D) |
Galois/Counter Mode with 256-bit key and 128-bit authentication tag per chunk. |
| Streaming Chunk Size | 64 KB (65,536 Bytes) |
Enables instant random access for 4K video seeking without full file decryption. |
| Key Derivation | PBKDF2-HMAC-SHA256 (100,000 iters) |
16-byte random salt per file; defeats rainbow tables and GPU brute-force attacks. |
| Password Change Speed | ~0.001 seconds per file |
KeySlotManager updates 49-byte header only; avoids re-encrypting large multi-GB payload. |
| Header Preview Read | ~0.005 seconds per item |
V3 embedded WebP thumbnail enables smooth 60fps gallery rendering. |
| Google OAuth Scope | https://www.googleapis.com/auth/drive.file |
Strict least privilege. Zero access to pre-existing user Google Drive files. |
| Licensing Architecture | $8.99 Lifetime (1-Time Purchase) |
No monthly subscriptions. Permanent Pro access synced across Android and PC Chrome. |