No signup
No account or app install. Create or open a card in the browser.
No signup. Free. Write a short note, then hand over a QR and password.
They can read it for one hour after opening — a temporary digital message card.
No account or app install. Create or open a card in the browser.
Share a password-protected message link via QR image — they unlock and read.
Readable for one hour after unlock, only in that browser. When time is up the screen switches away. After viewing ends, stored data is deleted later.
Enter a title, body, and signature for your note or letter.
Send the URL or QR, and share the password through another channel.
With the password, a finger-reveal viewer opens — readable for one hour in that browser only.
My message card is a free tool to safely deliver messages you don’t want to keep — via QR and password.
No signup — use it for thanks, anniversaries, surprises, and more.
Readers hold a finger to reveal text and turn pages with the bottom-left buttons.
Readable only in the opening browser for one hour. Share the QR on LINE, iMessage, or other apps.
Messages are password-protected and encrypted. Copy is blocked in the viewer (screenshots cannot be fully prevented).
After expiry they become unreadable, and server data is deleted later.
My message card is a free, no-signup way to deliver a message you do not want sitting in chat forever. You write a title, body, and optional signature, then share a QR (or URL) plus a separate 6-digit password. Content is encrypted with a password-derived key. After unlock, it is readable only in the opening browser for one hour. The core of reading is a finger-reveal viewer: text clears only where—and while—a finger is held. Lift the finger and it blurs again, so capturing a clean full-page screenshot is deliberately awkward. Copy is also blocked in the viewer (the OS screenshot button itself cannot be fully disabled, but the design leans toward “hard to keep”). Stored data is deleted within seven days of creation. It is a thin card for “deliver now, fade soon”—not a permanent letter archive.
Below are situations that fit the current product. The common thread: the message matters at the moment of opening, and reading under a finger makes leftovers harder.
LINE and email keep polite or awkward thank-yous forever. Send a QR in chat and the password separately. They read for one hour in the unlocking browser, holding a finger to reveal text. Use it for words that need to arrive once—not for notes meant to be revisited.
Create the card early, share the QR, and give the password on the day. Print the QR into a wrapping or send the image in chat. Until unlock, the body stays encrypted. After unlock they read by holding a finger—different from a always-clear chat bubble. Not an album, but right for a single day’s note. Handing over the password too early spoils the surprise.
Chat logs invite rereading and one-tap screenshots. Here, text does not appear until a finger is held, so an untouched screen stays blurred. Getting a clean shot of the full message while pressing is more work, and the whole page rarely sits clear at once. Add copy-block, first-browser binding, and a one-hour window: not perfect secrecy, but clearly harder to keep than a permanent chat log. Still not “impossible to capture,” so time the password carefully for heavy content.
On the Japanese UI you can choose horizontal or vertical writing—title, body, signature like a paper card. Meant for short notes, not long reports. The English UI does not offer vertical layout, but QR + password and the same finger-reveal viewer work the same.
Reading binds to the first browser that unlocks. Even with the correct password, another browser or device is rejected. Useful when you want them to open once on their phone. Even there, the full text is never always visible—only under the finger. One hour after unlock, it ends; “later on the home PC” is out of scope.
No extra app—just a browser. Send the QR image or copy the URL. If you can say it face to face, you do not need a card. It helps when you are apart, asynchronous, and do not want a lasting log. The QR is for opening later on their device and reading under a finger. Prefer a separate channel for the password when you can.
Not permanent letters, attachments, multi-reader archives, or account history. Finger-reveal makes screenshots harder; it does not ban the OS capture button. Do not casually post the QR on a public feed. A simple filter: out of chat history, enough to read once under a finger, and one browser enough?