When your agents talk to people, you decide what happens to what they say. For that data you are the controller, and we are your processor: we handle it only to run the Service for you, under our Data Processing Agreement.

A sub-processor is another company we engage to process that data for us. This page is the complete list of them. It covers the personal data in your workspace:

• what callers, customers and contacts say to your agents, and what the agents say back: call audio, recordings, transcripts, chat and text messages;
• their phone numbers and other contact details, and the records of each call and message;
• anything your agents' tools fetch or send during a conversation;
• the documents you add to a knowledge base, where they contain personal data;
• the names, email addresses and sign-in records of the people who use your console.

It does not cover vendors you bring your own account for (section 05), or the vendors we use for our own website and business (section 06).

Mirakash is a brand of Naridon, Inc., a corporation incorporated in Delaware, USA, which is the party to your contract with us.

These two process data for every workspace, whatever you configure.

Each vendor below processes your data only when the condition in its last column is met. A text-only chat agent, for example, involves no carrier and no speech vendor at all. Some of these are wired in as options and fallbacks and rarely carry traffic. They are listed anyway, so that the list covers every vendor the platform can route your data to.

Two things move data between vendors in these tables without you choosing a new one. If a speech vendor fails during a call, the call continues on the next available vendor so the sentence is finished; and if a language model fails, the next one in line answers. Both only ever move to vendors on this page.

Calls and text messages

Trial calls to the test numbers you verify also run on Mirakash's own carrier account. Between our carrier and the person at the other end, a call or text may also cross other telephone networks, as every call does. The carriers choose those networks, not us, and they are not listed here.

Speech

Pipeline voice agents use one vendor to turn the caller's speech into text and another to speak the reply. Native-audio agents use Google for both and involve none of these.

Language models

These depend partly on our settings rather than yours: when we have one of them switched on, it can take text replies and analysis ahead of Google, with Google as the fallback.

WhatsApp on Mirakash is being set up and is not yet available to customers. It is listed now so that the list is already right on the day it goes live.

When you connect WhatsApp, you do it in Meta's own sign-up window: you choose or create your WhatsApp Business Account and number, and grant the Mirakash Meta app access to it. The account stays yours.

That Meta app, together with the Meta business account and the WhatsApp Business Account that Mirakash's own WhatsApp features run on, is registered to Aikolumi Software Pvt Ltd (India), which operates them for Mirakash.

The messages themselves travel between Meta and our servers on AWS in Frankfurt: Meta delivers incoming messages to our servers, and our servers send replies to Meta. They do not pass through any system that Aikolumi runs separately.

You can run parts of the Service on your own accounts with other vendors. When you do, that vendor works for you under your own contract with it. It is your processor, not our sub-processor, and it is not on this list. That includes:

• your own model, speech, knowledge-base indexing or avatar vendor accounts, connected in the console's settings;
• your own Twilio or Plivo account, SIP trunk or SIM gateway for calls and numbers;
• messaging accounts you connect yourself, such as Telegram, Slack, Microsoft Teams or Discord, or your own Meta, Twilio or Plivo credentials;
• the systems your agents' tools, webhooks, connectors and MCP servers call;
• your own storage bucket for recordings, if you set one;
• the security tool you stream your audit log to.

We send those vendors what your configuration tells us to send, and nothing else. You choose them and you are responsible for your arrangement with them.

Bringing your own account moves one leg, not the whole call. If you bring your own speech-to-text account, the model and the voice still run on the vendors above. And it is not a hard fence:

• if your speech vendor fails during a call, the call can continue on a speech vendor listed above, on our account;
• if we cannot fetch your key when a call starts, that call runs on our accounts;
• if your own knowledge-base indexing account fails, search falls back to ours.

There is no setting today that switches those fallbacks off for a workspace. If you need that, tell us through /contact before you rely on it.

Some vendors process personal data for Mirakash's own purposes rather than for you. For that data we are the controller, so those vendors are not your sub-processors. Our privacy policy covers them:

• Google Analytics, on mirakash.com, and only if a visitor accepts analytics cookies;
• Amazon Web Services, which serves mirakash.com and keeps its access logs;
• the Mirakash Guide assistant and the public demo call on mirakash.com, which run on this same platform and the vendors above, for our own purposes;
• Stripe, when we take payment through it: it receives your billing contact and payment details, and none of your conversations.

Before a vendor handles customer data, we look at what it does with the data, where it processes it, and how it secures it. We use the protective settings a vendor offers where we have them wired in: every request we send to Deepgram, for example, carries its opt-out from its model-improvement programme.

Each sub-processor is bound by a written contract with data-protection terms that protect your data at least as well as our Data Processing Agreement requires of us, and we remain responsible to you for its work.

The Where column in each table says which vendors may process your data outside the European Economic Area.

We have no business associate agreement (BAA) with any vendor on this list, and we do not sign BAAs with customers today. Protected health information must not be processed on Mirakash.

We give at least 30 days' notice before a new sub-processor starts processing your data, or before we replace one. The notice goes on this page, with a dated entry in the changelog below, and to every customer who has asked to be told.

To be told: use the form at /contact(the topic “Notify me of sub-processor changes” is chosen for you) and give your company name. We will send each notice to the email address you give.

Moving your traffic between vendors already on this page, for example when a call fails over to the next speech vendor, is not a change to the list.

If you have a reasonable objection, on data-protection grounds, to a new or replacement sub-processor, tell us through /contact within the notice period. Say which vendor and why.

We will work through it with you. There is often a way round: many rows on this page apply only if you choose that vendor, voice, language or channel, and you can move a leg onto your own vendor account (section 05). There is no switch today that removes one listed vendor from the fallback paths for a single workspace, so an objection is handled by talking to us.

If we cannot resolve it, you may end the part of the Service that depends on the new sub-processor, as set out in the Data Processing Agreement.

If a sub-processor fails, stops providing its service, or becomes a risk to the security of your data, we may need to replace it sooner than 30 days allow. When that happens we will tell you as soon as we reasonably can, and you keep the same right to object.

You contract with Naridon, Inc. The one other company that operates part of Mirakash is Aikolumi Software Pvt Ltd (India), which holds the Meta accounts behind our WhatsApp features for Mirakash (section 04), and is in the table in section 03 for that reason.

WhatsApp messages do not pass through any system that Aikolumi runs separately; they travel between Meta and our servers on AWS.

Signed in to the console, Settings, HIPAA & PCI scope has a Subprocessors panel for your own workspace. It lists the model vendors named on your finished conversations, the speech vendors your agents are set to use, and the carriers behind your phone numbers.

It is narrower than this page. For speech it shows what your agents are set to use, not a vendor a call failed over to, and it does not show which vendor indexed your knowledge base. This page is the full list.

• 19 September 2026: initial publication.