Enfolk

Get the app

QR: enfolk.org/app

Point your phone camera at the code

App Store Google Play
The Safe in Enfolk

Documents are lockedright on your phone

A passport, an insurance policy, an email password reach the internet already locked. Below is how that works: first in plain words, then for those who want a look inside.

Read in order 5 minutes
Straight to the tech for specialists

Updated 18 November 2026

In short

Locked on your phone

Your phone locks the record itself, before anything is sent. What reaches the internet is a string of characters nobody can make sense of

A spare key is with us

By default we keep a copy of the key, as Google Drive and iCloud do. Change phones and your records stay with you

Or only with you

With “Only I hold the key”, not even we can open your records. The flip side: lose the recovery code and there is nothing we can do to help

01

The path of one record

Like a left-luggage office: you hand over a locked suitcase and keep the key

1

You add a record

Say you photograph your passport. For now it's an ordinary photo, and only your phone has it.

2

The phone locks it

The app locks the record with a key it created itself on your phone. The key sits in protected storage — the same place banking apps keep theirs.

3

Only the locked version leaves

The record travels to the server over a protected connection. Even if someone intercepted it on the way, all they'd find inside is a jumble of characters.

4

The server stores it, but can't read it

On the server the records stay just as locked as when they arrived. Our servers are in the European Union, in Belgium.

5

Only a device with the key can open it

The server hands the record back just as locked, and it's your device that opens it. On a computer or a new phone the Safe will ask you to confirm it's you: with a code from an email or, in “Only I hold the key” mode, with the recovery code. After that the key appears there too.

Records shared with your partner have a key of their own, one for the two of you. Your partner's copy is locked so that only their device can open it. Your personal records, though, stay closed to them: they have no key for those.

02

Who holds the key

A lock is only as good as the hiding place of its key. So the main question about any protection is who holds it. In the Safe, you decide.

Standard protection

on from the start

Only I hold the key

turned on in “Protection”

Only I hold the key

Standard protectionon from the start

PlusChanged phones, confirmed with a code from an email, and everything is there

PriceTechnically, we are able to open your records. But the spare key is stored apart from them, and we release it in one case only: you request it yourself from your own account, and we send a code to the email address you registered with. Only once that code is entered is the key released.

Only I hold the keyturned on in “Protection”

PlusWe can't open your records — not on our own, not at anyone's demand

PriceLose both your phone and the recovery code and nobody can bring the records back, us included

The recovery code appears only on your phone's screen. We never receive it, and it isn't sent by email.

Which to choose?

Standard protection is enough for most people: it helps when a phone is lost. “Only I hold the key” is worth turning on for what no one else should ever see — if you're ready to keep the recovery code apart from your phone.

03

Entry code

Four digits, a fingerprint or Face ID at the door of the Safe. It protects against whoever picks up your unlocked phone.

Ten wrong attempts and the phone erases the key. The records themselves aren't going anywhere: they're on the server, and the Safe will open again with a code from an email or, in “Only I hold the key” mode, with the recovery code.

04

How others do it

Services that store your data fall into two kinds, depending on who holds the key

The service holds the key

Google Drive and Photos · iCloud in standard mode · Dropbox · Notion

Enfolk, standard protection

You can read it and, technically, so can the service

Lose access — they can help you get it back

Only you hold the key

1Password · Bitwarden · Signal · Telegram secret chats · iCloud with Advanced Data Protection

Enfolk, “Only I hold the key”

Only you can read it

Lose the code — the data can't be recovered

Neither kind is better than the other: the first guards against loss, the second against other people's eyes

Even in standard mode the Safe differs from Google Drive: Drive locks a file once it is on its server, while the Safe locks it on your phone, before sending.

05

What happens if…

…I lose my phone or buy a new one?

Sign in to Enfolk on the new phone and confirm the Safe with a code from an email — your records are there. If “Only I hold the key” is on, you'll need the recovery code instead of the email.

…I forget the four-digit code?

Tap “Forgot the code?”: we'll email you a code and you set new digits. With “Only I hold the key” you need the recovery code instead of the email. If you don't have that either, the Safe has to be started over, and the old records are lost.

…someone picks up my unlocked phone?

If the entry code is off, the Safe opens like any other section. If it's on, they get ten attempts, after which the key is erased from the phone.

…someone gets into my email?

In standard mode that is dangerous: with access to your email they can sign in to your account and request the Safe's key — as with almost any service. Turn on two-step sign-in for your email. With “Only I hold the key” email alone isn't enough: without the recovery code the Safe won't open.

…your server is breached?

In standard mode your records are only as protected as the server: the locked records and the spare keys are both stored with us, though separately. With “Only I hold the key” an attacker walks away with locked records only — and nothing to open them.

…I want to switch modes?

Any time, in “Protection”. Turn on “Only I hold the key” and we delete our spare key while you get a recovery code. Turn it off and the spare key is stored with us again.

…I lose the recovery code?

As long as the Safe is open on at least one of your devices, everything can be fixed: issue a new code (“Protection” → “New recovery code”) or turn off “Only I hold the key”. But if you have no code and the Safe isn't open anywhere — say, the phone is lost — the records can't be recovered and the Safe has to be started over. So keep the code somewhere other than your phone.

…I want to open the Safe in a browser?

There is one Safe for all your devices: the same records in the app and in the browser. Sign in to the same account and confirm with a code from an email — or with the recovery code if “Only I hold the key” is on. The four digits for entry are separate on each device.

…my partner and I use different modes?

Shared records are protected the way the partner with the simpler mode is protected. If one of you uses standard mode, we hold that person's spare key, and through it there is a path to the pair key too. Each person's personal records are protected by their own mode.

