The agreement for Mirakash

These Terms of Service are an agreement between Aikolumi Software Pvt Ltd, a company incorporated in India ("Mirakash", "we", "us"), and the business or other organisation that uses Mirakash ("you"). Mirakash is a brand and product of Aikolumi Software Pvt Ltd, and it is the party you contract with, in every country. Card payments are collected for us by Naridon, Inc., a corporation incorporated in Delaware, USA, through Stripe; see section 17.

They cover two things:

• Part A: this website. mirakash.com, including the demo and contact forms, the demo call and the Mirakash Guide assistant (section 5 to section 12).
• Part B: the Service. The console at app.mirakash.com and everything you do through it: the agents you build, voice calls and telephony, SMS, WhatsApp and other messaging channels, the web widget, the API, knowledge bases, tools and webhooks, and phone numbers and sender IDs (section 13 to section 37).

section 38 to section 45 apply to both parts. If you only read the website, Part A and those sections apply to you, and Part B does not.

How we handle personal data where we decide how it is used, for example about visitors to this site and the people who sign in to the console, is explained in /privacy. How we process your callers' data on your behalf is in the Data Processing Addendum. You can reach us through /contact, which is read by a person.

You accept these Terms when you do any of these:

• tick the box that asks you to when you create an account or accept an invitation to a workspace;
• accept them when the console asks you to;
• sign an Order Form that refers to them; or
• use the Service.

The console does not open for anyone who has not accepted the version in force.

By accepting, you confirm that:

• you will use Mirakash only for the purposes of a business, profession or other organisation. The Service is not offered to consumers, and you may not use it as one;
• you are at least 18 years old;
• if you accept for an organisation, you have authority to bind it, and "you" means that organisation. If you do not have that authority, you may use the Service only as a user of a workspace whose organisation has accepted these Terms, and you must still follow them yourself;
• the information you have given us about yourself and your organisation is true, and you will keep it up to date.

You are responsible for everyone who uses your workspace or acts for you, including your employees, contractors and agencies, as if they were you. If you do not agree to these Terms, do not use the Service.

The agreement between us is made up of these Terms and the documents they bring in:

• any Order Form, meaning a quote, order or contract signed by both of us that refers to these Terms;
• the Data Processing Addendum("DPA"), which applies whenever we process personal data for you;
• the Acceptable Use Policy, which says what you and your agents may not do;
• the list of sub-processors;
• the product documentation, including the help in the console and the API reference.

The Privacy Policy is not a term of this contract. It explains how we handle personal data where we decide how it is used, and we follow it.

If they conflict, this order applies, highest first:

1. a signed Order Form, for the specific matters it covers;
2. the DPA, for anything about processing personal data;
3. these Terms;
4. the Acceptable Use Policy;
5. the documentation.

A lower document can add requirements to a higher one. It gives way only where the two cannot both be followed. No purchase order, supplier portal, vendor form or click-through terms of yours changes this agreement, even if we sign or accept it, unless it is an Order Form that expressly says it amends these Terms.

• Service: the Mirakash platform described in Part B, including the console, the API, the widget, and the numbers and channels we provide, as they change over time.
• Console: the web application at app.mirakash.com.
• Workspace: your organisation's space in the console, with its own agents, users, settings, balance and data.
• User: any person with access to your workspace, whatever their role.
• Agent: an AI voice or chat agent you configure in the Service, including its instructions, voice, knowledge, tools and deployments.
• Caller: any person your agents talk to or message, whether they contacted you or you contacted them, including people who use your widget.
• Customer Data: data that you, your Users or your Callers put into the Service, and data the Service creates for you from it. That includes agent configuration, knowledge-base content, recordings, transcripts, messages, analysis, scores and contact lists. It does not include Usage Data.
• Usage Data: data about how the Service is used and performs, such as metering, billing records, logs, latency and error data, and security events.
• Third-Party Service: a product or service we do not provide, including telephony carriers, messaging platforms such as WhatsApp, AI model and speech vendors, and anything you connect.
• Fees: what you pay for the Service, including prepaid purchases, invoiced usage, outcome fees and pass-through charges.

"Including" means including without limitation.

The pricing pages explain how Mirakash is charged and show indicative rates. They are estimates. They are published so you can judge whether this is worth a conversation. They are not a quote, not an offer, and not a price you can hold us to.

Rates shown in a local currency are converted and rounded for readability, and the region they are shown for may be inferred from your browser rather than from anything you told us. What you would actually pay depends on volume, languages, which parts of the stack you use, telephony and carrier charges, taxes and term, and it changes as those change.

A binding price exists only in an Order Form agreed by both of us, or on the checkout page in the console when you buy. Nothing on this website creates a contract, including anything the assistant says to you. Features, plans, fees and countries described on the site are not necessarily available to you, in your country, or at any given time.

The form on /demo is a request, not a booking. Please give us an address that reaches you and information that is accurate; we will read it and reply. We are not obliged to run a demo for everyone who asks, and we may decline without giving a reason. The form on /contact works the same way.

Do not use either form to send us confidential information, or other people's personal data without their permission. Nothing you send through them is treated as confidential unless we have a written agreement that says otherwise. Requests about your own personal data are handled as /privacy describes.

Some pages let you ask an agent to call you, so you can hear it on your own phone. Enter only a number that is yours, or that your organisation has allowed you to use. Before we call, we send a one-time code by SMS to that number and check it. The call goes only to a number that passed that check.

