Every deletion request goes through one form: mirakash.com/contact. We have no email address for these requests yet, so please don't write to one you have guessed, because it will not arrive. Customers signed in to the console can also reach us from there.

1. Open /contact. The topic Delete the data you hold on me is chosen for you when you follow this link.
2. Enter an email address we can reply to. If the data is held under an email address, use that one.
3. In the box headed “Anything that helps us find your records”, tell us:
   • the phone number or email address the data is under, written in full with the country code (for example +91 98765 43210);
   • the business you dealt with, if it wasn't Mirakash itself;
   • how: a phone call, WhatsApp, Messenger or Instagram, a chat window on a website (which website), our demo call, or one of our forms;
   • roughly when. For a website chat, also give the page you were on and something you said, because a chat is not linked to your name, number or email;
   • whether you also want never to be called or messaged again. That changes what we keep (see section 04).
4. Send it. The page confirms that your request has been logged.

What happens next

A person on our team reads every request. No machine decides anything. We check that the data is yours (section 10), find everything we hold under the details you gave, delete it, and write to you at the email address you gave when it is done. If we need more from you, or the data belongs to a business that decides what happens to it, we tell you.

The form needs an email address, because that is how we reply. It has no field for a phone number, so put the number in the message box.

Data-protection law gives the controller the decision over your data: the one who decides why and how it is used. When a business uses Mirakash to talk to you, that business is usually the controller, and we process your data for it under our contract with it (see the Data Processing Addendum). For this website, our demo call and console accounts, the controller is Naridon, Inc., the company behind Mirakash.

You can always ask us. Where the business decides, we pass the request on and help it act.

Businesses use Mirakash to answer messages on WhatsApp, and on Facebook Messenger and Instagram. When you write to one of them, Meta delivers your message to Mirakash and the business's agent replies through us.

What we receive from Meta

