Terms of Service

These Terms of Service (the "Terms") form a binding legal agreement between you and the Movoice group of companies governing your access to and use of Movoice AI (the "Service").

The Service is provided by Metawaveai Technologies Private Limited (incorporated in India), together with its affiliate Metawaveai Technologies Inc (collectively, "Movoice", "we", "us", or "our"). If you are located in India or contract in Indian Rupees, your contracting entity is Metawaveai Technologies Private Limited; otherwise your contracting entity is Metawaveai Technologies Inc. Both entities are bound by, and may enforce, these Terms.

By creating an account, clicking to accept, or accessing or using the Service in any way, you agree to be bound by these Terms, our Privacy Policy, and the Data Processing Addendum in section 12. The Acceptable Use Policy in section 6, the Community Rules in section 24 and the referral rules in section 25 are part of these Terms rather than separate documents.

How acceptance works, stated plainly. In the mobile app you tick a box before the account is created. On the web you are told, next to the button, that continuing accepts these Terms and the Privacy Policy. We do not currently store a per-user record of which version you accepted, and nothing re-prompts you when these Terms change. Continued use of the Service after a change takes effect is therefore the operative acceptance mechanism, as section 32 describes. Movoice AI Messaging is the exception: acceptance of the Messaging Terms and Community Rules is recorded against a version, and a change to them re-prompts you.

If you are entering into these Terms on behalf of a company or other legal entity, you represent that you have authority to bind that entity, and "you", "your", and "Customer" refer to that entity. If you do not agree to these Terms, you may not access or use the Service.

"Service" means the Movoice AI platform, including its web application, embeddable voice widget and demonstration pages, iOS and Android applications, macOS desktop application, public developer API, client libraries and MCP server, AI agents, calling, messaging, recording, transcription, voice synthesis, campaign, analytics, assistant, wallet, and related features, together with any documentation and updates. Movoice AI Messaging is part of the Service but is governed by sections 22 to 24 rather than by the business-product provisions.

"Customer", "you", or "your" means the business, organization, or individual that registers for, subscribes to, or otherwise uses the Service and is responsible for the account.

"Recipient" or "End User" means any natural person whom the Customer calls, sends messages to, records, uploads, profiles, or otherwise contacts or processes through the Service. Recipients do not register for the Service and are not parties to these Terms; the Customer alone owns the relationship with, and is responsible for, its Recipients.

"Customer Content" means all data, contact lists, phone numbers, names, scripts, prompts, audio, voice samples, recordings, transcripts, documents, and other materials that the Customer or its authorized users upload to, generate through, or transmit via the Service, including any personal data of Recipients.

"Sub-processor" means a third party engaged by Movoice to process Customer Content on our behalf in order to provide the Service, as listed in our Privacy Policy.

"Personal Data", "Controller", "Processor", and "Processing" have the meanings given under applicable data protection law, including the Digital Personal Data Protection Act, 2023 ("DPDP Act") and the EU/UK General Data Protection Regulation ("GDPR") where applicable.

Movoice AI is a voice-AI platform that enables Customers to design, deploy, and manage AI agents that place and receive telephone calls and send messages to the Customer's own contacts. Depending on plan and configuration, the Service may include:

• AI voice agents that conduct automated telephone conversations, inbound and outbound;
• Calling over telephony carriers and over the WhatsApp Business Platform;
• SMS, WhatsApp, Telegram, email and web-chat messaging;
• Call recording, transcription, and conversation summaries;
• Bulk and scheduled campaigns;
• Synthetic-voice creation from a speech sample;
• An in-app AI assistant that answers questions and, where separately agreed, operates controls in your account;
• A public REST API, client libraries and an MCP server for programmatic access;
• Outbound webhooks delivering call events, transcripts and recording links to endpoints the Customer nominates;
• An embeddable voice widget and shareable demonstration links for the Customer's own website;
• A prepaid wallet and usage credits;
• Know-Your-Customer / Know-Your-Business ("KYC/KYB") identity verification;
• Phone-number provisioning and leasing from carriers;
• Travel eSIM data plans, supplied by third-party mobile network operators through an eSIM aggregator;
• Contact synchronization and CRM, calendar, payment-gateway and e-commerce integrations;
• Caller-memory profiling that stores context about Recipients across interactions;
• A super-administrator monitoring console used by Movoice for security, compliance, abuse-prevention and support purposes, described in our Privacy Policy;
• Movoice AI Messaging, a separate end-to-end-encrypted personal messenger, governed by sections 22 to 24.

Movoice provides the technical platform. The Customer determines whom to contact, what to say, when to call, and for what purpose. Movoice does not initiate, direct, or control any specific communication and acts as the Customer's technical service provider and data processor with respect to Recipient data.

We may add, modify, or discontinue features at any time. We will use reasonable efforts to notify Customers of material adverse changes.

4.1 Eligibility. You must be at least 18 years old and capable of forming a binding contract. If you use the Service on behalf of an entity, you must be authorized to bind that entity.

4.2 Registration. You agree to provide accurate, current, and complete information and to keep it up to date. You may be required to complete KYC/KYB verification (section 15) before accessing certain features, including telephony and messaging. We screen registration email addresses for disposable-address services automatically and may refuse or remove an account on that basis; you may ask for a human review at privacy@movoice.ai.

4.3 Account security. You are responsible for safeguarding your account credentials and API keys and for all activity under your account, whether or not authorized by you. Notify us promptly at sales@movoice.ai of any suspected unauthorized use or security breach.

4.4 Authorized users. You are responsible for the acts and omissions of anyone who accesses the Service through your account, and for ensuring they comply with these Terms.

4.5 One account. You may not maintain multiple accounts to evade limits, suspensions, verification requirements, referral rules, or fees.

This section is fundamental to these Terms. Because the Service is used to contact Recipients who have not signed up for it, the Customer bears sole and primary responsibility for the lawfulness of every communication it originates. The Customer represents, warrants, and covenants, on a continuing basis, that:

5.1 Consent. Before placing any call or sending any message to any Recipient through the Service, the Customer has obtained all legally required prior consent from that Recipient. Where the communication is marketing, promotional, telemarketing, or advertising in nature, the Customer has obtained prior express WRITTEN consent in the form required by applicable law. The Customer will retain records of such consent and provide them to Movoice promptly on request.

5.2 Do-not-call, opt-out, and revocation. The Customer will maintain and honor do-not-call and do-not-disturb preferences and will honor any opt-out or revocation of consent by a Recipient, communicated by any reasonable means, promptly and in any event within the timeframe required by applicable law. The Customer acknowledges that Movoice does not scrub any national or regulatory registry on its behalf (section 9.5), and that an opt-out recorded in the Service applies to that Customer's account only.

5.3 Relationship requirement. The Customer will not upload, import, purchase, rent, or use any phone number, contact, or list with which it does not have a genuine, direct relationship and the requisite consent. Scraped, purchased, harvested, or third-party lists lacking valid consent are prohibited.

5.4 Determination of applicable law. The Customer is solely responsible for determining which laws, regulations, and industry rules apply to its communications — including the jurisdiction of each Recipient — and for complying with them. Movoice does not provide legal advice and the availability of any feature does not constitute advice that its use is lawful in a given jurisdiction.

5.5 Accuracy. The Customer is responsible for the accuracy and lawfulness of all Customer Content, scripts, prompts, voice samples, and caller identification information it configures.

5.6 The demonstration service. The public demonstration call on Movoice's own website is a marketing feature operated on Movoice's own carrier account. Requesting one requires possession of the number entered, confirmed by a one-time code. A request to stop received on a demonstration call is recorded against the demonstration service only and creates no opt-out against any Customer. Automated or abusive use of the demonstration endpoint is prohibited.

Breach of this section is a material breach of these Terms, may result in immediate suspension or termination, and triggers the Customer's indemnity obligations under section 27.

You agree not to use, and not to permit any person to use, the Service to:

