Privacy, plainly.
This page covers the Tuck beta waitlist website. It does not describe data processing inside the Mac app.
Last updated November 1, 2026.
What we collect
When you join, we store your email address, signup time, the signup source (“website-beta”), your consent, its wording version and consent time, subscription status, and invitation status. If you unsubscribe, we record that time. Invitation records include the email subject and message, send attempt time, provider message ID, and any send errors.
To limit abuse, we keep a keyed hash of a network identifier (IP address when the host supplies a trusted one), email address, or shared rate-limit bucket, with an attempt count and expiry. We don’t store raw IP addresses in the waitlist database. Our hosting provider may separately process IP addresses and request logs to operate and protect the service.
Why we use it
We use your email, with your consent, to invite you to the free Tuck beta and send occasional beta updates. Joining does not send an automatic welcome or invitation. We don’t sell the waitlist or use it to advertise a suite of other products.
Where it is stored
Waitlist records are stored in a hosted Postgres database on Neon. The website is hosted by Vercel, which processes requests to serve and protect the site.
Email delivery is not enabled yet. When invitations are enabled, they will be sent through Resend, which receives the recipient address and email contents when the founder sends a message. These providers may process data outside your country.
No third-party analytics, ad trackers, remote fonts, or tracking pixels are included in this website. Invitation content is sent as plain text.
Your choices
You can unsubscribe using the link shown after a new signup or the link in any invitation. Unsubscribing suppresses future beta emails, including invitations. Signing up again does not reverse that choice. To rejoin after unsubscribing, contact the founder.
We retain waitlist records while operating the beta. A minimal suppression record is retained to honor unsubscribes. You may ask the founder to access, correct, or delete your data; deletion requests will be handled along with your preference not to receive further email.
Cookies and security
Visitors do not need a cookie to join. The private founder area uses an HTTP-only session cookie for sign-in, expiring after eight hours. Admin routes require server-side authorization. No subscriber list or provider credentials are sent to public pages.