How VeilPair Works
VeilPair uses a 4-step workflow: Create, Share, Verify in original thread, and Connect privately.
The 4-Step Handoff Process
Step 1: Create a Temporary Handoff Link
User A creates a temporary handoff link (e.g. https://veilpair.com/p/deal-592). The product defaults to a single successful pairing in the UI, while the owner can configure request and reuse settings. No login or real-world identity information is required for the guest flow.
Step 2: Share in the Original Public Context
User A replies in the public thread (such as an anonymous Facebook group or Reddit post) with the VeilPair link.
Step 3: In-Context Pairing Challenge Verification
After User B opens the link and explicitly requests access, VeilPair presents a short challenge code (e.g. KITE-583). User B can comment this code back in the original public post. User A compares the public comment with the pending request before approving it. This links the requesting browser to control of the public persona at that moment; it does not prove legal identity.
Step 4: Ephemeral Private Relay & Direct Handoff
Once approved, both participants enter a private room. They can exchange contact cards (LINE, phone, email, Telegram) or finish their conversation. An unsaved room expires after 24 hours of inactivity; a saved room remains until destroyed. Either participant can destroy the room immediately.
Anti-Crawler & Preview Bot Protection
When sharing links on social platforms, preview bots commonly fetch the URL with a GET request. VeilPair does not create a pairing request on GET; creation requires an authenticated, rate-limited POST. This protects against ordinary GET-only preview fetches, but it is not a CAPTCHA and cannot prove that every POST originated from a human.