When your landlord asks for ID on WhatsApp
3 min read By NT²
Front and back of your ID in WhatsApp or LINE is fast for the landlord—and a permanent copy in a chat log you do not control.
A message you cannot unsend
You found an apartment in Berlin—or Taipei, or Lisbon. The landlord wants to verify identity before signing.
The instructions arrive as a chat bubble:
Please send photos of your ID card, front and back.
You open the camera roll. You snap both sides. You paste them into WhatsApp, LINE, or Telegram. Done. Lease one step closer.
Except:
- The images live in the chat forever unless someone deletes them—and you cannot force that on the other phone.
- They are full resolution—every detail a scanner would capture, not just what a lease requires.
- They may sync to cloud backups on both devices.
- Six months later, the same photos are still there when you need to prove address for something else.
Ana’s story on nt2.me/help/use-cases is this moment, named plainly: the wrong habit is not malice—it is convenience without structure.
What goes wrong is not only “hackers”
Security articles love breach headlines. Renters feel the problem sooner in smaller ways:
| Moment | Messaging-app path | Structured vault path |
|---|---|---|
| Wrong thread | Autocomplete sends ID to a group chat | Item stays in one encrypted place |
| Oversharing | Full card image every time | Share a file or link; recipient decrypts with a passphrase you set |
| In-person viewing | Hand over the phone unlocked | Safe presentation shows issuer + partial number; routing details stay masked |
| No expiry | Chat history is the archive | Encrypted links can expire; vault shares can be revoked |
You needed a landlord to see that you are you—not to give them a permanent scan of a government identifier.
How NT² is designed for this
NT² Vault treats identity scans as Document items: metadata fields (issuer, number, expiry) plus encrypted attachments for front and back images. Everything encrypted on your device with a zero-knowledge design.
Three pillars map to three moments:
- Store — One Document entry; attachments encrypted locally; unlock offline at the embassy or appointment.
- Share — Hand off a
.nt2sharefile, an encrypted link, or a vault-to-vault send—not a photo dump in chat. Share passphrases are separate from your master password. - Present — Meet in person? Show only what the moment requires on your screen—masked fields, nothing uploaded to the verifier’s server.
We are building Inbox accept/decline for vault-to-vault trust, so receiving a share feels like a deliberate decision—not opening an unknown attachment.
Pre-launch honesty
NT² Vault is in active development and not open to the public yet. This article describes design intent, not a tutorial you can run today.
That matters because the WhatsApp habit will not wait for our launch calendar. Knowing the alternative shape—structured item, encrypted handoff, redacted presentation—helps you decide whether to keep pasting ID photos when the next landlord asks.
Learn more
- Ana’s use case on nt2.me: nt2.me/help/use-cases
- Sharing modes overview: nt2.me/about
- Related store story: seed phrase in Apple Notes
- Follow the blog: RSS feed
When NT² launches at se.nt2.me, renting abroad should not mean another set of ID photos sleeping in someone else’s chat history.
Last updated 2026-06-28
Related stories
- Your seed phrase shouldn't live in Apple Notes
3 min read
- Null Trust² — what the name means
3 min read
- Welcome to the NT² Blog
2 min read