What goes
where.
Personal rules stay in your browser. Community voting needs a shared backend.
Website visits
This website has no sign-in form, advertising trackers, or analytics scripts. The interactive example runs in your page without saving choices or submitting votes. The hosting service may process ordinary request data such as IP addresses, browser information, and access logs to serve and protect the site.
Guest extension use
Your personal blocks, allowlists and settings are stored locally in browser extension storage. Guests cannot submit votes. While enabled, the extension sends visible video and account IDs to Supabase to retrieve public aggregate tallies and percentage bars. YouTube access lets BotControl read supported video cards and hide matches.
Member extension use
Supabase handles email authentication and stores voting data. Resend delivers sign-in emails. Signing in sends your email and code to the authentication service. Guests and signed-in members request visible video and account tallies even when automatic blocking is off. Votes send a target ID and choice; account reports include your written reason. The backend stores member IDs, votes, rate-limit events and moderation records.
Account identity lookups
The extension may request public YouTube channel pages with cookies omitted to resolve handles to permanent channel IDs. These requests go to YouTube. Mappings are cached locally for 30 minutes. The extension does not upload video/audio files or a full browsing history, and no AI model analyzes your feed.
Sessions and access
Session credentials use trusted browser session storage. Signing out or restarting the browser ends the stored session. Shared snapshots and channel mappings are cleared on sign-out; personal rules remain. Public tally endpoints return aggregate totals without voter identities. Member endpoints also return your own vote.
Security and public tally limits
Account identity and sign-in credentials stay in trusted extension storage. YouTube controls receive a separate view without email addresses or real account IDs. Public tally requests share minute and hourly budgets. Only shared counters are stored for these limits, without visitor IP addresses or queried IDs. This does not change ordinary provider logs. Guest tallies may temporarily pause when busy; personal filters keep working.
Export, removal and retention
Options includes personal data export and local reset. Click your selected AI? or Human? button again to remove that video vote. Local reset and uninstalling do not erase server submissions. Vote and moderation records otherwise remain until removed through the app or by the project owner; no fixed server retention period is currently promised. A dedicated server-account deletion flow and public support channel are still being prepared. During the invited test, contact the person who invited you for account-data requests.
Current limits
Email verification does not prove one human per account. Community labels can be wrong. This release provides filtering choices and member opinions, not forensic findings.