Privacy Policy

Last Updated: May 24, 2026

Effective Date: April 9, 2026

Welcome to Randoms Chat ("the App"), operated by gigasonet ("we," "us," or "our"). We are committed to protecting your personal data and maintaining full transparency about how we handle information on our anonymous, login-free platform.

By accessing or using Randoms Chat, you agree to the collection, usage, and disclosure practices described in this Privacy Policy. If you do not agree with these terms, please do not use our services.

1. INFORMATION WE COLLECT

A. Information You Voluntarily Provide

Randoms Chat is fundamentally designed as an anonymous platform. We do not require an account registration, email address, phone number, or social media linking to use the core features. However, you may choose to provide:

• Usernames: A temporary or custom display name of your choice (automatically initialized as a random alias, customizable by you).

• Avatars / Profile Photos: Images uploaded from your device or selected from standard preset modules to customize your user profile.

• Communication Content: Text messages, images, videos, and offline mailbox transmissions sent voluntarily within random match sessions or friend-list chats.

B. Information Collected Automatically

To deliver structural persistence, synchronization, and secure features without a formal login system, the App automatically collects specific device metadata:

• Persistent Device Identifiers: On Android, we process the hardware-bound Android ID; on iOS, we process the Identifier for Vendor (IDFV). These identifiers act as your anonymous account key to locally and securely persist your settings, premium state, friends list, and structural app configurations.

• Mobile Advertising Identifiers: We declare permissions to access the Google Advertising ID (AAID) on Android and the IDFA identifier on iOS devices to facilitate programmatic monetization.

• IP-Based Geolocation: We utilize lightweight diagnostic fallbacks (ipapi.co / ipinfo.io) to evaluate city and country-level positioning. This data is processed to optimize matchmaking regions and is hidden based on user preference toggles (Ghost Mode).

• Push Notification Tokens: Firebase Cloud Messaging (FCM) device tokens are securely registered to route operational real-time notifications to your terminal.

2. DEVICE PERMISSIONS REQUESTED

To facilitate native media exchanges and application integrity, the App requests explicit access to the following operating system frameworks:

• Photo Library / Media Storage: Accessed strictly when you initiate an outbound profile customization or attach media files within chat features.

• Biometric Authentication: Used locally via device hardware (Fingerprint/Face ID) to execute local app-lock security routines, if enabled by you in settings.

• Network / Internet Access: Standard permission required to interact with cloud infrastructure, execute matchmaking queues, and manage active web-sockets.

3. HOW WE USE YOUR INFORMATION

We process aggregated and device-specific telemetry data strictly under legitimate interest and operational performance parameters:

• Session Persistence: Mapping continuous application updates, inventory entitlements, and social contacts to your anonymous hardware ID without requiring credential management.

• Real-Time Communications: Running active regional lookup engines to pair anonymous communication channels securely.

• Premium Entitlement Tracking: Utilizing network hooks to confirm active transaction states and custom UI tiers.

• Infrastructure Optimization: Analyzing internal runtime diagnostics to mitigate edge-case exceptions, crash dumps, and system latency.

4. THIRD-PARTY DATA SHARING & INTERACTIONS

To manage scaling backend pipelines, monetization tiers, and billing networks, the App securely integrates specialized third-party software development kits (SDKs). These entities process data independently under their respective privacy policies:

• Infrastructure & Sync: Google Firebase (Auth, Cloud Firestore, Realtime Database) acts as our primary global database management framework for real-time signaling.

• Media Optimization Hosting: Cloudinary processes, transforms, and hosts dynamic binary objects (images/videos) transmitted inside communication windows.

• Subscription & Billing Engine: RevenueCat processes local store identifiers to track entitlement metrics for Weekly, Monthly, Annual, or Lifetime digital passes.

• Programmatic Advertising Networks: Google AdMob orchestrates dynamic monetization. AdMob utilizes specific device Advertising Identifiers (AAID/IDFA) to serve tailored commercial content. This includes mediation adapters mapping requests dynamically through networks such as Unity Ads and Meta Audience Network (Facebook).

Note: By default, the App executes unified user consent frameworks. If customized consent parameters are denied, the App routes alternate fallback requests enforcing restricted, non-personalized advertising setups.

5. IN-APP SECURITY & PRIVACY CONTROLS

To safeguard user interactions against digital exploitation, the App embeds strict operational features:

• Unified Media Blurring: All inbound communication files (images/videos) delivered across matchmaking interfaces are automatically initialized with blurred safety masks. Content is revealed only upon explicit, manual touch interaction by the receiver.

• Screenshot & Recording Restrictions: The application embeds active hardware hooks (expo-screen-capture) within the core media viewer interface to actively block and prevent screen capture or local screen recordings of your shared transient content.

• Server-Side Access Rules: We implement rigorous cloud configuration rules to restrict programmatic database lookups exclusively to authenticated, matching communication routes.

6. DATA RETENTION & VERIFIED DELETION POLICY

A. Retention Metrics

• Dynamic Chat Content: Conversations initiated inside standard random match configurations and persistent friend channels remain securely accessible via cloud nodes to preserve continuity across active device sessions.

• Account Profiles: Your assigned alias and active avatar choices remain associated with your device ID until explicit account removal is initiated.

B. Manual & Verified Data Deletion Process (Anti-Fraud Identity Verification)

Because Randoms Chat functions as a highly confidential, login-free environment, we do not maintain personal records like passwords or verified emails to instantly authenticate identity. To prevent malicious actors from requesting the deletion of an innocent user’s profile data, we enforce a strict, mandatory identity verification process.

To completely purge your profile data, chat histories, active connections, and server records from our systems, you must send a formal deletion request via email to kirtanmangukiya32@gmail.com containing the following two mandatory verification attachments:

1. The Hidden Identity Verification Screenshot: Navigate to the internal App Settings, locate the Android ID / Device ID display block, click the "Eye" icon on the right side to unhide and reveal the full alphanumeric sequence string, and take a screenshot.

2. The Active Profile Sidebar Screenshot: Open the primary application navigation drawer/drawer layout showing your current random username name and active avatar preview clearly, and take a screenshot.

⚠️ Compliance Notice: Deletion requests submitted without both matching screenshots cannot be programmatically verified against our database keys. Such unverified requests will be immediately discarded for security purposes to protect our users. Upon receipt of valid matching screenshots, all related cloud architecture elements linked to that specific hardware footprint will be permanently and unrecoverably purged from our production nodes within thirty (30) business days.

7. AGE RESTRICTIONS & TARGET AUDIENCE

Randoms Chat is strictly intended for adult audiences and mature users. The service requires all interacting parties to be at least eighteen (18) years of age or the age of majority in their jurisdiction.

The application does not intentionally engineer logic pipelines to harvest information from minors or children under the age of thirteen (13). We maintain strict report flows (reason_child_safety) to flag interactions violating community standards. If we discover or are systematically alerted that device footprints belonging to a minor have bypassed standard operational boundaries, all linked cloud records will be immediately expunged.

8. CONTACT INFORMATION & COMPLIANCE

For additional clarifications regarding this operational framework, compliance guidelines, or to route your verified account deletion dossier, please contact us at:

• Email Contact: kirtanmangukiya32@gmail.com

• Corporate Entity: gigasonet