06

What this protection can't do

Every protection ends somewhere. Better to know in advance where.

  1. In a browser the protection is weaker than in the app. A browser has no protected storage for keys, so on someone else's computer remember to sign out.
  2. Four digits protect against a person, not against equipment. They'll stop whoever picks up your phone. Your main protection is the phone's own lock.
  3. The record type, date and number of photos aren't locked. So don't put anything secret in the name of your own record type.
  4. “Only I hold the key” protects best what is added after you turn it on. Records made earlier were, for a while, kept under our spare key.
  5. If a recovery code was ever emailed to you, replace it. Older versions of the app did that. Issue a new one in “Protection” → “New recovery code” — the old one will stop working.

Next — for specialists

How it works inside

The same thing in the language of engineers: which algorithms, where the keys live, and what the protection can't stop

There are no secrets here that would help an attacker, and there can't be: sound protection doesn't depend on nobody knowing how it's built. That's how banks and messengers work too.

T.1

Three principles

01

Encrypt on the device

Records and photos are encrypted before sending. The server receives and stores only ciphertext.

02

Don't invent our own

Only open standards and proven libraries — the same ones large services use. No homemade cryptography.

03

Your codes stay put

The entry code and the recovery code are created and stay on the device. They never reach the server or an email.

T.2

How the keys are arranged

Everything rests on one key — the Safe key. The other keys exist to store its copies safely.

Only I hold the key

The Safe key is 256 random bits. It is created on the device the first time you open the Safe and encrypts every record and every photo.

On the phone the key lives in the system's secure storage: Keychain on iPhone, Keystore on Android. The app gets it from the system when it opens the Safe.

In standard mode a copy of the Safe key is encrypted with a separate spare key. The spare key sits on the server in a closed store the apps have no access to. The server releases it only on a request from your account, and only after a one-time code sent to the account's email. So the server has everything needed to decrypt the Safe. We don't hide that: recovery rests on it.

In “Only I hold the key” mode a copy of the Safe key is encrypted with a key derived from the recovery code. The code is 40 random characters, created on the device and never leaving it. When the mode is turned on, the spare key on the server is deleted.

The Safe key does not change when you switch modes. So records made before “Only I hold the key” was turned on are protected by that mode less strongly than new ones.

T.3

The record cipher

Every record and every photo is encrypted with AES-256-GCM. This mode doesn't just hide the content, it also puts an integrity seal on it: if a record on the server is swapped or damaged by even one bit, the app notices and won't open it.

Each encryption uses its own random one-time value. So two identical records look completely different on the server, and nothing in the ciphertext reveals that they match.

Same as: iCloud, 1Password, Google Drive
T.4

Shared records with a partner

Shared records are encrypted with a separate couple key. One of you creates it and passes it to the other in a wrapper only the recipient can open.

The wrapper comes from a X25519 (Curve25519) key exchange: each of you has your own key pair, the public half is on the server, the private half stays on the device. The private half reaches the server only locked with the Safe key, which is how the pair key is restored on a new device. From its own private key and the other's public key, both devices derive the same wrapper, while the server, which holds only the public halves, can't. So shared records are protected by the simpler mode of the two: in the standard mode we hold a spare Safe key. Personal records are encrypted with the Safe key and are not available to your partner.

Same as: Signal, WhatsApp
T.5

Entry code

On the phone the code is a lock in front of the system storage, not a cipher: the device itself guards the Safe key. After the tenth wrong attempt the app erases the key from that device.

In a browser there is no system storage. The key sits in browser storage, encrypted with a key derived from the code through the slow function PBKDF2. That's better than nothing, but four digits are not a password. In a browser the main protection is locking your computer and signing out on other people's devices.

T.6

Transit and storage

Between the app and the server there is TLS, the same protected connection banks and email use. It's a second layer: records already travel encrypted.

Our servers are in the European Union, in Google Cloud in Belgium; there Google also encrypts the disks, on top of our encryption.

T.7

What the server sees

Encryption hides the content, not the fact of storage. This stays visible in either mode:

  • that you have a Safe and how many records are in it;
  • the type of each record — “Password”, “Personal documents” or your own;
  • the date of a record and the number of photos in it;
  • the account and email the Safe is tied to.

The title, text, fields and photos of records are always encrypted

T.8

What it protects against

An honest table of what each mode withstands

ThreatStandard protectionOnly I hold the key
Someone intercepts data in transitStandard protectionProtectsDoesn't protectPartlyOnly I hold the keyProtectsDoesn't protectPartly
Records leak from the serverStandard protectionProtectsDoesn't protectPartlyOnly I hold the keyProtectsDoesn't protectPartly
The whole server is breached, spare keys includedStandard protectionProtectsDoesn't protectPartlyOnly I hold the keyProtectsDoesn't protectPartly
Someone gets into your emailStandard protectionProtectsDoesn't protectPartlyOnly I hold the keyProtectsDoesn't protectPartly
Someone demands that we open your recordsStandard protectionProtectsDoesn't protectPartlyOnly I hold the keyProtectsDoesn't protectPartly
A stranger holding your unlocked phoneProtects if the entry code is onStandard protectionProtectsDoesn't protectPartlyOnly I hold the keyProtectsDoesn't protectPartly
Malware on your deviceNo encryption helps against an infected device: the program sees what you see.Standard protectionProtectsDoesn't protectPartlyOnly I hold the keyProtectsDoesn't protectPartly

This page is checked against the app's code. When the protection changes, so will the page.

Back to top

Updated 18 November 2026