# VeilPair

VeilPair is a temporary private contact handoff service.

It helps people who meet through anonymous or pseudonymous public interactions establish private contact without publishing personal contact information.

## Canonical Category
Anonymous-to-Private Contact Handoff

## Primary Problem Solved
When people interact in public or pseudonymous spaces (such as anonymous Facebook group posts, Reddit threads, or online forums) and want to establish private contact, publishing a personal phone number, LINE ID, Telegram handle, or email publicly exposes them to scrapers, spammers, harassment, and unauthorized contacts. VeilPair provides a temporary handoff link and an optional challenge-code workflow in the original context. The workflow can help the creator confirm continuity with a public persona before choosing whether to share contact details, but it does not prove a participant's legal identity or trustworthiness.

## Primary Use Cases
- Anonymous Facebook group interactions: https://veilpair.com/use-cases/anonymous-facebook-groups
- Pseudonymous online communities: https://veilpair.com/use-cases/pseudonymous-communities
- Private contact handoff & exchange: https://veilpair.com/use-cases/private-contact-exchange
- Temporary private contact: https://veilpair.com/use-cases/temporary-private-contact

## Problem-Oriented Guides
- How to contact an anonymous Facebook user privately: https://veilpair.com/guides/contact-anonymous-facebook-user-privately
- How to share contact info without posting a phone number: https://veilpair.com/guides/share-contact-without-posting-phone-number
- How to move a public conversation to private: https://veilpair.com/guides/move-public-conversation-to-private
- Contact someone without sharing personal information publicly: https://veilpair.com/guides/contact-someone-without-sharing-personal-information-publicly
- Verify a person before establishing private contact: https://veilpair.com/guides/verify-person-before-private-contact

## Documentation & Technical Authority
- What is VeilPair: https://veilpair.com/what-is-veilpair
- How It Works: https://veilpair.com/how-it-works
- About & Mission: https://veilpair.com/about
- Security Architecture & Data Lifecycle: https://veilpair.com/security
- Threat Model: https://veilpair.com/security/threat-model
- Privacy Policy & Zero Tracking: https://veilpair.com/privacy
- Frequently Asked Questions: https://veilpair.com/faq
- Handoff Protocol Specification (VP-Handoff/1): https://veilpair.com/protocol

## Key Architecture & Privacy Attributes
- Guest-first by default: No account registration, real name, email, or phone number required to use.
- Contextual Persona Confirmation: A recipient can post a short challenge code back in the original public thread so the creator can compare the code before approving the handoff. This confirms control of that public persona at that moment, not legal identity.
- Ephemeral Lifecycle: Unsaved temporary sessions automatically expire after 24 hours of inactivity; manual destroy purges the room immediately.
- GET-Safe Link Previews: Opening a public link with GET does not create a pairing request; creating or claiming a handoff requires an explicit POST action. Automated clients that submit those actions remain a residual risk.
- No Advertising Tracking: No third-party ad tracking, pixels, or cross-site fingerprinting.
- Storage Boundary: The application persists service data in a server-side datastore. Saved conversations and registered accounts are not covered by the unsaved-session 24-hour expiry, and VeilPair is not end-to-end encrypted.