Documentation menu

Sender profile

An opt-in, verified identity card that proves a message really came from your account — set up under Settings → Sender profile. It's a trust feature, not a social profile: there's no directory or search of senders, no follower graph, and no third-party social account linking. Off by default; nothing about it is ever shown until you turn it on.

Setting it up

Fill in a handle (3-30 characters: lowercase letters, numbers, hyphens — this becomes your public URL at /p/<handle>), a display name, and optionally a short bio, a link, and an avatar URL (falls back to your account's Gravatar if left blank). None of this is public yet — check Make my profile public to turn it on, then Save.

Handles are globally unique and claimed on a first-come basis. Renaming your handle releases the old one and claims the new one at the same time.

Where it shows up

Turning on Make my profile public does two distinct things:

  1. Your public profile page, mailinapp.com/p/<handle> — your display name, bio, link, and avatar, plus a "Verified sender: mail.yourdomain.com" badge if you have a verified sending domain. The page is noindex (excluded from search engines) but reachable by anyone with the link. Turning public visibility back off makes the same URL 404 immediately — there's no cached or lingering copy.
  2. A verified sender card inside a connected recipient's Inbox — the real payoff. When a recipient has connected their own Gmail/Outlook account under MailInApp's native inbox rendering and opens an email you sent, a small card with your avatar, name, and verified-domain badge appears above the rendered message, linking to your public profile.

Why the card can be trusted

The card is gated on the same cryptographic manifest MailInApp already signs into every mailed email for native inbox rendering — the same mechanism that tells a connected Inbox "render this live" instead of showing it in a sandboxed frame. A profile card is only ever built from that already-verified manifest's own handle claim; it never comes from parsing the message content itself, so there's no way for a look-alike or forwarded copy of your email to trigger it. A message MailInApp can't cryptographically verify (forwarded mail, mail from anyone else, or anything routed through the sandboxed foreign-message viewer) never shows a card, no matter what it claims about itself.

Because the manifest is generated once at send time, the handle it carries is a snapshot of whether your profile was public at that moment — turning public visibility on after a send won't retroactively add the card to already-sent mail, and turning it off stops the card from resolving on the next open (the display name, bio, and avatar shown in an already-verified card are always fetched fresh, so an edit to your bio shows up immediately on mail already sent).

What's not included

This stays a narrow trust feature on purpose:

  • No public directory or search of MailInApp senders.
  • No follower graph, feed, comments, or likes.
  • No connecting a LinkedIn/X/Instagram account — bio and link are self-authored text only.