• violate any applicable law, regulation, court order, or third-party right;
• make fraudulent, deceptive, harassing, threatening, abusive, or unsolicited communications, or to engage in unlawful robocalling, spam, or telemarketing;
• impersonate any person or entity, or misrepresent your affiliation, identity, or caller identity ("spoofing") in violation of law;
• create or use a synthetic voice of any person without that person's informed written consent, or use a synthetic voice to deceive as to identity;
• transmit or generate content that is unlawful, defamatory, obscene, hateful, sexually exploitative of minors, or that promotes violence or illegal activity;
• collect, profile, or process personal information without a lawful basis and required consent;
• distribute malware, or probe, scan, overload, disrupt, or attempt to gain unauthorized access to the Service, its infrastructure, or any connected systems or networks;
• reverse engineer, decompile, or attempt to derive source code from the Service, except to the extent that restriction is prohibited by law or permitted by an open-source licence under which we distribute a component;
• resell, sublicense, or provide the Service to third parties except as expressly permitted in writing;
• use the Service to build a competing product, or to train a competing model on our outputs;
• circumvent usage limits, rate limits, spend caps, security controls, KYC/KYB, the AI-disclosure feature, or a suspension or ban;
• rely on the Service for emergency services or for any life-safety purpose, or in any use where failure could lead to death, personal injury, or severe environmental or property damage. Section 21 explains what the Service does and does not do about emergency calls, and you must read it.

We may investigate suspected violations, cooperate with law enforcement, and suspend or terminate access for violations.

7.1 Customer as owner of the consent duty. Many jurisdictions restrict the recording of telephone and electronic communications. The Customer represents and warrants that, before any call is recorded through the Service, it has provided all legally required disclosures and obtained all legally required consents from every party to the communication. This includes, without limitation: the United States, where states including California, Florida, Illinois, Pennsylvania, Washington and Massachusetts require the consent of all parties; the European Union and United Kingdom, where recording is processing of personal data requiring a lawful basis and appropriate notice; and India, where recording and monitoring are subject to consent and applicable telecom and data-protection rules.

7.2 What the Service actually records. Recording is controlled by a setting on the Customer's account and is ON by default. The Customer acknowledges the following, which is also stated in our Privacy Policy:

• Inbound AI calls, and outbound AI calls the Customer places itself over our international carrier — from the web console, the desktop application or the mobile app, including a test call started there — are recorded unless the Customer switches recording off.
• Every other way a call can be placed is recorded regardless of that setting, because those paths do not currently pass it through: bulk campaigns, scheduled and follow-up calls, the developer API, conversation flows, lead-form and social-message callbacks, WhatsApp call commands, the demonstration call on our website, and onboarding number verification. The setting reaches one dial path today.
• While a number is being verified for WhatsApp, every inbound call to that number is answered and recorded for the duration of the verification window, on either carrier and regardless of the setting.
• AI calls carried by our India domestic carrier are not recorded.
• AI calls held in a web browser are never recorded, and WhatsApp calls are not recorded.
• Calls the Customer conducts personally are not recorded at present. If that capability is enabled, a spoken recording notice is played into the call first, cannot be switched off, and recording cannot begin unless it has played.

Movoice does not warrant that any particular call will be recorded, and the Customer must not assume a recording exists.

7.3 Movoice acts only as processor. Where recording occurs, Movoice records, transcribes, and stores audio and transcripts solely as a processor acting on the Customer's documented instruction and configuration. The Customer is responsible for the lawfulness of recording. Transcription is performed by our transcription Sub-processors, meaning audio is transmitted to them to be converted to text; our transcription produces text only and does not create voiceprints, speaker-identification embeddings, or other biometric identifiers from Recipient call audio. Voice cloning is a separate feature governed by section 20.

7.4 Storage, access, and deletion. Call-recording audio and transcripts are stored with our object-storage Sub-processors in the United States, encrypted in transit and reached only through short-lived signed links, with encryption at rest provided by those providers at platform level. Movoice may access stored recordings solely to provide support, to investigate and resolve disputes and complaints, to protect the safety, security, and integrity of the Service, and to comply with law; such access is role-restricted, requires a written reason, and is logged in a record the Customer can review. Customer-side playback is logged from the call log and the inbox, but not from the campaign screen, and a download is not recorded separately from a playback. Recordings are deleted on account deletion or expiry of a retention window the Customer has configured, as described in sections 12 and 29.

7.5 Additional parties. The Service permits up to three participants on a call. Where a further party is merged into a call that is actively recording, an automated recording notice is played into the call. Where the call is not recording, no notice is played, and no AI-disclosure notice is played to a merged-in party in any case. The Customer is responsible for obtaining any consent required from an added participant before merging them.

7.6 Voicemail and verification calls. Voicemail messages left by Recipients are recorded and transcribed on both carriers, and the short automated call made when a number is being verified with a carrier is recorded. These are not governed by the recording setting.

7.7 Indemnity. The Customer will defend, indemnify, and hold Movoice harmless from any claim, fine, penalty, or expense arising from the recording, transcription, monitoring, or storage of any communication in violation of applicable law or without the required consent (section 27).

8.1 Affirmative disclosure duty. The Customer must ensure that every AI-generated or AI-assisted call and message clearly and conspicuously discloses to the Recipient, at the outset of the interaction, that the Recipient is interacting with an artificial-intelligence system and not a live human. This obligation reflects, among others: Article 50 of the EU Artificial Intelligence Act; the TRAI Telecom Commercial Communications Customer Preference Regulations, 2025 and applicable Indian directions on automated and AI communications; and United States federal and state bot-disclosure and AI-voice laws, including California's SB 1001 and comparable statutes.

8.2 What the Service does, and where it stops. Being precise here matters, because the Customer's duty is not discharged by a feature that does not reach every channel.

• On every AI call, a spoken announcement that the Recipient is speaking with an AI assistant — and, where recording is on, that the call may be recorded — is prepended to the agent's greeting in the agent's language, on every call-placement path, including where a personalised greeting generated by our models replaces the configured one. On our international carrier the Customer cannot disable, suppress, alter, or reorder it, and no screen in the product offers a way to do so; that carrier can reach any jurisdiction, and the obligation there falls on Movoice as provider. On our India domestic carrier, which places calls only within India, the Customer may switch the announcement off for its own account under section 8.3. Where it is switched off, no announcement is made on that carrier and the Customer's duty under section 8.1 is unaffected and undischarged.
• On the inbound menu that plays before an AI agent answers, the wording of the AI sentence is a free-text field the Customer edits. The Customer is responsible for what it says.
• AI-generated SMS, WhatsApp, Telegram and email messages, including follow-ups composed from a call, are sent without any AI-content label. Where law requires generated text to be labelled, the Customer must do it.

8.3 Switching the announcement off, where that is offered. The Service offers one control over the spoken announcement, and only on our India domestic carrier. Except through that control, the Customer must keep the announcement enabled and must not disable, suppress, alter, obscure, or circumvent it, and must never configure an agent to deny that it is an AI when asked. Defeating the announcement by any other means, on any carrier, is a material breach of these Terms.

Where the Customer uses that control, the Customer represents and warrants that it has declared its use of automated dialling to its telecom operator as required under applicable Indian telecom regulation, that the declaration remains in force, and that making calls without a spoken AI announcement is lawful for the calls it places. The Customer confirms that warranty in writing at the moment it switches the announcement off; Movoice records the confirmation, who made it and when, and makes that record available to the Customer. If the declaration is withdrawn in the Customer's account settings, the announcement resumes. The Customer acknowledges that this setting is applied to an agent when that agent is next synchronised to the voice engine, that a change is therefore not necessarily immediate, and that the Customer remains responsible under section 8.1 for every call placed in the meantime. Movoice makes no representation that switching the announcement off is lawful for the Customer's calls, and the Customer's obligations under section 8.1 are unchanged by doing so. Section 28 applies to any claim arising from calls placed without an announcement.

