When somebody demands your passcode

There is a moment that almost nobody prepares for, and it is over in about four seconds. Somebody has your phone in their hand and wants the passcode. You give it, or you do not, and either way the decision is made under pressure with no time to think.

Almost everything written about this treats it as one situation. It is at least two, and they want opposite things from you.

The two situations

Somebody is taking the phone. A street robbery. They are not going to read your messages. They want the device, and increasingly they want to move money before you can call anyone. The phone is probably not coming back.

Somebody is inspecting the phone. A border officer, a checkpoint, an employer, a partner. They want to look through it and then hand it back. The device is not the target. What is on it is.

These need different preparation, and advice that blurs them is worse than no advice. Hiding things helps in the second case and barely matters in the first. Transfer limits help enormously in the first and are irrelevant to the second.

If the phone is being taken

Hiding your banking app is worth doing, because a thief scrolling your Home Screen in a hurry will not find what is not there. But it is the smaller half of the answer. The larger half is making the phone useless as a way to move money.

Set low transfer limits in each banking app. In Brazil this means Pix limits, and setting a much lower night limit than day limit. In most countries there is an equivalent. This is the single most effective thing on this page, because the standard robbery is a forced transfer in the first few minutes, not a break-in later.

Turn on your bank's own street mode if it has one. Several Brazilian banks ship exactly this under names like Modo Rua. It restricts what can be done from the phone at all.

Turn on Stolen Device Protection in Settings under Face ID and Passcode. It requires biometrics with no passcode fallback for changing your Apple Account, viewing saved passwords, and erasing the device, plus a one hour delay when you are away from familiar locations.

Know how to erase remotely, from someone else's phone or a browser, and know your Apple Account password without looking it up. Practise it once.

If the phone is being inspected

Now hiding matters, and now the hard part shows up: you are going to give the passcode. Refusing has consequences that vary enormously by country and by your status in it, and a phone that is handed over locked often attracts more attention rather than less.

So the question is not how to keep the phone locked. It is what the passcode you give actually opens.

That is a decision to make calmly, at home, months before anyone asks. Not in the four seconds.

Decide in advance what you are willing to lose

Make a short honest list of what is on the phone that you would not want examined, and sort it into two piles: things that would be awkward, and things that would be genuinely damaging. Those are different, and conflating them leads to over-preparing in ways that look suspicious.

Then do the dull, effective thing: take the second pile off the phone where you can. A document that is not there cannot be found, hidden, or demanded. This is unglamorous and it is the strongest single move available.

For what remains, the useful property is not secrecy but plausibility. An examiner who believes they have seen everything stops looking. An examiner who is sure something is missing does not.

Why an empty phone is a problem

People preparing for this tend to overshoot. They wipe the messages, clear the photos, log out of everything, and hand over a phone that looks like it was bought yesterday.

That is a signal. A real phone has a mess on it: screenshots nobody needed, three years of receipts, blurry photographs, group chats about nothing. A phone with none of that is a phone that was prepared, and being visibly prepared is the thing you were trying to avoid.

The goal is not a phone with nothing on it. It is a phone with the ordinary amount of nothing on it.

Where a second passcode fits

This is the gap Vessum was built for. The idea is old and well understood: more than one passcode, each opening different contents, so that the one you hand over is one you decided in advance you could afford to lose.

Two things make the difference between that working and not working.

The decoy has to be full. Put real, ordinary, slightly dull material in it. Old receipts, holiday photographs, an insurance document. A space that opens onto nothing tells whoever opened it to keep asking, which is the exact opposite of what you wanted.

The decoy has to be identical. If the space you hand over is missing a feature the real one has, then anyone who has seen the app before spots it immediately, and you are worse off than if you had never installed it. We wrote about why most implementations fail this test in decoy passwords and why most of them do not work.

What none of this solves

Preparation changes what a person finds when they look at the phone in front of them. It does not change what a laboratory finds when the device is taken away, imaged, and examined with equipment designed for exactly that. If that is the situation you are preparing for, the honest answer has nothing to do with any app: do not carry the data.

It also does not change the law. Some jurisdictions compel passcode disclosure under threat of contempt. In some places presenting prepared material to an official carries its own consequences. The rules differ sharply between countries and sometimes between regions. Nothing here is legal advice, and it is worth knowing the actual rules where you live and where you are going.

The one thing to do today

If you take one action from this page, make it the boring one: set a low transfer limit in your banking app. It takes four minutes, it costs you nothing, and it defeats the most common version of this situation outright.

Then, when you have a quiet evening, do the other thing: decide which passcode you would be willing to give away, and make sure it opens something worth finding.