Privacy policy
Last updated October 14, 2026
On Chorus you propose prediction markets, vote on them, and talk about them. It's a waitlist: no trading happens here and no money changes hands. This policy says what Chorus collects, why, who helps run the site, and what you can do about it.
The short version
- Chorus collects your email, what you post, and your votes, to run the site and email you about your proposals.
- Your email is never public, and never goes to the AI model or to analytics.
- Analytics is anonymous and cookieless: it's never linked to your account, and nothing is stored on your device for it.
- Chorus doesn't sell your information or use it for advertising.
- To see, fix, or delete your data, write to hello@tradechorus.com.
What Chorus collects
- Your email, when you sign in: with a 6-digit code Chorus emails you. You need an account to propose or vote.
- Your account: your username, the day you joined, your confirmation that you're 18 or older, and, if you were one of the first 1,000 accounts, your Founding Proposer number (your place in sign-up order).
- What you post: proposals (the question, dates, resolution source and criteria, and outcomes), comments and replies with your stance if you pick one, likes, and reports.
- Your votes: which proposals you voted for, and when.
- Your record: when a market you made a call on resolves, what your call was and whether it happened. Only a call you made before the outcome was known counts.
- Which creator brought you: if you made your account through a creator's join link, which creator.
- X suggestions: when Chorus's admins write up a market from a public post on X, the poster's X handle and the link to the post, and a private link that lets them claim it.
- Reserved usernames: famous names, brands, and Chorus's own names need an admin's approval. If you get one, Chorus keeps the username, your sign-in email, a note on how you showed it's yours, and who approved it.
- Creator Board requests: if you ask for a Creator Board at /creators, your name, main platform, handle or channel link, rough audience size, the line about what your audience is watching, your email, and your account if you were signed in. If Chorus approves it, a verification code for your bio and when you said you added it. When Chorus verifies you, a record of how (the code in your bio, or a message or post from your account, with a note on where) and who at Chorus checked.
- Images Chorus's admins upload: event covers and creator avatars.
- Your calls: on each proposal, what you think will happen (Yes, No, or one outcome; on a date ladder, Yes or No on each deadline), if you make one, and each change to it with its time, so the call you had when a market's outcome became known is the one that counts toward your record.
- Your thesis and subtitle: if you add them to your own proposal, the lines you wrote. Like a comment, each is checked against the community rules first, and the check is kept. And the event's start time, if you set one.
- Your agreement: each time you agree to the Terms and this policy (when you make your account, or, before accounts were required, when you proposed or first voted), when you agreed and where.
- Your place on the waitlist: your place in line, whether you joined by proposing, voting, or making an account, when Chorus sent your welcome email, and whether you unsubscribed.
- Your watchlist: the categories you pick to watch, and when you added each.
- Your call streak: each day (UTC) you made at least one call, to count your streak.
- Your email settings: which kinds of emails you want (milestones, results, replies, the weekly digest), and a record of each of those emails sent to you (its kind and the day), to send each once and at most one a day.
- Days you use Chorus: each day (UTC) you were signed in on Chorus, to measure how many new members come back. Not what you did or looked at.
- Referrals: when your account is made with someone's invite link, who invited you and when your first vote, call, or proposal made it count; if the person who invited you was a Founding Proposer, that you became one through them, and when; and a log of every referral attempt, including the ones that were blocked (self-referrals, unknown links, and too many in a day), to keep it fair.
- Moderation records: the result of each automated check on a proposal, comment, or username, with the text that was checked; the checks for duplicate proposals; the decisions of Chorus's admins; and bans with their reasons.
- A daily count of the proposals each account sends, for the limit of 5 a day.
- Your IP address, which Chorus doesn't store. It goes to Cloudflare for the bot check and to PostHog for anonymous visitor counts (see Analytics), and Chorus's hosting provider handles it to serve the site.
How Chorus uses it
- To run Chorus: save proposals and votes, show the board and profiles, keep you signed in, catch duplicate proposals, and enforce the limits and rules.
- To email you: a sign-in code when you ask for one, one welcome email when you join the waitlist (with your place on it, your invite link, and the board's top proposals), and news about your proposals (live, with the final wording if Chorus changed it; in review; not listed; or resolved) with your place on the waitlist. Emails you can turn off in your email settings, at most one a day: when your market passes 10, 50, or 100 votes; when a market you made a call on resolves, with the result and whether you called it right; and when someone replies to your comment, with their reply. A weekly Most Wanted digest is built but isn't sent yet; it will be marketing email, with Chorus's postal address, and you can turn it off. If you ask for a Creator Board, emails about your request: that it arrived, your verification code if it's approved, and when you're verified. These are replies to your request, so they have no unsubscribe link. While you're on the waitlist, Chorus may also email you about its launch. Every email except a sign-in email has an unsubscribe link.
- To run the waitlist: your spot is your place in line, moved up for each friend who joins with your link and then votes, makes a call, or proposes. A friend who joins with a Founding Proposer's link and then makes a call or votes becomes a Founding Proposer too. Rewards are status only: your spot, badges, and founding status, never cash, prizes, or anything with money value.
- To keep Chorus safe: bot checks, automated and human moderation, and bans, and checking that a creator board belongs to the creator it names.
- To see how Chorus is used, with anonymous analytics.
Chorus doesn't sell your personal information, share it for advertising, or use it to target ads.
What other people can see
- Live proposals, with “Proposed by @username.” Proposals from before accounts were required show no name. Each proposal's share images show its question, the proposer's username, its vote count, and the crowd sentiment.
- Your “Founding Proposer #N” badge, if you have one, on your profile and next to your name. The official @chorus account shows an “Official” badge instead. If you became a Founding Proposer through someone's invite link, your badge reads “Founding Proposer, invited by @username,” with their username.
- A call streak badge on your profile once you make a call 3, 7, or 30 days in a row: only the badge, never your calls. Your current streak, your watchlist, and your email settings are shown only to you.
- The Daily Call: one live proposal featured each day, picked by Chorus's admins or by its votes.
- The crowd sentiment on each proposal, once 10 people make a call: the share who think each answer will happen, each person counted once by their latest call or comment stance. Once a market closes (its outcome is known), it shows what the crowd thought before then. Never what any one person thinks.
- The crowd sentiment over time, as a chart on each proposal and its card once 10 people make a call. Chorus saves only the crowd's totals (how many calls each way, at each change), never who made them. Open pages update as things change (see “Live updates” below); what they get is the same for everyone and says nothing about who's asking.
- The proposer's thesis and subtitle, if they add them, under the proposal's title, and the event's start time.
- Updates: what Chorus found about a proposal (such as a team eliminated or a candidate who withdrew), from official league data (such as MLB's public stats, which Chorus reads without sending anything about you) or Chorus's fact check, each a one-line summary in Chorus's own words with a link to its source, and the options marked Out (only from official league data, or by Chorus's team).
- Most Wanted: each week's 10 proposals that gained the most votes, with their questions and vote counts, saved every Monday and kept in a public archive.
- Your profile: your username, the day you joined, and your live proposals with their votes.
- Your comments and replies, with your username, your stance if you picked one, and their likes.
- A “Recruiter” badge on your profile once 3, 10, or 25 friends you invited count: only the tier, never the number or who they are. Your spot on the waitlist and your invite link are shown only to you.
- For a resolved market, how the crowd called it: the share of people who took each side, each counted once. Never what any one person thought.
- How many votes each proposal has. Who voted for what is never shown.
- Your record of calls on resolved markets is shown only to you, on your own profile. No one else's record is ever shown, and yours is never public.
- Event boards: each event's name, date, cover, and the live proposals attached to it with their votes and crowd sentiment.
- Creator boards, once the creator is verified: the creator's name, a link to the account they verified with, avatar, Chorus username if linked, and a “Verified creator” badge, with the live proposals of people who joined through their link and their own. Which creator brought you isn't shown anywhere else. A Creator Board request, its code, and how a creator was verified are never public; only the person with the request's private link sees its status and code.
- A market written up from a post on X shows “Suggested by @handle on X” with a link to the post, until the person it credits claims it; then it shows their username.
- “Too cursed to list”: Chorus may share the question of a rejected proposal with that stamp, never who proposed it, and only for unclear wording or an outcome the proposer or a small group controls.
Proposals that aren't live (in review or not listed) are seen only by you, by email and, for ones in review, on your own profile, and by Chorus's admins, along with any rewording the screener suggests. Your email is never shown to anyone.
Cookies and browser storage
Chorus uses only what it needs to work. There are no advertising or tracking cookies.
sb-…-auth-token(cookies from Supabase): keep you signed in. Signing out removes them. While a sign-in is in progress, a short-lived one (ending in-code-verifier) makes sure it finishes in the browser that started it.chorus_admin(cookie, 7 days): only for Chorus's admins, on admin pages.chorus.propose-draft(browser storage, up to a day): the proposal you were writing when you went to sign in, so it's still here when you're back. It's removed once you submit or discard it.chorus.pending-vote(browser storage, up to an hour): the proposal you tapped upvote on before signing in, so the vote counts once you're signed in. It's removed once it's used.chorus.pending-lean(browser storage, up to an hour): what you tapped on one of the top proposals on the home page (Yes, No, or an outcome) before joining, so it counts once you're in. It's removed once it's used.chorus.creator(browser storage, up to 30 days): the creator whose join link brought you here, so your account counts for their board when you make it. It's removed once you do. Chorus also takes it out of the page's address.chorus.ref(browser storage, up to 30 days): the username in the invite link that brought you here, so it counts when you make an account. It's removed once you do. Chorus also takes it out of the page's address.chorus.auth(browser storage): whether you're signed in, with your username, so your other open tabs catch up.chorus.join-bar(browser storage): when the small “Join the chorus” bar at the bottom was shown and how many times you closed it, so it shows at most twice a week and never after you close it twice.chorus.arrival(session storage, until you close the tab): the first page of your visit and whether you came from a shared link, a search engine, or straight in, so a proposal you opened from a shared link leads with “Make your call.”chorus.milestones-seen(browser storage): for your own proposals, the last vote milestone whose share card you closed, so each card shows once.chorus.graduations-seen(browser storage): for your own proposals, the ones whose Graduated moment you've already seen, so it plays once.
The bot check runs in a frame from Cloudflare, under Cloudflare's own policy. Analytics stores nothing on your device, and neither do live updates.
Live updates
Open pages keep themselves up to date without a refresh:
- Once a page has loaded, it opens a connection to Supabase's realtime service, which tells it that something public changed: a proposal went live, got votes or calls, closed, or resolved, or a discussion changed. The notice carries no data beyond the public proposal it's about; the page then asks Chorus for what changed, the same answer anyone gets. The connection uses the site's public key, not your account, so it says nothing about who you are; Supabase sees your IP address and browser, as with any connection. Your calls stay private: no notice says who did anything. Without the connection, open pages ask Chorus every 15 seconds instead.
- Your own panels on your profile (your proposals in review, your record, your streak, and your invite spot) update from Chorus directly, through your signed-in session, never through the realtime connection.
- Every couple of minutes, an open page asks Chorus which version of the site is live, without cookies. When a new one is out, the next page you open loads it; if you're in the middle of something, a small “New version available” button lets you choose when.
Analytics
Chorus uses PostHog to count visits and see which features get used. It's anonymous and cookieless:
- Nothing is stored on your device for it, which is why there's no cookie banner.
- It's never linked to your account. PostHog never gets your email, your username, or an account id.
- PostHog counts visitors with a code it makes from your IP address, your browser, and a value that changes every day, so even the same person counts as new each day.
- Chorus sends the pages you visit, with sign-in codes, tokens, and usernames taken out of the address, and what happened, such as where the visit came from (a shared link, a search engine, or straight in, never the address), joining started and finished (and what started it, like a vote or a call), the steps after joining, a Daily Call made, an invite shared or a friend counted, a proposal submitted, a vote cast, a call made, a comment posted, a share (only whether it was the share sheet or a copied link), or a share image saved (only its size). Never what you wrote.
- It goes through Chorus's own site first, which removes your cookies before passing it to PostHog. Admin pages aren't tracked.
Chorus doesn't track you across other sites, so it works the same whether or not your browser sends a “Do Not Track” signal.
Who helps run Chorus
These providers handle data for Chorus, only to run it:
- Supabase: the database and sign-in, including the sign-in emails, and the realtime connection open pages use for live updates.
- Vercel: hosting.
- Resend: sends Chorus's emails, including sign-in codes.
- Cloudflare Turnstile: the bot check when you propose, or ask for a sign-in email. It gets your IP address and signals from your browser.
- Anthropic: its AI model checks proposals, comments, and usernames against Chorus's rules, and compares new proposals with existing ones to catch duplicates. It gets that text (for a comment, also the market it's on and a few of your recent comments), never your email. It also fact-checks a proposal when it's submitted, shortly after its scheduled event, and at its close date, using Anthropic's web search, which sends search queries based on the proposal's question and outcomes (never anything about you) to a search provider.
- PostHog: anonymous analytics, as described above.
They may handle data in the United States and other countries. Chorus also shares information when the law requires it, or to protect Chorus and the people who use it. If Chorus is sold or merges with another company, your information would go with it, still under this policy.
How long Chorus keeps it
Chorus keeps your information while it runs, until you ask for it to be deleted. Unsubscribing stops the emails but keeps your waitlist entry, marked as unsubscribed. Chorus may keep records of bans and removed content for as long as it needs them to keep the site safe.
Your choices
- Unsubscribe with the link in any email.
- See, correct, or delete your information, or close your account, by writing to hello@tradechorus.com. You can't delete proposals or comments on the site yet; write to Chorus and it will be done for you.
- Depending on where you live, such as California or the EU, you may have more rights over your data. Write to Chorus to use them. Chorus won't treat you differently for it.
Age
Chorus is only for people 18 and older. Chorus doesn't knowingly collect information from anyone younger. If Chorus learns that someone under 18 signed up, it deletes their account and information.
Security
Emails, votes, the waitlist, and moderation records can only be read by Chorus's server, never by other visitors. Sign-in and admin cookies are signed and hidden from scripts on the page. No system is perfectly secure, but Chorus works to protect your information.
Changes
If Chorus changes this policy, the new version will be posted here with a new date. For a significant change, Chorus will also email the people on the waitlist.
Contact
Chorus is operated by Tyler DeGuzman, an individual based in California.
Questions or requests: hello@tradechorus.com. The rules for using Chorus are in the terms.