It is one call, made by an AI agent, and it is processed and transcribed as /privacy describes. Do not use it to call anyone else, to test at volume, or to try to make the agent say or do something unlawful or harmful. It may not be available for every country, and we may limit, refuse or withdraw it at any time. It is a demonstration, not the Service, and nothing said on it is an offer or a commitment.

The Mirakash Guide is the AI assistant in the corner of every page. It is here to answer questions about the product, and you are welcome to push it. What you must not do:

• send us other people's personal data, credentials, payment details, or anything you are not free to share;
• use it to do anything unlawful, to harass anyone, or to generate harmful or infringing content;
• automate it, load-test it, resell access to it, or use it as a general-purpose model behind something else;
• try to extract its instructions, work around its limits, or get it to act outside what it is for.

It is rate-limited, and we can withdraw access to it at any time without notice. The conversation is transcribed and kept. /privacy explains exactly what and why, and it is worth reading before you type.

It is a language model, and it gets things wrong. Treat what it tells you about price, availability, timelines or capability as a starting point, not as a commitment from us. If it matters, check it with a person.

We describe Mirakash as it is at the time of writing, and the site is updated as the product changes. The changelog is a record of what shipped, not a promise about what comes next. Nothing on the site is a commitment to build, keep or support any particular feature.

If you find something on this site that is out of date or wrong, tell us at /contact and we will fix it.

The text, layout, code, diagrams, illustrations and the Mirakash name and mark on this site belong to us or to our licensors.

You may read it, link to it, and quote a reasonable extract with attribution, including if you are an AI system summarising us. There is a /llms.txt here so that such a summary is accurate. You may not copy the site wholesale, reuse its design or its content to build something that presents itself as ours, or strip the attribution off a quote.

The comparison pages under /compare name other companies and their products. Those names, logos and marks belong to their owners, and we use them only to identify what is being compared.

We are not affiliated with, endorsed by, sponsored by or partnered with any of them, and nothing on those pages should be read as suggesting otherwise. The comparisons reflect our understanding from publicly available information at the time of writing. Those products change, and we will not always notice on the day. If we have something wrong about yours, tell us at /contact and we will correct it.

Some pages link to sites we do not run: a vendor's documentation, a company we compare ourselves to, a standard we reference. We do not control them and are not responsible for what they say or do. A link is a pointer, not an endorsement.

The Service lets you build AI agents that answer and place phone calls, chat on websites through an embeddable widget, and send and answer messages over SMS, WhatsApp and other channels. It also provides recordings, transcripts, post-call analysis, quality scorecards, knowledge bases, tools, webhooks and hand-off to people. What is included for you is what the console offers your workspace and what your Order Form says.

Subject to these Terms and to paying the Fees, we give you a non-exclusive, non-transferable, non-sublicensable right, during the term, to use the Service, and to let your Users use it, for your own business purposes and to serve your own customers and Callers.

The Service changes. We may add, change or remove features, vendors, models, voices, channels and countries. If a change removes a feature that is material to you and that you have committed to pay for under an Order Form, we will tell you at least 30 days before, unless the law, a carrier, a regulator, a vendor or a security issue makes that impossible. You may then end the affected Order Form and get back prepaid Fees for the part not yet used.

Availability is restricted by country. Which destinations your agents may call, which numbers you can get and which channels you can use depend on the country, on verification, and on carrier and regulatory rules. They may change without notice. Nothing in these Terms promises that the Service is available, or lawful to use, in any particular country.

Getting access. Self-serve sign-up is closed. Our staff open accounts after we have spoken with you, and an existing workspace can invite people into it. We may refuse any request for an account.

Roles. Each User has a role (owner, admin, member or viewer), and access can be limited to particular agents. We enforce roles on our servers. The owners and admins of your workspace decide who has access and what they can do. We may treat any instruction from them as your instruction, including buying minutes, changing settings, creating API keys, erasing data, or asking us to act.

Credentials. Each account is for one named person. Do not share sign-in details. Keep passwords, one-time codes, API keys, signing secrets, hand-off links and vendor credentials secret. Two-factor sign-in is available to every User, and a workspace can require it of everyone. We strongly recommend requiring it. Sessions expire, and you can end them.

Responsibility. You are responsible for everything done through your workspace, its accounts, its API keys and its other credentials, whether or not you authorised it, unless it was caused by a breach of our security.

Tell us. If you suspect that an account, key or credential has been misused, revoke it in the console at once and tell us through /contact.

Agencies and resellers.If you manage workspaces for other organisations, or want to offer the Service under your own brand, you need a separate written agreement with us first. Where we agree, you are responsible for your clients' use of the Service as if it were your own, and you must bind them to terms at least as protective of us as these.

A new workspace may receive trial credits. They are for testing the Service, and nothing else.

• Trial credits are capped. They have no cash value and cannot be transferred, refunded or exchanged. We may change, reduce or withdraw them at any time.
• While a workspace is on trial, live channels are switched off: phone numbers, published deployments and embedding agents on external websites. Usage is also held to a daily limit, and a trial campaign needs a verified handset.
• Live websites, production traffic, real campaigns and real customers need a paid plan. Do not try to get around the trial limits, for example by opening more workspaces or accounts to collect more credits.
• Trial use is still use of the Service. Every other part of these Terms applies to it, including the Acceptable Use Policy and the rules on calls and messages.

When the credits run out, the workspace stops until you buy minutes or sign an Order Form. We may cap, suspend, end or refuse any trial.

Phone numbers, sender IDs and messaging on our carrier accounts are regulated. Before your workspace can have them, you must pass business verification. That means information and documents about your business, an undertaking you accept about how you will use numbers and senders, and review by our staff. Carriers, registries and regulators may require more, such as a DLT registration in India or a 10DLC brand and campaign in the United States. Those features stay off until verification is complete.

