Nothing about your encrypted backup should look like anything

Encryption hides what is inside a file. It does not automatically hide the size, shape, or pattern of the file itself — and a locked box that is a distinctive size still tells an observer something, even if they can never open it. A two-word note and a ten-page journal entry produce very different amounts of ciphertext. Left alone, that difference is a small but real leak, even in an otherwise airtight design.

What a size difference actually reveals

Nobody needs to break your encryption to learn something from watching sizes alone. A burst of unusually large uploads might suggest a long entry was just written. A pattern of small, frequent objects might suggest short daily notes versus occasional long-form writing. None of it reveals content. All of it is more than a genuinely zero-knowledge system should be willing to give away, on principle — the goal is not "hard to profile." It is nothing to profile.

The fix: make everything the same shape before it is ever encrypted

The fix is conceptually simple, even though implementing it correctly takes care: pad every object — a note, a sync record, a backup checkpoint — up to the nearest of a small, fixed set of standard sizes before encryption ever happens. From the outside, a short note and a long one become indistinguishable. There is no shape left to fingerprint, because every object that leaves your device already looks like every other one, regardless of what it actually contains.

The goal was never encryption that is hard to break. It is a backup that gives an observer nothing to look at in the first place — not size, not shape, not pattern.

This is a published, peer-reviewed approach to the problem, not something we invented — padding schemes to eliminate size-based fingerprinting have real academic grounding, and we are applying the same principle to Prevon's sync and backup layer rather than treating it as a nice-to-have. It is one addition to an encryption step that already exists, not a new pipeline bolted on afterward.

This is part of the hardening work we are actively rolling out to the cloud sync architecture, alongside the account-delinked storage covered elsewhere on this blog. We would rather describe the standard honestly and tell you when a specific piece lands than round up in marketing copy — that is the same reason this blog exists at all.