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 Peer chat where the people you invite can reply.

Messages and chats use end-to-end encryption and direct browser connections. 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.
• Create an expiring short link to an ordinary web address using the separate URL tool.

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.

The shortener and feedback form have different data paths from encrypted rooms. Short-link destinations are stored on the server until expiry. Feedback and an optional reply email are stored for the creator to read. These tools do not inherit the end-to-end encryption of messages and chats.

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 through Feedback without supplying an email. Use a disposable example when reporting a sharing issue, and keep real secret links, identity recovery codes, and private message contents out of reports.