In addition to sections 5 to 8, the Customer must comply with all telecommunications and messaging laws applicable to its communications.

9.1 United States. The Customer will comply with the Telephone Consumer Protection Act (TCPA), the Telemarketing Sales Rule, and FCC rules, including rules treating AI-generated and synthetic or prerecorded voice calls as requiring prior express — and for marketing, prior express written — consent, honoring the National and internal Do-Not-Call lists, calling-time restrictions, and accurate caller-ID requirements, together with cooperation with the underlying carrier's call-authentication (STIR/SHAKEN) obligations. Where US A2P messaging is used, the Customer's business details are submitted to The Campaign Registry for 10DLC registration.

9.2 India. The Customer will comply with the TRAI Telecom Commercial Communications Customer Preference Regulations, 2025 and related directions, including registration on the Distributed Ledger Technology (DLT) platform as a principal entity, registration of headers and content templates, use of the correct numbering series, consent and preference scrubbing, and time-of-day restrictions. The registered sender is the Customer, not Movoice. Movoice enforces DLT only against the headers and template identifiers the Customer enters into Compliance Guard; we do not verify them with the DLT platform or TRAI, so an entry that looks correct but is not in fact registered will be rejected by the carrier rather than caught by us.

9.3 Other jurisdictions. Where Recipients are elsewhere, the Customer will comply with equivalent local telemarketing, calling, messaging, and consent laws.

9.4 Third-party channel terms. Messaging is delivered through third-party channels and the Customer must additionally comply with their terms. For SMS this includes carrier and aggregator policies, opt-in and opt-out keyword handling, and sender registration. For WhatsApp and the Meta / WhatsApp Business Platform the Customer must obtain valid opt-in before messaging or calling a Recipient, use only Meta-approved templates, honor block and opt-out signals, comply with the WhatsApp Business Messaging Policy, Commerce Policy and Business Terms, and not impersonate or use the branding, name, colors or logo of WhatsApp or Meta in a manner suggesting affiliation or endorsement. For Telegram the Customer must comply with Telegram's Bot Terms of Service. Violation may result in that channel suspending or banning the Customer's number or account, for which Movoice is not responsible.

9.5 Registries are the Customer's responsibility. The Service does not perform any lookup against a national or regulatory do-not-call or do-not-disturb registry. Suppression in the Service is limited to the Customer's own list, and applies to that Customer only.

9.6 Calling windows, per rail. For automated single AI calls, follow-ups and speed-to-lead dialling, the Service defers calls placed outside the Recipient's local window — by default 09:00 to 21:00, clamped to the destination country's legal window from an internal registry, with cold AI calls hard-blocked without prior opt-in in Germany, Austria, the Netherlands, Denmark and Poland. For BULK CAMPAIGNS, time-of-day is governed solely by the calling hours the Customer configures on the campaign; if the Customer configures none, the platform applies no time-of-day restriction. The Customer must not read the automated-call behaviour as covering its campaigns.

9.7 Shared sender risk. Where messaging is delivered on a Movoice-held aggregator or carrier account rather than the Customer's own, Movoice's sender registrations and carrier relationships are exposed to the Customer's traffic. A Customer whose traffic threatens a shared sender may be suspended immediately and without notice.

9.8 Authority over the Customer's Meta assets. The Customer authorizes Movoice to read and modify its WhatsApp Business Profile — including about, description, address, email, website links, vertical and profile picture — and to block and unblock contacts through the Meta Graph API on the Customer's instruction. Saving from the console overwrites the corresponding values at Meta, and Movoice is not responsible for values overwritten or cleared by such a save.

10.1 List ownership and warranty. For every campaign or bulk send, the Customer represents and warrants that it owns or is lawfully entitled to use the target list, that it has the required consent for each Recipient, and that the list has been scrubbed against applicable registries and against Recipients who have revoked consent.

10.2 Caller-ID accuracy. The Customer will use only caller identification and sender identifiers it is authorized to use and that accurately identify it. Spoofing or misrepresenting origin is prohibited.

10.3 Opt-out handling. The Customer will process opt-outs received during or after a campaign promptly and will suppress opted-out Recipients from future campaigns.

10.4 Throttling and fair use. The Customer will comply with applicable rate limits, calling windows, and any throttling that Movoice or the underlying carriers or channels impose. Movoice may throttle, queue, pause, or block campaigns that pose compliance, reputation, or abuse risk.

10.5 Destination restrictions the platform enforces. Regardless of the Customer's settings, the Service refuses premium-rate, satellite and international shared-cost ranges outright; requires approval for destinations with a high risk of international revenue-share fraud; refuses calls that would exceed a per-account daily international spend cap or an international dial-velocity cap; and refuses origination from a suspended account. These are service limitations, not compliance advice.

10.6 Campaign recording. Campaign calls are recorded regardless of the account recording setting (section 7.2). The Customer must account for that in the consent it obtains.

11.1 Ownership. As between the parties, the Customer retains all right, title, and interest in and to Customer Content. Movoice claims no ownership of Customer Content.

11.2 License. The Customer grants Movoice a worldwide, non-exclusive, royalty-free license to host, store, transmit, display, reproduce, process, and create derived data — such as transcripts, summaries, synthetic voices and caller-memory profiles — from Customer Content solely as necessary to provide, secure, support, and improve the Service for the Customer, and to comply with law. Movoice does not sell Customer Content and does not use Recipient personal data to train foundation models for unrelated third-party purposes.

11.3 Responsibility. The Customer is responsible for the legality, accuracy, and appropriateness of Customer Content and for having all rights and consents necessary to grant the license above and to have Movoice process Recipient personal data on its behalf.

11.4 Knowledge base and website ingestion. Documents the Customer uploads and pages Movoice crawls at the Customer's instruction are transmitted to and held by our AI Sub-processor for retrieval. The Customer warrants that it owns or is entitled to submit that content, that it has any consent needed for personal data inside it, and that it is entitled to have a third-party website crawled on its instruction. Our crawler does not evaluate a target site's robots directives, so that entitlement is the Customer's to establish.

11.5 Feedback. If the Customer provides feedback or suggestions, Movoice may use them without restriction or obligation.

This section constitutes the Data Processing Addendum ("DPA") between the parties and applies to Movoice's processing of Personal Data on the Customer's behalf.

12.1 Roles. With respect to Recipient Personal Data contained in Customer Content, the Customer is the Controller (or Data Fiduciary under the DPDP Act) and Movoice is the Processor. The Customer is responsible for the lawfulness of the collection and of its instructions.

12.2 Instructions. Movoice will process such Personal Data only on the Customer's documented instructions, including as set out in these Terms and through the Customer's configuration of the Service, except where required by law, in which case Movoice will inform the Customer unless legally prohibited.

12.3 Confidentiality. Movoice will ensure that personnel authorized to process Personal Data are bound by confidentiality obligations.

12.4 Security. Movoice will implement and maintain appropriate technical and organizational measures designed to protect Personal Data against unauthorized or unlawful processing and accidental loss, destruction, or damage, taking into account the state of the art and the nature of the data.

12.5 Breach notification. Movoice will notify the Customer without undue delay after becoming aware of a personal-data breach affecting Customer Content, and will provide information reasonably necessary for the Customer to meet its own notification obligations.

12.6 Sub-processors. The Customer authorizes Movoice to engage Sub-processors in the categories described in section 8 of our Privacy Policy, each bound by data-protection obligations no less protective than those in this DPA. The current list of named Sub-processors, with each one's purpose and location, is available to the Customer on request by writing to legal@movoice.ai. Movoice will update that list before a new Sub-processor begins processing Customer Content. We do not currently operate a separate notification subscription, so a Customer who wishes to review changes may request the current list at any time, and may object on reasonable data-protection grounds by writing to legal@movoice.ai.

