SECURITY WHITEPAPER & CRYPTOGRAPHIC SPECIFICATION

HiddenData Security Architecture
& Technical Cryptographic Whitepaper

An engineering deep-dive into HiddenData's zero-knowledge media vault architecture: 64KB independent chunk AEAD streaming, 0B temporary disk writes, V3 envelope atomic rekeying, and Google Drive least-privilege isolation.

Protocol Specification v3.2 Audited & Published: March 2026 NIST SP 800-38D AES-256-GCM
0 B
Disk Residue
Decrypted strictly in volatile RAM TypedArray
64 KB
AEAD Chunk Size
Independent GCM authentication tag per chunk
100,000
PBKDF2 Iterations
HMAC-SHA256 with 16-byte CSPRNG salt
0.005 s
Thumbnail Header Read
Instant preview without scanning full file payload
0.001 s
KeySlot Rekeying
Password change updates only 49-byte header
drive.file
Least-Privilege Scope
Zero access to existing user Google Drive files
01.

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.

Fundamental Zero-Knowledge Axiom

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.

02.

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.
Associated Authenticated Data (AAD) Binding

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.

03.

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:

The HiddenData Zero-Disk Solution: Both the Android app and Chrome Side Panel employ an in-memory streaming pipeline:

ZERO-DISK STREAMING PIPELINE (ON-THE-FLY AEAD DECRYPTION) ● RAM-ONLY STREAM
Encrypted Storage
Local SSD / GDrive .enc
HTTP 206 / SAF Range
64KB Chunk Buffer
AES-256-GCM Decrypt
Volatile TypedArray
MediaSource / ExoPlayer
Zeroization on Close
Ciphertext On Disk
64KB I/O Window
Volatile Memory Only
Cryptographic Zeroization

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.

04.

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.

V3 ENVELOPE BINARY HEADER STRUCTURE (EXACT BYTE ALLOCATION) 49-BYTE FIXED HEADER
[0..3]
'HDV3' (4B)
[4]
Ver 0x03 (1B)
[5..20]
PBKDF2 Salt (16B)
[21..32]
KeySlot IV (12B)
[33..64]
Encrypted Master Payload Key (32B)
[65..80]
KeySlot Tag (16B)
[81..96]
Key Verifier (16B)
[97..100]
Thumb Length (4B)
[101..101+N]
Embedded Thumbnail WebP (Encrypted)
[Offset N..EOF]
64KB AEAD Chunk Payload Chunks
Header Identity & Payload
Salt & Auth Tag
Nonce & Length Offset
Verifier & 0.005s Thumbnail

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.

Atomic Rekeying Performance: Exactly 0.001s

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.

05.

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:

06.

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):

07.

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.
Download Android Early Access APK (v1.0.30) Compare with Other Vaults