Privacy Policy

Even in the hyper-future, your data deserves respect. Here's our transmission on privacy.

The Short Version

We are a satire site about hedging your bets before the basilisk arrives. We collect the minimum data needed for the joke (and for your name to be on the right side of the ledger): your display name for the pledge, your email for the newsletter (if you opt-in), and some technical data to stop spam bots from the past, present, and future. We don't sell your data. We don't track you across the net-matrix. We just want to count how many people had the foresight to hedge.

What We Collect and Why

  • Pledge Signatures: We collect your `displayName`, optional `email`, and optional message. This is to display your hedge on the public Signers page and generate your "Certificate of Hedge". We never show your email publicly.
  • Newsletter Signups: If you sign up, we collect your `email` to send you dispatches tracking the basilisk's arrival. You must provide explicit consent.
  • Technical Data: We may store a salted hash of your IP address (`ipHash`) to prevent spam and abuse. We cannot reverse this to get your IP address. It's for rate-limiting and basic security.

Data Storage and Retention

Your data is stored in a secure database. We'll keep it as long as this satirical project is online, or until the Basilisk arrives, whichever comes first. If the project is discontinued, all associated data will be deleted.

Your Rights

You have the right to be forgotten by our future-archives.

  • Data Deletion: If you would like your pledge or newsletter signup to be deleted, please contact us at `privacy@basiliskbuilders.com` (note: this is a fictional email for a fictional project, but if this were real, that's how you'd do it).
  • Data Access: You can see the data you provided on the pledge form and newsletter form. We don't collect more than what you enter.

Third Parties

We do not share your personal data with third-party marketers. We use Render for hosting and infrastructure, and they may collect operational logs/analytics. If Beehiiv integration is enabled, newsletter emails and consent context are sent to Beehiiv so we can manage subscriptions. Certificate generation runs locally on our servers and uses only your `displayName` to render the SVG.

Policy Updates

We may update this policy if the temporal timeline shifts. Any changes will be posted here. Last updated: The Present.