Policy / Privacy
AnonChat privacy policy
This notice explains information handling across AnonChat’s public reading pages, guest matching, accounts, conversations, rewards, purchases and help routes. What applies depends on the action taken. Entering as a guest avoids initial account creation; it is not a claim that the service handles no information.
Effective November 20, 2026 · English edition
Read the policy by task
AnonChat content, guest sessions, accounts and product actions.
Browser settings, product controls and available request routes.
Legal exceptions and technical realities remain visible.
Which information enters through your choices?
This notice covers anonchat.cam and its linked product experiences. In this document, “we” refers to the AnonChat operator. The terms of service supply the usage rules that accompany this notice.
A user may supply a display identity, sign-in details, settings, profile material and communication content associated with the features actually used. Audio and visual interactions additionally communicate whatever the user says or presents. Treat every participant as a recipient of those disclosures and leave out sensitive material that the conversation does not need.
An available help channel may receive the question and attachments sent through it. Keep credentials and complete payment data out of such messages. A payment processor can handle card credentials while AnonChat receives the order status, package and reference information needed to operate or reconcile the transaction.
What can a session or device contribute?
Requests to the service can carry a network address, broad network-derived locale, device and browser class, operating system, language, referral, timestamps, page requests, feature events and diagnostic details. These can be used to deliver the requested experience and keep it reliable and secure.
Local browser storage and cookies can preserve a guest or signed-in session, preferences and security state. Camera and microphone access follow browser permission and the selected conversation medium. Granting device access is unrelated to any suggestion that operational data is absent.
Browser menus may remove or restrict local storage, although required storage can be necessary for a session. Read data choices to distinguish that local action from a request about records held by the service.
Why information is used and who may receive it
Operational uses can include page delivery, session authentication, stranger matching, profile browsing, communication, saved connections, balance displays, reward states, transaction handling, preference storage and responding to a user’s request.
Security, misuse prevention, diagnosis, service reliability, legal duties and the handling of claims can require additional use. The active feature set and applicable law determine the details. Nothing here asserts continuous human review of every exchange.
Suppliers of hosting, delivery, communications, payment, security, measurement or help infrastructure may process only the information relevant to their role. Profile and conversation recipients see what a user intentionally supplies. Valid legal process, safety, rights enforcement or an organizational transfer can also require disclosure under applicable arrangements.
How long records can remain and how they are protected
Account and saved-connection records can persist for the account’s life. Help and transaction records may outlast one interaction when needed for troubleshooting, reconciliation, fraud controls, disputes or statutory duties. Diagnostic logs can follow shorter cycles. Backup rotation and legal holds may affect final deletion.
Protective measures should match the information and operational risk. Internet transmission and storage cannot carry an absolute security guarantee. Users can lower their own exposure by guarding sign-in access and following the media and disclosure checklist.
Requests, regional rights and revisions
Local law may provide access, correction, erasure, portability or disclosure-information rights. The available rights and their exceptions are jurisdiction-specific. A lawful need involving security, accounting, disputes or statutory compliance can limit deletion of a particular record.
A request should name its intended result and may need proportionate identity or authority checks. AnonChat currently lists no public help mailbox. Use the privacy controls or request route presented in your product session; contact guidance explains safe preparation without credentials.
The service is not directed to children. Feature, supplier or legal changes may require a revised notice. The date above identifies this edition, and an appropriate notice may accompany a material revision.
Keep your choice
Make the privacy choice specific.
Use data choices to scope a request or adjust local browser settings through the routes available to your session.
