Privacy information
Know what you share when you chat.
FangoChat is provided by MAD GAMES STUDIOS. You can use the website and Android app without creating an account. This privacy policy explains the data used for calls, safety, support and advertising in Android versions that include ads. Contact [email protected] for privacy questions or requests.
Your camera and microphone
The home screen and information pages do not start your camera or microphone. In the chat room, access is requested after you choose Start and agree to the rules. Your browser or Android manages permission to use those devices.
Stop releases the camera and microphone used by FangoChat. Next keeps your permitted devices running while it looks for another person. You can revoke permission in browser site settings or Android app permissions.
Video, audio and messages
Calls and text messages use WebRTC. The chat application does not record calls or save the text of your conversation to its chat database. Messages are held in the page or app's memory during the conversation, and the displayed history clears when you start another session or use Stop.
A connection may go directly between the participants or use a relay when needed. A direct connection may expose your network address to the other participant. Other people can record or capture what they receive using their own tools, even though FangoChat does not provide a recording feature.
Information used to connect you
The service stores temporary session and room identifiers, country estimates, timestamps and connection signals, which can include network addresses. It processes IP addresses to estimate a country and limit excessive requests. The connection response also gives the matched participant your estimated country. Matching currently connects available visitors without country or gender filters. No GPS or Android location permission is requested.
Calls and messages go to the participant you connect with. The API uses HTTPS and WebRTC protects the call and message transport. Cloudflare handles website/API traffic; our hosting server and TURN relay support the service, and Google STUN helps find a connection route. These services process the network information needed to carry traffic. Android advertising has the separate data flows described below.
Android advertising and privacy choices
Current Android versions that include advertising can display Google AdMob banner ads in the idle Stranger pane before Start and after Stop. Ads are not shown while searching, connecting or in an active call. Earlier Android versions may display banners on the welcome screen. These advertising disclosures apply to those Android versions; the website does not load the Google Mobile Ads SDK.
When offered, you can choose to watch a rewarded ad for a 30-minute ad-free period. This period begins when the ad SDK confirms that you earned the reward and continues while the app is closed or in the background. The app stores its expiry time on your device in Android secure storage, separately from and without linking it to your Safety ID.
We request non-personalized ads. Google's Mobile Ads SDK processes network information such as your IP address and approximate location, app and ad interactions, performance diagnostics and device identifiers, including an advertising ID when available. Google uses this information for advertising, measurement and fraud prevention. Where applicable, its SDK can also process identifiers associated with signed-in accounts on the device.
Google's User Messaging Platform checks advertising privacy requirements and presents a message where required. This check can contact Google before an ad is requested. The app requests ads only when the consent-status check permits it. Use Ad privacy options, when shown in the Android menu or Privacy information, to review your choices. Non-personalized advertising does not mean no data collection. Android settings also let you reset or delete the advertising ID.
Advertising choices do not replace camera and microphone permissions or the rules for starting a chat. The chat service's random safety reference is separate from Android's advertising ID. Google's advertising records have their own retention periods and controls; the chat-data request process below does not directly delete those records.
An anonymous safety reference
After you choose to start a chat, the service issues a random browser or app reference. A protected browser cookie or Android secure storage keeps its secret so reports, blocks and suspensions can apply across ordinary session restarts. The server stores a hash of that secret. This is not an advertising identifier, hardware fingerprint or verified identity.
The public safety reference can help locate your records for support. Never send the secret or session token. Clearing storage, reinstalling or using another browser or device changes the reference and can defeat anonymous blocking.
Reports and review records
Reports contain the selected reason, report time, room/session identifiers and the reporter's and reported participant's anonymous references. A report is an allegation, not proof of what happened. The review tool does not contain recordings or conversation transcripts. Restricted review records document the operator's decision and any suspension or preservation request.
Only authorized operators can access the private review tool. Information may be supplied to the appropriate authority when needed to address child exploitation, comply with law or respond to a valid request. Do not attach or email suspected child sexual abuse material.
Retention
Inactive chat sessions become eligible for cleanup after 24 hours and connection signals after 10 minutes, or sooner when a conversation ends. Reports, review records and blocks normally have a 180-day retention period. Inactive anonymous references are eligible after 180 days, subject to associated safety restrictions and preservation holds. Cleanup happens on its next scheduled or application run; Stop does not immediately delete every service record.
An active suspension or documented preservation hold can require records to be kept longer. Operational logs and protected recovery backups are separate from the active chat database; removing an active record does not immediately remove an older backup copy. Privacy requests are reviewed against these records and any safety or legal reason for retention.
Access and deletion requests
Use the Privacy controls in the chat room or Android app to request an export or deletion for your existing anonymous reference. This submits an authenticated request and provides a receipt; it does not instantly erase data. Use Check request status on the same browser or app to retrieve the result. An approved export is available for up to 30 days. Contact [email protected] with the receipt if you need follow-up or cannot access that device.
We verify a request before disclosing or deleting records. An identifier by itself is not proof of ownership. Some safety restrictions and preservation records may need to remain; the response explains what can be removed and what is retained. Because no account name is collected, we may be unable to identify older records after you lose the device reference.
