Help.

Three honest possibilities. (1) Someone already opened the link. A wisp only resolves once — if anyone with the URL clicked it first, the ciphertext is wiped and the page reads “Someone glimpsed this one before you did.” (2) The 24-hour ceiling elapsed. Wisps expire 24 hours after send, even if nobody watched. (3) The link is missing the #k=… fragment. Some chat apps and link previewers strip URL fragments — if the recipient pasted a shortened link, the decryption key may not have made it. Sending again from /sent will fix all three cases.

Check spam first; hello@wisp.video is a new sender domain and some providers throttle it on the first delivery. If it’s genuinely missing, the link is also shown on the composer’s success screen for 10 minutes after you send — you can copy it from there and paste it into Signal, iMessage, Slack, anywhere. If you closed the composer too fast, email hello@wisp.video with the recipient address and approximate send time and we’ll recover the link from the database (we have the /v/<id>; you still have to provide the key — sent at compose time, see /security).

Browsers block getUserMedia in three common situations. (1) Permission was denied previously — open the site permissions panel (lock icon in the address bar) and reset camera + microphone to “Ask.” (2) Another app is holding the camera (Zoom, FaceTime, OBS). Close it and reload. (3) iOS Safari versions below 14.1 don’t support MediaRecorder — update iOS, or use Chrome on Android / any desktop browser instead. If the consent screen still won’t advance after retrying, email hello@wisp.video with the browser + version and we’ll dig in.

Open /sent and verify your email with the one-time code we send to the address you sent from — no password, no signup, that single code is the whole auth. Then tap the wisp and hit Recall. The ciphertext is wiped server-side immediately and the link stops resolving. If they’ve already viewed it, there’s nothing left to recall — wisps are wiped at view-time, not at recall-time.

Tokens are pay-per-send, not a subscription, so the dashboard won’t auto-charge you. Buy a pack from /tokens — packs start at 10 sends for $5 and never expire. Stripe or crypto checkout (BTC / ETH / stablecoin). Tokens land in your balance within a few seconds of a successful charge; refresh /tokens if you don’t see them.

This is almost always a copy-paste truncation — the recipient received a URL without the #k=… fragment. Email apps and chat apps sometimes break the URL across two lines or strip everything after the #. Send the link as a single line, ideally through a channel that preserves the full URL (Signal, iMessage, Slack). If you’re sure the full URL got through and decryption still fails, the ciphertext may have been tampered with in transit — let us know at hello@wisp.video so we can verify the SHA-256 server-side.

Sending requires an email so we can deliver receipts + the recall affordance, and so the recipient can see who sent it on the consent screen. Receiving requires nothing — the recipient never signs up, the link just works. There’s no password at any step; the sign-in flow is a one-time code emailed to you.

It doesn’t stop a determined recipient from screen-recording what they see. It doesn’t encrypt the recipient’s email address (we need it to deliver the link). It doesn’t offer real-time chat, scheduling, group sends, or analytics. By design — see /about for why the scope is deliberately narrow, and /security for the full threat model of what Wisp does and does not protect against.