Here. For a while.

A place for a temporary exchange

Some exchanges need a short note, a file handoff, or a small conversation while people are present. Held brings those into the browser. Create a secret link to a read-only message, or open a Group chat where the people you invite can reply.

Messages and chats use end-to-end encryption and browser connections, with an optional encrypted relay for restrictive networks. Their availability follows the live sessions holding them. This makes the connection between keeping something available and staying present visible, instead of offering a permanent inbox or a server archive.

What you can do with Held

Use the format that fits your exchange, and review its lifetime and privacy details before sharing.

• Share an immutable encrypted note, with optional Markdown formatting.
• Open a temporary group chat for up to 16 participants.
• Transfer files directly between browsers with explicit receiving and saving.
• Record a normal or locally disguised voice message and review it before sending.
• Use a saved signing identity when you want peers to recognize the same key in future rooms, with an optional website, short bio, and verified contact email.
• Create an expiring short link: choose Traditional for the shortest link or Encrypted to keep its destination private from Held.

Explain the boundaries

Private content sharing is not the same as anonymity, and temporary access is not a way to erase someone else’s saved copy. Held’s public documentation describes the connection metadata, browser storage, identity behavior, and network limitations that matter when deciding whether it fits your use.

Traditional short links are the default and store a destination Held can read until expiry. Encrypted short links are slightly longer: the browser encrypts the destination and keeps the secret in the complete link, so Held stores only the encrypted address. Local short-link history keeps the latest 100 destinations and complete links until removed, cleared, or replaced by newer entries. Optional identity websites and bios are self-provided and stored by Held with the public identity until changed or removed. Contact emails require verification through Resend and are stored until removed or successfully replaced; only authenticated, connected peers receive them. Feedback and an optional reply email are stored separately for Held’s team to read and are not encrypted like messages.

Questions and feedback

The public guides explain Held’s privacy model and practical limits. No independent security audit is claimed; development tests do not establish one.

You can send an idea or report a problem to Held’s team through Feedback without supplying an email. If you leave an email address, expect a reply within a couple of days. Use a disposable example when reporting a sharing issue, and keep real secret links, identity recovery codes, and private message contents out of reports.