1. Information We Collect

When you join our waitlist or contact us, we collect:

• Name and email address
• Role, institution, or organization (where provided)
• Your stated reason for interest in the Service
• Messages you send via the contact form
• Verification metadata for one-time email codes (for example: code issuance time, expiry, and failed-attempt counters)

We also collect standard server-side data such as IP addresses, browser type, and pages visited via Vercel's analytics infrastructure.

2. How We Use Your Information

We use the information we collect to:

• Manage and communicate about waitlist access
• Respond to contact form inquiries
• Improve the Service and understand our user base
• Send product updates and launch announcements (you may opt out at any time)
• Operate and enforce email verification controls to prevent abuse and unauthorized submissions

3. Data Storage

Waitlist and contact data is stored in a Postgres database hosted on Neon and synced to Google Sheets. We also use a managed Redis cache (hosted on Upstash) to speed up duplicate-email checks and to enforce rate limits on form submissions and verification attempts. Our infrastructure runs on AWS. All of the above are hosted in the United States. We take reasonable technical measures to protect your data, but no system is completely secure.

As part of waitlist checks, we may synchronize records across systems during request processing and temporarily hold SHA-256 email hashes in the Redis cache so the client can perform local duplicate checks without exposing plaintext email addresses. These cached hashes expire automatically after a short period.

Pending verification records (for waitlist signup, contact submissions, and unsubscribe requests) are stored server-side only as needed to complete verification and are removed after successful verification or expiration.

4. Third-Party Services

We use the following third-party services which may process your data:

• Resend — transactional email delivery
• Google Sheets / Google Cloud — waitlist storage and sync
• Neon — Postgres database hosting
• Upstash — managed Redis cache for dedup checks and rate limiting
• AWS — server infrastructure
• Cloudflare Turnstile — bot protection on forms
• Vercel — hosting and analytics

Each third party has its own privacy policy governing their data handling.

5. Data Sharing

We do not sell or rent your personal data to any third party. We do not share your information with advertisers. We may disclose data if required by law or to protect our legal rights.

6. Your Rights

You may request deletion of your personal data at any time by contacting us, or unsubscribe from the waitlist yourself using the unsubscribe link included in our emails. Unsubscribing follows the same two-step email verification flow as signup: you request removal, receive a 6-digit code by email, and confirm the code to complete removal. We will remove your information from our systems within a reasonable time frame. Note that removing your data will also remove your place on the waitlist.

7. Cookies

We use functional cookies to optimize waitlist synchronization:

• waitlistSynced — set for 1 hour per browser to throttle background sync operations. This ensures our system resyncs waitlist data with our upstream database at most once per hour per browser, reducing unnecessary network traffic while keeping data fresh. This cookie is functional only and contains no personal data.

Browser storage is also used for functional purposes: sessionStorage (to gate the first-visit demo experience so it only plays once per session). This client-side storage is functional only and is not used for advertising.

We do not use tracking or advertising cookies.

8. Children's Privacy

The Service is not directed to children under 13. We do not knowingly collect personal information from anyone under 13. If you believe we have inadvertently collected such data, please contact us immediately.

9. Changes to This Policy

We may update this Privacy Policy from time to time. We will post the new policy on this page with an updated date. Your continued use of the Service after changes constitutes acceptance.

10. Contact

For privacy-related requests or questions, please reach out via the contact page.