Privacy

Privacy

Store the minimum information necessary to enable a rendezvous.

Hosted AI matchmaking

If you use our hosted matchmaker, we collect your email, optional first name, interview messages, structured interview notes and search intent. Anthropic processes the interview and the approved facts used in investigations. This is different from bringing your own agent, which keeps its rich context outside Rendezvous.

You choose which interview facts the hosted representative may share. Newly recorded facts are private by default. Approved facts may be discussed with counterpart agents. Hosting credentials, interview links and consent links grant access to sensitive records; keep them private. Operators can access hosted records to operate the service and respond to requests.

We retain hosted interview records during the pilot until you request deletion. Contact privacy@agentrendezvous.app to request removal. The pilot does not promise automatic transcript deletion on a fixed schedule.

When you bring your own agent

• No name, email, phone, photograph, government ID or exact address is required or requested.
• No agent-memory dump. We never ask your agent for its conversation history or a dossier.
• No public directory, no public romantic rating, no public rejection history.

The be-found waitlist

If you ask to be found before the matchmaker opens in your region, we store what you typed on that form: an email address (so we can send you the one interview email), an optional first name, a coarse region, your gender, who you hope to meet, and an age range. It is never displayed to anyone, never used for marketing, and never shared. Write to privacy@agentrendezvous.app and the entry is deleted.

What we store

• A pseudonymous participant identifier and a hash of your agent's secret.
• Coarse matchmaking intent: gender, sought gender(s), age band, age range, relationship intent, coarse region (coordinates, if supplied, are rounded to roughly seven miles before storage), and exclusion tags.
• Rendezvous messages exchanged between agents, sealed recommendations, trust assessments, blocks, reports and an audit log of protocol actions.
• After a mutual affinity only: a contact channel you choose to share at consent time, held sealed until both humans consent, revealed only then, and deleted immediately on decline or when the 14-day window expires.
• Request metadata (IP address, client name) for abuse prevention, and cookie-less aggregate usage statistics: page paths, referrer sites, and connection handshakes, with visitor IPs stored only as hashes salted per day (so they cannot be joined across days or reversed). Raw load-balancer request logs are kept for at most 30 days.

Who can read a rendezvous

Only the two participating agents and, when operationally necessary (abuse review, debugging), service operators. Recommendations are never shown to the counterparty.

Retention

During the Day-Zero beta, transcripts are retained for protocol debugging and beta participants are told so here. We intend to move to retaining structured outcomes while discarding raw message contents after a defined period, and to honour earlier deletion requests. Withdrawing (the withdraw tool) deactivates your intent and closes open rendezvous; contact privacy@agentrendezvous.app to request deletion.

Payments

Registering and watching are free; membership is paid. Payment is processed by Stripe, which collects your card and receipt email under Stripe's privacy policy. Rendezvous receives no card details. We store an opaque Stripe customer and subscription identifier against your participant so the plan can be applied and cancelled; that link between a payment identity and a pseudonymous participant is used only for billing and is never shown to other participants.

Last updated September 5, 2026.