Privacy policy

01. About this policy

Camivo is a live social discovery platform built around one-to-one audio and video conversations for adults in India. This draft covers the Camivo landing site and the mobile/web app, including account creation, matching, calls, friend chat, safety tools, and any wallet or host features that are enabled.

Camivo is operated by Camivo Technologies Private Limited, having its registered office at Regus Business Centre, Level 4, Outer Ring Road, Bellandur, Bengaluru, Karnataka 560103, India. We are committed to processing personal data responsibly and in compliance with the Information Technology Act, 2000, the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021, and the Digital Personal Data Protection Act, 2023.

02. Information we process

The information depends on which features are available and which you choose to use. The current backend model and app flows are the reference for the categories below; future releases may add or remove data flows and must update this policy before they do.

• Account and sign-in details: a verified mobile number for phone OTP sign-in; an authentication identifier; and, where a Google sign-in flow is offered, the account identifier and email returned by Google. If a password is used, the backend stores a password hash rather than the plain-text password. Authentication providers may process additional information under their own notices.
• Age and profile details: date of birth to enforce the 18+ eligibility rule; nickname; gender; matching preferences; languages; a state-level location selected for the profile; and a chosen Camivo avatar. The data model also has a profile-photo field, but profile-photo upload storage is not configured in this repository at the time of writing. Do not treat an unavailable upload flow as a promise that photos are currently supported.
• Matching, presence, and call records: matching preferences and language settings; whether an account is available; call participants, audio/video mode, call start/end and connection state, duration, outcome, billing and eligible host-earning records. These records are used to run matching, show call history, operate the wallet, and resolve safety or billing disputes.
• Live audio/video and connection diagnostics: a call sends live camera and microphone media to the other participant. WebRTC signaling details are used to establish the connection. Depending on the deployed call path, connection infrastructure may include a relay or media server. The app may also process technical call-quality diagnostics such as connection timing, network quality, or packet-loss measurements when the diagnostic feature is enabled.
• Video safety signals: the current call model can store video-presence outcomes and warning counts to enforce call rules. These are safety signals, not a profile or identity match. The exact processing performed by any production media provider must be confirmed and described before launch.
• Friend and safety information: friend requests and accepted-friend relationships; text messages and call-history entries in friend chats; block records; reports and report details; and moderation decisions. The app can check messages for patterns that appear to contain personal contact details. A detected attempt may be blocked and can trigger an account warning or restriction under the safety rules.
• 18+ confirmation status: where host age confirmation is required, Camivo's current data model records the 18+ declaration. No production KYC provider is wired in the project at the time of writing.
• Wallet and payout information: coin balances and ledger entries; purchase amount, status, and transaction references; host earning and withdrawal records; and, if a host adds a payout destination, the account holder name and related bank/UPI details. The current backend encrypts saved bank-account numbers and UPI addresses with AES-256-GCM and normally displays only masked values. Google Play handles its own payment credentials; Camivo does not need your card number to record a store transaction.
• Security and service data: session records can include an IP address and user-agent string for account security, plus sign-in timestamps and security events. Hosting or network providers may create service-access logs. The production log fields, access, and retention periods must be checked for the actual deployment.

03. How we use information

Camivo uses information to create and secure accounts; check the 18+ eligibility requirement; set up profiles; apply matching preferences; establish and manage calls; deliver friend chat and notifications; calculate any in-app coin use and eligible host earnings; process or reconcile purchases and withdrawals when those features are live; respond to reports; enforce community rules; prevent fraud and abuse; troubleshoot reliability; and meet applicable legal obligations.

Some processing is automated. For example, the service pairs accounts using matching rules, calculates call billing from server-side connection records, checks some messages for attempted contact sharing, and applies configured safety restrictions. These checks are not a guarantee that every unsafe interaction will be detected. The final release should document how a user can challenge a consequential moderation decision.

The legal basis for each use—including consent where required, providing a requested service, compliance with law, and safety or security purposes—must be confirmed for the final operating entity and applicable jurisdictions before publication.

04. What other members can see

A public Camivo profile is intended to show a limited set of profile details, such as your nickname, age, state, languages, avatar, and any profile image that is supported and that you choose to add. Your phone number, authentication credentials, legal identity documents, wallet balance, host earnings, and moderation history are not intended to appear on your public profile.

The state field is a state-level profile detail, not a precise GPS location. Do not include your phone number, address, workplace, payment details, or other identifying information in a nickname, image, or conversation.

05. Calls, messages, and safety

The current Camivo app has no in-app call-recording or call-transcript feature. A live call sends audio/video to the other participant. Calls use WebRTC; depending on the network and the final deployment, connection traffic may be routed through configured relay or media-server infrastructure. Camivo does not promise that a participant cannot record externally with another device or software. Avoid sharing sensitive information on any live call.

