Privacy Policy

1. Provider, scope and contact

Sonkawade Labs, a sole proprietorship of Sumit Sonkawade, provides Phone Munshi and determines how account and service information is used. Address: Walandi, Deoni Taluka, Latur District, Maharashtra 413519, India. Website: [Website pending]. Support: sumitsonkawade@sonkawadelabs.in. Grievance officer: [Grievance officer name and email pending]. Business users also have responsibilities for the caller information they provide to the service.

This policy explains the information we use, why we use it, who receives it, and your choices and rights under applicable Indian data protection law.

The Digital Personal Data Protection Act, 2023 and Rules, 2025 have phased commencement. As at 2 October 2026, their main processing duties and individual-rights provisions have not all commenced. References to those rights apply when the relevant provisions become operative; the in-app controls described here are currently available as service features. Applicable existing Indian privacy and consumer requirements continue to apply.

Business contact: Sumit Sonkawade, Sonkawade Labs. Phone: +91 74986 01105. Email: sumitsonkawade@sonkawadelabs.in. Postal address: Walandi, Deoni Taluka, Latur District, Maharashtra 413519, India. GSTIN: 27KGQPS6459R1ZP.

2. Information we process

Account and profile information includes your account identifier, email, sign-in information, name, phone number, business name, optional gender or salutation, occupation, languages, work hours, service areas, assistant instructions, prices and preferences. Our account service provider handles sign-in.

Call information includes caller and called numbers, call identifiers, call type, date and time, status, audio for AI processing, recordings and voicemail, transcripts, summaries, caller names, enquiry details, location or area and requested timing. We may also store booking requests and confirmations, payment references, invoice details, replies, voice clips and test-call feedback.

When you choose contact import, contact names and phone numbers are uploaded. If you connect Tally, we receive company information, stock, prices, quantities and the time of the latest update. Website and IndiaMART imports collect public business information and its source addresses for your assistant.

Notification identifiers and content, app and device information, crash reports and service activity records help deliver notifications and troubleshoot problems. Notification providers may receive caller numbers, transcript excerpts and summaries. Notifications may display call details on your lock screen according to your device settings. Crash-reporting providers process crash information. The complete provider diagnostic-data inventory remains under review.

Email and password are currently used to sign in to your account. Google sign-in is not currently offered. Phone Munshi does not offer mailbox access. We do not use advertising or marketing analytics in the current service.

3. Purposes and consent

We use account and business details to identify you, configure your assistant and provide information you approve. Call information, contacts and recordings support answering calls, recognising callers, transcripts and summaries, reviewing and replying to calls, and capturing requests. Connected business information supports the features you choose. Sign-in, notifications, crash reports and service activity records support service delivery, security and troubleshooting.

At signup or before activating the assistant, actively select the acceptance checkbox to accept the Terms & Conditions, acknowledge the Privacy Policy and give the processing choices described on that screen. We keep the choices, accepted document version and acceptance time. Acceptance is remembered for that version; ordinary app reopening does not require acceptance again. Withdrawal or a material change requiring renewed consent may require another decision. Optional device permissions are requested separately and may be declined. Your acceptance does not provide consent on behalf of callers.

Use Withdraw consent in Settings → Legal / Help to stop new AI sessions and switch your account mode off. New notification registration and automatic crash diagnostics are also disabled on that device. Existing calls may continue, and information already collected is not automatically erased. Carrier forwarding must be disabled separately: voicemail may still record calls while forwarding remains enabled. Export and account deletion remain available after withdrawal.

4. Android permissions

The app does not request call-log access. It asks for phone-status access to identify the active SIM when it clears call forwarding during sign-out, and for phone-dialling access only when you press a control that places a call or sends a carrier code. Contacts access is optional: it reads names and numbers to label calls and uploads only the contacts you choose to import. Microphone access records your own voice clips when you press Record; it does not capture mobile-call audio from your handset. Notification access shows call and transcript alerts.

The app does not request access to your call log, SMS, camera, precise location or the list of installed apps. Because the call log is not read, the app cannot show calls it did not handle: call history lists only calls answered by the assistant. You can change permission and notification settings on your device; declining a permission limits only the feature that needs it.

5. Providers and recipients

The providers identifiable in the current service are Plivo (calling and hosted recordings), Google Gemini (AI audio processing and responses), Supabase (account sign-in and application database), Firebase Cloud Messaging (notifications) and Firebase Crashlytics (diagnostics), and Railway (backend hosting). Where configured, Cloudflare supports fallback routing and voicemail, and an operator alert destination receives failure details. Calling providers receive call audio and metadata. AI providers receive audio, transcripts and assistant information you approve. Notification providers may receive caller details and excerpts. Hosting and fallback providers may hold service numbers and routing information.

If you connect Tally, its services supply your business information. Websites you import receive requests for public pages. Operator alerts may contain account identifiers and failure details. Earlier payment providers may retain names, email addresses, phone numbers and payment details from previous subscriptions. Google Play is the chosen provider for future purchases. Purchase verification uses account-bound receipts, entitlement status and minute usage records.