12.7 Processing location and international transfers. Recipient Personal Data is processed in the United States, India, the European Union, Singapore, and — only where the mainland-China voice endpoint is selected for voice synthesis or cloning — China. Call-recording audio and the primary database are hosted in the United States. Movoice does not offer customer-selectable data residency and does not operate Indian, EU or other dedicated regional clusters. Where Personal Data is transferred across borders, the parties rely on a lawful transfer mechanism, including the applicable Standard Contractual Clauses or equivalent safeguards, incorporated by reference where required.

12.8 Deletion or return. On termination or expiry, and on the Customer's request, Movoice will delete or return Customer Content, including deleting call-recording audio from object storage, subject to legally required retention and to the categories our Privacy Policy identifies as surviving deletion.

12.9 Assistance and audit. Taking into account the nature of processing, Movoice will provide reasonable assistance to the Customer with data-subject requests, data-protection impact assessments, and regulator inquiries, and will make available information reasonably necessary to demonstrate compliance with this DPA and, no more than once per year and subject to confidentiality, allow for audits by the Customer or its mandated auditor.

12.10 Grievance Officer. For the purposes of the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021 and the Digital Personal Data Protection Act, 2023, Movoice's Grievance Officer is Sai Safalya Tudu, reachable at privacy@movoice.ai. We acknowledge every complaint within 24 hours of receipt and dispose of it within 15 days.

The Service integrates with and depends upon third-party services, including telephony carriers, messaging channels, AI model providers, storage, payment processors, CRM, calendar and e-commerce systems, and analytics and diagnostics tools, as identified in our Privacy Policy. The Customer's use of any integration is also subject to that third party's terms, and the Customer is responsible for complying with them and for maintaining any account it holds directly. Movoice is not responsible for the acts, omissions, availability, pricing, changes, or discontinuation of third-party services, and any suspension, ban, or throttling imposed by a third party — including a channel banning a Customer's number — is outside Movoice's control.

Destinations you nominate. Where the Customer configures a webhook endpoint, an automation platform, a CRM, or any other destination, Movoice transmits the configured data — which for call webhooks includes the Recipient's phone number, call metadata, the AI summary, the recording link and the full transcript — to that destination. The Customer selects and controls it. Movoice signs each delivery so it can be verified, but does not control processing at the destination and is not responsible for it. The Customer is responsible for the lawfulness of that onward transfer, including any transfer-impact assessment it requires.

14.1 Fees. The Customer will pay all fees for the plan and usage it selects, including subscription fees and usage-based charges for calls, messages, numbers, and other consumption. Prices outside India are stated exclusive of taxes; prices in Indian Rupees are inclusive of GST, and section 14.9 explains how that appears on the invoice.

14.2 Free trial. New accounts are enrolled in a time-limited free trial of a paid tier, with a quantity of included credit stated in the product at the time. Where a payment method is collected at signup, the subscription converts automatically to a paid subscription at the end of the trial unless it is cancelled before then, on the rail described in 14.5. The trial length and the conversion date are shown at checkout.

14.3 Wallet and credits. The Service uses a prepaid wallet. Credit is consumed as the Customer uses metered features. Credit does not expire, is not transferable, and has no cash value except as set out in 14.6.

The wallet pays for: calling, including WhatsApp voice calls; the monthly lease of wallet-billed phone numbers, charged on a monthly cycle, where an insufficient balance deactivates the number until the wallet is topped up; and the one-time SMS/A2P registration fee, which is consumed on submission and is not refunded if the carrier rejects the registration. Per-message SMS is not billed from the wallet — SMS is a monthly add-on.

WhatsApp Business Platform MESSAGING sent on the Customer's own Meta credentials is billed by Meta directly to the Customer's own WhatsApp Business Account and is not paid from the wallet. WhatsApp messaging carried on a Movoice-held rail is billed to Movoice and may be charged to the Customer under its plan.

Where the App Store refunds a purchase, the corresponding credit is removed, which may leave a negative balance. Movoice may also reverse credit corresponding to any other refund, reversal or chargeback, and may suspend metered use until a negative balance is cleared.

14.4 Per-destination pricing. Included plan minutes are domestic minutes. Calls to other pricing zones bill from the wallet at the published per-minute rate from the first second and do not draw the plan's included minutes, on every plan. An unrecognised destination is priced at the highest zone. Current rates are published in the product and on our pricing page.

14.5 Auto-renewal and cancellation, per rail. Subscriptions renew automatically at the end of each billing cycle at the then-current rate unless cancelled before the renewal date; the cadence is disclosed at checkout. Where you subscribed on the web or desktop, you cancel in account settings and cancellation takes effect at the end of the current billing cycle. Where you subscribed through the Apple App Store, you must cancel in your Apple ID subscription settings — Movoice cannot cancel an App Store subscription for you, and the mobile app links you to Apple for that purpose. Where a statutory cooling-off or withdrawal right applies, you may exercise it within the period and on the conditions that law requires.

14.6 Refunds. Unused credit may be refunded within 14 days of the top-up that created it, provided none of that credit has been used. This is handled on request rather than by a self-service control: write to sales@movoice.ai from the account email. After 14 days, or where any of the credit has been used, credit is non-refundable. Subscription fees are non-refundable except where required by applicable law.

Who issues a refund depends on where the purchase was made. Purchases through the Apple App Store are refunded by Apple under Apple's own policies; Movoice can neither grant nor refuse them, and the Customer should use Apple's "Report a Problem". Purchases made on the web are refunded by Movoice. Where Google Play purchasing is offered, purchases through Google Play may be refunded by Movoice or by Google.

14.7 Service ceilings. Plans carry a monthly cap on outbound AI calls, a requirement of an active paid plan for outbound calling, a pause when the wallet reaches zero, and monthly request quotas for the developer API. These limits are published per plan and may change with the plan.

14.8 Price changes. Movoice may change fees on at least 30 days' notice; changes take effect at the next renewal after the notice period. Continued use after the effective date constitutes acceptance.

14.9 Taxes and invoicing. The Customer is responsible for all applicable taxes other than taxes on Movoice's net income. For India, prices in Indian Rupees include GST at the prevailing rate, and the tax invoice shows the taxable value and the applicable CGST/SGST or IGST split. Elsewhere, where Movoice is required to collect tax it will be added to invoices. Tax invoices and receipts are issued for subscription charges, and credit notes for refunds of them; wallet top-ups and App Store consumable purchases do not currently generate a tax invoice.

14.10 Payment processing. Payments are processed by our named PCI-DSS-compliant payment processors, as listed in our Privacy Policy. Movoice does not store full payment-card numbers. The Customer authorizes Movoice and its processors to charge its designated payment method for all amounts due.

14.11 The Customer's own collections. Movoice is not a party to, and is not responsible for, any transaction between the Customer and its own Recipients or customers. Where the Customer connects its own payment gateway, Movoice stores those credentials encrypted and an AI agent may create a payment link and send it to a Recipient during a call. The Customer is the merchant of record for those collections, is responsible for the gateway's own terms and for its tax, refund, chargeback and consumer obligations, and warrants that it is authorised to have Movoice transact on that account.

14.12 Non-payment. Overdue amounts may accrue interest to the extent permitted by law, and Movoice may suspend the Service and reclaim provisioned resources, including phone numbers, for non-payment, per sections 15 and 28.

15.1 Verification. To comply with carrier, channel, and legal requirements and to prevent abuse, Movoice may require the Customer to complete KYC/KYB identity and business verification, performed via our identity-verification Sub-processor, before enabling telephony, messaging, number provisioning, travel eSIM purchases, or certain other features. Where Movoice upgrades its verification checks, it may require a Customer verified under an earlier check to verify again before buying a new number, porting a number in, or buying a travel eSIM; service already provisioned continues. The Customer will provide accurate, current, and complete verification information and warrants its authenticity. Movoice may decline, suspend, or revoke access if verification is incomplete, fails, or appears fraudulent.

