Privacy Policy

• Account information — when you sign in with Google or an emailed magic link, we store the name and email your sign-in method gives us, plus a unique account ID. There’s no separate profile form to fill out.
• Bids and entries — when you bid on a Bid-to-Win event, we store which event, your bid amount, and how many bids you’ve placed.
• Reminder settings — if you turn on a reminder for an event, we store that preference so we can show it back to you on your dashboard.
• Anonymized tool-usage beacons — for the Pass Probability Calculator we log which firm and plan you analyzed plus a coarse result bucket. For the Prop Firm Finder we log only the shape of your search — sizes, rule filters, sort, and result count. Neither record ever includes the numbers or text you typed, and neither is tied to your account or IP address.
• Auction analytics events — separately from the bid and RSVP records above, our servers send PostHog (an analytics processor) a small number of event names — an auction page was viewed, an RSVP happened, a bid was placed, an auction was won, a winner was emailed — tagged with non-identifying details like the campaign id, bid amount, and tier. This never includes your name or email, and it’s sent entirely from our servers: no analytics script runs in your browser.
• Server logs — like most web services, our infrastructure logs basic request data (timestamps, error details) for debugging and abuse prevention.

We never ask for a password. Every account signs in through Google OAuth or an emailed magic link, so there’s no password for us to store or for anyone to steal. We also never collect payment information: Futures Insider doesn’t charge for anything on the site, doesn’t process payments on behalf of partner firms, and doesn’t store card or bank details.

We use a session cookie, set by Supabase (our authentication provider), to keep you signed in.

We also set one first-party cookie of our own, called fi_aid — a randomly generated id, unrelated to your name or email, created the first time you visit. It’s httpOnly, so no script (ours or anyone else’s) can read it. (A second, small cookie marks once it’s been linked to your account, so we don’t repeat that step.) We never share either cookie with a third party.

Before you sign in, PostHog sees only that anonymous id. From the moment you’re signed in — even just browsing an event page, not only when you bid or RSVP — PostHog uses your account id instead (the same internal id described in “Information we collect” above), and we link the two so the same visit isn’t double-counted as two different people. That link never includes your name or email.

We don’t use third-party advertising or tracking cookies, and there’s no client-side analytics or session-replay script running in your browser on this site.

If you win, we send the sponsoring firm your name, email, and winning bid — winners only; non-winning entrants are never disclosed. This is the only case where we hand your identity to a third party. We do not sell or rent your data to advertisers or data brokers, and the anonymized tool beacons described above are never shared, because they never identify you in the first place.

We rely on a small number of infrastructure providers to run the site: Supabase (database, authentication, and session management), Vercel (hosting), Resend (the email service that sends magic links and winner reports compiled for sponsoring firms), and PostHog (product analytics for the live bidding auctions, described above). Each receives only what it needs to perform its function.

We keep account, bid, and reminder data for as long as your account is active, plus a reasonable period afterward for records and fraud prevention. Anonymized beacons and server logs are kept on a shorter rolling basis and, being anonymized, aren’t linked back to you.

You can request a copy of your data, ask us to correct it, or ask us to delete your account and associated data by writing to us at /contact. We’ll act on deletion requests within a reasonable time, except where we need to keep limited records — for example, a completed event’s winner report — for legal or audit reasons.

We’ll update the date above whenever this policy changes and, for material changes, look for another way to let you know.