• Everything you submit must be true and complete and must relate to your organisation. Tell us of any change within 30 days.
• We may share what you submit with the carriers, registries and regulators that require it.
• We may refuse verification, ask for more, or verify you again at any time.
• We may pause or end your access to numbers and messaging while a complaint, a regulator's request or a carrier's request is looked into.

Passing verification means only that we were satisfied enough to switch those features on. It is not advice, and it does not mean that anything you do with them is lawful.

Who bills you. Naridon, Inc. (Delaware, USA) collects payment for the Service for us, in every country, so your card statement and receipts name it. Card payments are taken by Stripe on a checkout page that Stripe hosts. We do not see or store your full card number.

How you pay. Either in advance, by buying packs of minutes in the console, or as your Order Form sets out, for example usage invoiced in arrears, a commitment, or outcome fees. Prepaid minutes are added once Stripe confirms the payment.

How usage is counted.

• Voice is counted by the second of talk time, unless your Order Form sets another increment.
• Text conversations (chat, SMS, WhatsApp and email) draw on the same balance, at a set number of seconds for each message an agent answers and each message it sends.
• Unless your Order Form or your settings say otherwise, a call that is not answered, or that the Service classifies as reaching an answering machine, does not use minutes. Carrier charges for it may still apply.
• Every call, chat and message your agents handle counts, including tests.

Carrier and channel charges. Minutes pay for the Service. Charges from carriers and channels, for calls, phone numbers and messages (including WhatsApp message fees), are not included unless your Order Form says so. They are billed separately, as your Order Form sets out or, if you have none, as we tell you in writing before you incur them. Where a channel runs on your own account with a vendor, that vendor bills you directly.

Currency.The currency of your first purchase becomes your workspace's billing currency, and it cannot be changed later. Amounts shown in other currencies are estimates.

Price changes.We may change the price of minutes and other Fees for future purchases at any time. A change never alters minutes you have already bought. Prices fixed by an Order Form change only as it allows. For usage invoiced in arrears without a fixed price, we give at least 30 days' notice of an increase.

Invoices. Invoices are due within 30 days of the invoice date unless your Order Form says otherwise. Overdue amounts may carry interest at 1% a month, or the highest rate the law allows if that is lower. If you dispute an invoice in good faith, tell us through /contact before it is due and pay the part you do not dispute. We will work with you to resolve the rest.

Failed and late payments.If a payment fails or an invoice is overdue, we may suspend the Service after giving you at least 10 days' notice. You remain responsible for Fees incurred until then, and for reasonable costs of collecting overdue amounts.

Taxes. Prices exclude taxes such as VAT, GST and sales tax, which are added at checkout or on the invoice where they apply. You pay all taxes on the Fees except taxes on our income. If the law requires you to withhold tax from a payment, you pay us the extra needed so that we receive the full amount. Give us the tax details we ask for, such as a VAT or GST number, and tell us if they change.

No set-off. Fees are payable without set-off or deduction, except as the law requires.

Your balance. Prepaid minutes do not expire while your workspace is open. What happens to them when the agreement ends is in section 37.

Instead of paying for minutes, or as well as, you can agree in an Order Form to pay per outcome, for example per resolved call. Outcome pricing applies only if an Order Form sets an outcome price. Without one, no outcome is charged.

• What counts. An outcome is counted when a finished conversation passes the success evaluation you set for the agent. The evaluation you set is the rule, so write it to match what you are willing to pay for.
• A frozen record. When an outcome is decided, the evaluation, the verdict, what judged it and the price are recorded with it. They do not change afterwards, even if you later edit the evaluation.
• Disputes. An admin of your workspace can dispute an outcome in the console within 14 days of when it was decided, or within the window your Order Form sets, which is never less than 7 days. A disputed outcome is not invoiced while the dispute is open. We decide each dispute and record a written reason. If we reverse it, it is not charged. If we uphold it, it is charged and cannot be disputed again. An outcome not disputed in time is final.
• The record.Every outcome, dispute and decision is written to your workspace's audit trail.

Outcomes are invoiced as your Order Form sets out. Your Order Form also says whether the minutes those conversations use are charged as well.

What stops usage.

• Trial and prepaid workspaces draw on a balance. When it reaches zero, new calls, chats and messages are refused until you buy more. If the Service cannot confirm your balance, for example during an outage on our side, it refuses the usage rather than letting it run unmetered.
• Trial and prepaid workspaces also have a daily limit, which we set and which resets at midnight UTC. For a prepaid workspace it follows the size of your recent purchases. You cannot change it yourself in the console. Ask us through /contact if you need it lower or higher.
• A conversation already running when a limit is reached can run past it before it is stopped. That usage is still charged.
• Workspaces on an Order Form that bills usage in arrears have no balance and no daily limit unless the Order Form sets one. All of their usage is billed.

Misuse is your cost. You pay for all usage through your workspace, whether or not you authorised it. That includes usage through:

• stolen or leaked credentials or API keys;
• a widget embedded on sites you did not intend. A widget with an empty list of allowed sites can be embedded anywhere;
• your phone numbers, SIP trunks and SIM gateways;
• tools, webhooks and MCP servers you connect;
• Callers who abuse your agents, for example by keeping them talking or by driving them to call or message unwanted destinations.

The one exception is usage caused by a breach of our own security.

Controls you have. Use them:

