The emergency code

How you get back out

You request the emergency code. Kaze sends an e-mail to the address you stored. You type the code from that e-mail, and the block ends.

With strict mode on, the e-mail still arrives at once — but the code in it only works ten minutes after your request. Type it earlier and the app tells you from when it works. The ten minutes keep running on the clock even if you quit Kaze in the meantime. That wait is the point of the mode: it stands between the impulse and the way out.

Where the code is made and where it lives

The code is made on your phone. What stays on the device is an unreadable fingerprint of it — enough to check what you type, not enough to recover the code from.

In readable form it exists in exactly one place: in the mailbox Kaze sends the code to. That is not a weakness, it is the design — the detour through your mail is the friction Kaze is built on. It also means the e-mail sits there until you delete it.

What the code can and cannot do

It ends one block — the one you requested it for, not all of them.

It does not expire. A code you requested hours ago still works.

Request a new one and it takes over from the previous one. If the previous one already worked, it keeps working until the new one does — so there is no moment in which neither opens. After that, only the code from the newest e-mail opens. The code screen tells you which one currently works.

What we see — and what we do not

We learn that the mail server accepted your message. We do not learn that it reached you. Nobody at Kaze sees your code — it is made on your device and goes straight to you.

That is why the app says “on its way” and not “delivered”. It does not claim what it cannot know.

What happens to your address

Your address is processed in order to send the e-mail. Kaze itself does not retain it — if an e-mail cannot be delivered, all that remains with us is one figure per day: how many were undeliverable. No address, no content. Sending runs through a mail provider, and the provider keeps a log of its own in which the recipient address appears — that is how sending mail works, with any provider. How long it keeps that log is something we are clarifying, and we will state it here once we know.

If nothing arrives

The e-mail should be there by now — if not, look in your spam folder or send the code to a different address; the block keeps running unchanged.

Sending to a different address works on the code screen itself. Your stored address stays as it is unless you change it yourself.