Sent to me
Last updated: 8 Jun 2026
NT² Vault runs at se.nt2.me—not because “se” means secure, but because the hostname reads as sent to me. Here is how that name fits the product, the app URL, and the links people send each other.
What does se.nt2.me mean?
Read across the hostname: se + nt (from NT²) → sent; 2 → to (English homophone); me → me. Together: sent to me—someone sent something for you to receive in your vault.
Why is the app not at nt2.me?
nt2.me is the product marketing site—landing, pricing, privacy, and help. se.nt2.me is the encrypted vault app (PWA), service worker, and canonical host for share links like https://se.nt2.me/?m=…. Splitting origins keeps SEO and storytelling separate from the app shell and deep-link policy.
What is the ?m= link format?
User-to-user and third-party handoffs publish https://se.nt2.me/?m=<envelope> at the origin root. The m parameter carries an encrypted vault message envelope. Recipients can open the link while locked; NT² stashes the intent and routes it after unlock. See Use cases for sharing scenarios.
Can other websites generate se.nt2.me links?
Yes. Any service that needs its users to receive, store, and re-share sensitive data can publish https://se.nt2.me/?m=… links. NT² does not need to host the sender's payload—the envelope travels in the URL; decryption happens in the recipient's browser after unlock.
Two doors, one brand
NT² uses two public web addresses on purpose:
| URL | Role |
|---|---|
| nt2.me | Product story—what NT² is, pricing, privacy, help |
| se.nt2.me | The vault app—open, store assets, install the PWA |
You discover NT² on nt2.me. You use NT² on se.nt2.me. That split keeps marketing deploys separate from vault crypto, and keeps the app origin stable for PWA scope, local storage (OPFS), and published links.
Read the hostname: sent to me
The se subdomain is not an abbreviation for “secure environment” or a random engineering prefix. It is product branding baked into the URL.
Spell it across the domain:
se + nt 2 me
│ │ │ └── me (you)
│ │ └── to (homophone)
│ └── nt from NT²
└── completes “sent”
Sent to me. Someone sent you something—a contact invite, an inbox message, a handoff from another app—and you open it in NT² Vault.
That is why the canonical production vault URL is https://se.nt2.me, not a generic name like app.nt2.me or the marketing apex nt2.me. Moving the app to the apex would break the wordplay and mix product SEO with the encrypted PWA.
NT²: Null Trust²—and sent to me
The product name NT² stands for Null Trust²: structured storage with zero-knowledge encryption—you do not have to trust NT² operators with your plaintext.
The vault URL se.nt2.me adds a second layer of meaning aimed at human handoff:
- Null Trust² — how your data is protected at rest and in optional cloud sync (How it works).
- Sent to me — how data reaches you: a link, a QR code, a message from a friend or a third-party service.
Same letters on the domain; two stories that meet when you unlock.
What happens when you open a link
Published share and inbox links use one shape:
https://se.nt2.me/?m=<base64url-envelope>
| Step | What you experience |
|---|---|
| Tap or scan | Browser opens se.nt2.me (install the PWA for the best offline experience). |
| Locked | NT² can stash the message intent before you pick a vault or enter your master password. |
| Unlock | The app routes by message type—contact, inbox item, or other vault actions. |
| Store & share | Content lands in structured templates; you can forward or re-share under your control. |
Plain navigation (settings, scan UI) uses normal paths like https://se.nt2.me/—not ?m=. Receive and Send hub tabs use path segments such as https://se.nt2.me/receive/{tab} and https://se.nt2.me/send/{tab}. The sent to me URL is for payloads addressed to you, not for browsing the marketing site.
For third parties and integrators
If your product helps users hand sensitive data to someone else—a credential, a document, a structured record—you can offer a single HTTPS URL:
https://se.nt2.me/?m=…
Recipients do not need an account on your service. They need NT² Vault (or a compatible client) to decrypt after unlock. NT² servers are not required for the link to open; the design is local-first and zero-knowledge end to end.
Use se.nt2.me in QR codes, copy buttons, and API examples—not legacy aliases. Marketing and legal pages stay on nt2.me.
What to remember
| You want to… | Go to… |
|---|---|
| Learn about NT², pricing, privacy | nt2.me |
| Open the vault app | se.nt2.me |
| Open something someone sent you | https://se.nt2.me/?m=… (sent to me) |
Sent to me. Secured by you.
For practical sharing examples, see Use cases. For encryption and storage mechanics, see How it works. Ready to start? Open the vault app.