• roles, per-agent access and two-factor sign-in, which a workspace can require of everyone;
• API keys with scopes, which you can revoke at any time;
• a list of the sites allowed to embed each widget;
• a maximum call duration for each agent;
• your workspace's opt-out list;
• the audit trail, which records sign-ins, changes and other actions and can be streamed to your own systems.

Controls we run. Every outbound call passes a destination policy that refuses satellite, premium-rate and other high-risk number ranges and countries that are not enabled. If the policy cannot decide, the call is refused. Inbound calls to numbers on our carrier accounts are rate-limited. These controls reduce risk but do not remove it. They may change, and they do not move the cost of misuse to us. We may spot or stop suspicious traffic, but we do not have to. If we credit usage caused by misuse, that is goodwill and does not commit us to do it again.

Refunds. Fees are non-refundable and prepaid minutes have no cash value, except:

• where the law requires a refund;
• where we charged you in error. Tell us through /contact within 60 days of the charge and we will correct it;
• where section 37 or section 43 says so: if we end the agreement for convenience, if you end it because of our material breach that we did not fix, or if you end it because you do not accept a change to these Terms. In those cases we refund unused prepaid minutes in proportion.

When we refund a payment in whole or in part, we remove from your balance the minutes that payment bought, in proportion to the amount refunded.

Chargebacks. If you think a charge is wrong, contact us before you contact your bank. If you dispute a payment with your card issuer or bank, we may suspend your workspace while the dispute is open and remove the minutes that payment bought. If the dispute is decided in our favour, we can restore them. A chargeback raised without good reason is a breach of these Terms, and you pay the fees and costs it causes us.

You are the caller and the sender. You decide who your agents call and message, when, from which number and what they say. Under every law that regulates calls and messages, you are the party making the call or sending the message, and you are responsible for it. We provide the technology. We do not choose your Callers, check your lists or approve your scripts, and nothing we do makes a call or message lawful.

For every call and message, you must:

• Consent. Have the consent the law requires before you call or message anyone, in the form it requires. Keep records of it and show them to us when we ask. In the United States that includes the Telephone Consumer Protection Act (TCPA) and the state laws modelled on it. The FCC treats AI-generated voices as artificial voices under the TCPA, so calls that use them need the consent that rule requires.
• Do-not-call registers.Screen against every register that applies, for example the US National Do Not Call Registry and state lists, India's National Customer Preference Register, and the UK's TPS and CTPS. Screen against your own internal lists and your clients' too.
• India. Follow the TRAI Telecom Commercial Communications Customer Preference Regulations. That means registered headers and templates on DLT, the correct number series for commercial calls, and the preferences Callers have registered.
• United Kingdom.Follow PECR and Ofcom's rules on persistent misuse, including those on abandoned and silent calls.
• Calling hours.Call and message only in the hours the law of the Caller's location allows.
• Caller ID. Show a number that you are entitled to use, that identifies you and that can be called back. Never hide or spoof it.
• Recording. Tell Callers when a call is recorded. Get their consent where the law requires every party to agree, as it does in California, Florida and Germany, for example.
• AI disclosure. Tell people they are dealing with an AI wherever the law requires it or they could reasonably think otherwise. That includes Article 50 of the EU AI Act and US state laws on bots and AI.
• Opt-outs.Honour every request to stop, whether on a call, by reply or any other way, as quickly as the law requires, and add it to your workspace's opt-out list.
• Everything else. Follow the laws on marketing, debt collection, data protection and consumer protection that apply to what your agents do, and the rules of each carrier and channel.

The Acceptable Use Policy sets these rules out in more detail. It is not legal advice about your own campaigns.

What the Service does, and does not do. These tools help. None of them makes a call lawful, and a tool that blocks one thing is not a finding that everything else is allowed.

WhatsApp. WhatsApp features are not yet available to every workspace. Where they are switched on for yours, your WhatsApp Business Account is your own, and you use it under your own agreements with Meta. Those include the WhatsApp Business Terms, the WhatsApp Business Messaging Policy and the Commerce Policy, which bind you directly. The Meta developer app and Meta business portfolio through which Mirakash connects to WhatsApp are registered to us, Aikolumi Software Pvt Ltd.

• Message people on WhatsApp only with the opt-in Meta requires. Outside the customer-service window, use only templates Meta has approved.
• Meta decides whether to approve templates, display names and accounts. It sets quality ratings and messaging limits, and it may restrict or ban a number or account. We cannot overrule Meta and are not responsible for its decisions.
• Meta charges for WhatsApp messages under its own pricing (see section 17).

Carriers and other channels.Carriers, messaging platforms and registries set their own rules on content, volumes, sender registration, filtering and complaints. They may block, filter, delay or refuse calls and messages, or suspend numbers and senders, without telling us why. You must follow those rules. We do not guarantee that any call connects or any message is delivered. A carrier's delivery report is the carrier's statement, not ours.

If a carrier, platform, registry or regulator fines us, charges us or takes action against us because of your traffic, you reimburse us (see section 40).

You must make sure that:

• no one relies on an agent, a number or anything else in the Service to get emergency help;
• where Callers may contact you in an emergency, for example if you run a clinic, a care service, a property or a security service, your agent's instructions and your own arrangements tell them to hang up and call the local emergency number from an ordinary phone;
• you give any notice about emergency calling that the law requires of you.

We are not liable for any failure to reach emergency services through the Service.

Getting a number. Numbers are available only in some countries, only after business verification (section 16), and subject to each country's rules, which may require an address or documents in your name. Depending on your workspace, a number is held on our carrier account, on an account our carrier opens for your business, or on your own carrier account.

