Privacy policy

Without a public account

Basic chat does not ask for a name, email or public profile. The service still processes an anonymous session identifier, search preferences, connection information and technical data such as IP address and browser information to operate the conversation.

Anonymous account and recovery code

Using chat creates an anonymous account without email or a password. A permanent secret code restores your saved profile, but not past conversations. Anyone with the code can access the account. Without the code or a valid session, access cannot be recovered.

Account profiles, directory consent and encrypted recovery codes are stored without automatic expiry. Login sessions expire after 30 days or are revoked when you log out. Recovery attempt counters use a keyed hash of your IP address and expire after 15 minutes; physical deletion may be delayed.

Optional directory and location

Entering the online directory makes your card visible by default. You can hide it in your profile. While visible, other participants can see your nickname, self-declared age, country and city where provided. Your card is removed from availability while you are in a conversation and after the service detects your disconnection. Selecting a visible available person opens a private chat immediately for both participants. Country and city are optional profile fields, not location filters or verified location.

Messages and conversation metadata

The server relays private text and keeps message identifiers, senders and reactions during an active conversation. It does not create a persistent text archive. The “This or that” game stores current choices only for the active conversation. Refreshing or closing the page ends the live connection; there is no saved inbox or restoration of messages in this MVP. Your partner can still copy text or take screenshots.

Optional photos and Firebase

Sharing a photo is optional. For uploads, the browser signs in anonymously with Firebase Authentication, prepares a WebP image and stores it in Firebase Storage. The resulting download link is sent to your partner. Firebase receives the upload and associated technical information. Do not share a download link outside the conversation if you want to limit access.

Photo deletion has limits

Deleting an image or ending a conversation initiates removal of uploaded files. Cleanup can fail or be delayed; immediate or guaranteed erasure is not promised. Deleting a file does not erase copies already saved by a recipient.

Browser storage and visit analytics

Cookies and browser storage support sessions and preferences. Google Analytics and Yandex Metrica measure visits and site use and receive technical information. Yandex session replay, click maps, link tracking and hash tracking are disabled in the site configuration. The chat does not deliberately send private message text as an analytics event.

Reports, blocks and retention

Reports and blocks are stored in Firestore with anonymous session identifiers and a 30-day expiry. Legacy anonymous session profiles expire after 30 days; permanent account profiles and directory consent do not expire automatically. Conversation records contain category, site and activity metadata, not message text, and expire after 7 days. Daily aggregate counters expire after 30 days. Automated deletion can be delayed; access and matching must not rely on expired blocks. Clearing browser data does not erase database records or copies made by another participant.

Your choices

You can decline photos, delete your own shared images, leave, report or block. Clearing site data removes browser-held settings but is not a request to erase data held by another participant or provider. Avoid sharing identifying details.

Changes to this policy

The date above identifies this revision. Read the policy again before sharing sensitive information; changes to the service may require a new explanation of its processing.