Hidden Vaults Without a Visible Vault List

Hidden vaults in Vaultaire are an interface and key-routing property: the app shows no plaintext cross-vault list and opens a vault only after deriving its key from the pattern. On disk, separate encrypted index files remain enumerable, so this design does not make vault count forensically invisible.

What Does "Hidden Vaults" Actually Mean?

Most vault apps work like filing cabinets. Open the app, and you see a list of your vaults. Maybe they have names. Maybe they show a count. Maybe there is a little lock icon next to each one. The app knows exactly how many vaults you have, and that information is visible to anyone who opens the app — or examines the device.

Vaultaire works differently in the interface. There is no screen listing your vault names or asking which one to unlock. When you draw a pattern, the app derives a 256-bit vault key with PBKDF2, hashes that key to form the expected index filename, and attempts authenticated decryption of that encrypted index. If the index exists and its AES-GCM tag verifies, Vaultaire unwraps the random master key and opens the files. Otherwise it presents an empty state.

This routing is part of the storage architecture, but its protection has limits. Vaultaire does not maintain a plaintext master registry mapping vaults to patterns or labels. It does create one encrypted index file per vault, and the app has maintenance paths that enumerate those files. A filesystem examiner can therefore count encrypted indexes even though they cannot read the index contents without a key.

This Is Not a "Hidden Folder"

The phrase "hidden vault" might make you think of apps that tuck a folder away where you cannot easily see it. Maybe the folder is named with a dot prefix so it does not show up in a file browser. Maybe the app uses a "calculator" disguise to conceal its real purpose. These are camouflage tricks, and they all share the same fatal flaw: the hidden data is still there, in a known location, waiting to be found. If that is the workflow you are evaluating, read our guide on creating a secret folder on iPhone before you trust it with sensitive files.

A forensic examiner with access to your device can trivially find a hidden folder. File system tools list every directory. Storage analyzers show where disk space is allocated. Even a moderately tech-savvy friend with five minutes and a search engine could locate most "hidden" folders.

Vaultaire does not rely on a disguised folder or a calculator skin. Inside its app container, it stores encrypted vault indexes plus encrypted blob files. The index contents hide user filenames, MIME types, dates, file maps, and the wrapped master key behind AES-256-GCM. Those contents do not become readable until the correct pattern-derived key authenticates the index.

The practical difference is between a plainly named secret folder and an authenticated encrypted container selected by a key-derived filename. A device examiner can see that the container exists. Without a correct credential, they do not get its readable file map or contents.

What Storage Layout Reveals

Even without a vault list, a clever adversary might try a different approach: analyzing disk usage. If Vaultaire uses 500 MB of storage today and 800 MB tomorrow, maybe you added a vault. If deleting photos from one vault reduces storage by exactly 200 MB, maybe there is a correlation to exploit.

Vaultaire does not keep the local storage footprint constant. Adding files consumes storage, deleting a vault can release storage, and one encrypted index file exists for each vault. Encryption protects content and integrity, but it does not erase all size, count, and timing information from the filesystem.

An observer with app-container access may correlate file counts, sizes, and modification times with activity. iOS Data Protection can restrict access while the device is locked, and the encrypted payloads remain confidential without their keys, but Vaultaire does not advertise local traffic-analysis resistance.

Where Padding Is Used

Vaultaire does use padding in specific formats. Encrypted file headers reserve a fixed header size so ordinary filenames and MIME types are not exposed in plaintext. Encrypted iCloud backup uses fixed 10 MB records plus decoy chunks. Those controls should not be confused with a constant-size local storage pool.

Local vault indexes and blob files still have recognizable application-level filenames and sizes. AES-GCM hides their plaintext and detects modification; it does not make every byte or filesystem artifact indistinguishable from arbitrary random disk sectors.

Forensic Resistance: What Happens When They Take Your Phone

Let us be specific about the threat model. Someone glancing through the app sees no vault catalog. Someone who obtains app-container access through a compromised or unlocked device has a stronger view and can inspect filenames, counts, sizes, timestamps, Keychain availability, and encrypted payloads.

What Forensic Tools Can See

A forensic examiner may see that Vaultaire is installed, how much storage it uses, how many `vault_index_*.bin` files exist, their key fingerprints, encrypted blob files, and modification metadata. The examiner may also copy the ciphertext for offline pattern guessing.

What Encryption Still Protects

• Readable vault labels and file maps. The encrypted index protects file records and the wrapped random master key.
• Original filenames and MIME types. These fields live inside authenticated encrypted file headers rather than plaintext directory names.
• Photo, video, and document contents. File payloads use AES-256-GCM under the random vault master key.
• The pattern itself. Vaultaire does not store it as a plaintext preference, though the encrypted local recovery database contains pattern and phrase material while the device is in normal use.
• A shortcut around guessing. PBKDF2 raises the cost of each candidate, but a copied index filename and AES-GCM tag still let an attacker verify guesses offline.

How Hidden Vaults Enable Plausible Deniability

Hidden vaults provide the interface compartmentalization behind Vaultaire’s plausible deniability feature. The connection, and its limit under filesystem examination, matters when evaluating the claim.

In Vaultaire’s interface, different valid patterns can open different real vaults. You can choose one pattern for sensitive material and another for a less sensitive vault. An observer who sees only the unlocked interface is not shown a label identifying either vault as “real” or “decoy.”

This can reduce disclosure during casual inspection or shoulder-surfing, but it does not satisfy the strongest forensic definition of plausible deniability. An examiner with access to the app container can count encrypted indexes. Use this feature as interface compartmentalization, not as proof that no additional vault exists.

The Complete Chain

• Step 1: You create multiple vaults with different patterns — one for real files, one for decoys, as many as you want.
• Step 2: If pressured, you draw the decoy pattern. The observer sees a vault with boring photos.
• Step 3: The unlocked interface shows no cross-vault list or prompt naming the other vault.
• Step 4: You keep the separate threat boundary in mind: filesystem access can reveal encrypted index count even when the observer cannot decrypt the contents.

The result is practical compartmentalization inside the app, backed by encryption for content. It is not a mathematical guarantee that a device examiner cannot detect additional encrypted containers.

Why This Matters

You might think forensic resistance sounds extreme. Most people are not facing device seizures or court orders. But the principle behind hidden vaults protects you in everyday scenarios too.

A person who reaches Vaultaire’s lock screen does not receive a list of vault names to target. A coworker borrowing your device cannot browse between vaults through a picker. A thief still knows Vaultaire is installed and may target the app or device, but encrypted contents remain protected by the pattern, PBKDF2 cost, AES-GCM, and the surrounding iOS security boundary.

Hidden vaults answer a narrower privacy question: does opening one vault reveal a catalog of the others? In the normal interface, the answer is no. Whether a stronger examiner can detect encrypted containers depends on the device state and access level, and Vaultaire documents that limit directly.