Privacy Policy

• No accounts, emails, or phone numbers are required to chat.
• We do not sell your personal data.
• We minimize what we collect and shorten how long we keep it.
• Where we must process something sensitive, we prefer hashed or aggregated forms.

Session data. An anonymous session identifier and rotating public handle stored on your device. These aren't tied to any account.

Device signals for safety. IP addresses and User-Agent strings are received when your browser connects, but we store only a hashed form (SHA-256 with a rotating daily salt) used for rate limiting, abuse detection, and ban enforcement. We do not retain raw IPs beyond immediate request handling.

Chat messages. Text messages transit our servers so they can reach the other participant and be shown to moderators when a chat is reported. Messages tied to an active chat are retained only for the operational window described in the Data Retention Policy.

Video/audio streams. WebRTC media is delivered peer-to-peer where possible, with a TURN relay when direct connections fail. We do not record video or audio streams.

Reports and moderation records. When a user reports another user or is subject to enforcement, we retain the report, related metadata, and moderation outcome for as long as needed to run the service safely.

Analytics. Aggregate, anonymous product analytics (screen views, event counts) with no third-party ad trackers.

Push subscriptions (optional). If you opt into browser push, we store the subscription endpoint your browser gives us so we can send you notifications for pending invitations.

• Provide the service: match you with another user, deliver messages, run video calls.
• Safety and abuse prevention: rate limits, ban enforcement, moderation reviews.
• Legal compliance: respond to lawful requests, keep audit records where required.
• Product improvement: understand aggregate usage patterns.

Specific retention windows are listed in the Data Retention Policy. In short: chat messages are retained for the operational lifetime of the chat and are not surfaced back to users after a chat ends; hashed device signals rotate daily; reports and enforcement records are kept longer to support appeals and repeat-offender detection.

We share information only with:

• Infrastructure providers that host the service (databases, hosting, TURN relays), bound by data-processing agreements.
• Trust & safety partners when required to protect users (for example, reports of child sexual abuse material are escalated to the appropriate authorities and to NCMEC).
• Law enforcement, when we receive a valid legal request — see Law Enforcement Requests.

We do not sell personal data or share it for cross-context behavioural advertising.

We rely on a short-lived session cookie and a few localStorage keys to keep chats and preferences working. Details are in the Cookie Policy.

Depending on where you live (for example the EEA, UK, California, Brazil), you may have rights to access, correct, delete, port, or object to processing of personal data we hold about you. Because YapperWoo doesn't require accounts, we may not be able to link a request to specific historical records without additional information you provide.

To exercise these rights, contact {{PRIVACY_EMAIL}}. Where required, you can also lodge a complaint with your local supervisory authority.

YapperWoo is not for anyone under 18. See the Child Safety & Protection Policy for how we handle suspected under-age use and any content involving minors.

We may process data in countries outside your own. Where required, we use appropriate safeguards such as Standard Contractual Clauses.

We'll bump the policy version at the top of this page and re-prompt for consent before your next chat when material changes affect your rights.

Privacy questions: {{PRIVACY_EMAIL}}. Data Protection Officer: {{DPO_EMAIL}}. Mailing address: {{COMPANY_LEGAL_NAME}}, {{REGISTERED_ADDRESS}}.