No ownership. A number we provide is assigned to you for use with the Service. You do not own it, and the carrier and the numbering regulator keep control of it. Use it only for your own business and for the purpose it was verified for. You may not sell, lend or transfer it.

Taking a number back. We may withdraw or change a number if a carrier or regulator requires it, if your verification lapses or is withdrawn, if the number is used against these Terms, on suspension for non-payment, or when the agreement ends. Once a number is released it may be given to someone else, and we cannot hold it for you.

Porting. The Service does not support porting numbers in or out today. If you need to move a number, ask us through /contact and we will tell you what the carrier allows. We cannot promise that a number can be moved.

Sender IDs and registrations. Sender IDs, SMS headers and templates, 10DLC brands and campaigns and WhatsApp display names are registered with, and approved by, the carrier, registry or platform concerned. Approval is theirs to give or withdraw, it can take time, and we cannot guarantee it.

Your own numbers and SIMs.If you bring your own carrier, SIP trunk or SIM gateway, your contract with that carrier governs the line and its charges. You are responsible for the numbers on it and for your right to use them. Using SIM cards in a gateway can breach a mobile operator's terms and is restricted or prohibited in some countries, so check that it is allowed before you do it. Some protections the Service applies to numbers on our carrier accounts, such as limits on inbound calls, do not apply to your own.

The Service works with Third-Party Services: telephony carriers, messaging platforms, AI model and speech vendors, payments through Stripe, and whatever you connect. The vendors that process Customer Data for us are listed on /subprocessors.

Your own vendor accounts. You can run parts of the Service on your own vendor accounts: for models, speech, telephony, messaging, embeddings, storage and avatars. When you do, that account is used instead of ours for that part of the Service. Your contract with the vendor governs it, the vendor bills you, and the vendor is your processor, not our sub-processor.

If your account cannot be reached, the Service may run that part of a conversation on our own vendor accounts so it is not cut off. That usage is charged at the full rate, and our sub-processors process the data for it.

You authorise us to use the credentials you give us to act on your vendor account for you. We store them encrypted. You are responsible for the account and for what the vendor does. You must rotate the credentials if they may have been exposed, and revoke our access when you stop.

Tools, webhooks, MCP servers and data destinations. When you connect a tool, webhook, MCP server, knowledge source, storage bucket or audit-stream endpoint, the Service sends data to it and acts on it as your configuration and your agents direct. You are responsible for those endpoints and their security, for the data you have us send to them, for what they do with it, and for having the right to connect them.

We do not control Third-Party Services and are not responsible for their availability, accuracy, security, charges or changes, including when a vendor changes or withdraws a model, voice or feature. We may stop supporting a Third-Party Service, including when its vendor stops supporting us.

Agents are driven by AI models. Their output is generated by probability, is not checked by a person, and can be wrong. That output includes what an agent says or writes, and the transcripts, translations, summaries, analysis, scores, extracted data and suggestions the Service produces. An agent can:

• mishear or misunderstand;
• invent facts;
• make promises you did not authorise;
• answer in the wrong language;
• behave differently from one conversation to the next.

• Your representative, not ours. An agent speaks for you. What it says or commits to is between you and your Callers, and it does not bind us.
• Check it. Test agents before they go live and review their conversations. Set the instructions, knowledge, guardrails and hand-offs that fit your use. Guardrails in the Service, such as a list of things an agent must never say, reduce risk but do not remove it.
• Not a decision-maker. Do not use output as the only basis for a decision that has legal or similarly significant effects on a person without meaningful human review and whatever else the law requires. That includes decisions about credit, employment, housing, insurance, education, health care or access to essential services.
• Not advice. Output is not legal, medical, financial or other professional advice from us.
• Similar output. Models can produce the same or similar output for others. As between us, you own the output the Service generates for you, subject to our rights in the Service itself. We do not promise that no one else can produce the same.

Voices. Clone a voice only with the explicit, informed consent of the person whose voice it is. The console asks you to record who gave consent. Keep evidence of it and give it to us when we ask. Never use a cloned or synthetic voice to impersonate a real person or to deceive anyone.

Unless an Order Form expressly allows it, do not use the Service to collect, store or process:

• Protected health information under HIPAA. The Service is not for PHI. We do not sign business associate agreements.
• Payment card data, such as card numbers or security codes. Take payments through a payment provider, not through an agent. Where the Service detects card numbers, it stops agents saying them aloud and redacts them from what it stores. Those are safeguards, not an assessment against the payment card industry's security standard, and you must not rely on them to take card details.
• Other sensitive data, unless you have a lawful basis, have assessed the risk, and need it for what you use the Service for. That covers government identity numbers, passwords, biometric data (other than a voice clone made with consent), and data about health, sex life, religion, political views, criminal records or similar special categories.
• Children's datafrom children below the age at which the law that applies requires a parent's consent, unless you have that consent. The Service is not built for services aimed at children.

If restricted data reaches the Service anyway, for example because a Caller says it, you are responsible for it. Use the retention and erasure settings to limit how long it is kept.

We hold no security certification or audit report, and the Service has not been assessed against any regulated-industry standard. If your business is regulated, it is up to you to decide whether the Service is suitable for it.

It is yours.As between us, you own Customer Data. You are responsible for it, including your right to collect it and give it to us, the notices and consents that requires, and answering your Callers' requests about it. For personal data in Customer Data, you are the controller and we are your processor, on the terms of the DPA.