For each message: your WhatsApp phone number (on Messenger and Instagram, an ID that Meta gives you for that business's page instead of a number), your WhatsApp profile name, the text, any button or list option you tapped, the type, file name and caption of a photo, voice note, video or document you send, a location or contact card you share, and the message's ID and time. Meta also sends delivery and read receipts.

What we keep

• your number (or the Meta ID);
• the conversation: your messages, the agent's replies and a short preview of your message. For an attachment, we keep a note in the transcript, such as “sent a photo” with its caption, the file name of a document, or the coordinates of a location you shared;
• if the business takes WhatsApp calls through us, a log of each call (your number, when, how long) and whether you allowed the business to call you.

We don't store your profile name or the delivery and read receipts. We don't download the photos, voice notes, videos or files you send. Voice notes are not transcribed.

How to have it deleted

• Ask the business. One of its administrators can erase your WhatsApp conversations, found by your number, in the Mirakash console straight away (section 04 explains what that removes). The same erasure deletes whether you allowed the business to call you on WhatsApp and takes your WhatsApp ID off its WhatsApp call log, leaving only the date and length of each call.
• Or ask us through /contact. Name the business and the number you wrote from. For Messenger and Instagram, where we hold Meta's ID rather than your number, give the business's page and roughly when you wrote so we can find the conversation. We pass your request to the business and, where our agreement with it allows, carry out the deletion for it.

To stop the messages

• Block the business in WhatsApp.This works immediately and doesn't depend on the business or on us.
• Tell the business, or us, that you don't want to hear from it again. Your number then goes on a do-not-contact list, which Mirakash checks before the business can start a WhatsApp conversation with you or its agent can call you.
• Replying “STOP” in a WhatsApp chat or to a text messageadds your number to that business's do-not-contact list automatically, before its agent sees the message. The message must be that one word (UNSUBSCRIBE, CANCEL, END, QUIT, STOPALL and OPTOUT work too). If we cannot tell which business it was, your number goes on the list for every business on Mirakash. No confirmation is sent on WhatsApp.
• Text messages from a US number that a business registered through us: reply STOP. The carrier handles it and stops further texts from that sender.

Meta keeps its own copy

Meta carries these messages on its own systems and keeps what its own policies say. Deleting your data from Mirakash does not delete it from Meta, and deleting a chat on your phone deletes it only from your phone. See the WhatsApp Privacy Policy and the Meta Privacy Policy.

Who runs our Meta app

The Meta developer app and the WhatsApp Business Account that Mirakash's WhatsApp features run on are registered to Aikolumi Software Pvt Ltd (India), which operates them for Mirakash. Requests about data that passed through them come to us at /contact, like any other.

Businesses use Mirakash to answer their phone lines with an AI agent and to place calls, for example to follow up an enquiry or to call you back at a time you asked for.

What we hold

• your phone number, and the time, length and direction of each call;
• a recording of the call, if the business records its calls;
• a transcript of what you and the agent said, with a summary and an analysis drawn from it (for example, whether your question was answered, and details the business asked the agent to note);
• what the agent looked up or did during the call, and the notes and quality scores the business's team adds when it reviews the call;
• depending on how the business uses Mirakash, your number may also sit on a call list it uploaded, on a callback you asked for, on a record of consent you gave, or on its do-not-contact list.

Recordings are kept in our storage in Frankfurt, Germany, unless the business keeps them in a storage account of its own.

What is deleted automatically

Each business sets how long recordings and transcripts are kept. Both are 90 days unless it changes them. A sweep runs twice a day and deletes whatever is past its window. Recordings in our storage are deleted after 365 days at the latest, whatever the setting says. The automatic sweep removes the audio and the words, and with the words everything written from them that could quote you: the summary, the analysis, reviewers' remarks, your satisfaction comment and any test scenario made from the call. Once nothing of the call's content is left, it also takes your number (and the carrier's reference for the call) off the call's entry. The entry itself stays in the business's call log, with the date, length and cost.

How to have it deleted

• Ask the business. One of its administrators can do it in the Mirakash console under Settings → Call data (app.mirakash.com/settings/data). They type your phone number or email, check what would go and erase it. This removes the data at once, whatever the retention setting says. The same erasure is available through our API (POST /api/data/erase). Today the API takes requests only from an administrator signed in to the console, not from a business's own servers.
• Or ask us through /contact, naming the business and the number. We pass it to the business and, where our agreement with it allows, carry it out for it.

What erasure removes, and what it leaves

Erasure deletes every recording (outright, because our storage keeps no older versions), transcript, summary and analysis for that number. It also deletes what the agent looked up during those calls, reviewers' notes and the reason any call was escalated. The agent can no longer recall earlier calls with you, because the history it would read is gone.

It leaves the call's entry in the business's call log (date, length, cost and scores, with none of your words), so the business's bills and reports still add up. Your number on that entry is replaced by a short code worked out from it. The code cannot be turned back into your number, but someone who already knows your number could check whether a code matches it. It is kept so that the deletion can be proved later. The business's audit trail gets a receipt: that an erasure happened, when, who ran it, and a fingerprint (a SHA-256 hash) of what was deleted, not the content.

The same erasure also deletes your number from the business's call lists, callbacks booked to you, your callback preferences, the consent records the business holds for you, the test numbers its team set up, and the rows its agents saved about you in its Mirakash data tables. It does not reach documents the business uploaded to its agents' knowledge base, its own staff's chats with our in-console assistant, or the step-by-step logs of its automated workflows. If you may be in one of those, say so when you ask us and we search them by hand.

If you never want to be called again

Deleting your data and blocking your number pull in opposite directions: to stop calls to a number, a system has to remember that number. If you want both, we delete everything else and keep only an entry on a do-not-contact list. The entry holds:

• your number itself, not a scrambled form, because it has to be recognised to be blocked;
• whose list it is on (one business's, or every business on Mirakash);
• when it was added, how the request reached us, and your reason if you gave one.

Mirakash checks this list before a business's agent places a call and before a business starts a WhatsApp conversation, and refuses if your number is on it. Telling the agent during a call or a text conversation that you don't want to be contacted again adds your number to that business's list: every agent has a built-in step for it, used when the conversation has your number. It depends on the agent recognising what you asked, so to be sure, ask the business or us as well. You can also ask for the entry to be removed later. After that, nothing on our side stops the business calling you.

The Mirakash Guide, on this website

The assistant in the corner of mirakash.com is our own agent, and we decide what happens to what you tell it. We keep the transcript of the chat, the page you were on (its address, without anything after a “?”), anything you typed into a form it showed you, and the language, timing and running cost. If you spoke to it by voice, the transcript is kept the same way. The Privacy Policy has the detail.

A chat is not linked to your name, number or email, unless you typed them into it. So to delete one, tell us through /contact the day and rough time, the page you were on, and something you said. We find the conversation and delete it.

An agent on another company's website

If the chat window belongs to another company, that company decides. Ask it first. Its transcripts are deleted when its retention window passes (section 04). Because a website chat is not tied to a phone number or email, the console's per-person erasure cannot find it. You, or the company, can ask us through /contact, with the website, the day and time and something you said, and we delete it.

On mirakash.com you can have our agent ring you once. We decide what happens to that data. We keep:

• the number you entered and the use case you picked;
• whether the number was verified, when codes were sent and how many attempts were made. The code itself is never stored, only a one-way fingerprint of it, which is deleted once you are verified;
• when we called;
• a shortened one-way fingerprint of your internet (IP) address, which limits how many numbers one visitor can try;
• the call itself: recording, transcript, summary and analysis, as described in section 04.

The code is sent by text message, or by a short call that reads it out if the text fails, through our telephone carrier. The carrier keeps its own record that it sent it.

We delete the demo entry automatically 12 months after it was last used, or 30 days after it was made if the number was never verified and never called. That entry is also what stops us calling the same number twice, so after it is deleted the number can ask for the demo again. To delete it sooner, ask through /contact and give the number. We erase the call and delete the demo entry. If you would rather we never call it again, say so, and we keep only the number on our do-not-contact list instead.

Both forms send us what you typed: your email, and if you gave them your name, company, phone number (demo form) and message, plus the topic (contact form). With it we record the page that sent you here, any campaign tags in the link, and your browser type. Your IP address is used only to limit how many forms can be sent in an hour and is not stored with what you sent. Our servers also note that a form arrived, with the email address masked, and those logs are deleted after 14 days.

We delete an entry automatically 24 months after it was last updated. To delete it sooner, ask through /contact from the same email address if you can. We delete it.

A deletion request sent through that form is itself an entry. We keep it, with the email you gave and what you asked for, as the record that we did what you asked, and it is deleted on the same 24-month clock.

The console at app.mirakash.com is for businesses, by invitation. For your account we hold your name and email; your password in scrambled form only (we cannot read it); your second-factor settings if you use one; your sign-in sessions (the browser and when); the workspaces you belong to and your role in each; which version of our Termsyou accepted and when; and the actions you take, in the workspace's audit trail.

Leaving a workspace, or deleting your account

An owner or administrator can remove you from a workspace. That removes your access but not your account. There is no delete-account button yet. Ask through /contact from the email address on the account, or from inside the console. We delete the account within 30 days. A workspace always keeps at least one owner, so if you are the last one, hand ownership on or close the workspace first.

Closing a workspace: export first

Before you close, an administrator can download from the console:

• the conversation log (one row per conversation) as CSV or NDJSON;
• your data tables, as CSV or JSON;
• the audit trail;
• recordings, one at a time.

There is no one-click export of every transcript yet. Ask us and we will help. Then the owner asks us through /contact to close the workspace. Within 30 days we delete its agents, knowledge bases, conversations, recordings, transcripts, contact lists, connected accounts and stored keys. Backup copies are gone within 14 days after that. Our contract with the business, including the Data Processing Addendum, governs this in detail.

What we have to keep, and why

If your business connected its own WhatsApp Business Account to Mirakash, through Meta's sign-up popup or with an access token, we hold: the IDs of that account and its numbers; each number's display number, verified name and quality rating; the access token Meta issued for your account; and the two-step verification PIN we set when we registered your number. The token and PIN are stored encrypted. We also hold the conversations your agent had (section 03).

Disconnecting

In the console, go to Channels → Numbers, then the WhatsApp panel. There are two buttons:

• Hand back, for one number: first removes the number from WhatsApp's Cloud API at Meta, then deletes it from Mirakash. The number is yours again and can go back on the WhatsApp app.
• Disconnect, for the whole account: deletes our copy of the access token, the PIN and the numbers' records. It changes nothing at Meta. Your numbers stay registered to the Cloud API, the token stays valid, and our app stays subscribed to your account's messages. Until you remove that, Meta may keep sending us notifications for messages to your numbers.

So after disconnecting, also remove the Mirakash app's access to your WhatsApp Business Account in your Meta business settings. Removing it there is what ends our app's access at Meta.

Disconnecting does not delete your past conversations. They stay in your workspace under its retention window until you erase them (section 04) or close the workspace (section 08). Meta keeps its own records of your account under its terms.

Before deleting anything, we make sure the request comes from the person the data is about, so that nobody can wipe or read someone else's records. We ask for as little as the risk calls for:

• If you write from the email address the data is held under, that is usually enough.
• For a phone number, we may ask details only its holder would know (when you called or were called, and what about), call or message the number to ask you to confirm, or ask the business you dealt with to confirm the number is yours.
• We never ask for a password, a one-time code or payment details, and we never ask you to read out a code sent to your phone.

Asking for someone else. Someone can make the request for you, such as a lawyer, a relative or a service you have authorised. They need your signed permission, and we may confirm with you directly before we act.

If we cannot verify a request, we tell you why and what would work. We use what you send us to verify only for your request.

We complete a verified deletion within 30 days, or sooner where a law that applies to you requires. We answer rights requests within the shortest period that law allows.

When a business is the controller, the law that applies to it sets its deadline. We pass your request on without delay.

• Statistics that no longer identify you, such as counts, totals, averages and the length and cost of an erased call.
• Copies the business holds outside Mirakash, such as its own customer records, emails or files it exported. Ask the business.
• Meta's copies of WhatsApp, Messenger and Instagram messages (section 03).
• Telephone carriers' records, yours and the business's, of calls and text messages. Each keeps its own.
• Google's analytics data, if you accepted analytics on this website. Google holds it under its own settings (see the Cookie Policy).
• Our service providers. Speech and language-model providers process conversation content to produce replies and keep it under their own terms. They are listed on Sub-processors.
• What the law requires us to keep, or what we need for a legal claim (section 08).
• A do-not-contact entry, if you asked never to be contacted (section 04).
• Your own devices. A chat on your phone stays there until you delete it.

When you send the form, the page confirms your request is logged and shows a reference. Keep it: it is how we find your request if you follow up. When the deletion is complete, we confirm it in writing, by email to the address you gave. We say what we deleted, and anything we had to keep and why.

If a business erases your data in its console, the erasure and its receipt are recorded in that business's audit trail. Ask the business for confirmation.

Meta lets an app give either a data deletion callback URL, which Meta calls automatically, or a page of instructions. Mirakash uses this page. There is no automatic callback.

Nobody signs in to Mirakash with a Facebook account as a consumer. The only Facebook sign-in we use is the one a business goes through to connect its own WhatsApp account (section 09). If you removed Mirakash from a Facebook or Meta business account and want what we hold deleted, follow section 01.

Tell us first, through /contact, and we will look at it again. You can also complain to the data protection authority in the country where you live or work. The Privacy Policy explains your rights. If your complaint is about how a business used Mirakash, the authority that oversees that business is usually the right one.

• Privacy Policy: what this website and Mirakash collect, and your rights.
• Data Processing Addendum: how we process data for the businesses that use Mirakash, including deletion when a contract ends.
• Sub-processors: the providers that process data for us.
• Cookie Policy: what this website stores in your browser.
• Terms of Service and Acceptable Use Policy: the rules for businesses using Mirakash, including when they may call and message people.
• Contact: for every request on this page.