VibezIn Privacy Policy

Operator and scope

VibezIn is operated by Mekala Revanth, 9th Line, Srinivasaraopet, Guntur, Andhra Pradesh 522004, India. This policy covers the VibezIn Android app, Web app and related support. Contact privacy@vibezin.com for privacy questions and rights requests. Other sites and services you choose to visit have their own privacy practices.

Identity, eligibility and account security

We process your Firebase account ID, email address, sign-in provider, verification status and security/session events. Firebase Authentication handles email and password credentials and sends a verification link for email signup. Google sign-in supplies the account details you authorize Google to share. A phone-linked account uses the verified number for the supported identity features.

The age screen transmits a self-reported date of birth to calculate eligibility. The acceptance record stores eligibility, the minimum age, document version, links and time of acceptance. The account acceptance record excludes the date of birth. We use these records for account operation, eligibility, account recovery and protection against abuse.

Profile, social activity and content

We process your display name, Vibe ID, profile media, bio, interests, language, moods, relationship choices and preferences you provide. We use post, poll, VibeClip, story, comment, reaction, Fire, Revibe, share, rating, viewing and game-result activity for the features you use, moderation and feed recommendations. Media can include photos, videos, audio, voice notes and information you include in them. Restrict the audience where the feature offers that choice. Public material can be shared outside VibezIn.

VibezIn processes chat messages, participants, media attachments, delivery and activity information to deliver conversations and enforce access controls. Communities and Channels use member and role information for discovery, invitations, membership, publication and moderation. Some visible content can be retained by its recipients or reproduced outside VibezIn.

Camera, microphone, files and calls

The camera, microphone and chosen photos, videos and files support capture, editing, voice notes, attachments and voice or video calls you initiate or join. Calling processes signaling, call participants, connection information and call state. Call media may travel over a direct connection or the configured relay. Bluetooth access supports compatible call audio devices. You can manage these permissions in device settings.

Contacts and Nearby

When you select the Contacts audience for supported stories or Flash Vibes, the app reads phone numbers available under your permission. The publish request sends up to 1,000 numbers to match verified VibezIn accounts and uses matched account IDs to determine who can view the content. Choose a different audience to use the feature without matching contacts.

If you enable Nearby, the app uses a fresh location fix and its accuracy to provide nearby results. Turning Nearby off sends a request to clear the saved location. You can manage location permission in device settings. Approximate region, language or places you enter can also be used to personalize the service.

Notifications, preferences and security information

We process push tokens, notification preferences, relevant device or browser information and delivery events for notifications. Web storage and device storage can keep sessions and preferences, including your chosen theme. The service and its infrastructure may process network addresses, request times, integrity signals, errors and limited security logs to operate, troubleshoot and protect the app. You can control notifications in VibezIn and in system or browser settings.

Advertising and recommendations

Feed interests and engagement signals help select recommendations. Where Vibe Ads is enabled, campaign context, broad region or language and supported public activity can be used to select ads. Advertising interests are an optional setting. The service can record impressions and clicks for delivery, measurement and abuse prevention. Where Google Mobile Ads is enabled, Google can process device or ad identifiers, network information and ad interactions under the ad settings and choices presented in that build. Payment and campaign records apply to transactions actually offered. Links to advertisers lead to services with their own policies.

Who receives data

People in your chosen audience receive content and profile information necessary to use the feature. Google and Firebase provide authentication, database, function, push and integrity services. Cloudflare provides configured media storage and delivery and, where enabled, call relay. Authorized personnel and contracted providers can access information needed to deliver support, investigate security and safety reports or administer the service. We can disclose information to competent authorities or affected parties where required or permitted by applicable law, limited to the relevant purpose.

Safety and rights requests

We process the details you submit in reports, blocks, appeals and rights requests, together with relevant account and content references and the decisions made. Authorized reviewers use this information to investigate, enforce rules and handle appeals. We limit access to case information according to role and need. An urgent restriction can be applied while a report is reviewed.

Retention and account removal

We keep information for the period needed for its purpose and applicable obligations. An accepted account-deletion request starts a 30-day cancellation period. After it ends, the cleanup job removes eligible account and associated data and retries provider failures. See the Account Deletion page for the request and cancellation steps.

Registration information after closure: Applicable Indian intermediary rules require retention of registration information for 180 days after account cancellation or withdrawal. The code includes an optional 180-day legal_registration_records archive, but the currently selected LEGAL_RECORD_RETENTION_ENABLED=false setting prevents new records from being archived through that mechanism. The account-closure job can delete original account data. We cannot yet claim verified 180-day preservation after cancellation; this implementation must be enabled and tested before production release. Security logs: Selected logs routed to our Mumbai Google Cloud Logging bucket are retained for 180 days. Logs in our default bucket are retained for 30 days. Audit logs in Google's required bucket are retained for 400 days. Moderation evidence: VibezIn records reports and moderation actions in Firestore. Applicable Indian intermediary rules require preservation of certain removed or disabled information and associated records for 180 days, or longer under a lawful direction. The optional 180-day legal_moderation_records archive exists in our code but is currently disabled in the deployment configuration being prepared. Its archived metadata does not by itself preserve original Cloudflare R2 media files. We cannot currently guarantee recovery of permanently deleted evidence; preservation implementation and verification are required before production release. Financial records: VibezIn does not accept payments, paid subscriptions or advertiser payments at launch. We hold no customer payment records for these features. Backup and provider copies: Point-in-time recovery is disabled for our default Firestore database. Firestore retains historical document versions for up to one hour. This database has no scheduled Firestore backups. Presence and typing information: Device connection and typing session entries are cleared on disconnect. We keep the latest last-seen value while the account is active. When account access is disabled, we clear presence and linked chat typing records. Retention for a legal hold or mandatory preservation ends according to the applicable obligation.

International processing and regional rights

Google Firebase supports app services and Cloudflare R2 stores media. Firebase Authentication processes data in the United States. Other processing locations depend on the service and its configuration.

We use personal data to provide requested app features, protect accounts and comply with applicable obligations. Where applicable, you can request access, correction, deletion, consent withdrawal or grievance handling at privacy@vibezin.com.

Eligibility, choices and policy updates

Minimum account age: 18. Regional eligibility requirements apply. If you believe a child is using VibezIn below the applicable age, contact safety@vibezin.com. You can edit your profile, adjust permissions, choose available audiences, change advertising preferences, block or report accounts and request deletion. For help exercising privacy rights use privacy@vibezin.com.

Grievance process: Mekala Revanth handles grievances for VibezIn. Email safety@vibezin.com with your Vibe ID, the relevant post or profile link if available, and a short description. We will acknowledge your complaint, review it, and share the outcome. To request a review of our decision, reply with your case reference and explain what you want us to reconsider. We publish the date and version of this policy. We communicate material changes and obtain any permission required by applicable law.

Planned 30-day Recently Deleted recovery

A universal 30-day Recently Deleted recovery window for deleted posts, messages, comments, photographs, videos and Cloudflare R2 objects is not currently available. Some deleted content may become unrecoverable immediately. We plan to introduce a 30-day recovery feature after its storage, access controls, deletion and legal-preservation processes are implemented and tested. Legally required preservation may apply independently of that future feature.