Privacy Policy
Last updated November 17, 2026
This policy explains what R3fute, operated by Bhron LLC, collects and why. Accounts are optional, and we collect as little as we can.
What we collect
- What you post and vote. Answers, replies, videos, links to X posts, chat messages, and votes. Posts and chat messages are public.
- A guest cookie. The first time you post or vote, we store a random guest ID in a cookie on your browser and show a random public name like “Refuter 1234.” It links your contributions together so you can see your activity and edit your own posts.
- A scrambled network identifier. We don't store your IP address. We store a one-way, salted hash of it, used to limit votes to one per network and to slow down spam.
- A visit counter. While a page is open, your browser reports in about once a minute with a random ID kept in its local storage, so we can count how many people are on the site. We store only a scrambled form of that ID and the hour, never linked to your posts, your account, or your network, and delete it after 90 days.
- Site analytics. To see how the site is used, our own code (no outside analytics service) records which pages you open, how long each one is showing on your screen, how far down you scroll, which links and buttons you press (their words and where a link goes, never what you type), the site that sent you and any campaign tag on the link, your device type, browser, and operating system, your country (from our host's network location, not your IP address, which we don't store), and whether you're signed in. It's tied only to the random visit ID above and a random session ID kept in your browser's local storage, both stored only in scrambled form and never linked to your posts, your account, or your network. It uses no cookies, only the R3fute team can see it, and we delete it after about 13 months. Clearing your browser's site data starts you over as a new visitor.
- If you sign in. Depending on how you sign in: your email address, your phone number, or your X account's ID, username, name, profile picture, and (if X shares it) email. We use these to sign you in, keep your account secure, and, only if you turn them on in settings, send you notifications by email or text. They are never shown publicly. Your chosen username is public.
- A profile picture, if you add one. It's cropped and shrunk in your browser before upload, which removes photo data such as location. It's stored publicly so it can be shown with your account. Removing it deletes the file.
- Audio, transcripts, and cover photos you add to a video or audio post. Audio is sent to our AI provider to be transcribed and is deleted from our storage once it's transcribed. The transcript is kept so the arguments and their times can be found and checked. A cover photo is stored publicly so it can be shown with the post.
- If you protect posts you made without an account. A code you choose is stored as a one-way hash on each post it protects, plus an encrypted copy that only your browser session can reveal. A passkey stores only its public key with us; the private key stays on your device or in your password manager.
- Support tickets: what you write, a link to a post if you add one, and your email address only if you give it (so we can reply). Only the R3fute team sees them.
- Standard server logs kept by our hosting provider for security and reliability.
We don't use advertising or tracking cookies, and we don't sell your information.
Services we use
- Vercel hosts the website, and Supabase stores its database and handles sign-in.
- Sign-in codes are texted through Twilio and emailed through our email provider. Signing in with X goes through X.
- Notifications you turn on are emailed through Resend or texted through Twilio. In-site notifications (the bell) are stored with your participant identity and are only visible to you.
- When AI features are on, post text is sent to our AI provider (OpenAI or Anthropic) to write the deductive form of answers and replies, produce labeled AI opinions, work out where a post belongs, or suggest splits. When you post, we keep the scrambled network identifier described above and the time of each attempt, to limit use. We also keep a private record of everything submitted as a post, including posts that weren't published (for example, ones AI found argue no belief system true or false): the text, when, your participant identity, and what happened to it. Only admins can see it.
- When you use Ask R3fute in the search bar, your messages are sent to our AI provider to answer them. We don't save the conversation; it stays in your browser tab. To limit use, we keep only the time of each message and the scrambled network identifier described above.
- When you paste a link to a post on X, we read that post through X's public embed service and keep its text, its author's name and handle, and its link, to credit it on R3fute.
- Embedded videos load from YouTube's privacy-enhanced (no-cookie) player.
How long we keep it
Public contributions stay up as part of the shared debate record unless removed. Deleting your own post removes your name from it, but its text, deductive form, and rating stay, and it can still be refuted. Moderation decisions are kept to improve duplicate review.
Your choices
You can clear your cookies at any time; if you aren't signed in, we then can't connect you to earlier posts. To delete your account, or to ask us to remove something you posted, contact us through Support with a link to it.
Children
R3fute is not for children under 13, and we don't knowingly collect their information.
Changes
We'll update this page if our practices change.