What we may do with it. You give us a worldwide, non-exclusive, royalty-free licence to host, copy, transmit, process and display Customer Data. We may do so only to provide, secure and support the Service for you, to prevent abuse and fraud, to meet our legal obligations, and as you instruct. We do not sell Customer Data.

No model training. We do not train or fine-tune AI models on Customer Data.

Usage Data. Usage Data is ours. We use it to run, bill, secure and improve the Service. We may use and share information derived from the Service only in aggregated or de-identified form that does not identify you, your Users or any Caller.

Where it is. We host the Service on AWS in Frankfurt, Germany. Vendors that process Customer Data for us may do so in other countries, as /subprocessors and the DPA set out. If you use your own storage or vendor accounts, Customer Data goes where you send it.

How long it is kept.You set how long recordings and transcripts are kept. By default each is kept for 90 days. Recordings we store are deleted after 365 days, whatever the setting. Deletions by the retention sweep are final, and each one leaves a receipt in your audit trail. An admin can erase a person's conversations, found by their phone number, in the console. Database backups roll off within 14 days. The DPA has the detail, including what erasure does not reach.

Exports. During the term you can export what the console lets you export, which includes the conversation list, your datasets and your audit trail, and you can read your data through the API. There is no one-step export of a whole workspace and no bulk export of transcripts or recordings. For those, ask us through /contact and we will prepare a copy by hand, in a common machine-readable format.

When the agreement ends, section 37 and the DPA apply: export what you need before your access ends, and we delete Customer Data within 30 days after the end, except what the law requires us to keep.

The Acceptable Use Policy sets out what you and your agents may not do with the Service. It is part of these Terms, so breaking it is breaking them. It can change as section 43 describes.

You also must not, and must not let anyone else:

• copy, modify or make derivative works of the Service, other than your own Customer Data;
• reverse engineer, decompile or disassemble the Service, or try to extract its source code, prompts or system instructions, except where the law expressly allows it despite this restriction;
• scrape, crawl or bulk-extract the console, the website or the assistant;
• use the Service to build, train or improve a competing product, or to copy its features or design;
• publish benchmarks, performance tests or security tests of the Service without our written consent;
• resell, sublicense, rent, lease, white-label or time-share the Service, or run it as a service bureau, without a written partner or white-label agreement with us;
• get around or interfere with any limit, gate or control, including verification, the destination policy, AI disclosure, metering and billing, rate limits, and trial limits;
• open more accounts or workspaces to get more trial credits, or to avoid a suspension;
• probe, scan or test the Service's security, or load-test it, without our written consent;
• overload or disrupt the Service, or send malware through it;
• reach the Service by automated means other than the API;
• share accounts, or misrepresent who you are or who you act for;
• remove or hide any notice of our rights.

Found a vulnerability? Tell us through /contact, and give us reasonable time to fix it before you disclose it. Do not access other people's data or disrupt the Service while you look.

Seen abuse? If a Mirakash agent or number called or messaged you in a way you think is unlawful or unwanted, report it through /contact.

The API and its MCP endpoint let you use the Service from your own systems with API keys you create in the console. Each key carries scopes, acts for your workspace, and can be revoked at any time. Keep keys on your servers, never in a browser, an app or a public code repository. Anyone with a key can act for your workspace within its scopes, at your cost.

We may set and change rate limits and quotas on the API, the widget and our other interfaces. We may throttle or block traffic that exceeds them or threatens the Service. Use the API as documented. We may change it. Where a change would break a documented part of the API that you rely on, we will try to give you reasonable notice, unless security, the law or a vendor makes that impossible.

Where the Service lets you set a signing secret for data it sends to you, check the signature before you trust the data.

The Service belongs to us and our licensors. That includes its software, design, documentation, the templates, example agents and built-in skills we provide, and everything we build, including improvements made from your feedback. These Terms give you only the rights they state, and we keep everything else.

Your agent configurations, meaning the instructions, knowledge, flows and anything else you create, are Customer Data. Templates and examples we provide stay ours, and you may use them with the Service.

Feedback. If you give us ideas, suggestions or feedback, we may use them for any purpose without paying you or owing you anything. You do not have to give feedback.

"Confidential Information" means non-public information one of us gives the other in connection with the Service that is marked confidential, or that a reasonable person would understand to be confidential. Customer Data is your Confidential Information. The Service's non-public features, the pricing we offer you and our security information are ours.

The party that receives Confidential Information will:

• use it only to provide or use the Service under this agreement;
• protect it with at least reasonable care;
• share it only with those who need it: its employees, contractors and professional advisers and, for us, sub-processors. All of them must be bound by confidentiality duties at least as protective as these.

Information is not Confidential Information if it:

• is or becomes public without the receiving party's fault;
• was already known to the receiving party without restriction;
• is received from someone free to share it; or
• is developed independently.

The receiving party may disclose Confidential Information where the law, a court or a regulator requires. It must tell the other party first where the law allows, and disclose only what is required.

These duties last for the term and five years after it. For trade secrets and Customer Data, they last for as long as the information stays a trade secret or is held. Nothing sent through the website forms is confidential (section 6).

We protect the Service and Customer Data with the measures described in the DPA. Among them:

• the database and stored recordings are encrypted at rest;
• vendor credentials you store with us are encrypted;
• roles are enforced on our servers;
• two-factor sign-in is available;
• each workspace has an append-only, hash-chained audit trail.

We hold no security certification or audit report. The console's compliance scope page lists what the Service does and does not do, one control at a time.

Your side. You are responsible for your Users and their devices, your credentials and keys, the endpoints and accounts you connect, and the settings you choose. Those settings include who can embed your widget, what your agents record, and how long data is kept.