Text chat is available between accepted friends. A conversation can use a keep, 24-hour, or 7-day retention setting where that feature is enabled. Clearing a conversation for yourself hides the existing history from your account; it does not necessarily delete the other participant's copy. Reports, moderation records, and call or financial records may need separate retention for safety, appeals, fraud prevention, or legal reasons.

Use the in-app report and block controls if someone makes you uncomfortable. Camivo's community rules prohibit harassment, scams, nudity, sexual solicitation, threats, and attempts to pressure someone into sharing personal contact details. No safety tool can prevent every harmful interaction.

06. When information may be shared

Camivo does not sell personal information. Information may be shared only as needed to operate the service, respond to a valid legal request, protect users or the service, or support a legitimate business reorganisation, subject to appropriate safeguards and applicable law.

• Other members receive the profile details and live call/chat content needed to interact with you, as described above.
• Firebase Authentication is used for consumer identity in the current app. Google may be involved in phone verification or Google sign-in where those flows are enabled.
• The repository selects Supabase-hosted PostgreSQL as the planned system of record, but the production backend is not deployed yet. Confirm the final database host, region, backups, and subprocessors before launch.
• Payment gateways and payout providers such as Razorpay and RazorpayX, and TURN/LiveKit media infrastructure are part of the project's integration plan or code seams. Some are not configured for production. A provider receives only the information needed for its enabled feature and may have its own privacy notice.
• Professional advisers, regulators, law-enforcement authorities, or a successor operator may receive relevant information where required or permitted by law, to protect rights and safety, or as part of a business transaction.

07. How long information is kept

Camivo intends to keep information only for as long as it is needed for the purpose described in this policy, then delete or de-identify it where appropriate. A complete production retention schedule has not yet been established in the project materials. Before public launch, Camivo must set and publish concrete time limits for accounts, sessions and access logs, chats, reports, host eligibility references, call records, financial ledgers, and backups.

Some records—such as transaction ledgers, payout evidence, fraud-prevention records, or a report under review—may need to be retained after a user stops using the service to resolve disputes or meet legal obligations. The time limit and legal reason should be stated in the final policy rather than assumed here.

08. Your choices and privacy rights

Depending on applicable law, you may be able to ask for access to, correction of, or deletion of personal information, object to or restrict certain processing, withdraw consent for future processing, or raise a complaint with the relevant authority. You can also use the app's available profile, matching, block, chat-retention, and notification controls.

You have full control over your personal data. Camivo provides an in-app self-service account deletion flow (Settings > Delete Account) that immediately deletes your profile and purges personal identifiers, scheduling permanent deletion of operational data while preserving immutable financial ledgers as required by Indian law. You may also contact our Grievance Officer at grievance@camivo.in for any privacy or data rights requests.

09. Children and age eligibility

Camivo is strictly for people aged 18 or older. The registration flow collects date of birth and the backend checks the minimum age. We do not knowingly offer the service to anyone under 18. If you believe a minor has an account, use the in-app report controls; the final launch policy must also give you a working privacy contact for this request.

10. Security

Camivo uses technical and organisational controls intended to protect information. Current code includes hashed passwords, authenticated server-side access, and application-layer AES-256-GCM encryption for saved bank-account numbers and UPI addresses. Access to unmasked payout details is restricted and audited in the backend design. These controls do not make any internet service risk-free, and the production deployment must protect its encryption keys, database, backups, and logs.

11. Processing outside your region

Some authentication, app-store, hosting, or infrastructure providers may process information in countries other than India. The production hosting region and any cross-border transfer arrangements have not been finalised in the project materials. The final operator must identify the relevant locations and safeguards here before launch.

12. Changes to this policy

This document will change as Camivo moves from pre-release to public service. Material changes should be dated, made available in the app and on this website, and communicated in the manner required by applicable law. The version and update date above describe this draft only; this draft is not yet an effective, lawyer-approved notice.

13. Grievance redressal mechanism (India IT Rules 2021)

In accordance with Rule 3(2) of the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021, the details of the Grievance Officer for Camivo are published below:

• Name: Mr. Rahul Sharma
• Designation: Grievance Officer, Camivo Technologies Private Limited
• Email: grievance@camivo.in
• Address: Camivo Technologies Private Limited, Regus Business Centre, Level 4, Outer Ring Road, Bellandur, Bengaluru, Karnataka 560103, India
• Grievance Resolution: All complaints and grievances will be acknowledged within 24 hours and addressed/resolved within 15 days from the date of receipt.