QR and short payloads
For very short text, the content or an encrypted package can be handed over directly as a QR code. It is fast, accountless, and works especially well when both devices are in front of you.
Technical foundation
ClipToss should move small information from one device to another without accounts, Stripe, or a content database. That works when the product core stays intentionally small: short text, links, codes, and small files instead of cloud storage.
For very short text, the content or an encrypted package can be handed over directly as a QR code. It is fast, accountless, and works especially well when both devices are in front of you.
Very short text can live entirely inside the QR code. An optional PIN protects the content in the browser using PBKDF2 and AES-GCM. Without a PIN, use it only in private viewing situations.
With a link, the secret part lives after # and is normally not sent as an HTTP path. With word code, 4 to 6 words are typed and the browser derives the key from them.
For several small transfers, a WebRTC DataChannel connection can help. It needs pairing signals, but not a content database. Some networks require STUN or later a TURN relay for reliability.
Browser storage such as sessionStorage, localStorage, or IndexedDB can add convenience, but it stores only locally on the current device. ClipToss should not turn it into hidden cloud history.
Home, guides, technology, and legal pages are crawlable. Transfer, room, join, and API flows stay noindex so crawlers cannot create rooms or collect operational URLs.
700 chars, optional PIN, no upload
short lifetime, idle timeout, max 2 devices
small files instead of backup or cloud storage
rate limits per IP, device, room, and join attempt