When you create or change a password through our app or website, the server checks Have I Been Pwned's Pwned Passwords service. It sends only the first five characters of a SHA-1 password hash, never your password, full hash, email or account identifier. The response is checked locally and is not retained. A leaked password is rejected; if the check is unavailable, password creation or change is temporarily unavailable. This check does not apply to Google sign-in or one-time passcodes.

We may disclose information where legally required or to authorised providers for the purposes described in this policy. We do not promise that all information is processed only in India or protected by end-to-end encryption. Provider locations, subprocessors, retention and AI-model training terms have not yet been verified. Do not supply confidential or sensitive material while these arrangements remain unresolved.

For Tally inventory answers, Phone Munshi supplies relevant product, quantity, unit and price information to the AI. The full synced inventory catalogue is not included in the AI call prompt. Information used in an answer may appear in call transcripts or summaries; those records are outside the Tally inventory encryption described below.

6. Storage and security

Our data-storage providers hold account and service records, and our calling providers hold recordings. Your device stores sign-in information, preferences, drafts, pending call events and recently viewed activity. A connected Tally computer stores its connection settings. Hosting and outage-support providers may also hold call-routing information.

The service uses encrypted network connections and limits access to account information. Do not assume all locally stored information or information held by providers is encrypted at rest. Provider encryption at rest and backup protections have not yet been verified. Protect your device and account credentials. No system can guarantee absolute security.

Synced Tally company details and inventory contents, including product names, prices, quantities and units, are encrypted in cloud storage. Phone Munshi can access the information needed to provide the service after account access checks. This is not end-to-end encryption.

This protection applies to synced Tally company details and inventory contents, not all account data. Some account, connection and sync information remains outside this protection. Call audio, transcripts, summaries, contacts, business profile fields, company labels used during pairing, local Tally files, connector settings and readable exports are also outside its scope. Older backups may contain historical unencrypted data. Other provider protections remain subject to the limits stated above.

7. Retention and deletion

Most account and service records remain until account deletion. Server cleanup removes raw call transcripts and schedules deletion of known provider recordings after 29 days. Booking, contact and payment records remain until account deletion or applicable retention requirements. Provider deletion failures are retried; unresolved recording identifiers remain in a restricted cleanup queue for operator action. Minimal purchase fingerprints and their original account binding remain after deletion to prevent receipt reuse; raw purchase tokens and purchase-processing secrets are removed. No fixed retention period has yet been set for these restricted anti-replay records. Retention arrangements for provider backups, diagnostics, device copies and legally required records have not yet been finalised.

Use Delete Account in Settings and enter your phone number to confirm. This deletes linked account and service records and requests removal of your sign-in account. Successful in-app deletion also clears stored sign-in details, activity and booking history, pending events, saved replies and profile drafts on that handset.

Account deletion invalidates this server's cached call-routing profiles, ends its active calls and queues known recording links for provider deletion. Provider deletion can take longer or require operator action. Recordings whose links arrive after account deletion, provider backups and copies held elsewhere may require separate cleanup. Deletion does not cancel payment mandates or release a rented number. Contact support about remaining copies or a sign-in account that is still accessible after deletion.

If you no longer have the app, sign in on the website and use its account deletion page, or contact sumitsonkawade@sonkawadelabs.in. The final public account-deletion website address is pending. Cancel recurring payments and disable carrier forwarding separately before deletion.

8. Access, correction, export and complaints

You can review and correct editable profile details in Settings. Data Export saves your account and service records, including transcripts and voice clips, in a downloadable file after sign-in. It does not include external call recordings or provider-held crash reports. Available recordings can be played in the app. Keep exports private because they include caller information.

Use the support or grievance contact to request access, correction, completion, updating, erasure or withdrawal, or raise a caller-data complaint. We may request reasonable identity verification to protect you and others. Statutory nomination and escalation rights apply when the relevant legal provisions are in force; no nomination feature is currently implemented. Consumer grievances must be acknowledged within 48 hours and redressed within one month where the E-Commerce Rules apply. The data-rights procedure, nomination arrangements and grievance-officer appointment still require confirmation before public release.

An account data export includes your Tally inventory in readable form. The exported file is not protected by the Tally cloud encryption. Store it privately and protect it on your device before sharing it.

9. Children and breaches

The service is intended for adults aged 18 or over. Do not knowingly provide children's information without a lawful basis and any required verifiable parent or guardian consent. A verified procedure for handling children's information is not yet available; do not use this service for that purpose until the necessary arrangements are in place. Contact support if you believe a child's information has been provided.

If a personal data breach occurs, affected people and authorities will be notified as required by applicable law. The breach-response contact and notification procedure must be finalised before public release.

10. Changes

The version and last-updated date identify this policy. Material changes require notice and renewed consent where appropriate. Terms & Conditions and Refund & Cancellation Policy are available in Legal / Help.