1. About this policy
This policy applies to the Call Mitra mobile application and this website. It explains the information we collect, why we use it, who may process it and how to request access, correction or deletion.
2. Who operates Call Mitra
CALL MITRA is a sole proprietorship operated by Dipu Kumar Sharma, based in Goregaon West, Mumbai, Maharashtra, India. Contact app9.india@gmail.com or +91 8169027622 for privacy questions and grievances.
3. Eligibility
Call Mitra is for adults aged 18 and over. The app records an adult self-declaration during account setup. We may suspend an account where age or identity information appears inaccurate.
4. Registration information
The app uses a mobile number and OTP to authenticate accounts. Registration includes a name and gender, with optional email and referral information. Authentication and session records support sign-in and account security. OTPs and passwords should never be submitted through website support forms.
5. Profile information
The app stores user and listener profile information. Legacy data models also contain optional birth and family fields; their current use and any historic retention must be reviewed. Do not assume that a field remaining in the database is needed for supportive conversations.
6. Support-topic preferences
Where the wellness feature is enabled, optional topic preferences are stored against the user account to support the experience. Topics may reveal sensitive personal experiences. The app includes controls to clear preferences. An explicitly shared session topic is distinct from saved private preferences; the service limits access to the session participants while the session is active. Production rollout and cleanup must be verified.
7. Listener information
Listener profiles may contain names, photos, languages, availability, prices, a support bio and a conversation approach. Admin-reviewed support topics can be published where enabled. A review flag does not establish professional mental-health qualifications. Earnings and payout information are maintained separately for business administration.
8. Messages and communication data
Text chat content and associated participant identifiers, timestamps, delivery or seen status and media URLs are stored by the application. Chat is not a zero-retention service. We retain chat content for up to 90 days after a conversation ends, unless a longer period is needed for a safety report, dispute, legal obligation or account investigation.
9. Call and session metadata
The backend stores conversation participant identifiers, request and session references, mode, status, connection and end times, duration, applicable rates, billing amounts, earnings and connection heartbeats. This metadata is distinct from recordings of the conversation.
10. Voice and video recording
Call Mitra does not intentionally record voice or video conversations. Call and session metadata may still be retained for billing, safety and technical support. If recording is introduced, the app and this policy will be updated before the feature is enabled.
11. Payment transactions
The app retains payment and recharge references, amounts, transaction states and provider-related verification data. Payments are processed by the configured provider. The review did not establish storage of full card credentials by Call Mitra; do not submit full card details to the business through this website.
12. Wallet and billing records
Coin credits, balances, conversation deductions and ledger references are stored to operate the prepaid wallet and reconcile usage. Financial records may need to remain after an account request, subject to confirmed lawful obligations. The categories, reasons and durations must be finalized.
13. Earnings and payouts
The business records listener earnings, platform allocations, payout references, status and destination details needed for manually completed payouts. These records are not public website content. Manual payouts are separate from user recharge payments.
14. Payment service providers
The code includes Razorpay and PhonePe integrations. This does not confirm that either is currently active or authorized for the production business. The final policy must identify active providers and their applicable privacy notices. The website does not provide a payment checkout.
15. Communication and infrastructure providers
The inspected code includes Agora for real-time voice and video, Firebase Cloud Messaging for device notifications, and Azure Blob Storage for uploaded media. Backend integrations also include Exotel telephony, AWS-compatible storage, DigitalOcean Spaces blog storage, Redis, PostgreSQL, Slack and Discord operational notifications. Their presence in code does not establish which vendors are active in production. Active vendors, regions, transferred data, processor arrangements and retention still require operator confirmation.
16. Analytics and diagnostics
The mobile application includes Firebase Analytics, Firebase Performance, Mixpanel and Facebook App Events. Its custom event allowlist restricts event names and parameters to fixed operational values, but this does not establish that SDKs collect no device identifiers, app activity, network information or diagnostics automatically. OTPless, Razorpay and PhonePe SDKs are also installed. Production SDK settings and historical vendor data require review. This website adds no advertising analytics or emotional-topic tracking.
17. Notifications
Device messaging tokens support app notifications and incoming-call prompts. The in-app deletion route removes FCM tokens associated with the account. Device permissions and provider practices also affect delivery.
18. Why information is used
Information supports account authentication, profiles and discovery, conversation delivery, wallet reconciliation, listener earnings, support, moderation and operational diagnostics. Final purpose-by-purpose legal grounds, notices and consent requirements need qualified review before launch. Support preferences are not added to website advertising tracking.
19. Information sharing
Selected profile details are available to other app users. Conversation participants receive information necessary for the session. Configured infrastructure and payment providers process information needed to operate their services. Authorized support and administration personnel may review relevant records. Any legally required disclosure must follow applicable obligations; sharing categories and vendor contracts need confirmation.
20. Storage and security
The application contains authentication, authorization and validation controls. The website validates requests and keeps delivery credentials on the server. No system can promise absolute confidentiality or security. We use access controls, encrypted transport and routine operational safeguards; this policy makes no security-certification or end-to-end encryption claim.
21. Retention
We retain account and profile information while an account is active and for up to 30 days after verified deletion, except where records must remain for payment reconciliation, fraud prevention, safety investigations, tax, accounting or legal obligations. Wallet, payment and payout records are retained for up to 7 years where required for accounting or disputes. Backups age out within 90 days. We do not promise that every record disappears immediately when a request is submitted.
22. Privacy requests
Contact support to request information about your data, correction, preference removal or account deletion. We verify ownership before disclosing or changing account information and aim to acknowledge requests within 3 business days. Do not send PAN, Aadhaar, passwords or OTPs through this website.
23. Account deletion
The authenticated in-app deletion request disables the account, revokes authentication sessions, removes notification tokens and available optional support preferences, and stops active sessions. Website submissions create a request for manual ownership verification. After verification, we target completion within 30 days, subject to active disputes, safety reviews and records that must be retained by law.
24. Website submissions and updates
Contact forms collect your name, reply contact, issue category and message. Deletion forms collect a registered mobile number, optional email and confirmation. Requests are sent to the support mailbox through configured server-side delivery; this website has no separate customer database. Short-lived rate-limit identifiers may be processed to prevent abuse. Support requests are retained for up to 24 months after resolution, unless a longer period is needed for a dispute or legal obligation. Material changes will be reflected in the version and effective date above.
25. Support and grievances
Email app9.india@gmail.com, or contact +91 8169027622. Business: CALL MITRA, Goregaon West, Mumbai, Maharashtra, India. We aim to acknowledge support and grievance requests within 3 business days. This is not an emergency response channel.