Current website practices

Privacy, explained in the same language as the product.

How the Relay website handles waitlist emails, reservation traffic, limited attribution data, retention, and deletion requests.

Last updated: August 16, 2026

Scope of this notice

This notice covers the public Relay website and its current waitlist and reservation flows. Relay is still in development. The marketing website does not receive the clipboard content, files, task evidence, or workspace data shown in product illustrations.

Data the website handles

  • Waitlist: the email address you submit, a normalized copy used to prevent duplicates, the form location, and submission time.
  • Limited attribution: the landing path, a coarse referrer category, and approved UTM source, medium, campaign, and content values.
  • Reservation: Relay records an anonymous Stripe button click. Stripe handles the checkout and payment details on its own site.
  • Hosting: infrastructure providers may process standard request and security data needed to serve and protect the website.

Relay does not use advertising cookies, cross-site tracking, session replay, or fingerprinting in this measurement flow. Raw search queries and payment card details are not stored in Relay's waitlist or conversion tables.

Why the data is used

Waitlist data is used to prevent duplicate entries and, when updates begin, to send Relay product and invitation messages. Limited attribution data is used to understand which landing pages and campaigns lead to a waitlist entry or a Stripe checkout click.

Storage, providers, and retention

Waitlist records are stored in the database attached to Relay's Sites deployment. Website hosting and storage providers operate the infrastructure. Stripe separately processes payment and checkout information under its own privacy notice. Providers may process data where they operate their services.

Waitlist email records remain while the list is active unless the matching email is removed. Anonymous conversion events use a 90-day rolling retention window. Expired events are removed when the next conversion event is written, so a dormant database may contain expired rows until another event occurs.

Remove your waitlist email

The self-service removal form on this page deletes a matching waitlist entry immediately. It does not send a confirmation email and it does not affect a separate Stripe transaction.

Contact and privacy requests

For privacy questions, waitlist removal help, or reservation support, email support@relay-handoff.com. Relay is the product name used for this development-stage project and is not represented as an incorporated organization in structured data.