What the waitlist form collects
The form asks for your email address. The submission includes the page where you signed up and may include a request identifier. Our form and email services process the request and its delivery metadata. The form does not ask for your name, a password or payment information.
Existing waitlist records
If you joined through an earlier version of the site, your record may also contain finish and quantity preferences, first-seen and updated timestamps, a source page, a preference summary and notes. Joining through this email-only form does not change those earlier preferences.
How we use it
We use your email to send Relay development and availability updates and to answer your messages. We do not sell, rent or trade your email address.
Services involved
Web3Forms handles form submissions and forwards them to our inbox. Google email and spreadsheet services hold correspondence and existing waitlist records. Our website host receives ordinary request metadata, such as IP address, browser information and the requested page, to deliver the site and manage abuse.
Website measurement
We use Vercel Web Analytics to measure visits, campaign sources and interactions such as waitlist attempts and accepted requests. These events contain no email address or form contents. We use no advertising pixels or cross-site tracking IDs. Our analytics code does not load when your browser sends Do Not Track or Global Privacy Control. Analytics may miss visits or submissions when blocked; an accepted request is not a purchase or a verified email subscription.
Access, correction and removal
Email kavin@relay5g.com to ask what we hold, correct or export your information, leave the list, or request deletion. You do not need to cite a law or create an account.
Responsibility and contact
Sovereign ATX LLC is responsible for Relay’s waitlist data. Send privacy questions and requests to kavin@relay5g.com.
Cookies and analytics
Vercel Web Analytics uses no analytics cookies. We do not store email addresses or persistent visitor IDs in browser storage for analytics. The host may use cookies for private-preview access and processes the request data described above.