Skip to content
CallTheTwist

Privacy

Privacy

What we collect, why, for how long, who else handles it, and what you can do about it.

Version 2026-11-xx

[[LEGAL REVIEW]] set COMPANY_LEGAL_NAME runs this website and the CallTheTwist accounts on Instagram, Facebook, YouTube and TikTok. Our address is [[LEGAL REVIEW]] set COMPANY_POSTAL_ADDRESS. For anything about your data, write to [[LEGAL REVIEW]] set PRIVACY_CONTACT_EMAIL.

This page says what we collect, why, for how long, who else handles it and what you can do about it. [[LEGAL REVIEW]]

  • Public comments. When you comment on our posts we read your comment, the handle you comment under, the id the platform gives the account, the time, and the likes. We use them to count votes on every platform. We read only what the platform shows publicly on our own posts.
  • Your email address, when you sign in (we send a one-time code), sign up for the newsletter or send us a cameo application.
  • Linked handles. If you link a platform account to your account here, by commenting a one-time code from it, we keep that link.
  • Payments. Payments go through Stripe. We keep the order: what you bought, the amount, the currency, the date and a Stripe payment reference. We never see or keep a card number.
  • What you give us to show: a founder display name for the case board, and the details of a Business Cameo application.
  • Analytics, only if you accept them on the banner: which pages are visited and a few named events (see Analytics below).
  • Technical data. Our host and our bot check see the address of your device (IP address) and the browser details every website sees.
  • To run your account and what you buy (sign-in, your Founder's Pass, a boost, a cameo): contract. [[LEGAL REVIEW]]
  • To count the vote from public comments and keep the League honest, and to keep the site safe from bots and fraud: our legitimate interest. You can object (see Your rights). [[LEGAL REVIEW]]
  • For analytics and for the newsletter: your consent. You can say no to analytics on the banner and take the answer back at any time, and every newsletter email has an unsubscribe link. [[LEGAL REVIEW]]
  • To keep the records of orders that tax and accounting law require: legal obligation. [[LEGAL REVIEW]]

A voter file is a page about one person: how many parts they voted in, the hidden options they found, their streak. It is built from public comments.

  • A file stays private until you claim it. Until then, the League shows you only as an anonymous label such as Agent 3F9A21, made from a secret code nobody can turn back into a handle.
  • You claim a file by linking your account: you ask for a one-time code and comment it from the account. Nobody else can comment from your account, so nobody else can claim your file.
  • Even after you claim it, your file is public only if you switch that on. You can switch it off or unlink the account at any time, and your handle leaves the League and the search at once.
  • One-time claim codes: deleted 30 days after they expire or are used.
  • Newsletter sign-ups that were never confirmed: deleted 7 days after the confirmation link expires (the link lives 48 hours).
  • Checkouts that were started and never paid: deleted 30 days after they were made.
  • Orders: kept for as long as tax and accounting law require, with the link to you removed if you delete your account. [[LEGAL REVIEW]]
  • Votes and comments: counted once, and kept as part of the history of each part. If you ask us to forget you, your handle and the text of your comments are blanked in our comment records and the votes stay as counts, so that a result that was announced never changes. A vote stays attached to the id the platform gives your account, and some copies are cleaned by hand; how to delete your data lists what is blanked, what is cleaned by hand and what stays. [[LEGAL REVIEW]]
  • Raw copies of comments as Instagram or Facebook delivered them, the summary of what commenters said in each part (which lists by handle the commenters whose theories came true) and the files of labelled comments we use to teach our comment-reading model: kept as part of the history of the show, and read only by our team. They are not changed when you are forgotten; we clean the ones that hold your handle or your words by hand when we answer your request. [[LEGAL REVIEW]]
  • Your account and everything tied to it: until you delete it (see Your rights). Analytics events are kept by PostHog for the period set in our PostHog project. [[LEGAL REVIEW]]
  • The address of someone who unsubscribed stays on a list of addresses we must not email, so that it is not mailed again by mistake.
  • Access and a copy: sign in and download your data as a file.
  • Deletion: sign in and delete your account. If you only commented and have no account, see how to delete your data.
  • Correction, objection and restriction: write to [[LEGAL REVIEW]] set PRIVACY_CONTACT_EMAIL.
  • Withdraw consent: switch analytics off on the banner (the "Analytics choices" link in the footer) and unsubscribe from the newsletter from any email. Withdrawing does not change what we did before.
  • Complain to your data protection authority if you think we have handled your data wrongly. [[LEGAL REVIEW]]

We answer within 30 days. [[LEGAL REVIEW]]

We use PostHog to count visits. If you accept on the banner, it remembers your browser with a cookie. If you reject, we still count the visit, but nothing is stored on your device. We do not record sessions or what you click beyond a few named events, we never put your email address or handle into an event, and we collect nothing on the pages our team uses to run the show. PostHog does receive the address of your device (IP address).

We use these services. Each one handles your data only to do the job named here.

  • Supabase: the database, the email-code sign-in and the live tally. It receives your email address, account settings, linked handles, votes, orders and the public comments we count.
  • Vercel: hosts this website. It receives the address of your device (IP address) and the pages you request, in server logs.
  • Stripe: takes payments on its own checkout page. It receives your payment details, which you type on Stripe and we never see, and the receipt email; we get back the order, the amount and a payment reference.
  • Resend: sends our emails: sign-in codes, order and founder notes, and the newsletter. It receives your email address and the message.
  • PostHog: counts visits and a few named events, with the analytics choice you make on the banner. It receives the page address without its query string, the event names, a random browser id (only if you accept) and your IP address.
  • Cloudflare (R2, Turnstile): R2 stores the images and videos of the show; Turnstile checks that a person, not a script, is using the sign-in and the forms. It receives for R2, the files we upload; for Turnstile, your IP address and browser signals when you use a form.
  • Anthropic (comment and moderation processing): reads public comments to understand votes and theories, labels comments to teach our own comment-reading model, writes the summary of what commenters said that our writers read, and gives a first opinion on founder display names and cameo applications before a person decides. It receives public comment text together with the commenter handle, the display names founders choose and the text of cameo applications; never your email address.
  • TypeSafe AI (Jev): a language model that reads each public comment and says whether it is a vote, and for which option, before the vote is counted. It receives the text of public comments, with no handle and no account id.
  • Modal (Laya): runs Laya, our own comment-reading model, which decides whether a comment is a vote once we have put it to work, and trains it on comments that people or models have labelled. It receives the text of public comments, with no handle and no account id, the label each one was given and the options of the part it was made on.
  • Meta: Instagram and Facebook, where the show is posted and where you comment. It receives the public comments on our posts, with the commenter handle and the id Meta gives the account.
  • Google / YouTube: YouTube, where the show is posted and where you comment. It receives the public comments on our posts, with the commenter handle and the id YouTube gives the channel.
  • TikTok via Upload-Post: TikTok, where the show is posted and where you comment; Upload-Post is the service we use to post to and read from TikTok. It receives the public comments on our posts, with the commenter handle and the id TikTok gives the account.
  • Zernio: the other service we may use, instead of Upload-Post, to post to and read from TikTok. It receives the same public TikTok comments and handles.
  • Trigger.dev: runs our background jobs: reading comments, counting votes, making the show, sending emails. It receives whatever those jobs handle while they run: public comments, handles and email addresses.

Several of these services are based in, or run from, countries outside yours, including the United States. When your data is sent there we rely on the safeguards the law allows, such as standard contractual clauses. [[LEGAL REVIEW]]

An account on this site is for people aged 13 or older, and a purchase is for people aged 18 or older. We do not knowingly keep an account of anyone younger. If you think we have, write to [[LEGAL REVIEW]] set PRIVACY_CONTACT_EMAIL and we will delete it. [[LEGAL REVIEW]]

If this page changes in a way that matters, we say so on the site before the change applies. This is version 2026-11-xx.

See also the terms and the vote rules.