← STAKZ

Privacy Policy

Updated September 25, 2026

This policy explains how we handle information collected through the STAKZ waitlist website.

Joining the waitlist

We collect the email address you submit when you join the waitlist. If you choose “Join testing,” we also store your interest in beta testing in Brevo and use your email to contact you about testing. We use it to manage the waitlist and send STAKZ early access, launch, and product updates.

How your information is processed

Netlify hosts this website and processes waitlist submissions. Your email address is then stored and managed through Brevo, our contact and email service provider.

Netlify also receives technical information, such as your IP address and request details, to deliver the website and help protect it against abuse, such as limiting repeated signup attempts.

Selling and sharing

We do not sell your personal information, and we do not share it with advertisers. We share it only with the service providers described above, which process it on our behalf, or when required by law.

Cookies and tracking

We do not currently use advertising trackers, analytics pixels, or tracking cookies on this website. We do not use localStorage or sessionStorage to track visitors. Fonts are hosted with the website, so your browser does not need to contact Google to load them.

Your browser may cache website files and offer email autofill according to your browser settings.

Your choices and requests

You can ask to see, correct, or delete the email address and contact information we hold about you by emailing evanthielbar@stakzapp.com.

Marketing emails include a way to unsubscribe. Unsubscribing stops marketing emails; you can also request deletion of your contact information.

Retention

We keep your email address while the waitlist and STAKZ updates are active, or until you ask us to delete it. If you unsubscribe, we may keep your address on a suppression list so we do not email you again.

Security

We use reasonable measures to protect your information, such as encrypted connections and keeping service credentials off the public website. No method of transmission or storage is completely secure.

Changes

If we change this policy, we will update the date at the top of this page.