Privacy Policy
Effective date: 15 November 2026
Service: RandomMeet. Contact: randommeetapps@gmail.com.
This policy describes information handled by the current RandomMeet website and Android app (package com.randommeet.app), and includes RandomMeet's published Child Safety Standards. It should be read with our Terms of Use.
1. Information we handle
- Account and profile: Firebase account identifiers and authentication information, email address, display name, profile details such as gender and matching preference, language and interest choices, and profile photo if you provide one.
- Matching and service operation: online/presence status, queue and call type, match identifiers and timestamps, block information, and limited previous-match references used for the Premium reconnect feature. Guest matching uses an anonymous Firebase session and server-side counters to apply guest limits.
- Calls and connection: WebRTC signaling (offers, answers, and connection candidates) needed to establish a call, plus connection/network data required for signaling and relaying. A direct peer connection may expose network information such as an IP address to the other participant. When friend calling becomes available, call participants, times, duration and coin charges may be recorded and visible to administrators for service and billing operations.
- In-match text chat: during an active match, participants can send text messages to each other. Messages are stored in Firebase Firestore with the sender's account identifier and timestamp so the active participants can view them. Match cleanup deletes these messages when the match ends.
- Approximate location: we infer your country from your device time zone and language (not GPS) and store a two-letter country code in your profile. Your country and gender are shown to the person you are matched with.
- Safety and moderation: reports submitted about a participant, including reporter and reported account references, selected reason, match reference, review status, and related timestamps. Automated moderation outcomes (violation count, warning/ban status, ban expiry and last violation time) are stored on the offending account. Blocking information is used to prevent future matches.
- Payments: Android subscriptions use Google Play Billing and server-side purchase verification. Older website Premium orders were processed through Razorpay; related records may still be processed for verification, support or refunds. The server stores purchase/account/plan status, expiry, and the Play purchase token for active subscriptions to verify purchases and process eligible refunds. Tokens are stored in server-only records inaccessible to app users. Token removal is triggered when the server processes an expired or revoked subscription or account deletion. Payment providers may process information under their own privacy terms.
- Advertising: when Android ads are enabled, the Google Mobile Ads (AdMob) SDK may process device or advertising identifiers, IP address, diagnostics, and ad interaction data to request, deliver, measure, and protect ads. The app uses Google's consent flow when a consent message is required. Ads are limited to the home/match screen for signed-out and free users; Premium users do not see ads, and the administrator can disable ads for everyone.
- Referrals: referral codes and links identify the user who invited a new account. The server stores referral-code ownership and a server-only reward record containing the referring and newly registered account identifiers, code, reward amount, and timestamp to credit 50 coins once and prevent duplicate claims.
2. Audio and video
Audio and video are exchanged for live calls using WebRTC. The app needs camera and microphone permission for this; you can turn them off in your device settings, but calls will not work without them. The current app does not upload call media to Firebase Storage or record calls. Calls may be peer-to-peer or relayed through a TURN/SFU service when a direct connection is not possible. Participants may independently record, screenshot, or share what they see or hear; avoid sharing sensitive information.
2A. Automated safety moderation
To help keep RandomMeet safe, your device analyses the video you receive from the other participant during calls using free AI models (NSFWJS and TensorFlow.js COCO-SSD) that run locally in the app. The analysed frames are processed on your device only; they are not uploaded, recorded or stored by RandomMeet. If nudity or explicit content is detected, the video may be blurred and the app sends only the match identifier to our servers as an automated report. Accounts that show nudity or explicit content may receive warnings and may be temporarily or permanently banned by automated moderation. Automated detection can be wrong; contact randommeetapps@gmail.com to appeal a ban. The AI model files and code libraries are downloaded from the jsDelivr CDN the first time they are needed.
3. How information is used
Information is used to authenticate accounts, maintain profiles, find compatible matches, connect video calls, apply safety and automated moderation controls, review reports, enforce service rules and guest limits, provide Premium entitlements and coin balances, attribute eligible referrals and issue rewards, deliver and measure enabled ads, prevent abuse, secure and troubleshoot the service, and meet legal obligations.
Accepted friends can see an approximate online or offline status based on recent foreground activity. Status may be delayed or inaccurate when the app is closed, disconnected, or an older version does not report activity. Blocked accounts are excluded from the friend list.
4. Providers and disclosures
RandomMeet uses Firebase Authentication, Cloud Firestore, Cloud Storage, Cloud Functions, and Firebase Hosting. It also uses Google Play services for Android subscriptions and coin purchases, Google Mobile Ads (AdMob) for Android advertising when enabled, Razorpay for legacy website payments, Cloudflare for WebRTC relay/SFU connectivity, and jsDelivr to deliver the on-device moderation libraries. Information may be disclosed to these providers to operate the service, to service administrators for account and safety operations, or to authorities and other parties where required or permitted by law. Check provider terms and privacy notices for their independent processing.
5. Retention and deletion
When an account is deleted, the app deletes the account, profile and profile photo, coin wallet and admin coin-grant history, queue/presence data, match signaling records, block list, and bounded previous-match history, where applicable. Remaining coins are lost. References to the deleted account in safety reports are removed or anonymized, and reports may remain for safety operations until an administrator deletes them. There is no automatic time-based deletion for safety reports.
Payment orders are deleted with the account. A reduced payment record may remain, containing transaction identifiers, amount, status, refund status, and creation time, with account identifiers removed. There is no automatic expiry configured for these reduced payment records, so they may be retained without a fixed time limit for accounting, fraud prevention, disputes, or legal requirements.
Referral reward records may be retained to prevent duplicate rewards, investigate abuse, and reconcile wallet credits. Referral codes are not recycled after account deletion.
Delete your account in Profile after re-authenticating. If you cannot sign in, submit a request using the Account Deletion page. A request may require reasonable account verification. Do not send passwords, one-time codes, payment card details, or purchase tokens by email.
6. Child Safety Standards
These standards apply to RandomMeet's website and Android app. RandomMeet is an adults-only random chat service.
Children are not allowed
RandomMeet is strictly for people aged 18 or older. Children must not create accounts, appear in calls, or use matching, chat, or other service features. The age screen is a self-declaration and does not independently verify identity or age. Do not invite or help a child access RandomMeet. If an account is reasonably believed to belong to someone under 18, access may be restricted or terminated and appropriate steps taken under applicable law.
Zero tolerance for child sexual abuse and exploitation
RandomMeet prohibits all child sexual abuse and exploitation (CSAE), including child sexual abuse material (CSAM), grooming, sexual solicitation of a child, sextortion, trafficking, and any attempt to exploit, abuse, or endanger a child. Do not create, request, show, send, possess, store, or distribute CSAM or facilitate CSAE through live video, audio, text, profiles, links, or any other feature. Suspected violations may result in account restrictions or termination and reporting or disclosure to competent authorities when required or permitted by law.
Sexually explicit or pornographic material and sexual solicitation are prohibited on RandomMeet. Never ask a participant to reveal identifying or intimate information.
How to report a child-safety concern
- During a match, select the flag/report control.
- Choose the closest reason. For suspected child abuse, exploitation, or a minor on the service, choose “Other / Child safety concern” and submit the report.
- For additional details or a concern outside an active match, email randommeetapps@gmail.com.
Do not attach, forward, download, or make copies of suspected CSAM. Provide a description and relevant account or match information only. For immediate danger, contact local emergency services. RandomMeet is not an emergency-response service.
Blocking and ending a match
Use Report to submit a safety report and end the current match. Use Block User to end the match and prevent future matches with that account. Use Stop or leave the call whenever you feel unsafe. Reporting and blocking are not emergency services; if a report cannot be submitted, use Block or Stop to leave the call.
Review and appropriate action
Reports are made available for review by the RandomMeet administrator. Depending on the information and applicable law, action may include restricting or terminating an account, removing access to the service, retaining relevant records for safety or legal purposes, and reporting or cooperating with competent authorities. RandomMeet does not claim that live calls are continuously monitored, that call media is recorded, or that every report will receive a specific outcome or response time.
Child-safety and grievance contact
Contact the RandomMeet Safety Team at randommeetapps@gmail.com. This mailbox should be monitored by the responsible person or team and able to respond to questions about child-safety practices and user grievances. No individual's name or postal address is published on this page.
Additional safety guidance
- Do not share your address, phone number, passwords, financial details, or other sensitive information with strangers.
- WebRTC calls may expose network information, such as an IP address, to the other participant. Another participant may capture or share what they see or hear.
- Be cautious with links, requests for money, or requests to move a conversation elsewhere.
7. Your choices and privacy requests
You may update supported profile information in the app, use its account-deletion control, block or report a participant, and contact us about privacy requests or grievances. We will handle requests under applicable Indian data-protection and other laws, including the Digital Personal Data Protection Act, 2023 and rules to the extent applicable and in force. Applicable rights may depend on the law and the circumstances.
8. Security
We use Firebase and provider security controls to protect information, but no internet service can guarantee absolute security. Use a strong sign-in method and do not share credentials or verification codes.
9. Contact and grievances
Privacy, support, and child-safety contact: randommeetapps@gmail.com.
Grievances and child-safety concerns: email randommeetapps@gmail.com.
Public contact: RandomMeet Support, randommeetapps@gmail.com. No individual's name or postal address is published on this page. This policy is not legal advice; have it reviewed against actual data flows and applicable requirements.