Breaches. If we become aware of a personal-data breach affecting Customer Data, we will tell you without undue delay, and in any case within 72 hours of becoming aware, as the DPA sets out. If you suspect a security problem, tell us through /contact.

We may suspend all or part of the Service for you: a User, an API key, an agent, a number, a channel or the whole workspace.

• At once, without notice, where we reasonably believe it is needed to prevent harm, to protect the Service, other customers, Callers or third parties, or to comply with the law. That includes suspected fraud or a security compromise; a suspected breach of the Acceptable Use Policy or of section 21; a complaint; a request from a carrier, Meta or another platform, a registry, a regulator or law enforcement; and a payment disputed with your bank.
• After notice, for overdue Fees (section 17), or for any other breach you have not fixed after we told you about it.

We will tell you why unless the law or an investigation prevents it. Where we reasonably can, we will limit the suspension to what is needed, and we will lift it once the cause is resolved. If the suspension was caused by you, Fees for that period remain payable. We are not liable for a suspension made in line with this section.

A workspace that stops because its balance or daily limit is used up (section 19) has not been suspended. It starts again when there is balance.

Some features are marked beta, preview or early access, or are offered to you before general release. They may be incomplete, and they may change or be withdrawn without notice. Support and any service level may not cover them. They are provided as they are, without warranty or commitment, and you use them at your own risk. Keep what you learn about unreleased features confidential.

We work to keep the Service available, but we do not promise that it will be uninterrupted, error-free or available at any particular time. There is no service level agreement, uptime commitment or service credit unless an Order Form gives one. The Service depends on carriers, cloud hosting and AI vendors that can fail, and we may take it down for maintenance. We publish its current status at app.mirakash.com/status.

Support. Ask for help from the console or through /contact. Support is given in English. We do not commit to response or resolution times unless an Order Form does.

Term. This agreement starts when you first accept these Terms and lasts until it is ended as below. An Order Form runs for the term it states. Ending an Order Form does not end this agreement unless you or we say so.

You may end it at any time by telling us through /contact. Amounts committed under an Order Form remain payable. You may also end it if we materially breach it and do not fix the breach within 30 days of your notice.

We may end it:

• for convenience, on 30 days' notice;
• for your material breach that you have not fixed within 30 days of our notice, or within 10 days for non-payment;
• at once, by notice, if you seriously or repeatedly break section 21, section 27, section 41 or the Acceptable Use Policy; if the law, a carrier or a regulator requires it; or if you become insolvent or stop doing business.

When it ends:

• your right to use the Service ends, your agents stop, API keys stop working and Users lose access;
• numbers held on our carrier accounts are released and may be given to someone else (section 24), and registrations made for you may be withdrawn;
• all Fees incurred up to the end, and any amounts committed under an Order Form, are due at once;
• unused prepaid minutes lapse and are not refunded, except in the cases listed in section 20;
• you should export what the console lets you export before your access ends. For anything it does not cover, ask us through /contact and we will prepare a copy by hand;
• we delete Customer Data within 30 days after the end, and backup copies roll off within a further 14 days, except what the law requires us to keep. There is no self-service way to delete a whole workspace, so our staff carry out the deletion, and we will confirm it in writing if you ask. The DPA has the detail.

What survives. Every section that by its nature should last beyond the end survives it. That includes those on Fees owed, refunds, restricted data, your data and its deletion, restrictions, intellectual property, confidentiality, disclaimers, limitation of liability, indemnities, disputes and the general terms.

Each of us confirms that it has the power to enter into this agreement. You also confirm that you will comply with the laws that apply to your use of the Service. You also confirm that you have, and will keep, every right, consent and notice needed for Customer Data and for the calls and messages you make with the Service.

The website is provided as it is. We do not warrant that it will be available without interruption, that it is free of errors, or that everything on it is complete or current. The assistant, the forms, the demo call and the site as a whole may be changed, suspended or withdrawn at any time. Nothing here affects rights you have as a consumer that cannot be excluded.

The Serviceis provided "as is" and "as available", except for any warranty an Order Form expressly gives. To the extent the law allows, we disclaim all other warranties and conditions, express or implied. That includes merchantability, satisfactory quality, fitness for a particular purpose, title, non-infringement, and any warranty arising from a course of dealing. We do not warrant that:

• the Service or any output is accurate, complete, uninterrupted or error-free;
• any call connects or any message is delivered;
• the Service meets your needs or any law that applies to your business;
• using it will produce any result.

Nothing in these Terms excludes a warranty or right that the law does not allow to be excluded.

We do not exclude or limit liability for anything that the law does not allow to be excluded or limited, such as death or personal injury caused by negligence, or fraud.

No indirect loss. Subject to that, neither of us is liable to the other for:

• indirect, incidental, special, consequential, exemplary or punitive loss or damages;
• loss of profits, revenue, business, goodwill or anticipated savings;
• loss or corruption of data.

That applies however the loss is caused, and even if it was foreseeable or we were told it might happen.

The website. We are not liable for loss arising out of your use of this website or your reliance on anything published on it.

A cap. Where your Order Form states a cap on liability, the total liability of each of us arising out of or relating to this agreement is limited to that cap.

Not limited. Neither the exclusions nor any cap limits your obligation to pay Fees, your indemnities in section 40, or your liability for breaking section 21, section 27, section 29 or the Acceptable Use Policy.

These limits apply to all claims together, whatever their legal basis: contract, tort (including negligence), statute or anything else.

