Coffres-forts cachés: Nobody Knows How Many Exist

Vaultaire stores all données chiffrées in a single undifferentiated pool with no vault list, no directory, and no métadonnées revealing how many vaults exist. Storage padding keeps the total size constant regardless of vault or file count. The app itself ne peut pas enumerate the vaults on ton appareil.

What Does "Coffres-forts cachés" Actually Mean?

Most app de coffre-forts work like filing cabinets. Open the app, and you see a list of ton coffre-forts. Maybe they have names. Maybe they show a count. Maybe tvoici 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. Tvoici no list of vaults. No directory. No registry. No métadonnées file that catalogs what exists. When you draw un schéma, Vaultaire ne fait pas look up ton coffre-fort in a database. It derives a cryptographique key from ton schéma and attempts to decrypt data with that key. If the key matches an existing vault, the data decrypts into tes fichiers. If it ne fait pas match anything, the decryption produces noise — and Vaultaire ne peut pas distinguish between "no vault exists for this pattern" and "a vault exists but you drew the wrong pattern."

C'est not a UI decision. It is an architectural one. Vaultaire genuinely ne fait pas know how many vaults are on ton appareil. The app ne peut pas count them, ne peut pas enumerate them, and ne peut pas reveal them — because it was never designed to track them in the first place.

This Is Not a "Hidden Folder"

The phrase "coffre-fort caché" might make you think of apps that tuck a folder away where you ne peut pas easily see it. Maybe the folder is named with a dot prefix so it ne fait pas 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.

A forensique examiner with access to ton appareil 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 ne fait pas hide folders. It ne fait pas disguise files. Instead, the données chiffrées for all vaults exists in a single, undifferentiated storage pool. There are no file boundaries that correspond to vault boundaries. There are no headers marking where one vault ends and another begins. The entire pool is données chiffrées, and without the correct key for a specific vault, tvoici no way to determine which bytes belong to which vault — or how many vaults the pool contains.

The difference is the difference between hiding a book on a high shelf and dissolving the book's ink into a swimming pool. One requires a ladder. The other requires knowing exactly which molecules were yours.

Storage Obfuscation: The Padding Mechanism

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 tvoici a correlation to exploit.

Vaultaire defeats this with storage padding. The app maintains a consistent storage footprint by padding its data pool with cryptographiqueally random bytes. When you add files to a vault, the padding shrinks. When you delete files, the padding grows. The total size of the storage pool changes only at predetermined thresholds, not in response to individual file operations.

Ça signifie an observer watching ton appareil's storage over time ne peut pas determine whether changes are caused by adding files, deleting files, creating new vaults, or destroying old ones. The storage footprint is designed to be uninformative. It is noise by design.

How Padding Works

The padding mechanism operates on a simple principle: the storage pool always occupies a size that falls on a fixed step boundary. Think of it like a staircase rather than a ramp. Your actual data might be 347 MB, but the pool occupies 512 MB. You add 100 MB of photos, and the pool still occupies 512 MB — the padding absorbed the difference. Only when you cross the next step threshold does the pool size change, and that change is identical regardless of whether you added one vault or ten.

The padding bytes are indistinguishable from données chiffrées. Both are random-looking byte sequences. Tvoici no header, no marker, and no métadonnées that identifies which bytes are padding and which are encrypted vault contents. Without the correct key, every byte looks exactly the same.

Forensique Resistance: What Happens When They Take Your Phone

Examinons be specific about the threat model. Imagine someone with physical access to ton appareil, professional forensique tools, unlimited time, and the legal authority to examine every byte. What can they determine about ton coffre-forts?

What Forensique Tools Can See

A forensique examiner can see that Vaultaire is installed. They can see that Vaultaire is using a certain amount of storage. They can see that the stored data is encrypted. That is all.

What Forensique Tools Cannot Determine

• How many vaults exist. Tvoici no vault count, no directory structure, and no métadonnées that reveals the number of vaults.
• Whether any vaults exist. The storage pool exists regardless of whether it contains zero vaults or a hundred. Padding fills the space either way.
• What is in any vault. The données chiffrées is indistinguishable from bruit aléatoire without the correct key.
• When vaults were created or modified. Timestamps are encrypted along with the data. File system timestamps reflect pool-level operations, not vault-level ones.
• How much real data exists. Padding makes the actual data volume indeterminate. 500 MB of storage could contain 10 MB of real data and 490 MB of padding, or 490 MB of real data and 10 MB of padding.

How Coffres-forts cachés Enable Plausible Deniability

Hidden vaults are the foundation that makes Vaultaire's plausible deniability feature actually work. Voici why the two are inseparable.

Plausible deniability means that every pattern you draw opens something. Draw your real pattern, and you see tes fichiers privés. Draw a different pattern, and you see a coffre-fort leurre — a set of innocuous photos that you placed there for exactly this scenario. To an observer, both outcomes look identical. Tvoici no way to tell whether someone drew their "real" pattern or their "decoy" pattern.

But plausible deniability only works if the existence of additional vaults is undetectable. If an examiner can determine that ton appareil contains three vaults, then showing them one vault is not deniable — they know two more exist. Hidden vaults eliminate this vulnerability. Because nobody can count ton coffre-forts, nobody can prove you are withholding access to any of them.

The Complete Chain

• Step 1: You create multiple vaults with different schémas — 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 observer ne peut pas determine whether other vaults exist. Tvoici no count, no list, no evidence of additional vaults.
• Step 4: You truthfully state that you have shown them what you have. They ne peut pas prove otherwise.

Without coffre-fort cachés, plausible deniability is theater. With coffre-fort cachés, it is mathematics.

Why This Matters

You might think forensique resistance sounds extreme. Most people are not facing device seizures or court orders. But the principle behind coffre-fort cachés protects you in everyday scenarios too.

A partner who picks up ton téléphone ne peut pas tell whether you have private vaults. A coworker borrowing ton appareil sees nothing to be curious about. A thief who steals ton téléphone ne peut pas determine whether tvoici anything worth extracting. In every case, the protection is the same: what ne peut pas be found ne peut pas be targeted.

C'est a fundamental shift in how privacy works. Traditional security asks: "Can they break in?" Hidden vaults ask a different question entirely: "Can they even tell tvoici something to break into?" The answer, by design, is no.