Account & authentication
Name, email, phone number, authentication state and security/session records needed to operate and protect your account.
MANGLO processes information to run your account, fund and protect your wallet, execute supplier-linked orders, recover unfinished work, provide support, improve the product and power optional AI assistance. This page explains what that means without hiding the important parts.
MANGLO does not need every piece of information about you. The main categories below are tied to account access, transactions, fulfilment, support or product operation.
Name, email, phone number, authentication state and security/session records needed to operate and protect your account.
Selected service, public destination URL, quantity, order status and supplier-linked fulfilment information needed to execute and support an order.
Wallet balance, ledger entries, Cashfree order references and payment-status information. Raw card numbers, CVV values and UPI PINs are not stored by MANGLO.
Support tickets and, when you choose to use MANGLO AI, conversation content plus relevant live MANGLO tool results needed to answer the request.
Depending on how you use MANGLO, we can process your name, email address, phone number, authentication and session information, profile information, saved favourites, public social-media destinations you submit for an order, selected service and quantity, order history, wallet and transaction records, payment references and statuses, referral attribution, temporary order drafts, support messages, optional AI conversations, and limited first-party product-usage events.
We also maintain operational and security records needed to investigate abuse, protect accounts, reconcile money movement, troubleshoot supplier submissions and maintain the reliability of the service.
Information is used to create and protect accounts, authenticate customers, operate the live marketplace, prepare quotes, validate destinations, fund and reconcile the wallet, submit and track orders, recover unfinished orders, calculate eligible referral rewards, answer support requests, prevent abuse, understand product performance and meet applicable legal or financial-record obligations.
MANGLO also uses real order outcomes to maintain supplier-service health scores. Those scores are service-performance signals; they do not require exposing one customer’s order destination to another customer.
MANGLO records first-party events such as page visits, marketplace searches, service views, order-review steps, recovery interactions, referral milestones and confirmed transaction milestones. Campaign information such as UTM source, medium, campaign, content or term can also be recorded, together with the referring website hostname.
Analytics is designed not to store the public destination URL you enter for an order, raw payment credentials, full external referrer URLs, or marketplace search text that looks like a URL or account handle. URL- or handle-like search text is redacted before analytics storage.
The destination needed to fulfil an order is kept in the order flow rather than copied into first-party marketing analytics.
When you open a valid MANGLO referral link, MANGLO can store the referral code in a secure HTTP-only cookie for up to 30 days. If a genuinely new customer creates an account during that period, the inviting account can be recorded as the referrer subject to the referral rules.
The referrer is not given the referred customer’s email address, phone number or order destination. Reward eligibility is checked server-side and eligible rewards are recorded through the wallet ledger.
For signed-in customers, MANGLO can save a meaningful prepared order after a live service, valid public destination and valid quantity have been entered. A prepared draft becomes recoverable after at least 30 minutes of inactivity and can remain restorable for up to 14 days.
The destination is not placed in the recovery URL or analytics event. Drafts are removed after placement, manual discard, scheduled expiry cleanup or later relevant account/order activity.
Payments: Cashfree hosts payment entry and processes checkout information. MANGLO receives the payment/order information needed to verify status and reconcile your wallet. MANGLO does not store raw card numbers, CVV values or UPI PINs.
Supplier fulfilment: the applicable upstream supplier receives information required to fulfil the selected service, such as the supplier service ID, public destination link and quantity. MANGLO keeps the supplier identity and internal credentials on the backend.
Authentication: account authentication is handled through Supabase Auth. MANGLO uses secure server-side session handling rather than exposing authentication secrets to customer-facing pages.
MANGLO AI currently uses Groq as an external inference provider. When you choose to use MANGLO AI, the message you send and relevant live MANGLO tool results needed to answer the request can be sent to Groq for processing.
Do not enter passwords, OTPs, card numbers, CVV values, UPI PINs, banking credentials or other secrets into AI chat. AI output is not the transaction authority: MANGLO’s own server rechecks live service availability, quantity, destination, price and wallet balance before an order can be submitted.
MANGLO uses secure authentication, HTTP-only session cookies, server-side authorization, encrypted transport, restricted secret storage, rate limits and transaction-side checks to reduce common account, payment and ordering risks. Sensitive supplier and payment credentials are not sent to the browser.
No online service can promise absolute security. If you believe your account or information has been compromised, contact support promptly and change credentials where appropriate.
Temporary order drafts have the expiry behaviour described above. Other records—such as account, order, wallet, payment, fraud-prevention, support and security records—can be retained for as long as reasonably needed to operate MANGLO, reconcile transactions, resolve disputes, protect the service or meet applicable legal obligations.
Deletion of eligible profile or conversation information does not necessarily require deletion of transaction, security or legal records that MANGLO must or reasonably needs to retain.
You may contact MANGLO to ask about your personal information or request access, correction or deletion of eligible data. The result of a request can depend on account ownership verification and on records MANGLO needs to retain for financial, fraud-prevention, security, dispute or legal reasons.
For account-specific requests, use signed-in support when possible so the request can be connected to the correct account. You can also email support@manglo.shop.
This Privacy Policy should be read together with the Terms & Conditions, Refund & Cancellation Policy and Trust & Safety page. If MANGLO materially changes how a feature handles customer information, the public policy will be revised to reflect that operating model.
Use signed-in support for account-specific requests, or contact MANGLO directly without sharing passwords, OTPs or payment secrets.