The verification email proves booking linkage through the booking email already on file. It must be warm and safe, but never leak booking-private details.
Delivery Rule
Verification emails go only to the booking email already on file.
Guest-entered email is never trusted as the destination.
The guest may supply information that helps find a candidate booking, but the delivery destination is owned by the booking record.
Privacy Boundary
The verification email must not expose:
The guest-facing chat must not expose:
Current Implementation
Current email implementation:
This is current live-development implementation. Deliverability, rate limiting, replay defense, and production consent copy remain hardening work.
Tone Contract
The email should feel:
It should not feel:
The guest should understand that Lucia is helping verify the connection without seeing private booking information.
See Also