15.2 Number leasing. Any phone numbers made available through the Service are leased from underlying carriers and are not sold to the Customer. The Customer obtains only a limited, non-exclusive, non-transferable right to use assigned numbers while the account is active and in good standing, subject to carrier terms and regulatory requirements. Movoice does not guarantee availability of a number in any given country or area code; where a carrier has no inventory for the quantity purchased, the shortfall is reported back and no number is created for it, and provisioning for some countries is completed after purchase rather than instantly.

15.3 Emergency address registration. For United States numbers, the Customer may be asked to supply a registered service address, which Movoice passes to the carrier. Supplying and maintaining an accurate address is the Customer's obligation. Movoice's registration attempt with the carrier is best-effort: a failed registration is surfaced as a status rather than blocking the number, no number is disabled for lacking an address, and Movoice does not warrant that a supplied address has been accepted by or transmitted to the carrier. Read section 21 before relying on any of this.

15.4 Porting. Where the Customer asks Movoice to port a number in, it must supply the requester's legal name, individual or business status, legal business name, full service address, the numbers to be ported, and where requested a copy of a phone bill. The Customer warrants it is authorised to port those numbers.

15.5 Reclamation and reassignment. Movoice or the underlying carrier may suspend, reclaim, port-restrict, or reassign a number upon non-payment, wallet depletion, prolonged inactivity, account closure, regulatory or carrier direction, or violation of these Terms. In practice today: on wallet depletion a wallet-billed number is deactivated rather than released, and reactivates once the wallet is topped up, and we send a low-balance notice before that point. One path is irreversible — where a number slot obtained through an in-app purchase lapses or is revoked, the number is released at the carrier and cannot be recovered. On account deletion, provisioned numbers are given up and cannot be recovered: international numbers are released back to the carrier automatically, and Indian numbers are released by hand, because our Indian carrier offers no automatic release. The Customer has no ownership right in any number and no right to a specific number, and is responsible for any regulatory obligations attached to numbers it uses.

16.1 Scope. Movoice publishes a REST API, client libraries and an MCP server. Everything in these Terms applies to use of them, and in particular sections 5 to 10: the API is not a route around any compliance obligation, and consent, disclosure, opt-out, calling-window and registry duties apply identically to API-originated traffic.

16.2 Access and keys. API access requires a paid plan. Secret keys are shown once and cannot be recovered; publishable keys are scoped to the chat widget and are safe to embed; legacy account keys are accepted for the widget only and are subject to retirement. Secret keys must be used server-side only. The Customer is responsible for all activity under any key it issues, whether or not authorized, and must revoke a suspected-compromised key immediately. Movoice may revoke, disable, rate-limit or expire a key for security, abuse or non-payment.

16.3 Sandbox keys, and what they do not do. A test key prevents a real call being placed and a real message being sent, returning a synthetic response marked as not live. It does not isolate anything else: a test key creates, modifies and deletes real agents — including pushing configuration to our third-party voice engine — creates and deletes real contacts, and can hang up a live call. The sandbox is not a separate environment and must not be treated as one.

16.4 Spend. A secret key can place billable calls and send billable messages. Messaging is capped at 500 sends per key per rolling 24 hours and is gated on account balance. Calling has no per-key spend cap; it is subject to the account-level daily international spend ceiling and the anti-fraud destination and velocity blocks described in 10.5, and DOMESTIC calling is not spend-capped. The Customer bears all charges incurred through its keys, including charges resulting from a leaked key.

16.5 Limits and fair use. Requests are subject to a per-key velocity limit and a monthly per-tier request quota, which may change. These controls are applied on a commercially reasonable basis. They are not a spend cap and not a guarantee against overuse: both the velocity limiter and the quota check fail open on infrastructure fault, and the Customer remains liable for the resulting usage.

16.6 Webhooks. The Customer may register HTTPS endpoints for call events. The payload contains the Recipient's phone number, call metadata, the AI summary, the recording link and the full transcript. Deliveries are signed with HMAC-SHA256 and the Customer is responsible for verifying the signature. The Customer is solely responsible for the destination it nominates, for the security and lawfulness of processing there, and for any onward disclosure. We retry failed deliveries and disable an endpoint after 15 consecutive failures. We do not guarantee delivery.

16.7 MCP and third-party AI tooling. The MCP server is designed to receive the Customer's secret API key through a third-party AI client's configuration, where it is typically stored in plaintext. The Customer is solely responsible for keys placed into third-party tooling and for any action such tooling takes under them.

16.8 Change and no warranty. Endpoints may be published in our API documentation while still under verification, and scopes may exist that no endpoint yet serves. Endpoints and scopes may be added, changed, deprecated or withdrawn. No API endpoint carries a warranty of fitness beyond the general disclaimer in section 26.

17.1 What it is. The Service includes an in-app assistant. By default it answers questions and points you at the right control. It can also carry out steps in your account — navigating, highlighting, filling, selecting, toggling and pressing controls — but only after you separately accept an in-app agreement that describes that capability. That agreement is versioned; when the capability widens, we re-ask, and an acceptance given for a narrower capability does not carry over.

17.2 Levels. You choose how far it may go: point only; ask me before each change; or work unattended. Unattended means it stops asking, which is the point of it and also the risk of it.

17.3 What it cannot do. It cannot spend money — no checkout, plan change, top-up or number purchase. It cannot delete anything. It cannot contact anyone — no calls, SMS, WhatsApp or campaigns. It cannot touch credentials. It cannot submit identity or regulatory documents on your behalf.

17.4 What it can change. Within those limits it may, after a single in-app confirmation, make reversible account changes including adding to and REMOVING FROM your do-not-contact suppression list, changing inbound routing and WhatsApp answering and recording settings, renaming or deactivating a number, pausing or activating an agent, and creating an agent. You remain responsible for the compliance consequences of any such change, including a suppression-list change.

17.5 Your acts. Anything the assistant does at your direction is your act, and you are responsible for it exactly as if you had clicked it yourself.

17.6 It can be wrong. It reads the structure of your screen, not your intent, so it can pick the wrong row or misread what you meant. Check anything that matters before relying on it.

17.7 Record. We keep a per-step record of what it did, including the control, the route, the outcome and the value before and after. It is review-only; it is removed by your retention window or when you delete your account.

17.8 Messages it generates. The Service can compose and send messages to your Recipients on your behalf after a call, and can compose the greeting spoken at the start of that Recipient's next call. Do-not-contact and opt-out suppression is applied before sending. You warrant you have the consent required for a Recipient to receive them, and you remain responsible for AI-content labelling under section 8.2.

The Service, and all software, models, interfaces, designs, text, graphics, trademarks, and other content provided by Movoice (excluding Customer Content), and all intellectual-property rights therein, are and remain the exclusive property of Movoice and its licensors, and are protected by copyright, trademark, and other laws. Subject to these Terms and payment of applicable fees, Movoice grants the Customer a limited, non-exclusive, non-transferable, revocable license to access and use the Service during the term solely for its internal business purposes. No rights are granted except as expressly set out.

Open-source components. Client libraries and integration tooling that Movoice distributes under an open-source licence — including our client SDK and MCP server, published under the MIT Licence — are governed by that licence, and nothing in this section limits the rights it grants.

"Movoice" and related marks are trademarks of Movoice; the Customer may not use them without prior written consent. All third-party names and marks are the property of their respective owners, and Movoice is not affiliated with or endorsed by WhatsApp, Meta, Telegram, Apple or Google.

Movoice provides client applications for iOS, Android and macOS. Subject to these Terms, Movoice grants the Customer a limited, non-exclusive, non-transferable, revocable licence to install and use them.

The macOS desktop application checks for, downloads and installs updates automatically in the background, without further prompting. Updates are cryptographically verified against our signing key and take effect the next time the application is quit and reopened. If you do not wish an update to be installed, your remedy is to stop running the application. Mobile applications are updated through the App Store and Google Play under those stores' own settings.

