SUPER VC · PUBLIC INFORMATION

Privacy Policy

Brand: Super VC
Legal Business Name: Manoj Kumar S
Operated by Manoj Kumar S
Website: https://supervc.in
This notice explains how Super VC handles information when you visit our website or use our app. It covers information you provide, information needed to operate the service, and service providers involved in delivering it. Questions and privacy requests can be sent to supervc777@gmail.com.
Questions about your information?
supervc777@gmail.com

1. Account and profile information

Registration collects your name, email address and mobile / WhatsApp number to create and identify your Super VC account, maintain your profile and support account-related requests. A WhatsApp number does not itself authorise promotional messaging. Where an opt-in is offered, it is handled separately.
Email/password authentication uses a server-side password hash rather than storing your password in readable form. Profile photos, where supplied, are used to display your profile.

2. Google Sign-In information

If you choose Google Sign-In, Super VC requests your Google account identity, email address, basic profile name and available profile photo, using the openid, email and profile scopes.
The Laravel backend verifies Google's signed identity before creating or signing in to a Super VC account. The stable Google subject identifier (sub) identifies the account; matching email addresses alone do not silently merge accounts. Super VC does not ask for your Google password. Google information is used for authentication and your account profile, not to access Gmail, Drive or contacts.
Super VC uses its own application session after sign-in. Removing Google's app permission is separate from requesting deletion of your Super VC account and records.

3. Device, app and session information

Installation identifiers, platform information and session records help recognise a signed-in installation, maintain login and revoke sessions when appropriate. Your browser stores application cookies, including secure session cookies. The hosting service also processes ordinary connection information, such as IP addresses and request metadata, to deliver requests and help investigate security or service problems.
Camera and microphone access is requested for broadcasting. Device permissions can be managed through your browser or operating system. Denying a permission can prevent the related feature from working.

4. Wallet, transactions and recharge proofs

We keep credit balances, wallet transactions and registration-grant records to calculate balances, prevent repeated credits and maintain an account history. Where recharge is available, recharge requests, amounts, payment references and uploaded proof are used to review the request and investigate payment disputes.
Payment screenshots may contain financial or third-party details. Share only information needed for the request; do not send passwords, card security codes, PINs or unrelated account details. Uploading proof is not confirmation that a recharge has been approved.

5. Live broadcasts and community activity

Live-session information can include the broadcast title, location or place you provide, schedule, timestamps, session status, participant records and comments. These records support discovery, joining, scheduling, moderation and credit accounting. Content and profile details you share in a broadcast may be visible to other participants.
Agora provides real-time audio/video transport. Where recording is enabled for a session, recording files and related processing/review metadata may also be handled. Do not broadcast personal information or other people's content without the necessary permission. Viewers may capture content independently of Super VC.

6. Notifications and support

In-app notification records and read status help deliver account and broadcast updates. On supported native devices, Firebase Cloud Messaging (FCM) registration tokens and installation information are used for push delivery. Notification availability depends on permissions and configuration. FCM is used for messaging, not Firebase Authentication or Firestore account storage.
Support enquiries, messages and attachments you choose to send are used to investigate issues and respond to you. This includes email sent to supervc777@gmail.com and in-app support where available. Please do not include passwords or authentication tokens in support messages.

7. Storage and service providers

The current production account system uses a Laravel backend and Hostinger MySQL for users, authentication mappings, wallets and application sessions. Google Sign-In maps to this same account system rather than a separate Google-managed application database.
Hostinger provides application hosting and the MySQL database. Agora processes live audio/video and related session information. AWS S3 is used for private media and recording storage where those features are enabled. FCM processes device tokens and notification payloads for push delivery. Google OAuth provides identity verification when you choose Google Sign-In. Email providers process support correspondence.
Providers receive information relevant to the service they perform and operate under their own service terms and privacy notices. Processing locations can depend on hosting and provider configuration; this notice does not promise that all data stays in one country. Earlier service records may remain in legacy storage during migration; their deletion has not been completed or represented as complete.

8. Security and access

The application uses HTTPS, server-side password hashing, protected session cookies and access controls to help protect account information. Backend credentials are not intended for public pages or app bundles. No internet service can guarantee absolute security.
Information may be accessed by authorised personnel for support, administration, security or legal obligations. Limit the personal information you share publicly and report suspected unauthorised access to our contact email.

9. Retention and deletion requests

Retention depends on the purpose and type of record. Account and session information supports access to the service; wallet and transaction records may need to be retained for accounting, fraud prevention, dispute handling or legal obligations. Media may have separate lifecycle settings. Backups and provider-held records can have different retention processes.
We do not promise a fixed retention or deletion deadline in this notice. To request account deletion, email supervc777@gmail.com from your registered email where possible, with the subject 'Super VC account deletion'. We may need to verify that you control the account; never send your password. We will review the request and explain any records that must be retained. Logging out or uninstalling the app does not itself delete server records.

10. Your choices and requests

You can contact supervc777@gmail.com to request access to your information, correction of inaccurate details, account deletion, or to raise a privacy concern. Available rights and any exceptions depend on applicable law. Identity verification may be required before account information is disclosed or changed.
You can manage camera, microphone and notification permissions through your device settings. If you believe a child has provided information without appropriate authorisation, contact us so we can review the situation. Changes to this notice will be published on this page.
Super VC
Operated by Manoj Kumar S
supervc777@gmail.com
© 2026 Manoj Kumar S