Back to Call Vani

Privacy Policy

Last updated: 17 October 2026

CallVani is an AI-powered voice communication platform operated by Nexadly Technologies Private Limited.

1. Our role and your business customer’s role

Nexadly Technologies Private Limited operates CallVani as a SaaS brand. This policy covers our website, accounts and services. Nexadly determines how account administration, billing, support, service security and its own legal obligations are handled. For those purposes, it acts as a controller or data fiduciary where those terms apply.

A business using CallVani usually decides whom to contact, why a call is made, what its agent says, which contacts or knowledge it uploads, and whether to retain recordings. For that customer-directed processing, Nexadly generally provides processing services on the customer’s instructions, subject to applicable law and the agreed data-processing terms. The customer is responsible for its own lawful basis and participant notices. Roles depend on the actual activity, rather than a single label for all information.

2. Information processed through CallVani

Account information can include your name, business name, email address, telephone number, login and security information, workspace settings, team roles and support correspondence. Billing records can include business and tax details, plan selections, credit balances, usage, invoices and payment-provider references. Hosted payment providers handle the payment details entered into their checkout.

Customers may upload contact lists, phone numbers, names, contact attributes, business documents, agent instructions and knowledge sources. Calls can produce inbound and outbound numbers, direction, timestamps, duration, status, carrier references, recordings where enabled, transcripts, AI-generated summaries and quality or conversation analysis. Connected CRM systems and customer-selected integrations may supply or receive relevant records.

We also process IP-related network identifiers, authentication events, service diagnostics and security logs. Own-voice features, when used, process voice samples, speaker details, authorization evidence and verification information. Avoid uploading sensitive or regulated information unless your use is authorized and the agreed service safeguards support it.

3. Why information is processed

Information is used to establish and secure accounts; provide the features customers enable; connect calls; understand speech; generate spoken responses; maintain call history; run configured follow-ups and integrations; produce requested transcripts, summaries and reports; support customers; meter usage; collect fees; prevent misuse; and meet applicable legal obligations.

A customer must establish the lawful basis for its contact lists, calling purposes and related processing. Acceptance of our website terms, an imported contact or a saved consent flag does not itself establish a recipient’s legally valid consent. Recording, marketing, voice rights and other permissions must be assessed separately.

4. Live audio, recordings and AI services

Live voice processing may send audio to a speech-to-text service, relevant text and business context to an AI model, and response text to a text-to-speech service. This processing can occur during a call even when a retained recording is disabled. A recording setting is therefore different from whether speech is processed to conduct the conversation.

The software supports speech or AI integrations such as Google, Sarvam, ElevenLabs, Cartesia, Deepgram, OpenAI and Anthropic. The information sent depends on the enabled feature, configured provider and applicable routing. This list describes supported services; it does not mean every provider is active for every account or receives every call. Provider-specific retention and use of submitted content depend on the relevant service terms and account settings.

AI transcripts, summaries and responses can be inaccurate. Workspace playbook or quality-review features may use permitted historical conversations when the customer enables them. Uploading content is not authorization to train an unrestricted general-purpose model or to impersonate a speaker. We do not make a universal zero-retention or no-provider-training promise without the applicable contractual and technical settings.

5. Who may receive information

Relevant information may be available to authorized workspace members and to service providers supporting hosting, storage, telephony, speech processing, AI models, payments, security and support. Customers control the integrations and webhook destinations they enable. Connecting a service can disclose the records required for that connection, and the receiving service’s terms may also apply.

A provider may process some information on instructions and other information independently for network operations, fraud prevention, billing or legal requirements. We may also disclose information when legally required, to protect rights and service security, or in a lawful corporate transaction with appropriate protections. Contractual roles, recipients and safeguards must reflect the actual arrangement.

6. Retention and deletion

Retention depends on the information, enabled feature, customer instructions, service configuration and applicable obligations. Recording-retention controls are available, but a recording expiry does not also erase transcripts, summaries, call metadata, provider copies or backups. A saved transcript-retention preference should not be treated as confirmation that all associated data has already been deleted.

Account, invoice, payment, security and authorization records may need to be retained for lawful purposes after operational content is removed. Deletion requests require scope and authority checks, consideration of legal exceptions and coordination with relevant providers. Cancellation or signing out is not a request to erase every record. This draft does not promise an automatic universal deletion period or immediate removal from backups.

7. Security and international processing

The application uses measures such as authenticated sessions, workspace access controls, password hashing, encryption of stored integration credentials and operational security checks. Measures depend on the system and configuration. These controls do not mean every record is end-to-end encrypted or that a service can be completely secure.

Selected providers and infrastructure may process information outside your country. Locations, access and retention depend on the actual services used. Where required, the appropriate contractual safeguards and lawful transfer mechanism must be in place. Do not assume India-only storage or that use of an overseas API by itself satisfies international transfer requirements.

8. Your choices, privacy rights and requests

Depending on applicable law and our role, you may have rights to information, access, correction, deletion, restriction, objection, portability, withdrawal of consent or a complaint to the relevant authority. These rights can be subject to identity checks and lawful exceptions. Withdrawing consent does not automatically invalidate earlier lawful processing, and we will explain where another permitted basis or retention obligation applies.

If a business contacted you through CallVani, contacting that business is often the quickest way to stop its calls or request changes to its records. You may also contact Nexadly about its own processing or assistance with identifying the responsible business. We may need the relevant call date, business name and number involved to locate the record; do not send passwords, OTPs or unnecessary identity documents.

9. Children, browser storage and policy updates

CallVani is intended for authorized business use, not independent use by children. Customers must assess any processing involving minors and obtain the notices, permissions and protections required by law. Do not assume an educational or counselling use automatically permits contacting or profiling children.

Cookies and browser storage support sign-in, preferences and selected features as described in our Cookie Policy. We may revise this policy to reflect service or legal changes and identify the revision date. Material changes should be reviewed before relying on the affected processing.

10. Contact Nexadly

For privacy, support or grievance requests, email hello@nexadly.com. Account holders may also use Support tickets in the CallVani customer panel. A CallVani account is not required to exercise applicable privacy rights.

Nexadly Technologies Private Limited. Business address: RK Garden, New BEL Road, RMV 2nd Stage, Bengaluru, Karnataka – 560054, India. This is the supplied business address and is not identified as a verified registered office.