20.1 What it is. The Service can create a synthetic voice from a short speech recording and use it to speak on calls. The sample is transmitted to the voice provider selected for the request, which builds and stores a persistent voice model. Where the mainland-China endpoint is selected, the sample is processed in China.

20.2 Whose voice. The Customer may create a synthetic voice only of (a) its own authorized representative who has consented, or (b) another person who has given informed, written consent to the creation and the intended use. The Customer represents and warrants that it holds that consent and will produce it on request, and that it will not use a synthetic voice to impersonate anyone or to deceive as to identity.

20.3 Biometric and likeness laws. The Customer is responsible for compliance with laws governing voice, biometric identifiers and likeness, including the Illinois Biometric Information Privacy Act, the Texas Capture or Use of Biometric Identifier Act, Washington's HB 1493, and Tennessee's ELVIS Act, together with equivalent laws elsewhere.

20.4 Indemnity. The Customer will defend, indemnify and hold Movoice harmless from any claim, fine, penalty or expense arising from the creation or use of a synthetic voice without the required consent or in violation of any law referred to in 20.3. This indemnity is subject to section 27.2 and is not capped.

20.5 Deletion. A synthetic voice can be deleted in the product, or by writing to privacy@movoice.ai, and we will ask the provider to delete the model.

21.1 The Service is not a telephone service. Movoice is not a replacement for a traditional or wireless telephone line and must not be relied upon to reach emergency services.

21.2 Emergency routing is the carrier's, not ours. No Movoice dial path detects, routes or blocks an emergency number; the Service hands the call to our underlying carrier like any other call, and any emergency handling that happens is theirs. For United States and Canada numbers the carrier does route a call to 911: to the emergency centre for the registered service address where an address has been registered and accepted, and otherwise to a national call centre, which must ask the caller where they are before it can help. Outside those countries there may be no emergency path through the Service at all, and there is none in India.

21.3 It can fail even where it exists. Emergency calling may be unavailable during a power, internet or device failure; while the Service is suspended for non-payment or a depleted wallet; before a number is fully provisioned; where the registered address is missing, inaccurate or out of date; or if the call is placed from a location other than the registered address. In those circumstances a call may be routed to the wrong answering point, to a national call centre, or not at all.

21.4 Registered address. Where the Customer supplies a registered service address for a United States number, it warrants that the address is accurate and complete and undertakes to update it whenever the location of use changes. Movoice's registration with the carrier is best-effort as described in 15.3 and Movoice does not warrant that an address has been accepted or transmitted.

21.5 Advisory and acknowledgement. The Customer must review the emergency-services advisory presented in the product and acknowledge it. Movoice keeps a dated record of that acknowledgement.

21.6 Notify your users. The Customer must inform every person who may use the Service through its account of the limitations in this section, and must place a clear notice where those users will see it.

21.7 Liability. To the maximum extent permitted by law, Movoice, its affiliates, licensors and Sub-processors have no liability for any claim arising from the inability to reach emergency services or from a misrouted emergency call, and the Customer will defend and indemnify Movoice against any such claim brought by a person using the Service through the Customer's account.

22.1 A separate service. Movoice AI Messaging is an optional, personal, end-to-end-encrypted messenger inside our mobile app. It is not the business calling and campaign product. The Customer/Recipient roles, the Data Processing Addendum in section 12, the campaign and telephony compliance obligations in sections 5 to 10, caller-memory, and the wallet do not apply to it. Sections 22 to 24 and our Privacy Policy section 23 govern it. You use Messaging as an individual, and Movoice is the controller of your Messaging data.

22.2 Acceptance. Before you can message anyone you must accept these Messaging Terms (sections 22 and 23) and the Community Rules (section 24). Your acceptance is recorded against the version in force. If we materially change either, we will ask you to accept again.

22.3 Eligibility, and what each step is for. Access requires all of the following: you are 18 or over; you verify your phone number by a code we send you; you prove the SIM for that same number is in the device you are using; you accept the documents in 22.2; and you complete an identity check that establishes your age. If the identity check does not establish an age, access is refused — that is a separate outcome from an ID showing you are under 18, and we treat it as such. A number banned for abuse cannot be used to open or reactivate a Messaging account.

22.4 Your content. Movoice carries sealed envelopes and cannot read your message content. It follows that we cannot pre-screen it. You are solely responsible for what you send. The only content we can act on is what a recipient chooses to attach to a report.

22.5 Handles. You may claim one active public handle. Reserved and confusable names are refused. You may change your handle, but the name you release is permanently withheld from reuse. Movoice may reclaim a handle used for impersonation or abuse.

22.6 Devices, backup and recovery. Your account may have a limited number of registered devices, and you can remove one remotely. Actions with the shape of an account takeover — including replacing your encrypted backup — are subject to a cooling-off delay and an out-of-band alarm. If you lose your recovery code we cannot restore your message history: we do not hold a key. If you enable the optional PIN unlock for your encrypted backup, we hold a wrapped copy of your recovery code, and you should read the qualification in our Privacy Policy section 23 before you turn it on. A Registration Lock may be set to stop your number being re-registered elsewhere.

23.1 What we can act on. Because we cannot read messages, enforcement rests on reports you send us and on behaviour observable without reading anything — such as how many new people an account contacts, how often it is replied to, and how many people block it.

23.2 Reporting. When you report someone, the messages you choose to attach are sent to us in readable form. That is your copy and your decision, and it is the only place message content exists in readable form in our systems. We keep the report, the reason, the date and any note you add.

23.3 What we can do. We may issue a warning; pause your ability to send; revoke a device; suspend your account; or ban the verified phone number. A pause stops new sending only — it never blocks you reading or receiving messages. A ban is always a human decision.

23.4 Child sexual abuse material. A report of child sexual abuse material triggers an immediate automatic pause on sending, before any human reviews it, and is flagged for immediate human review, after which we report to the relevant authorities where we are required or able to do so. Cases of this kind are retained indefinitely.

23.5 Appeal. If you believe an action against you was wrong, write to privacy@movoice.ai and a person will review it.

23.6 Records. Safety records outlive the case, and some outlive your account. A report is deleted 12 months after it is filed provided the case is closed by then, and an open case is never deleted at any age. A block on a number outlives a deleted account — that is the point of blocking a number rather than a login — and is deleted after 3 years. Cases and blocks involving child sexual abuse material are held indefinitely. Our Privacy Policy sections 9 and 23 carry the same detail. These records exist to keep people safe; they are never used for advertising, never sold and never shared with data brokers.

These are the rules of Movoice AI Messaging, in the words they are enforced in. Breaking one can pause your sending, revoke your devices, or ban your number.

• No illegal content of any kind.
• No nudity or sexual content.
• No harassment, threats or hate.
• No spam, scams or bulk messaging.
• 18 and over only.

What those mean in practice:

Illegal content includes child sexual abuse material, content that promotes or arranges violence or terrorism, the sale of drugs, weapons or stolen data, and material that infringes someone else's rights. Reports of child sexual abuse material are treated as set out in section 23.4.

Harassment includes repeatedly contacting someone who has blocked you or asked you to stop, threats of violence, sexual harassment, and coordinated pile-ons. Hate means attacking people on the basis of race, ethnicity, national origin, caste, religion, sex, gender, sexual orientation, disability or serious disease.

Spam and scams include unsolicited bulk messaging, phishing, impersonating a person or a business to obtain money or credentials, investment and romance fraud, and using Messaging as a marketing channel. Messaging is a personal messenger. If you want to message customers at scale, use the business product, where the consent and disclosure obligations in sections 5 to 10 apply.

Impersonation means presenting yourself as someone you are not, including through a handle, a display name or a profile photo.

Messaging is for adults. Do not use it if you are under 18, and do not help anyone under 18 to use it.

We do not read your messages, so these rules are enforced when someone reports a breach or when behaviour we can observe makes one apparent. That is a deliberate trade-off in favour of your privacy, and it means the rules depend partly on people reporting what they receive.

