Maghgo
How Maghgo handles data
Technical overview of the data and machine-learning behavior currently implemented in Maghgo. Updated 18 October 2026.
Store and account records
Maghgo stores merchant accounts, storefront catalogs, orders, and payment ledgers in PostgreSQL. Store designs, automation rules, and conversational memory use MongoDB when that service is connected. Application queries scope merchant records to the owning store.
Machine learning in Maghgo
Search, recommendations, inventory forecasts, analytics, payment review, and sign-in review use store-scoped records. Catalog search requests are bounded and are not saved by the search endpoints. Customer groups are calculated with merchant-specific HMAC pseudonyms; the dashboard receives aggregate counts and averages, not customer contact values.
AI providers and conversation memory
Bot conversations, recent messages, shopper preferences, and reasoning summaries are stored in MongoDB to support conversational continuity. Gemini requests include the current message, recent conversation text, and a small set of retrieved store facts; the configured Maghgo CPU text endpoint receives the current message, up to four recent turns, and its grounded prompt. AI design requests send the prompt and editable design tokens to Gemini. Common email addresses, phone-like or long number sequences, bearer credentials, API keys, and labeled password or OTP values are masked before these calls. Pattern masking cannot identify every kind of personal information, so do not send payment credentials or other secrets in a chat or design prompt.
Payment and security signals
Payment review compares a paid order’s amount and line-item count with earlier paid orders. It produces a manual review signal and never declines, delays, or reverses a payment. Failed sign-in events store HMAC fingerprints for the source and account reference; this event recorder does not write raw IP addresses or user-agent strings. The background cleanup worker removes failed sign-in fingerprints after 30 days when enabled.
Online payments
A shop can connect its own Razorpay account and, when configured, Stripe or Cashfree. The selected provider processes the customer’s payment for that shop; Maghgo stores order and payment-verification metadata needed to confirm the result. Maghgo checkout does not ask customers to enter card numbers into the AI chat.
Account protection
Merchant passwords are stored as password hashes. Merchants can enable Google Authenticator two-factor sign-in. Gateway secrets are kept server-side and are not included in public storefront responses.