Privacy policy

• 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.

• Your email, when you sign in: with a link or code Chorus emails you, or with Google. You need an account to propose or vote.
• Your account: your username, the day you joined, and your confirmation that you're 18 or older. If you sign in with Google, Google also shares your name and profile picture; Supabase keeps them with your sign-in, and Chorus doesn't use or show them.
• 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.
• 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 position, whether you joined by proposing, voting, or making an account, when Chorus sent your welcome email, and whether you unsubscribed.
• 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.

• 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 link and code when you ask for one, one welcome email when you join the waitlist (with your place on it and the board's top proposals), and news about your proposals (live, in review, waiting for your confirmation, or not listed) with your place on the waitlist. 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 keep Chorus safe: bot checks, automated and human moderation, and bans.
• 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.

• Live proposals, with “Proposed by @username.” Proposals from before accounts were required show no name.
• 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.
• How many votes each proposal has. Who voted for what is never shown.

Proposals that aren't live (in review, waiting for your confirmation, or not listed) are seen only by you, by email, and by Chorus's admins. Your email is never shown to anyone.

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.auth (browser storage): whether you're signed in, with your username, so your other open tabs catch up.

The bot check runs in a frame from Cloudflare, under Cloudflare's own policy. Analytics stores nothing on your device.

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 a proposal submitted, a vote cast, or a comment posted. 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.

These providers handle data for Chorus, only to run it:

• Supabase: the database and sign-in, including the sign-in emails.
• Vercel: hosting.
• Resend: sends Chorus's emails, including sign-in links and codes.
• Google: only if you choose “Continue with Google.” Google confirms who you are and shares your email, name, and profile picture with Chorus's sign-in provider, Supabase. Google's own privacy policy covers your Google account.
• 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.
• 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.

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.

• 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.

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.

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.

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.

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.