25.1 The programme. Movoice may operate a referral programme under which an existing account that refers a new one receives credit, and the referred account may receive credit too. The current reward amount is published in the product on the referral screen.

25.2 Form of the reward. A reward is non-transferable, non-withdrawable credit in your Movoice wallet. It is not cash, has no cash value, and is subject to the wallet terms in section 14.3.

25.3 Eligibility. A referral is attributable only where the referred account is genuinely new, signs up through your link, and does so within the attribution window shown in the product. One attribution per referred account. Self-referral, referring an account you or your organisation control, and creating accounts to generate credit are prohibited. Movoice's own and internal accounts are excluded.

25.4 When it vests. A reward vests when the referred account first takes up a paid plan, which for a plan that begins with a free trial means at the start of that trial.

25.5 Clawback. Movoice may withhold, reverse or claw back a reward where the referred account's trial is cancelled, its first payment fails, its payment is refunded, reversed or charged back, or where the referral is duplicated, fraudulent, or obtained in breach of these rules or of section 4.5.

25.6 Promoting your link. You are responsible for complying with the law when you promote a referral link, including anti-spam and advertising-disclosure rules, and you must not misrepresent Movoice or its pricing.

25.7 Changes. Movoice may vary, suspend or end the programme at any time on notice, without affecting a reward already vested.

25.8 Tax. You are responsible for any tax arising on a benefit you receive.

TO THE MAXIMUM EXTENT PERMITTED BY LAW, THE SERVICE AND ALL RELATED MATERIALS ARE PROVIDED "AS IS" AND "AS AVAILABLE", WITH ALL FAULTS AND WITHOUT WARRANTY OF ANY KIND. MOVOICE AND ITS AFFILIATES, LICENSORS, AND SUB-PROCESSORS DISCLAIM ALL WARRANTIES, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT, AND ANY WARRANTIES ARISING FROM COURSE OF DEALING OR USAGE OF TRADE. MOVOICE DOES NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED, ERROR-FREE, OR SECURE, THAT AI OUTPUTS, TRANSCRIPTS, OR SUMMARIES WILL BE ACCURATE, COMPLETE, OR SUITABLE FOR ANY PURPOSE, THAT ANY PARTICULAR CALL WILL BE RECORDED OR ANY RECORDING RETAINED, OR THAT COMMUNICATIONS WILL BE DELIVERED. AI-GENERATED OUTPUT MAY BE INACCURATE OR INAPPROPRIATE, AND THE CUSTOMER IS RESPONSIBLE FOR REVIEWING AND FOR ITS USE OF SUCH OUTPUT. MOVOICE DOES NOT WARRANT THAT USE OF THE SERVICE WILL CAUSE THE CUSTOMER TO BE, OR RESULT IN THE CUSTOMER BEING, IN COMPLIANCE WITH ANY LAW; COMPLIANCE IS THE CUSTOMER'S RESPONSIBILITY.

27.1 Exclusion of indirect damages. TO THE MAXIMUM EXTENT PERMITTED BY LAW, NEITHER PARTY, NOR MOVOICE'S AFFILIATES, LICENSORS, OR SUB-PROCESSORS, WILL BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR ANY LOSS OF PROFITS, REVENUE, GOODWILL, DATA, OR BUSINESS OPPORTUNITY, ARISING OUT OF OR RELATED TO THESE TERMS OR THE SERVICE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

27.2 Aggregate cap. TO THE MAXIMUM EXTENT PERMITTED BY LAW, MOVOICE'S TOTAL AGGREGATE LIABILITY ARISING OUT OF OR RELATED TO THESE TERMS OR THE SERVICE WILL NOT EXCEED THE TOTAL FEES ACTUALLY PAID BY THE CUSTOMER TO MOVOICE FOR THE SERVICE IN THE TWELVE (12) MONTHS IMMEDIATELY PRECEDING THE EVENT GIVING RISE TO THE CLAIM.

27.3 Carve-outs. THE EXCLUSIONS AND THE CAP IN 27.1 AND 27.2 DO NOT APPLY TO, AND ARE EXPRESSLY CARVED OUT FOR: (A) THE CUSTOMER'S INDEMNIFICATION OBLIGATIONS UNDER SECTION 28; (B) THE CUSTOMER'S BREACH OF ITS OBLIGATIONS UNDER SECTIONS 5 THROUGH 10, SECTION 20 (VOICE CLONING) OR SECTION 21 (EMERGENCY CALLING); (C) THE CUSTOMER'S PAYMENT OBLIGATIONS; AND (D) ANY LIABILITY THAT CANNOT BE LIMITED OR EXCLUDED UNDER APPLICABLE LAW. The Customer's liability under the carve-outs is uncapped.

27.4 Basis of the bargain. The parties agree that these limitations are an essential basis of the bargain and reflect a reasonable allocation of risk.

28.1 General indemnity by Customer. The Customer will defend, indemnify, and hold harmless Movoice and its affiliates, and their respective officers, directors, employees, and agents, from and against any third-party claim, and any resulting loss, liability, damage, fine, penalty, cost, or expense (including reasonable legal fees), arising out of or related to: (a) Customer Content; (b) the Customer's use of the Service; (c) the Customer's breach of these Terms or of any representation or warranty herein; or (d) the Customer's violation of any law or third-party right.

28.2 Standalone, uncapped compliance indemnity. Without limiting 28.1, and notwithstanding any other provision of these Terms, the Customer will defend, indemnify, and hold harmless Movoice and its affiliates from and against any and all claims, demands, actions, investigations, fines, penalties, statutory or liquidated damages, settlements, judgments, and expenses (including reasonable legal fees) arising out of or related to the Customer's calls, messages, recordings, transcriptions, synthetic voices, consents, list sourcing, caller identification, campaigns, or use of the developer API, including any claim under: the Telephone Consumer Protection Act and FCC or Telemarketing rules; TRAI / TCCCPR-2025 and Indian telecom rules; the DPDP Act; the GDPR and UK GDPR; U.S. federal or state wiretap, eavesdropping, or recording laws; biometric and likeness laws including BIPA, CUBI and the ELVIS Act; AI-disclosure or bot laws; emergency-calling claims under section 21; and any suspension, ban, penalty, or claim imposed by a third-party channel or carrier, including where that suspension affects a sender or account shared with other Movoice customers. This indemnity is NOT subject to the limitation of liability or the aggregate cap in section 27.

28.3 Procedure. Movoice will promptly notify the Customer of any claim for which it seeks indemnity, provide reasonable cooperation at the Customer's expense, and allow the Customer to control the defense, provided that any settlement imposing non-monetary obligations on, or admitting fault by, Movoice requires Movoice's prior written consent, and Movoice may participate with its own counsel at its own expense.

29.1 Availability. Movoice will use commercially reasonable efforts to make the Service available but does not guarantee any particular level of uptime, and the Service is provided without a service-level guarantee unless a separate written service-level agreement is executed. The Service may be unavailable due to scheduled or emergency maintenance, third-party outages, or events beyond our reasonable control. Support is provided by email at sales@movoice.ai on a commercially reasonable-efforts basis and in accordance with the Customer's plan.

29.2 A behaviour worth knowing. Where call waiting is not enabled on an account or deployment, a second inbound call arriving while the account owner is already on a call will not ring the device. It is still recorded in call history and the missed-call flow still runs. A Customer that depends on receiving concurrent inbound calls should enable call waiting rather than discover this later.

29.3 Termination by the Customer. The Customer may terminate by cancelling its subscription on the applicable rail (section 14.5) and ceasing use. Cancellation takes effect at the end of the current billing cycle and prepaid amounts are handled per section 14.

29.4 Suspension. Movoice may suspend or limit all or part of the Service, immediately and with such notice as is reasonably practicable, if: (a) the Customer breaches these Terms, including sections 5 to 10, 16, 20 or 24; (b) the account is overdue or the wallet is depleted; (c) KYC/KYB is failed or incomplete; (d) there is actual or suspected fraud, abuse, toll fraud or security risk; (e) it is required by law, regulator, carrier, or channel; or (f) the Customer's activity threatens the integrity, reputation, or security of the Service, of a shared sender, or of others.

