Privacy Policy

1. Scope and contact

This policy covers our website and random text, voice and video chat service. Operator and contact details are on the Contact page. Anonymous chat means you do not need to reveal your real name to a partner; it does not mean that no personal data is processed.

2. Information used to run chat

• Guest identity: a signed random browser identifier links your connection to a guest session. It is not your name.
• Participation declaration: we record a signed policy-version and expiry marker after you confirm adult eligibility and agreement to the rules. This form does not collect your date of birth, identity documents or verified age.
• Session and matching data: session identifiers, selected mode, queue and match state, connection status and protocol events are needed to pair users, recover connections and prevent duplicate operations.
• Text: your messages pass through our realtime service to your current partner. Typing indicators are transient realtime events.
• Connection information: requests necessarily expose information such as IP address, browser information and request timing to hosting or network providers. Operational logs may include request metadata and errors.
• Abuse prevention: short-window connection counters use daily rotating pseudonymous keys derived from network address or guest/account identity. These counters are separate from chat content and do not make network-provider processing anonymous.
• Security challenge: when you choose to participate, Cloudflare Turnstile processes browser and network signals to check for automated abuse. We send the challenge token to Cloudflare for validation, not chat content. A separate signed, HttpOnly cookie records a successful check for up to 15 minutes and is bound to your guest or account identity; it is not age or identity verification. See Cloudflare's Turnstile Privacy Addendum.

3. Optional accounts

Where sign-in is available, the authentication service processes account identifiers, name, email, avatar and session information needed for that sign-in. Signing in does not mean that your email or sign-in name is automatically shown to strangers. The sign-in provider processes information under its own policies.

If you save chat preferences while signed in, we store your chosen nickname, preferred chat language and interests with your account. The nickname is for your own account controls and is not sent to your chat partner. Language and interests are sent to the realtime matching service when you join a queue; they are preferences, not guaranteed filters. Account preferences remain until changed or the account record is deleted; ending a chat or signing out does not erase them. An automated account-deletion flow is not currently available; use the Contact page for data requests.

4. Voice, video and network privacy

Voice and video are transmitted using WebRTC, preferably directly between browsers. When a direct connection cannot be established, a TURN relay may carry encrypted media traffic. The relay provider processes connection and traffic metadata needed to relay it.

We do not currently record calls, transcribe audio, take periodic safety screenshots or run server-side media content analysis. Transport encryption is not a guarantee that a partner cannot record what they receive.

A direct peer-to-peer connection can reveal your public IP address or other network information to the other participant. Do not use this service if your safety depends on keeping that information hidden from your partner.

5. Cookies and browser storage

• The guest identity cookie is HttpOnly and expires after up to 30 days.
• The adult/rules declaration cookie is signed, HttpOnly and expires after up to 30 days. Changed participation rules can require a new declaration.
• Authentication cookies support sign-in when used. Their duration is controlled by the authentication configuration.
• Browser preferences may remember language, appearance and sidebar layout.
• Guest chat language and interests are stored in this browser's local storage until changed or site data is cleared. They are not automatically copied into an account when you sign in. Account preferences do not overwrite the guest preferences left in that browser.

Clearing site data removes locally remembered preferences and cookies; it does not itself erase service-side records. Essential participation storage is not permission for advertising tracking.

6. Text retention and operational records

Our realtime service keeps a bounded text-message buffer for connection recovery: at most the most recent 100 messages per match, with a five-minute expiry per message. Expired records are removed by scheduled cleanup; this is not a promise of instant deletion from every infrastructure layer. Messages already delivered may remain in a participant's open browser or their recordings.

Match/session metadata, account data and infrastructure logs are separate from this short-lived text buffer. Their retention depends on the operational purpose, provider settings and applicable legal obligations. Ending a conversation does not instantly remove every identifier or log. We do not offer a permanent chat-history archive.

If you submit a report, we store your selected reason and description, internal identifiers linking the two participants to the actual match, the mode and submission/match times, and any review decision, reviewer identifier, time and reason. These identifiers are not shown to your chat partner. Authorized administrators can read reports for safety review. The form does not collect recordings, screenshots or chat transcripts. Report and review records are stored separately and do not expire with the five-minute message buffer. They support safety follow-up and applicable legal obligations; use the Contact page for a request about them.

When an administrator makes a separate temporary restriction decision, we also store the affected internal identifier, related report, reason, administrator and start/end times, plus delivery status, attempt counts and times for notifying the realtime service. That service stores the identifier and expiry needed to enforce the restriction. These safety records are not chat history and are not automatically deleted when a restriction expires or cookies are cleared. Use the Contact page for requests about these records or review of a restriction.

7. Purposes and recipients

We process information to deliver conversations, maintain accounts when used, recover connections, protect service integrity, investigate issues and meet applicable legal obligations. Where a legal basis is required, the appropriate basis depends on the processing and applicable law; accepting chat rules is not blanket consent to unrelated processing.

Your partner receives content you send or show. Hosting, authentication and network providers receive information necessary for their roles. We may disclose information when legally required or necessary to protect rights and safety. We do not sell chat content.

Cloud hosting and network routing can involve processing outside your country. The service does not currently offer a country-specific data-residency guarantee.

8. Your choices and requests

You can stop a conversation, decline device access, revoke browser permissions, clear site data or choose not to sign in. Depending on applicable law, you may have rights to access, correct, delete or restrict processing of your data, or to object or complain to a supervisory authority.

Use the Contact page for a privacy request. We may need proportionate information to locate your records and establish that the request concerns you. Do not send a password or an identity document in your initial message. Rights and deletion can be subject to legitimate security or legal retention requirements.

9. Children and safety

The service is only for adults who are at least 18 and legally adult where they live. Self-declaration does not verify age. If you believe a minor has used the service or shared personal information, stop the interaction and contact us. Do not send or redistribute sexual material involving a minor.

10. Changes

We will update this page when our processing materially changes, with a revised date and additional notice where appropriate. Future paid features, analytics or moderation systems must be reflected here before they are enabled.