Under construction & unstable

About the creator

Hi, I'm San Tran.

I built Trust Envelope as a personal project — a small, careful tool for keeping words safe until the people who need them are ready.

S

San Tran

Software engineer · security & tools

Why I built Trust Envelope

A friend named Emma — and a sister who sees this every day.

Emma was a friend of mine. She fought cancer with more grace than most people manage when nothing is at stake. She lost.

In the months after, I kept thinking about all the things she might have wanted to say to people she loved — at birthdays she wouldn't see, weddings she wouldn't attend, mornings of bad news that she wouldn't be there to soften. I built this for her, in a way. For the version of her that might have wanted somewhere to put those words ahead of time.

But Emma is only part of the reason. My little sister is an oncologist. She spends her working life with patients who are fighting cancer — and, sometimes, with patients whose treatment becomes about managing the end of their life as gently as possible. Over the years she has shared so many of the stories that stay with her: the things people wished they'd said, the goodbyes that came too quickly, the families that were left holding silence where there should have been words. Some of those stories are devastating. Some are quietly beautiful. They all sit with me.

Trust Envelope is for all of those people too — the ones still in the fight, the ones running out of time, and the families left behind. And it's for the rest of us, who don't get a warning at all. None of us know how much time we have. Some words shouldn't wait for the right moment, because the right moment may never come.

A promise

Free, accessible, and here for the long run.

This is not a business and I don't want it to become one. Trust Envelope will stay free to use for as long as I can possibly keep it that way — because the people who most need to leave a message behind shouldn't also be asked to pay for the privilege.

I'm working out how to keep the lights on without compromising that: small voluntary donations, sponsorship, partnerships with hospice and palliative care groups, and eventually a foundation or trust structure so that the service can outlive me and continue delivering messages decades from now. If you have ideas, or you'd like to help, please get in touch.

The hardest part of a service like this is the promise of "we'll deliver it years from now." I take that promise seriously. I want to make sure that even if I'm no longer the one running it, your messages still find their way.

A bit about me

The person on the other end.

I'm a software engineer who has spent most of my career working in security and developer tooling. I care a lot about building things that don't betray the people who use them.

[More to come — this is a placeholder for now while I figure out what's worth saying here.]

How it's built

Small, careful, transparent.

  • ·Encryption in your browser. AES-256-GCM via the native Web Crypto API. No third-party crypto libraries, no novel algorithms.
  • ·Plain, boring tech. Next.js, Postgres, Node. Hosted on a VPS I can see and reach. No third-party trackers or analytics.
  • ·No surprises in the data. If you delete a message, it's gone — from the database and from object storage.
  • ·Built in the open. I'm happy to walk anyone through the architecture — just drop me a line.

Thanks for reading this far.

Try Trust Envelope