Privacy notice — 9 November 2026
Your data,
your choices.
Cookies & measurement
Before Got it, our entrance counters and Microsoft Clarity work without analytics cookies. Clarity records the public question and email screens with typed text hidden. It uses a new identifier for each page view, without recognizing you across pages. Yandex/Webvisor starts only after the optional choice; its limited mode uses cookies. Saved refusals and Global Privacy Control remain in force. Providers receive connection information, including your IP address in transit.
Clarity shows the layout, clicks and scrolling of the public entrance. Unfinished questions and email addresses are hidden. Google Analytics measures usage; Meta measures completed registrations. Yandex receives a separate view of entrance stages. The separate game-question view contains only your published question. Photos, answers, private chats, extra profile information and participant reports are excluded. Providers and people with project access can access the data sent to them. The six-player room is for its participants and may be moderated.
What we collect
We collect your email, date of birth, profile details, photos, question, game answers and ratings, choices, messages, ticket activity, and reports you submit. We store sign-in sessions and the time and version of your User Agreement acceptance. Your date of birth is used to check that you are 18 or older; your displayed age is your choice.
Why we use it
We use these details to confirm your email, create your account, form rooms, run and score the game, show matches and conversations, protect users, handle reports, and maintain the service. A sign-in email is sent when requested. A room invitation is sent when your game is assembled. Browser alerts depend on permission and an open tab.
Who sees what
Players see your question, answers, and ratings as the game allows. Main profile photos become visible to finalists in the final round. A mutual finalist pair can see each other's additional photos and private profile. A voluntarily attached photo appears to the other person in the anonymous side chat. Your email and date of birth are not shown to other players. Content you share with someone can be saved by that person outside Banterfly.
Service providers
We use Vercel to host the site and private photo storage, a hosted PostgreSQL database for accounts and game data, Resend to deliver sign-in and room emails, and Cloudflare Turnstile to check registration and place confirmations. These services process data needed for those functions. We do not sell your profile or messages as an advertising list.
Visit statistics and campaign measurement
Entrance path measurement
A random reference links one entrance document to fixed loading and action signals for up to 15 minutes. A registered public advertising-link token may label that attempt; it identifies the link, not a person or a verified ad click. Temporary tab storage and a one-use URL fragment carry an admitted same-tab question transition; the fragment is removed before optional providers start. The server deletes expired references on the next minute cleanup. Hourly counts of joint stage sets, grouped by public token and separately marked synthetic QA, remain for seven UTC calendar days. They show which signals occurred in the same attempt, not their order or a reason for leaving. No IP, IP hash, user-agent, fingerprint, email, question text, raw URL, referrer, account or persistent browser identifier is put in this diagnostic store. These data are not sent to analytics or advertising providers or joined to their identifiers. Selecting a dose is a draft choice, not a ticket award; question-document acceptance and a visible question form are separate signals. Missing signals remain unknown. Declining statistics in Privacy settings or Global Privacy Control stops future collection. Expired references cannot be reconstructed and aggregate contributions cannot be identified. This additional campaign-path scope is separate from optional account attribution and provider analytics. Contact hello@auth.banterfly.club about access, objections or deletion. Linking expires after 15 minutes. A leftover tab-storage entry is discarded on the next eligible page or when the tab closes. An explicit QA attempt is linked to its verified test control only until cleanup; the aggregate retains only the synthetic category. The fixed signals also include the first non-empty edit of the question in this document and the rendered email form. Restoring a draft alone is not a new edit; reopening the form in the same attempt is counted once. Neither field contents nor individual keystrokes are sent. A new document or an expired attempt does not identify a returning person. We also count when the question meets the form requirements and Next is available, separately from clicking Next. A restored ready draft can produce this signal. We also count a successful Got it acknowledgment once per attempt. This count does not prove that an external analytics provider received data. The first entrance request, including a language redirect, is distinguished from acceptance of the destination document and its loading signals. A signed reference briefly travels in the redirect URL and is removed before optional providers start. HTML requests without Fetch Metadata can be counted, but are not proof of a human visitor or a displayed screen.
Even before you choose your settings, we count how often people open the hint and start typing afterward. We don't save who opened it or what they wrote. If you opt out or send a privacy signal, we don't count it.
Hourly source request totals
We count accepted entrance and question-page requests by UTC hour and an immutable public source category from reviewed campaign links or links created by the owner in our registry. Unknown or invalid tags are grouped as unknown. This separate table stores only the hour, page-stage category, source category and count. It stores no account, browser or session identifiers, IP address, user-agent, raw URL, query, referrer or content, and is not joined to individual visits or accounts. Reloads, automation and internal use can be included. These totals are not unique people, proof that a page was displayed or ad-click conversions.
We create no new browser storage or tracking request. We read only the existing statistics-refusal cookie and the Global Privacy Control request signal to skip this count; they are not stored in it. Playing is unaffected. Only authorised operators access the totals through our existing hosting and database services; they are not sent to Google or other analytics or advertising services. We retain seven UTC calendar days; cleanup continues when counting is paused.
Where applicable, we rely on legitimate interests in checking entry-route reliability and aggregate traffic from reviewed links, separately from optional browser analytics. You can ask about or object to this processing at hello@auth.banterfly.club. We cannot identify or remove one person's contribution; we can suspend this count while assessing an applicable objection. Existing statistics, recording and advertising choices keep their effect.
Daily service totals
We count accepted page requests and completed service operations to understand reliability, use of the service and progress through registration, profile creation, booking, waiting, saving a question and starting a game. These are product and business-stage totals, not unique people or proof that a page was displayed. Repeated requests and internal, automated and test operations can be included.
While processing those existing requests and operations, we add one to a daily total. This separate table contains only the UTC date, a fixed event name and a count. It contains no account or browser identifier, question or other content, IP address, URL or campaign label, and creates no individual path. It uses no new browser storage or tracking request and is not sent to Google, Clarity, Yandex or advertising services. Access is restricted to authorised operators using our existing hosting and database services. We keep 30 calendar days; scheduled cleanup continues when counting is stopped.
These limited server totals are separate from optional browser statistics, linked visits, campaign attribution, recording and advertising. Their permissions and refusals keep their existing effect. For the transient processing that creates these totals, where applicable we rely on legitimate interests in maintaining and improving Banterfly, not on an optional analytics permission. We do not use the totals to make decisions about individuals or create advertising audiences.
You can ask about or object to this processing by emailing hello@auth.banterfly.club. We assess applicable objections and can suspend this count system for everyone while doing so; playing continues. This system does not offer individual exclusion. We do not reconstruct a person's contribution to a total or promise that an individual contribution can be removed. hello@auth.banterfly.club
With visit statistics allowed, Banterfly records fixed facts about opening the question page: a navigation attempt, a displayed page, a ready form, or a known entrance refusal or loading error. A short-lived random reference joins an attempt to its result. These events contain no question text, email, photos, personal fields, full URLs or error messages and are not sent to Clarity or Yandex. A missing result means unknown, not that you left. The question and account screens remain excluded from session recordings.
With your permission, a random visitor cookie links invitation tags (source, channel, campaign and creative) to your signup and account. We keep the first known and last known tagged source; untagged visits do not overwrite them. Visitor cookies last up to 90 days and your preference up to one year. You can play without visit statistics. Changing your preference stops new visitor collection; contact us to request removal of existing linked records.
A new entrance choice with Visit statistics enabled, or an explicit Privacy Save, permits our own report to link reviewed source/channel/campaign/creative to visits, question display/readiness/save, email verification, account/profile, booking and confirmed queue entry. We use a random visitor ID, permission receipt and authenticated account ID: underlying records are pseudonymous, not anonymous. Campaign snapshots are immutable. Events/snapshots last 30 days. Minimal permission evidence depends on the still-valid original choice and lasts at most one year plus 30 days for its last events. A separate withdrawn-epoch hash lasts up to 366 days only to prevent reuse, never for attribution. Cleanup continues while collection is off. Refusal/withdrawal stops new linked events without stopping play; no historical backfill or automatic deletion. These records/content are not sent to analytics providers; their separate choices remain. Withdrawal does not extend identifier cookies: old visitor/receipt references can remain inactive until their original expiry or replacement by a new choice, so a delayed cleanup response cannot erase that new choice. A separate browser cleanup reference permits withdrawal only, never tracking; it expires with the original permission, and only its deny-check hash may remain for up to 366 days after withdrawal. A queued withdrawal may keep a separate technical reference for at most one year until acknowledged; retries do not renew it and it cannot enable tracking.
Our private operator dashboard counts account, queue, confirmation, game and conversation facts. It receives no email address, birth date, sign-in token or message/answer text. Two-sided conversation counts use the presence of messages from both people. Security limits keep short-lived pseudonymous request counters, not raw IP addresses.
Email invitations and news
This optional subscription starts only after you verify the email code, even if you do not finish a profile. We retain the email, consent wording/version, language, source and times, subscription status and minimal delivery records. Sign-in codes and service messages for a game or session you joined are separate. Every future invitations/news email must provide an unsubscribe link.
Loading email preference…
Machine interface: technical documentation
The public machine screen offers the ASK operation and a link to the versioned machine protocol. Its output is public interface content, not a human account or game room.
Profile, media and queue operations require a signed key and server admission checks. The protocol's limits and errors apply. Game, chat, credentials and private profiles are outside public interface recording.
This checkbox also applies the measurement choices in the agreement. You can turn them off there without losing access. Only an independent optional replay choice covers masked, cookieless Clarity recording of this public machine area. Stop recording and Privacy settings withdraw future collection. Public ASK output is masked; private API/session data, keys, profiles, games and chats are excluded. Reading technical terms alone grants no measurement permission.
Banterfly visit statistics and Google Analytics on eligible public pages require permission. Google starts only after permission and stops on refusal or withdrawal. It may use random browser identifiers and cookies for up to 90 days and receives technical connection information, including IP in transit. We send no question, answer, message, photo, email, account ID, private content, raw URL/query, unknown parameter or click ID. Advertising and automatic form tracking stay off. Google user/event retention is two months; aggregates may last longer. Withdrawal does not automatically delete earlier records.
Public campaign labels (optional)
After a new entrance choice with this setting ON, or an explicit Privacy Save, Banterfly may send reviewed public source, medium and campaign labels from its fixed registry to Google Analytics and Yandex Metrica to attribute traffic. Google receives named campaign fields; Yandex receives a reconstructed public page address with only those three reviewed labels. We never forward the original URL/query string, unknown parameters, click IDs or private data. Creative labels remain in Banterfly's own consented statistics, and Clarity receives no campaign or creative labels. Each provider's existing permission and public-page restrictions still apply. Earlier choices without this campaign-label scope do not grant it. The new entrance draft is ON; saved refusals remain OFF. Turning it off does not block entry, questions or ordinary first-party statistics. A first-party preference cookie, valid for up to one year, binds this versioned choice to the current statistics consent; a local-storage signal synchronizes changes between tabs. A new entrance action saves the chosen campaign-label setting with its new statistics epoch. Withdrawal stops new label handoffs and clears pending application handoffs and campaign context; it cannot recall requests already dispatched to a provider. Reload already-open pages to apply updated site code.
Meta advertising measurement
Meta advertising measurement starts only after a saved choice. A new common entrance checkbox applies the Advertising measurement setting, initially ON for a new visitor; a saved refusal remains OFF. You can turn it off in the agreement or Privacy without losing access. Visit statistics alone does not enable it. If you opt in, Banterfly may send Meta one confirmation of your first completed registration, our public home address and, when available, a fixed campaign label and A/B/C/D variant. We use campaign attribution only when you also allow visit statistics. We do not send email, account IDs, profile details, orientation, questions, answers, chats, invitation tokens or private page addresses. Meta receives technical connection information, such as your IP address and browser information, and may receive or set its own cookies. We do not load Meta's JavaScript SDK or enable advanced matching or server-to-server Conversions API. Our bf_meta and bf_meta_v cookies remember this separate choice for up to one year. When allowed, bf_meta_epoch records a random consent reference for the same period; it stays with Banterfly and is removed when you withdraw. A local storage signal synchronizes the choice across tabs for up to one year. Declining does not affect access to Banterfly. Withdraw below at any time to stop new measurement and cancel pending delivery; this does not recall a request already sent or delete Meta's cookies or previously received records. Meta's own processing and retention are described in its Privacy Policy. You can also manage its cookies in your browser.
We store site RSVPs and preferred game times with your account. Optional visit-statistics collection can use the existing analytics visitor cookie; declining statistics stops those optional signals. The independent operational presence described below and game-queue presence do not change your analytics choices.
Visible pages at the entrance and inside the site send operational presence every 30 seconds, independently of optional visit statistics. Signed-in sessions are deduplicated by account. Guests use the separate random bf_presence cookie (HttpOnly, 120 seconds, renewed while active). A returned cookie is required before a guest is counted. Presence records contain only a session reference or cookie hash and current timestamps, not page addresses, content, IP addresses or advertising identifiers. They count for 90 seconds; minute maintenance deletes expired records, including when collection is off. Pending cookie handshakes expire after 120 seconds. Cleanup can be delayed during an outage. No browsing history is retained in these records. Cookies/JavaScript blocked means unobserved, and browsers are not exact people. Optional analytics choices and game admission are unchanged.
Separate optional analytics report (not the Activity panel): Within that consented presence coverage, the operator also sees aggregate counts of men, women and accounts whose profile gender is unavailable. We use the existing profile gender and never infer a guest's gender. The observed total adds deduplicated signed-in accounts to anonymous browser IDs; it mixes units and is not a unique people count. A valid session without a recent visible-page heartbeat is not counted as presence.
Storage and requests
Sign-in links expire after 15 minutes, onboarding sessions after 24 hours, and unclaimed question drafts after 30 days. Other account and game data may remain while the account operates and for operational or safety needs. To ask about access, correction, or deletion, email hello@auth.banterfly.club. We will verify that a request concerns your account before acting. Blocking another player limits access in the service; it cannot undo content already copied.
Updates
We will post changes to this notice here with a new date. Review the User Agreement, Detailed Game Rules, and Community Rules for the associated account, game, and conduct terms.