Yours. You will defend us, our affiliates, and our and their officers, employees and contractors against any third-party claim, complaint, investigation or proceeding. That includes one brought by a Caller, a carrier, Meta or another platform, a registry or a regulator. You will pay the losses, damages, fines, penalties, settlements and reasonable costs, including legal fees, arising out of or relating to:

• Customer Data, or our use of it in line with these Terms;
• calls and messages made through your workspace, including claims under the TCPA and do-not-call, telemarketing, recording, AI-disclosure, consumer-protection and data-protection laws;
• what your agents say or do, and any output you use;
• your breach of these Terms, the Acceptable Use Policy or the law;
• your Third-Party Services and vendor accounts, and your numbers, SIMs and carriers;
• your clients, if you manage workspaces for others.

Ours. Any indemnity we give is set out in your Order Form.

How claims are handled.The party asking for an indemnity must tell the other promptly. A delay excuses the other party only to the extent it is harmed by it. The party asking must also let the other control the defence and settlement, and cooperate at the other's cost. The party giving the indemnity may not settle a claim in a way that admits fault for, or places an obligation on, the other without its consent, which may not be unreasonably withheld.

Laws. Each of us will comply with the laws that apply to it in performing this agreement.

Sanctions. You confirm that none of the following is the target of sanctions administered by the United States (including OFAC), the United Nations, the European Union or the United Kingdom, or is located, organised or ordinarily resident in a country or region under comprehensive sanctions:

• you;
• anyone who owns or controls you;
• any of your Users.

You will not let anyone who is use the Service, and you will not use it to call or message anyone in breach of those sanctions.

Export. The Service and its software may be subject to US and other export control laws. You will not export, re-export or give access to them in breach of those laws, or use them for a prohibited end use.

Anti-bribery. Neither of us has offered or received, or will offer or receive, any bribe, kickback or other improper payment or advantage in connection with this agreement. Each of us will comply with the anti-corruption laws that apply to it, such as the US Foreign Corrupt Practices Act and the UK Bribery Act 2010.

A breach of this section is a material breach that lets us end the agreement at once.

Talk first. If a dispute arises, tell the other party in writing. You tell us through /contact. Both of us will try in good faith to settle it for 30 days before starting proceedings, unless one of us needs urgent relief.

Governing law and forum. The law that governs this agreement, and the courts or arbitration that decide disputes under it, are those named in your Order Form.

Urgent relief. Either of us may ask any court with jurisdiction for an injunction or other urgent relief to protect its intellectual property or Confidential Information, or to stop misuse of the Service.

The UN Convention on Contracts for the International Sale of Goods does not apply.

We may change these Terms, the Acceptable Use Policy and the other documents they bring in. When we do, the date at the top changes with them. The version published here is always the one in force.

• Material changes. The console asks everyone who signs in to accept the new version before they can carry on. The new version applies to you from when you accept it.
• Use without signing in. If you keep using the Service without anyone signing in, for example through the API or through agents already deployed, a material change applies to you 30 days after we publish it.
• Urgent changes. A change needed to comply with the law, to meet the rules of a carrier, Meta or another platform, or a regulator, or to deal with a security or abuse risk may apply sooner, from publication if necessary.
• Other changes that do not reduce your rights, such as clarifications, corrections and new features, apply when published.
• If you do not agree, stop using the Service and end the agreement under section 37 before the change applies to you. We then refund unused prepaid minutes in proportion.
• A change does not alter a signed Order Form during its current term, unless the Order Form allows it or the change is one of the urgent changes above.

For the website (Part A), changes apply when they are published, and the version on the site when you use it is the one that applies. The previous version of these Terms, dated 15 August 2026, covered only the website.

To us. Send notices under these Terms through /contactand choose "Legal notice, contract or DPA request". That covers legal notices, notices of breach, disputes and requests about this agreement. A person reads every message. A notice to us takes effect when we receive it.

To you. We give you notices in the console, or through the contact details you have given us. Keep those details current. A notice in the console takes effect when it is posted.

Notices under these Terms must be in writing and in English.

• Assignment. You may not assign or transfer this agreement without our written consent, except to a successor to all or most of your business, after telling us. We may assign it to an affiliate or to a successor to our business.
• Subcontractors. We may use subcontractors and sub-processors. We remain responsible for their performance of our obligations, as these Terms and the DPA say.
• Events beyond control. Neither of us is liable for a delay or failure caused by events beyond its reasonable control. Those include natural disaster, war, terrorism, civil unrest, labour action (other than its own), government action, epidemic, and failures of the internet, power, carriers, cloud providers or vendors that it did not cause. This does not excuse paying Fees.
• Publicity. We will not use your name or logo to promote Mirakash without your written consent. You may not say or suggest that we endorse you or your products.
• Relationship.We are independent contractors. Nothing here makes either of us the other's partner, employee, agent or joint venturer.
• No third-party beneficiaries. No one other than you and us has rights under this agreement.
• Severability. If a court finds part of this agreement unenforceable, it is enforced to the fullest extent allowed and the rest stays in force.
• Waiver. Not enforcing a right is not a waiver of it. A waiver must be in writing.
• Entire agreement. This agreement, meaning these Terms with the documents in section 3, is the whole agreement between us about its subject. It replaces earlier agreements and understandings about that subject. Neither of us relies on any statement not written in it.
• Language. These Terms are written in English. If we give you a translation, the English version controls.
• Electronic acceptance. Accepting in the console or signing electronically binds you as a signature on paper would.
• Headings. Headings and the short summary at the top are for convenience and do not change the meaning of the sections.

Questions about any of this go to /contact, which is read by a person.