Privacy Policy
Effective date: 2026-11-11
This policy explains how MonkeyChat handles personal information when you use the website at www.monkeychat.fun and its embedded chat service (the “Service”), contact us, make a purchase, or report a concern. It also explains your choices. Read it with our Terms of Service, Cookies and Similar Technologies notice, and Account Deletion and Privacy Requests page. Agreeing to the Terms does not give us unrestricted permission to use your information.
1. Who is responsible
Bigglesworth Tech Limited (Hong Kong registration no. 77649784), at Room 1911, Lee Garden One, 33 Hysan Avenue, Causeway Bay, Hong Kong, is responsible for the processing described in this policy. Contact privacy@monkeychat.fun about privacy and support@monkeychat.fun about account or payment assistance. Include the website or app you used so that your request reaches the correct team.
This policy covers the Service identified above. A similar brand name, a shared login, or a link to another website does not by itself make that website part of this Service. Independent sign-in providers, app stores and payment providers may also process information for their own purposes under their own notices.
In this policy, personal information includes information relating to an identified or identifiable person, including identifiers that can be linked to an account or device. Content means material you submit or communicate, such as profile images, messages, video and audio. Interaction metadata means information about an interaction, such as participants, time and connection events; it is different from the words, images and sounds of the interaction. Removing a name alone does not necessarily make information anonymous.
The Regional Privacy Notice explains additional rights where a regional law applies. The Age Eligibility and Assurance page explains any age-check process selected for your version and location. A feature-specific collection notice adds detail at the point of collection; it does not silently override the scope of this policy.
2. Information and purposes
The information involved depends on the features you actually use:
The Service provides account-based one-to-one video matching, text within a match, matching preferences and paid membership features. Google and Facebook sign-in are offered. The purchase screen identifies the membership and benefits available to you.
| Information and source | Purpose and requirement | Audience or recipients |
|---|---|---|
| Sign-in token, provider/account identifiers and nickname associated with your selected sign-in | Authenticate and create the account; authentication is needed for account features | Our account service and the selected sign-in provider; authentication credentials are not shown to a match |
| Name, date of birth and gender supplied in registration; profile information returned with the account or match | Complete registration, apply the adult-only rule and provide matching; name, date of birth and gender are needed to complete registration | The matching interface can display name, image, age and country. Exact date of birth and email are not displayed profile fields |
| Camera and microphone stream, room text, room identifier, participants and connection events | Deliver a match and its communications; camera/microphone access is needed for the corresponding live feature | The other participant, our communication systems and the communication providers described below |
| IP address, device identifier, browser/platform, language, time zone, errors, feature events and acquisition channel | Establish connections, maintain sessions, diagnose faults, measure use and protect accounts | Our technical services and the relevant analytics or infrastructure providers |
| Membership selection, order reference, payment status and entitlements | Fulfil purchases, renewals, cancellations and billing support; needed for a purchase | Our billing service and the payment provider identified at checkout |
| Reports, reported account/room, correspondence and information you send with a request | Investigate the concern and respond to support, safety and privacy requests | The teams and providers handling that request, subject to the disclosure limits in this policy |
A sign-in provider may supply a profile image for browser-side display or storage. That does not mean every field visible to the provider is copied into our account database. The provider also processes information under its own account and authentication notice.
Provide only information relevant to the feature or request. Do not send passwords, full payment card details, or copies of identity documents in an ordinary support email. If a verification process needs additional information, we explain its purpose and secure submission route before collection.
Without information necessary for registration, a connection, purchase or verification, we may be unable to provide that feature. Optional profile details are your choice. Other users may submit information about you in a report even if you do not have an account.
Optional features and information about other people
Signing in through another service can provide the account identifier, authentication token and permitted profile fields associated with the sign-in. The permission screen and the feature notice explain the fields requested. Disconnecting a sign-in provider can affect future access; it does not necessarily remove information already associated with an account.
If you supply information about another person, do so only where you are entitled to and avoid unnecessary detail. An uploader's permission does not automatically constitute every other person's consent. Someone whose details appear in a report, contact upload or shared content may contact our privacy address without creating an account.
Who can see content
In a one-to-one interaction, content is delivered to the other participant. For any additional feature identified above, its audience and available controls are explained before you share. Private messages and publicly visible content have different audiences.
A private audience setting does not necessarily mean end-to-end encryption or that content cannot be processed for a disclosed support, safety or legal purpose. Conversely, a safety purpose does not make private content publicly available. Blocking affects the contacts and features described in the block control; it cannot withdraw copies already received or prevent all contact outside the Service.
3. Live interactions, messages and safety
When you choose to join a live interaction, your camera image, voice, messages and the profile information shown with the feature are made available to the other participants. Consider what appears behind you and what you reveal. Another participant may use external tools to capture an interaction; our rules prohibit non-consensual capture and sharing, but rules cannot guarantee that it will never happen.
Browser or device permission lets a feature access a camera or microphone. It is not consent to every use of the resulting information. You can stop a live interaction and change device permissions; revoking a permission does not itself delete information already lawfully processed.
Live video and audio are transmitted using Agora. Room text is submitted through our messaging service, with Tencent IM used for messaging and signalling. Profile images and account details are submitted to our systems for the account and profile features.
During a video match, the browser captures local-camera still images at entry, at intervals determined by room rules, and when leaving. It requests an upload destination and sends images together with the room identifier, the matched user's identifier, capture timing, detected face count and, when sampled, a content-risk score. These inputs support safety screening and investigation. The face-count check runs in the browser using a TensorFlow/BlazeFace model; it counts detected faces rather than establishing a person's identity or age. A zero content-risk score can also mean that a sampled check did not run. These signals are not conclusive proof of misconduct.
Still-image capture is distinct from a continuous recording. Reports and retained safety evidence can be examined with related account and interaction records. You may challenge a restriction through the appeal route; a report or automated score does not by itself establish that a violation occurred.
Reports and related information may need to be examined to assess abuse, protect affected people and resolve appeals. A safety report does not authorise unrelated advertising use of its contents. Legal restrictions, other people's privacy and the integrity of investigations may limit information we can disclose about an investigation.
An eligibility estimate, content-risk score or device signal can be wrong. We distinguish signals that assist a decision from a decision that itself limits access. Where law gives you the right to human intervention, express your view or contest a qualifying decision, use the privacy or appeal route described below. We may withhold exploitable security details or another person's information, but that does not remove an applicable obligation to provide a meaningful explanation.
We do not treat a general permission to operate the Service as permission to use private interactions to develop unrelated advertising, face-identification systems or general-purpose AI models. A materially different use requires its own lawful basis, clear information and any necessary choice before it occurs.
4. Grounds for processing
Where European or UK data protection law requires a lawful basis, the basis depends on the purpose:
- Providing a contractually requested service: necessary account administration, matching and communication delivery, purchased entitlements and billing.
- Legitimate interests: proportionate security, fraud prevention, service reliability and handling complaints, balanced against the rights and interests of affected people. This basis does not remove a separate consent requirement or authorise processing prohibited by law.
- Legal obligations: processing required by an applicable law, such as particular accounting, reporting or preservation obligations. Not every voluntary disclosure to an authority is a legal obligation.
- Vital interests: narrowly necessary processing to protect someone's life or vital interests where that ground applies, such as a genuine emergency. Routine safety screening is not automatically an emergency, and separate sensitive-data conditions still apply.
- Consent: optional processing for which we ask for consent, including tracking where required. You may withdraw it without affecting the lawfulness of processing before withdrawal.
Additional conditions may apply to sensitive information, biometrics or decisions with legal or similarly significant effects. Such processing requires its own applicable condition and notice; a general safety purpose or acceptance of these Terms is not a substitute. See the feature-specific disclosure in section 3.
Purpose-by-purpose explanation
The table below explains the grounds for the processing described in this policy where EEA law applies. A ground applies only to the corresponding activity; a consent requirement is not replaced by a general service purpose.
| Purpose | Relevant information | Ground and limits |
|---|---|---|
| Register, authenticate and maintain an account | Necessary account, sign-in and account-state information | Contract for the requested account; separate security processing may rely on legitimate interests |
| Deliver a selected match, call, message or paid entitlement | Necessary content, connection, preference and order information | Contract to the extent objectively necessary for the feature requested, not for unrelated tracking |
| Verify eligibility | Age information, verification result and any separately disclosed verification input | The applicable eligibility process and law determine the ground; legal obligation only if a specific law requires it, and additional consent/conditions where required |
| Protect users, prevent fraud and handle violations | Relevant reports, interaction metadata, security signals and disclosed evidence | Legitimate interests subject to proportionality and balancing; legal obligation for specific mandatory duties |
| Respond to support, complaints and appeals | Account reference, correspondence and relevant evidence | Contract where needed to deliver the service; legitimate interests for handling and defending complaints; legal obligation where required |
| Reconcile transactions and keep required records | Order, tax and transaction records | Contract for fulfilment and legal obligation for applicable accounting/tax duties |
| Maintain reliability and improve a feature | Necessary technical diagnostics and actual feature-use measurements | Legitimate interests where justified; any device-access consent requirement still applies |
| Provide optional personalisation, advertising or marketing | Only the categories specified for the actual optional activity | Consent or another applicable ground as specifically disclosed; separate advertising, electronic-marketing and opt-out rules remain applicable |
| Respond to valid legal process or preserve specified material | The particular information within the lawful request or duty | Legal obligation where applicable; another lawful ground only where its conditions are met |
| Respond to a genuine threat to life or vital interests | Only the information necessary for that emergency | Vital interests where applicable; any disclosure, sensitive-data processing or international transfer must also meet its own requirements |
You may object to processing based on legitimate interests for reasons relating to your situation. Where the law permits continued processing, we must have the grounds required by that law. Direct-marketing objections are handled differently: where the applicable right is absolute, we stop that marketing, including related profiling, rather than balancing our marketing preference against your objection.
5. Who receives information
Other participants receive the information you communicate or display to them. Providers supporting hosting, real-time communication, authentication, payments, diagnostics and support receive information needed for their roles. The relevant role matters: a provider acting on our instructions is different from an independent controller handling its own payment, fraud or legal duties.
Information may also be disclosed to competent authorities or other recipients when legally required or otherwise lawfully justified, including for child-protection reporting, valid legal process and protecting people from serious harm. Requests are subject to applicable law; this policy does not promise unrestricted access to private communications.
If a reorganisation or transfer of the business affects personal information, it must be handled consistently with applicable law, including required notices and safeguards. A change of ownership is not permission for an undisclosed incompatible use.
Our disclosures are limited by the purpose and legal basis involved. We do not assume that common ownership alone permits unrestricted pooling of information across brands. Professional advisers, auditors or dispute handlers may receive relevant information where lawfully needed for their role. Their inclusion does not authorise access to every communication.
For a government or legal request, the relevant considerations include the requesting authority, jurisdiction, legal basis, scope, available records and applicable restrictions. A request to preserve existing information is not the same as an order to disclose it or a request to start future surveillance. User notice may be required, permitted, prohibited or delayed depending on the situation; we do not promise that every request will be disclosed to the affected user.
Information described as anonymous or aggregated is treated that way only if the applicable legal standard is met. Pseudonymous identifiers and data that can reasonably be linked back to a person remain subject to the relevant protections.
| Recipient or service | Information involved and purpose |
|---|---|
| Agora | Live audio/video and connection/session data needed to carry the call |
| Tencent IM | Account/session identifiers, signalling and messaging information needed to operate communications |
| Google/Firebase and Meta/Facebook, when chosen for sign-in | Authentication and the profile fields permitted in the sign-in flow; these providers also have their own account and security purposes |
| DataRangers/BytePlus analytics | Feature events, account identifier, age, gender, country, membership status, language/platform and acquisition channel for usage measurement and product analysis |
| Hosting, storage and delivery services | Website requests, account/profile records, uploaded content and technical records needed to host and operate the Service |
| The payment provider identified in your checkout | Payment credentials entered in its checkout, order and transaction information for payment execution, fraud checks and reconciliation; its own legal obligations can make it an independent controller for those activities |
| Support and safety systems | The account/room reference, correspondence and relevant evidence needed to handle the particular request or report |
The scope of a provider's access follows the service it supplies. Selecting a social sign-in does not make all account information available to every other sign-in provider.
6. How long information is kept
Retention depends on the purposes, account status, legal obligations and specific unresolved disputes or safety matters described below. We delete or effectively anonymise information no longer needed for a lawful purpose.
| Record category | Retention criterion and end of use |
|---|---|
| Account and profile records | Keep the information needed to maintain the account while it is open. On a verified closure request, remove or de-identify information no longer needed, separating any specific records retained for a transaction, dispute or legal duty |
| Profile images and submitted communications | Retain for the profile or communication feature and any identified support, safety or legal purpose. Removal from a profile or closing an account triggers assessment of associated copies; copies already received by another participant are outside that action |
| Room metadata, safety images, risk signals and reports | Assess from the interaction or report date against the particular safety investigation, appeal and applicable preservation duty. When that purpose ends, remove the evidence or retain a less identifying record if sufficient; a risk label alone does not justify indefinite retention |
| Technical and analytics records | Keep identifiable events only for the operational, fault-investigation or measurement period for which they are needed. Use aggregation or de-identification where individual records are no longer necessary |
| Orders, payments, refunds and chargebacks | Count from the transaction and, where relevant, the final resolution of the dispute. Retain the records required for the applicable tax, accounting and payment-dispute periods, rather than retaining unrelated chat content with a receipt |
| Support and privacy correspondence | Retain while resolving the case, then only the record needed to document the response, honour a choice or meet an applicable claims or legal period |
| Backups, vendor copies and specific legal holds | Apply the relevant deletion instruction to active systems and providers; isolate retained backup or held records from ordinary use. Release a hold when its legal purpose ends and remove residual copies through the relevant backup/vendor lifecycle |
A request can cover a particular category without closing your account. We explain any applicable exception when responding to an erasure request.
Routine safety screenshots, where the feature is used, are retained for no more than three days from capture. If a screenshot is needed for a specific report, appeal, investigation or legal preservation duty, the relevant copy can be retained separately for that purpose. We limit access and review the continuing need; the exception does not extend routine retention of all room images. This rule covers retained copies held for us by our service providers. Backup handling remains subject to the restrictions below.
Deleting an account, cancelling a subscription, removing content from display and erasing every retained record are different actions. Where a legal preservation duty applies, relevant information may need to remain despite an ordinary deletion request. See our Account Deletion and Privacy Requests page.
Retention criteria include the original collection purpose, whether the information is still needed for the feature, whether a less identifying record will suffice, the applicable claim or statutory period, and the scope and review status of a specific hold. A safety record is not kept indefinitely merely because it might one day be useful.
Backup expiry is different from deletion in active systems. If a backup is restored, we reapply applicable deletion instructions and access restrictions so that deleted information does not return to ordinary use. The retention details above describe the backup and provider lifecycle; erasure is not necessarily simultaneous across systems.
7. International handling
Communicating with a participant in another country may make the information you share visible there. Service providers or authorised personnel may also handle information outside your country, depending on the actual infrastructure and access arrangements.
The Service connects people across countries and uses the communication, authentication, analytics, hosting and payment services listed above. The location of another participant and the providers involved can differ from your location. The controller's postal address does not identify every storage or processing location.
Where an EEA, UK or other law restricts a transfer, the transfer must meet that law's requirements, including an applicable adequacy decision, contractual safeguards or another permitted basis. Acceptance of the Terms is not a blanket consent to restricted transfers. Contact the privacy address for information about the destination and safeguards applicable to your data, including a copy of relevant safeguards where available, with necessary protection for confidential information.
8. Cookies, analytics and advertising
Cookies, local storage, SDKs and similar technologies may be used in delivering the features described in our Cookies and Similar Technologies notice. That notice identifies the actual technologies, their purposes, lifetimes and available controls. Browser settings alone do not replace a consent or opt-out mechanism required by law.
We use DataRangers analytics to measure feature use, acquisition channels and membership activity. Events can be linked to an account identifier and profile attributes; they are not necessarily anonymous. Acquisition-channel information helps measure how visitors reach the Service. The presence of a sign-in SDK is not itself a declaration that it is used for advertising.
For an applicable objection, marketing withdrawal, or opt-out of sale, sharing or targeted advertising, use the privacy contact on this page and identify the website and browser or account concerned. The Cookies and Similar Technologies notice describes device-level controls. We assess disclosures under the applicable legal definitions rather than assuming that describing a recipient as an analytics provider removes an opt-out right.
Some analytics attributes use default values when an account attribute is missing. An age or gender value in an analytics event is therefore not necessarily verified information about a person.
9. Your choices and rights
Depending on applicable law, you may ask to access, correct, delete or receive a portable copy of information; restrict or object to processing; withdraw consent; opt out of sale, sharing or targeted advertising; limit certain uses of sensitive information; or challenge qualifying automated decisions. The scope and exceptions differ by jurisdiction.
Send a request to privacy@monkeychat.fun. Our Account Deletion and Privacy Requests page explains what to include, verification, response periods and complaints. You need not close your account to exercise a privacy right. We will not unlawfully discriminate against you for doing so. You may also complain to your competent data protection authority, including the UK ICO or Hong Kong PCPD where appropriate, and an EEA supervisory authority where you live, work or believe an infringement occurred.
For California residents, the Regional Privacy Notice explains applicable categories and practices during the preceding 12 months and submission methods. A lawful exemption from a right does not justify ignoring a request.
Communications and device settings
Service notices, receipts, safety messages and responses to requests are different from promotional communications. Where promotional messages are offered, use their unsubscribe route or contact our privacy address to exercise the applicable marketing choice. A limited suppression record may be needed to honour a choice; it must not be repurposed to continue the marketing you declined.
Camera, microphone, photos, location and notification permissions are managed through the relevant device or feature settings. Turning off a notification permission does not necessarily unsubscribe an email address. Clearing cookies does not erase an account. The request page explains the action that corresponds to each outcome.
10. Age and children
The Service is for people aged 18 or older who meet the Terms' eligibility requirements. Parental permission does not allow an underage person to use it.
If you believe a child has used the Service or supplied information, contact support@monkeychat.fun or privacy@monkeychat.fun. Someone seeking help about harm connected with the Service does not need an account or need to be old enough to use the Service. Information associated with a suspected child must be handled under the applicable child-protection, privacy and preservation requirements; it is not automatically all retained or all immediately erased.
11. Security and updates
No internet service or interaction is risk-free. Avoid sharing sensitive details with strangers and contact us if you suspect unauthorised account access. If a personal-information breach requires notice to individuals or a regulator, we will provide that notice as required by the applicable law. This policy does not represent that the Service is end-to-end encrypted.
The website and account API use HTTPS. Account authentication and session credentials control access to account functions, and communication services use session authentication. Camera and microphone access is subject to browser permission. These measures protect particular parts of the connection and account flow; they do not make a conversation end-to-end encrypted or prevent another participant from making an external copy. Keep your sign-in account secure and do not share session credentials.
We will identify the effective date when this policy changes and provide additional notice or obtain consent where required for a material change or new purpose. A revised policy does not retrospectively authorise an incompatible use of previously collected information.
Contact: privacy@monkeychat.fun; Bigglesworth Tech Limited (Hong Kong registration no. 77649784), Room 1911, Lee Garden One, 33 Hysan Avenue, Causeway Bay, Hong Kong.