29.5 Termination for cause. Either party may terminate for the other's material breach that remains uncured 30 days after written notice; Movoice may terminate immediately for breach of sections 5 to 10, 20 or 24, non-payment, unlawful use, or where required by law.

29.6 Effect. On termination, the Customer's right to use the Service ceases, leased numbers are given up and cannot be recovered, and Customer Content is handled per section 30. Termination does not relieve the Customer of accrued payment obligations. Sections that by their nature should survive — including 5, 6, 7, 8, 9, 10, 11, 12, 14, 16, 18, 20, 21, 23, 26, 27, 28, 30, 31, 33 and 34 — survive termination.

30.1 Retention during the term. Movoice retains Customer Content, including recordings and transcripts, for as long as needed to provide the Service, or for a shorter retention window where the Customer has configured one. Automatic time-based deletion is off by default; the control is currently in the mobile app under Settings → Data retention, with a minimum window of 30 days.

30.2 Deletion on termination or expiry. On account deletion, on termination, or on expiry of a configured retention window, Movoice will delete Customer Content — including call-recording audio in object storage, transcripts, and derived data such as caller-memory profiles — within a commercially reasonable period, except for data Movoice is required to retain by law and the categories our Privacy Policy identifies as surviving deletion. Deletion is requested in Settings, billing stops immediately, and the erasure itself runs after a short grace period so that a deletion made in error can be undone.

30.3 Carrier-held copies. Where a recording is held by an underlying carrier rather than in our own object storage, it is deleted on that carrier's own cycle.

30.4 Export. Before deletion, the Customer is responsible for exporting any Customer Content it wishes to retain, using Settings → Export my data or by request to sales@movoice.ai.

30.5 Legal holds. Movoice may retain limited data as required to comply with law, resolve disputes, prevent fraud and abuse, or enforce these Terms. Where a legal hold is in force, scheduled deletions are suspended — including the audit-log purge and configured retention sweeps across accounts, not only the account a dispute concerns.

Apple App Store. If you download the Movoice AI application from the Apple App Store, you acknowledge and agree that:

• These Terms are concluded between you and Movoice only, and not with Apple. Apple is not responsible for the application or its content.
• Your licence to use the application is a non-transferable licence to use it on any Apple-branded device you own or control, as permitted by the Apple Media Services Terms of Service.
• Apple has no obligation to provide maintenance or support for the application.
• Apple is not responsible for addressing any claim you or a third party has relating to the application, including product-liability claims, any claim that the application fails to conform to a legal or regulatory requirement, and claims under consumer-protection or similar law.
• Apple is not responsible for investigating, defending, settling, or discharging any third-party claim that the application infringes intellectual-property rights.
• If the application fails to conform to any applicable warranty, you may notify Apple, and Apple may refund the purchase price (if any). To the maximum extent permitted by law, Apple has no other warranty obligation with respect to the application.
• You represent that you are not located in a country subject to a U.S. Government embargo or designated as a "terrorist supporting" country, and that you are not listed on any U.S. Government list of prohibited or restricted parties.
• Apple and its subsidiaries are third-party beneficiaries of these Terms and, upon your acceptance, will have the right to enforce these Terms against you.

Google Play. If you download the application from Google Play, your use is also subject to the Google Play Terms of Service. Google is not a party to these Terms and is not responsible for the application.

Store billing. Where you buy a subscription or credit through Apple or Google, the store is the merchant for that transaction and its refund and cancellation policies apply, as section 14.5 and 14.6 describe.

The Customer represents that it is not located in, organized under the laws of, or ordinarily resident in any country or territory subject to comprehensive sanctions, and is not on any restricted-party or denied-persons list maintained by India, the United States (including OFAC), the European Union, the United Kingdom, or the United Nations. The Customer will not use, export, re-export, or make the Service available in violation of applicable export-control, economic-sanctions, or anti-money-laundering laws, and will not use the Service for any prohibited end-use. The Customer will not permit any Recipient contact or communication that would cause Movoice to violate such laws. Breach of this section permits immediate suspension or termination.

Movoice may modify these Terms from time to time. Where a change is material, Movoice will post the updated Terms with a revised "Last updated" date before the change takes effect, and may in addition give notice by email or in-product notice. Changes are effective on the stated effective date.

Because we do not store a per-user record of acceptance for these Terms (section 1), the Customer's continued access to or use of the Service after the effective date is what constitutes acceptance of the modified Terms. If the Customer does not agree to a change, its sole remedy is to stop using and cancel the Service before the change takes effect. The Messaging Terms and Community Rules in sections 22 to 24 are the exception: acceptance of those is recorded against a version and a material change re-prompts you in the app.

34.1 Governing law. These Terms and any dispute arising out of or related to them or the Service are governed by the laws of India, without regard to conflict-of-laws principles.

34.2 Arbitration. Any dispute, controversy, or claim arising out of or relating to these Terms or the Service, including its existence, validity, breach, or termination, that is not resolved amicably, will be finally resolved by arbitration seated in India and conducted under the Arbitration and Conciliation Act, 1996, as amended. The arbitration will be conducted by a sole arbitrator (or a panel where required), in the English language, at the seat determined by Movoice's registered office. The arbitral award is final and binding.

34.3 Injunctive relief and exclusive jurisdiction. Notwithstanding the arbitration agreement, either party may seek urgent or interim injunctive or equitable relief, and the courts located at the registered office of Movoice's contracting entity in India will have exclusive jurisdiction for such relief and for the enforcement of any arbitral award.

34.4 Waiver of class actions. To the extent permitted by law, disputes will be resolved on an individual basis, and the parties waive any right to participate in a class, collective, or representative proceeding.

35.1 Force majeure. Neither party is liable for any failure or delay in performance (other than payment obligations) caused by events beyond its reasonable control, including acts of God, natural disasters, war, terrorism, civil unrest, labor disputes, governmental or regulatory action, carrier or channel outages, internet or utility failures, and pandemics.

35.2 Assignment. The Customer may not assign or transfer these Terms without Movoice's prior written consent. Movoice may assign these Terms to an affiliate or in connection with a merger, acquisition, reorganization, or sale of assets. These Terms bind and benefit permitted successors and assigns.

35.3 Severability. If any provision is held invalid or unenforceable, that provision will be modified to the minimum extent necessary or severed, and the remaining provisions remain in full force.

35.4 Entire agreement. These Terms, together with the Privacy Policy and any order or plan the Customer selects, constitute the entire agreement between the parties regarding the Service and supersede all prior agreements and understandings on the subject.

35.5 Waiver. No waiver of any term is effective unless in writing, and no failure or delay in exercising a right waives it.

35.6 No third-party beneficiaries. Except for Movoice's affiliates and indemnified parties, and except for Apple as stated in section 31, these Terms create no third-party beneficiary rights, and Recipients acquire no rights under these Terms.

35.7 Relationship. The parties are independent contractors; these Terms create no agency, partnership, joint venture, or employment relationship.

35.8 Notices. Legal notices to Movoice must be sent to legal@movoice.ai. Movoice may give notices to the Customer by email to the account address, by in-product notice, or by posting in the Service. Notices are deemed received when sent or when posted.

35.9 Order of precedence. In case of conflict, a signed written agreement between the parties prevails over these Terms, and these Terms prevail over any linked policy, except where a data-protection provision in the DPA is more protective.

For questions about the Service or these Terms, contact us:

• Support: sales@movoice.ai
• Privacy questions and Grievance Officer (Sai Safalya Tudu): privacy@movoice.ai
• Legal notices: legal@movoice.ai

Movoice AI is provided by Metawaveai Technologies Private Limited (incorporated in India), together with its affiliate Metawaveai Technologies Inc.