Sent to me means ciphertext to you

A name for the receiving side

Most security products talk about sending: share, export, invite, upload.

NT² also cares about the other side of the handoff. Something sensitive arrives. The recipient needs to understand it, decide whether to accept it, and store it safely if it belongs in their life.

That is why se.nt2.me reads as "sent to me." It is a small reminder that sharing is not complete when the sender clicks a button. It is complete when the recipient can handle the data safely.

The server should not become the reader

The phrase also carries a boundary. Sent to me does not mean readable by NT².

When NT² uses a relay or cloud-shaped path, the product goal is still blind transport: sealed bytes move through infrastructure, while keys and plaintext remain with vaults and users. The server can help deliver. It should not become the audience.

That distinction matters for everyday sharing. A bank field sent to a family member, an ID scan sent to a landlord, or a credential sent to a co-founder should not become server-readable just because delivery needs a network.

A product promise in a small URL

Names cannot secure data. Architecture has to do that.

But names can remind a product what it is for. NT² is built around Store, Share, and Present. The share part is not "broadcast my secrets." It is "send exactly what this person needs, under rules I understand, so they can receive it safely."

That is the serious meaning behind the small wordplay: sent to me, ciphertext to you, control with the people at both ends.

Read more about the NT² design pillars at nt2.me/about, or follow the RSS feed.