How do you read a security claim in a vault app?
A list of cipher names and key sizes tells you very little. What matters is who the app defends you against, what it assumes, and what it leaves exposed. A vault that resists a curious relative may do nothing against someone who steals the phone and unlocks it, and a vault that resists thieves may do nothing against a malicious update. A good claim is specific about both sides, and a weak one reads the same whichever adversary you had in mind.
Six questions that separate real claims from slogans
- Against whom? Name the adversary: a nosy acquaintance, a thief, a company server that gets breached.
- Where are keys made and kept? On the device, in the cloud, or both, and who can reach them.
- What does the service see? If there is a server, list what it can learn, even if the files are protected.
- What is outside the protection? Backups, thumbnails, notifications and screenshots are common leaks.
- Has anyone independent checked? A vendor's own statement is not an audit, and an audit has a scope and a date.
- What happens when something goes wrong? Lost phone, forgotten secret, a bug found later.
Absolute slogans about being impossible to break answer none of these, and Veldrin doesn't use them. Apple's own platform security guide is a good model for how a vendor can document specifics, and our guides on whether photo vault apps are safe and on what a security audit of a vault app does and does not show apply the same questions to the apps on the store today.
What does Veldrin protect, and where does each protection stop?
The right-hand column of this table carries as much weight as the left.
| Feature | What it does | Stated limit |
|---|---|---|
| Pattern unlock | A pattern on a 5x5 grid feeds a key derivation and opens the vault, with no account. | A pattern is a smaller secret than a long passphrase and is easy to watch. |
| Hidden vaults | Several vaults, each opened by its own pattern, with no list, names or count shown. | Someone inspecting storage may still estimate how many vaults hold files. |
| Recovery phrase | A nine-word sentence recovers a vault after a forgotten pattern or on a new device. | Lose it along with the pattern and the vault cannot be opened. |
| Hidden vaults | Several vaults, each opened by its own pattern, with no list, names or count in the interface. | Someone inspecting the app's storage may still estimate how many vaults hold files, and backups and exported copies are unaffected. |
| Local backup and restore | A backup you start, encrypted on the device before it is saved to a place you choose; a restore needs the pattern or the recovery phrase. | Veldrin has no iCloud backup, and the place you save the file decides who else can reach it. |
| Local-first storage | Files stay in the encrypted vault on your device, with no Veldrin account and no device sync. | A lost or wiped phone takes the vault with it unless you made a backup. |
| Secure camera | Captures go encrypted into an open vault, never to the camera roll. | It cannot stop a screenshot, a second camera or what is in the frame. |
| App icons | Seven alternate icons and an optional named Home Screen tile. | iOS shows an alert on each change, and the name stays in the App Library, Settings and search. |
| Import and export | Import from Photos and Files, and export any file at original quality. | An exported file is an ordinary copy, outside the vault's protection. |
Two ideas run underneath all of it. The pattern derives a key that opens an encrypted index, and the index holds a separate random master key that protects the file contents, so changing the pattern re-wraps one key and not every file. First run needs no account, and a backup is a file you start and save yourself.
Who each protection is aimed at
A protection only means something against a particular person. Here are six adversaries worked through against the features above, with the limit that applies to each.
| Adversary | What helps | What does not |
|---|---|---|
| A friend or relative who picks up your unlocked phone | The vault needs its own pattern, hidden vaults show no list or count, and an alternate icon changes what the Home Screen shows. | The app name remains in the App Library, Settings and search, so a determined person can still find that it is installed. |
| Someone who has watched you draw your pattern | A long pattern with several direction changes is harder to copy by eye, and a second vault with a different pattern keeps the most sensitive files apart. | A pattern is a smaller secret than a long passphrase, and anyone who has seen it can repeat it. |
| A thief with your locked phone | Files in the vault are encrypted, and the vault stays shut without the pattern. | Veldrin cannot add protection if the thief also obtains your phone passcode and your pattern. |
| Someone with your Apple Account password | Veldrin has no iCloud backup, so the vault is not stored in your Apple Account, and a restore needs the pattern or the recovery phrase. | Originals still in the Photos library, and any backup file you save to iCloud Drive yourself, stay reachable through that account. |
| Someone who pressures you to unlock | A hidden vault shows no list, names or count, and each vault opens with its own pattern. | It cannot stop a person from demanding that you open the vault they can see, and a drawn pattern is easy to watch. |
| A person you handed an exported file to | Veldrin has no sharing in the current app; you export a single file at original quality when you choose to. | An exported file is an ordinary copy and cannot be recalled. |
What is the cryptographic stack, and what is each layer for?
Every encrypted vault is built from the same four jobs, whatever the marketing calls them. One layer turns a human secret into a key, one encrypts the file contents, one protects the record of what the files are, such as names, folders and sizes, and one decides where keys live while the app runs. A weakness in any layer undoes the others, so a vendor who talks only about the second one has told you a quarter of the story. This page doesn't print algorithm names, key sizes or iteration counts for Veldrin, and the sections below explain what to look for in each layer so you can judge any app's answer.
File encryption and why the mode matters
File encryption is the layer people name first, and the name that appears most often is AES with a 256-bit key. The key size is rarely the weak point. What counts is the mode of operation wrapped around it, because a good cipher in a bad mode leaks patterns or accepts tampered data silently. The mode vendors should cite is an authenticated one, such as GCM, which both hides the content and detects any change to it, so a corrupted or altered file fails to open instead of opening wrong. Our AES-256 explainer walks through the modes in order.
Per-file initialization vectors
In an authenticated mode each encryption needs a fresh value, called an initialization vector or nonce, and that value must never repeat under the same key. Reusing it is one of the classic ways good encryption fails. So put one simple question to a vendor: is a new value generated for every file and every change, or is one shared across the vault? If they can't answer in a sentence, ask a follow-up.
How does key derivation protect a short secret?
A pattern or a passcode is a small secret, and a small secret needs help. Key derivation runs the secret through a deliberately slow function before it becomes a key, so every guess costs an attacker real computation. The two numbers that matter are how slow the function is on the device and whether it's tuned against dedicated guessing hardware. That's also why a long pattern with several turns beats a short one: derivation slows each guess, but it can't add secrecy that was never there.
How PBKDF2 and similar functions protect your pattern
PBKDF2 is the long-standing standard for this job: it repeats a keyed hash many thousands of times so that each guess at a pattern costs far more computation. Newer functions add a memory cost to resist graphics-card guessing. When a vendor names one, ask for the cost setting and the date it was chosen, because a setting that suited 2015 phones is too low in 2026.
Why do vaults protect metadata with authenticated encryption?
Why authenticated encryption for metadata?
File names, folder structure, dates and sizes often say more than the contents. A folder called Divorce Papers tells a reader what the files are without opening one. A vault that encrypts file bodies and leaves the index in the clear has hidden the least interesting half. Veldrin protects the index with the pattern-derived key and keeps a separate random master key inside it for the contents, so the structure of a vault is as closed as its files. With authenticated protection, any index that has been tampered with fails to open instead of misleading you.
What does zero-knowledge mean in practice?
What zero-knowledge means in practice
The phrase usually means the service holds ciphertext and no key, so it can't read what you store. Whether that's true depends on the whole system, including recovery, sharing and backup, not on the file encryption alone. Veldrin doesn't use the phrase as a label. What it states instead is narrower and checkable: no Veldrin account exists, files stay on your device, any backup is a file you start and save yourself, and the current app has no iCloud backup, device sync or sharing. Read zero-knowledge encryption explained for how to test the phrase when someone else uses it.
Where do keys live, and what happens to them when the app closes?
Apple's Keychain stores small secrets under hardware-backed protection, and the app sandbox stops other apps reading an app's files. Both are real boundaries, and both are Apple's, not any vault vendor's. They protect a locked, healthy phone best. A jailbroken phone, a debugger attached to a running process or a kernel-level bug can move the boundary, which is why no app can promise protection on a compromised device.
While a vault is open, the keys that open it must sit in the phone's memory. What matters is how quickly an app removes them after locking or leaving the screen, and whether a crash or a force-quit leaves anything readable. Veldrin makes no memory-handling guarantee on this page, so treat the question as open for any app you rely on and test the behavior you can see: lock the vault, switch away, return, and confirm the pattern is required again.
What should you ask Veldrin to show you?
Use the six questions above on this page. Against whom: a curious person with your unlocked phone, a roommate, someone who watches you draw. Keys: derived from your pattern on the device, with a separate master key for the files. Service: none, since Veldrin has no account and no iCloud backup, device sync or sharing in the current app. Outside the protection: screenshots, a second camera, and anything already collected. Independent checking: ask any vendor, us included, for scope and date before you accept a word like audited. When something goes wrong: the recovery sentence is the way back, and without it and the pattern a vault stays shut.
What does Veldrin leave to you?
Pick a long pattern with several turns, keep the recovery sentence on paper away from your phone, decide where you save any backup you start, and treat an exported file as an ordinary copy that cannot be recalled. Our design principles put local storage ahead of cloud, keep keys with you and keep the number of parts small. A principle is worth only as much as the behavior you can check against it, so the checking is yours to do, with the table above in hand.
Ten minutes to test the stated limits yourself
- Create a vault with a test pattern and add one harmless photo.
- Close the app, reopen it and confirm that the pattern is required again.
- Draw a wrong pattern and note what you see. A wrong pattern opens what looks like an empty vault.
- Check Photos for the picture you imported. Import copies the file, so the original stays there until you delete it.
- Look at Settings and the App Library to see what a stranger would see, and compare it with the stated limits for app icons.
- Write the recovery sentence on paper, and confirm you can read it back without opening the phone.
The same routine works as a template for any vault app. The point of writing down what you saw is that a claim you tested yourself is worth more than one you read.
Hold any vendor to a list like this one
If a claim from Veldrin or anyone else goes beyond what the vendor can show, it's wrong, and the table above is the standard to measure it by. Vendors like to invoke zero-knowledge, and zero-knowledge encryption explained treats it separately, because it's a good example of a phrase that needs a threat model attached.
Questions people ask
Is Veldrin secure?
Veldrin states what it protects and where each protection stops, and avoids absolute words like secure without a threat attached. Read the stated limits for each feature and judge them against who you are protecting your files from.
What is a threat model?
A written statement of who an app is defending you against, what it assumes about your device, and what it doesn't cover. A vault that resists a curious relative is a different product from one that resists a thief, and a threat model says which.
Does an independent audit prove an app is safe?
No. An audit has a scope and a date, and it shows what the reviewer examined at that point. It can find problems but can't show their absence. Ask what was covered, when, and whether the findings were published.
How does Veldrin protect my files?
Your drawn pattern derives a key that opens an encrypted index, and the index holds a separate master key for the files. Changing the pattern re-wraps that one key, and the files stay as they are.
Does Veldrin need an account?
No. First run needs no account, no email and no configuration. A backup is a file you start and save yourself, and the current app has no iCloud backup, device sync or sharing.
Can anyone break AES-256?
NIST's 2021 review of AES (NISTIR 8319) identifies no practical attack on the cipher itself, and the weak points sit around it: a guessable unlock, a leaked backup, a malicious update or a compromised phone. Judge the whole system, as the table above does, and be wary of any vendor who says nothing can break it.
Why use PBKDF2 for key derivation?
Because a pattern or passcode is a small secret, and deliberate slowness makes each guess expensive. PBKDF2 is a long-established, widely reviewed choice. Newer functions add memory cost, so ask any vendor which function and what cost setting it uses.
What data does Veldrin send to its servers?
Veldrin has no account, so there is no sign-in record to send. Files stay on your device, and any backup is a file you start and save to a place you choose. Veldrin doesn't claim anything beyond this.
Can a jailbroken iPhone compromise my vault?
A jailbroken or otherwise compromised phone weakens every protection that relies on iOS, including Keychain and the app sandbox. No vault app can promise safety on a device someone else controls, so keep iOS updated and avoid jailbreaking.
How is metadata encrypted?
Veldrin protects the vault index with the pattern-derived key, and the index holds the separate master key for file contents. Names, folders and structure sit behind the same lock as the files themselves.
What happens to my keys if the app crashes?
Veldrin makes no promise about memory handling on this page. Keys must exist in memory while a vault is open, so after a crash lock the phone, reopen the app and confirm the pattern is demanded again before trusting the state.
What happens if I lose both my pattern and my recovery phrase?
The vault can't be opened. Veldrin has no account and no reset that works without your secret, which is how the protection works and also its cost, so keep the recovery sentence on paper somewhere other than the phone.
Is a drawn pattern as strong as a long password?
No. A pattern is a smaller secret than a long passphrase and is easy to watch. Key derivation slows each guess, and a long pattern with several direction changes raises the effort, but it can't add secrecy that someone has already seen.
Sources