MiraQ Shopper Agent Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
MiraQ is an AI shopping assistant that helps customers find products and buy them, right inside your WooCommerce store.
MiraQ reads your live WooCommerce catalog, including variation-level attributes and real stock status, so its answers reflect your actual inventory.
What MiraQ does for your shoppers
- Answers product questions in natural language — specs, compatibility, availability, and more
- Searches and filters your catalog, down to individual product variations (size, color, material, and any custom attribute you sell by)
- Guides customers through checkout, right inside the chat
- Helps with order tracking and post-purchase support
How it works with your store
- Live catalog. Product data, pricing, and stock stay in sync with your store automatically — no manual training or content uploads.
- Variation-aware. Filters and recommends at the variation level, not just the parent product, so answers are actually accurate for what’s in stock.
- Built for WooCommerce. Native integration with WooCommerce’s product, order, and checkout data.
Getting started is free
MiraQ includes a free tier — 50 questions/day, no credit card and no license key required. Paid plans lift that daily limit for stores with higher chat volume and show your own logo and footer text in the chat widget. A small “Powered by MiraQ” credit is never shown unless you switch it on in the Branding tab. Everything else works the same on every plan.
Support
Need help? Reach out to our team:
Email: info@silfratech.com
External Services
This plugin relies on the MiraQ service, operated by Silfra Digital (https://silfratech.com). The chat assistant cannot work without it. The plugin talks to two endpoints:
- MiraQ backend: https://silfratech.in/chatbot-shopify-multi/api
- Silfra license server: https://silfratech.in/silfra-license-server (paid license keys only)
What is sent, and when
- Free-tier activation (no license key): your site URL, site domain, an install ID generated by the plugin, and your site key’s public half (see “What this plugin creates on your site”) are sent to the MiraQ backend to register your store. The backend then reads the public key back from your site to confirm the request came from it.
- License activation (paid key): your site domain, install ID and the activation key you entered are sent to the Silfra license server to validate the license. Your site URL, site domain, install ID, your site key’s public half and the signed license details returned by the license server are then sent to the MiraQ backend to register your store, which reads the public key back from your site in the same way.
- Catalog refresh (products, categories, tags, attributes, currency): the MiraQ backend periodically asks your store for a catalog version number and, when it changes, reads the updated catalog through public endpoints this plugin adds. They return only published products and the same storefront details any visitor can see, never drafts, private products, sales or stock counts. The backend keeps a copy so the assistant can answer product questions without querying your store on every message.
- Branding changes: the widget logo URL and footer text you save are sent to the MiraQ backend, signed with your site key. The backend also reads them from your store once a day, through a public endpoint this plugin adds, in case a change was missed.
- Widget loading: on every storefront page that shows the widget, the visitor’s browser requests the widget script from https://silfratech.in and the widget makes brief status and settings requests to the MiraQ backend. This happens when the page loads, before the visitor opens the chat or turns on the AI chat. The widget, including its chat button, is hosted on the MiraQ service, so it cannot be displayed without these requests. Silfra receives technical request information such as the visitor’s IP address and browser details, plus your store’s identifier, but no chat message. No chat message is sent until the shopper turns on the AI chat and sends one.
- Chat widget use: when the visitor sends a message with the AI chat turned on, the message and relevant product data are sent to the MiraQ backend to generate replies. If the customer is logged in, their WordPress user ID, name, email address and account role are also sent, from the moment they turn on the AI chat, so the assistant can personalise replies and look up that customer’s own orders. The page itself carries none of these details: the widget asks your site for them only when the customer turns on the AI chat. Your site records the customer’s choice on their account, so on later visits the widget fetches these details when it loads, to show their earlier chats and a welcome-back screen, until the customer turns the AI chat off, which removes that record.
- Store lookups by the backend: when a logged-in customer asks about their orders, the MiraQ backend reads that customer’s own orders from an endpoint this plugin adds. The request must carry the customer’s identity token, which your site signs, and the endpoint returns only orders belonging to that customer. Checkout itself runs in the customer’s browser through WooCommerce’s own Store API, the same way your checkout page does.
- Uninstall: when you delete the plugin, it tells the MiraQ backend to deactivate your store. The request carries your install ID and proves it comes from your store with either your license details (paid plans) or a signature made with your site key (free plan), over HTTPS. See “What happens when you delete the plugin” below for what is removed and what is kept.
Privacy policy: https://silfratech.com/miraq-shopper-privacy-policy/
Third-party AI service: Mistral AI
The MiraQ backend (not the plugin on your site) uses Mistral AI’s API in two cases. Both only happen after a shopper turns on the AI chat in the widget and sends a message.
- The built-in logic cannot work out what a message means, such as an unclear or conversational request.
- A product search finds nothing, and the AI is asked to suggest a spelling correction or a broader search.
- What is sent in case 1: the current message and up to the three messages before it in that conversation; the intent the MiraQ service guessed, with its confidence score; and the search details it already pulled out of the message (for example a product term). Email addresses, phone numbers and card numbers in the messages are replaced by placeholders before sending, and email addresses in the extracted details are masked. An earlier assistant reply is included only if it was product browsing; every other assistant reply, such as one showing order or address details, is replaced with “[reply omitted]”. Email lookups and name, billing or shipping address changes are never included.
- What is sent in case 2: the current message, with the same removal, and the name of the intent. Nothing else.
- What is not sent: customer or order records, customer IDs, payment details, keys, and your product catalog.
- Limit: only email addresses, phone numbers and card numbers are removed. Other text a shopper types, such as a name or address, is not.
- Mistral AI privacy policy: https://legal.mistral.ai/terms/privacy-policy
- Mistral AI terms of service: https://legal.mistral.ai/terms/commercial-terms-of-service
Silfra does not use shopper conversations to train its own AI models. Mistral AI’s handling of API inputs is governed by its own terms.
Hosting and delivery: BigRock and Cloudflare
The MiraQ backend is hosted by BigRock in Mumbai, India. BigRock provides the servers, which store the data the backend holds (chat history, logs, and store and license records). Traffic to and from the backend passes through Cloudflare, which processes requests and responses in transit, including chat messages and technical request data such as IP addresses, to deliver and secure the service.
- BigRock website: https://www.bigrock.in/
- BigRock privacy policy: https://www.bigrock.in/support/privacy.php
- Cloudflare privacy policy: https://www.cloudflare.com/privacypolicy/
Services contacted by the visitor’s browser
These are contacted directly by the visitor’s browser, not by your site or by the MiraQ backend. Silfra does not receive what they collect.
- Google Fonts: the widget’s cart and checkout screens use the DM Sans and DM Serif Display fonts, which the visitor’s browser requests from Google Fonts (fonts.googleapis.com) when the widget’s styles load on a page. Google receives the visitor’s IP address and browser request information. Terms: https://developers.google.com/fonts/terms. Privacy policy: https://policies.google.com/privacy
- Browser voice input (optional): if a visitor taps the microphone button, speech recognition is done by the browser’s built-in service, which depending on the browser may be operated by the browser vendor (for example Google for Chrome). The MiraQ service receives only the resulting text as a chat message, never the audio.
- WhatsApp support link: the assistant may show a “Chat with us on WhatsApp” link. Nothing is sent to WhatsApp unless the visitor clicks it, which opens WhatsApp with a pre-filled message. Terms: https://www.whatsapp.com/legal/terms-of-service. Privacy policy: https://www.whatsapp.com/legal/privacy-policy
The plugin itself does not connect to WhatsApp, Instagram or any other Meta service.
What this plugin creates on your site
- A site key. On activation the plugin generates an Ed25519 signing key for your site, using the libsodium library built into WordPress. The private half is stored in your site’s options (
miraq_site_key) and never leaves your site. Only the public half is sent to the MiraQ backend, which uses it to check that a request, or a signed-in customer’s identity, really comes from your site. The public half cannot be used to sign anything, so nothing the MiraQ service stores can act on your store. - REST endpoints under
/wp-json/miraq/v1/. The catalog endpoints return only published products and storefront details./my-ordersreturns orders only for the customer named in an identity token your site signed./site-keyreturns the public key./ai-consentand/identityare for the logged-in customer only: the first records or removes their choice to use the AI chat, and the second returns their own identity token, user ID, first name and role to the chat widget, only after that choice was made. - A user meta entry (
miraq_ai_consent) on a customer’s account when they turn on the AI chat. It is removed when they turn the AI chat off, and for every customer when you delete the plugin.
The plugin creates no WordPress user and no WooCommerce API key. The MiraQ service has no access to your store’s admin or REST API, and cannot create orders or change customer accounts: orders are placed by the customer through your normal checkout, and account changes are made by the customer on your My Account page.
What happens when you delete the plugin
Deactivating the plugin changes nothing described here. Deleting it runs the steps below, in this order.
On your site, immediately
- The plugin asks the MiraQ backend to deactivate your store (see “External Services”). This step needs your site to reach the MiraQ service. If it cannot, for example because your site is offline, the plugin still finishes step 2 but the store stays registered with the MiraQ service. Email info@silfratech.com and we will remove it by hand.
- All of the plugin’s settings are deleted, including your site key, your branding logo URL and footer text, and every customer’s AI chat consent record. A logo you uploaded to the Media Library stays there, because it is your file.
On the MiraQ service
- Immediately: the store is marked archived and removed from active use, its copy of your site’s public key is erased, and the catalog copy is deleted.
- 7 days later: the store’s dedicated database is permanently dropped. It holds the store’s chat history, order confirmations, last-visit records and daily question count.
- Kept: a minimal store record that is not deleted automatically: store and license IDs, plan and dates, your site domain and WordPress address, and the logo URL and footer text last saved to the service. We keep it for audit and billing records. Email info@silfratech.com to have it removed.
- Logs: operational logs that mention your store are deleted on the normal schedule, about one month after they were written.
Screenshots
License tab: you are on the free plan, or enter a license key to upgrade.
Branding tab: set a custom widget logo and footer text.
Widget home: the chat assistant as shoppers first see it.
Browsing and filtering products inside the chat.
Popular products suggested in the chat.
Ordering a product by chat: the assistant asks for the quantity.
The cart inside the chat.
Checkout inside the chat: billing details and order summary.
Reviewing the order before placing it.
Order confirmation with the order number.

