Security

What we protect, and what we will not pretend.

You are trusting us with words you may only get to say once. The least we owe you is a precise account of how they are stored — including the parts that are not reassuring.

What we guarantee

Encrypted in transit

Every connection to MyWishLetter is served over HTTPS with a certificate issued by AWS Certificate Manager. Session cookies are marked Secure and HttpOnly, so they are never sent over plain HTTP and are not readable from JavaScript.

Your letters and files are encrypted before they leave your device

Every attachment — photograph, voice note, video or document — is encrypted in your browser with its own AES-256 key before it is uploaded, and our servers only ever receive the encrypted result. Since 4 October 2026 a letter's words are encrypted the same way: in your browser, with their own AES-256 key, before the letter is saved — and when the letter is opened, the words are decrypted in the reader's browser. We store only the encrypted words. A letter's title, who it is for and when it opens are not encrypted this way, because our servers need them to list and deliver it. There is no passphrase for you or your recipient to keep: the letter opens on the date you chose.

Administrators cannot open your letters or files

Each letter's key and each file's key is sealed by a key in AWS Key Management Service whose policy grants decryption to the application alone. Our administrators — including the account owner — are able to manage that key but are explicitly not permitted to use it to decrypt. An administrator opening our database or storage console sees encrypted text they have no permission to unseal, and every decryption the application performs is recorded in an AWS audit log naming the key it was for.

Encrypted at rest

Letters live in Amazon DynamoDB, which also encrypts every table at rest. Nothing is written to disk unencrypted, and no letter or attachment is stored in a publicly reachable location — the attachment bucket blocks all public access and refuses any request that is not over TLS. A letter saved before 4 October 2026 is protected by this encryption at rest until it is next saved, when its words are encrypted on the device too.

Never publicly addressable

There is no URL that lists letters, and no letter can be reached by guessing an identifier. Reading a letter requires either your own authenticated session or a signed, expiring link issued to the named recipient.

Sign-in without a password

We use email sign-in links, so there is no password for us to store or for you to reuse. A sign-in link is valid for fifteen minutes, works once, and is cryptographically bound so it cannot be modified or extended.

Notifications never quote a letter

A delivery email tells the recipient that a letter is waiting. It does not include the letter's text. Neither does any push notification, log line, or error report. A chat pop-up on your phone can show who wrote and the first words of a message, but never for a locked chat, a timed message or a Full Privacy chat, and one switch in Settings keeps every name and word off your lock screen.

Least-privilege infrastructure

The servers running MyWishLetter can read and write only MyWishLetter's own database tables and only its own payment credential. They have no access to any other system in our account, and payment secrets are held in AWS Secrets Manager where every read is logged.

Deletion, exactly as it works

Deleting a letter cancels every pending delivery and removes it from your account at once; the stored copy is removed for good when you delete your account. A letter that has already been delivered stays with the person who received it — deleting it clears your archive, not their copy. Deleting your account removes your letters, recipients and delivery history. This is free and needs no explanation from you.

An audit trail on privileged actions

Administrative actions are recorded to a separate audit log with the actor, the action and the time. Administrators do not read letter content in the course of support work.

Encryption: what it covers

The words of letters you write yourself, the files you attach and your one-to-one chat messages are encrypted on your own device before they reach MyWishLetter; a letter Wish Buddy writes for you is encrypted on our servers instead. Here is what that covers, and where its limits are.

One-to-one chat messages

A text message in a one-to-one chat is encrypted on your device before it is sent, for every device of both people. So that your chats follow you to a new phone with nothing for you to do, we keep an encrypted backup of each account's chat key, locked with a secret our servers hold: a copy of our database alone cannot open it, and your own signed-in device restores it for you. When a message cannot be encrypted this way — the other person has not opened Chat on a supported device yet — it is encrypted on our servers instead.

Letters protected with a passphrase before 4 October 2026

Until 4 October 2026 a letter's words could also be protected with a passphrase. That option has gone — a surprise should open without anybody having to know a passphrase, so every letter is now encrypted for you and opens on its date. A letter protected before then stays protected: its words, and the files attached while it was protected, still open only with the passphrase its author chose, and nobody at MyWishLetter, Wish Buddy included, can read them. If that passphrase is lost, nobody — not even MyWishLetter — can open the letter.

What still sees the words

Write for me in Chat sends the draft you choose to our AI service, and Wish Buddy reads what you give it. Writing help on a letter reads what you send it. If you report a message, our safety team sees its words only if you choose to include them; your device shares that message's key and we check it against what was sent, so the words cannot be forged.

The limits, plainly

The code that encrypts is delivered by our servers each time you open MyWishLetter, and the chat key backup is locked with a secret our servers hold, so this protects your words from a copy of our database and from our storage — but not from someone who controls our servers. Group chats, photos, voice messages and other files in chat are encrypted on our servers. Calls run through Amazon IVS and are encrypted between each device and IVS.

What we do not claim

Plenty of products in this category imply more than they deliver. Here is what MyWishLetter does not do.

Letters can be opened by our servers when they may be read

A letter's words are encrypted in your browser before they are saved. So that the person you write to can open it from a link with no key of their own — possibly years from now, and without you present — our servers keep each letter's sealed key and unseal it when the letter may be read; Wish Buddy, the export you ask for, and a reported anonymous letter a moderator is cleared to review are read the same way, and every one of those unseals is logged. So we can technically read your letters, and so could anyone who compromised our infrastructure. We restrict, log and design against that. We do not call MyWishLetter zero-knowledge.

Nor is it zero-knowledge for letters and files, strictly speaking

We hold the sealed key to each of your letters and files, even though our administrators are not permitted to unseal it. That is a deliberate trade: a scheme where only you held the key would mean a letter scheduled for 2038 could never be delivered if you forgot a password or were no longer here — which would defeat the purpose of the product. The account owner can, in principle, change the key's policy to grant themselves decryption; doing so leaves a permanent record in the audit log. Removing even that ability requires organisation-level controls we have not yet put in place, and we would rather write that down than imply a guarantee we cannot make. Files attached to a letter protected with a passphrase before 4 October 2026 carry a second layer, inside this one, that only the passphrase opens.

We are not a legal will

A letter delivered on a condition you set has no legal force. It does not transfer property, appoint a guardian or replace a will. Please talk to a lawyer for anything that must hold up legally, and use MyWishLetter for the words a will has no room for.

Email is only as private as the inbox

Once a letter is delivered, it lives in your recipient's email account under their control and their provider's policies. We cannot recall a delivered letter, and we cannot protect it there.

We have not been independently audited

MyWishLetter has had no third-party penetration test or SOC 2 audit. When that changes we will say so here, with a date. Until then, treat these statements as our own description of our own system.

Reporting a vulnerability

If you have found a security problem, please email support@mywishletter.com with enough detail to reproduce it. We will acknowledge you within three working days. We will not pursue legal action against anyone who reports a flaw in good faith, does not access other people’s letters, and gives us reasonable time to fix it before publishing.

For what we collect and how long we keep it, see the privacy policy.

    Security · MyWishLetter