MakePay Privacy Policy

This Privacy Policy explains how MakePay handles information when people visit MakePay pages, contact us, use the MakeCrypto merchant dashboard for MakePay settings, connect commerce plugins, create or pay MakePay payment links, use embedded checkout, or interact with MakePay support.

A merchant may also have its own privacy policy for its store, website, checkout, or customer support. MakePay is not responsible for the merchant's separate privacy practices.

MakePay is operated by MakePay Global LLC, registration number 2026-002114917, a Limited Liability Company incorporated in Wyoming, United States, with principal office at 75 E 3rd St, Ste 7, Sheridan, WY 82801, USA. References to MakePay, we, us, and our in this policy refer to that operating entity and the MakePay service.

We process account and merchant information such as names, business names, email addresses, websites, dashboard account details, support messages, merchant configuration, branding, settlement preferences, and integration settings.

For payment flows, we process information needed to create, display, route, reconcile, and support a payment. This can include payment link identifiers, order references, amounts, fiat currencies, selected crypto assets or chains, payer email when provided by the merchant integration, return URLs, payment status, wallet or transaction references, timestamps, and webhook delivery metadata.

For technical operation, we process device, browser, IP address, request, security, error, and log data needed to operate the site, prevent abuse, debug integrations, maintain availability, and secure accounts and payment flows.

We use information to provide MakePay pages, merchant dashboard features, payment links, hosted checkout, embedded checkout, subscriptions, deposits, webhook delivery, API access, merchant support, security monitoring, fraud and abuse prevention, troubleshooting, product improvement, and legally required records.

We do not sell personal information. We do not use payer payment data to run third-party advertising profiles.

We share information with service providers that help host, operate, secure, monitor, and support MakePay. We may share information with merchants when it relates to their payment links, orders, customer support, settlement, refunds, or compliance responsibilities.

We may disclose information when required by law, legal process, or enforceable government request, or when we believe disclosure is necessary to protect MakePay, merchants, payers, or the public from fraud, security incidents, or abuse.

MakePay may use cookies or similar technologies for authentication, security, preferences, fraud prevention, basic measurement, and site operation. Some browser or device settings allow you to limit cookies, but parts of the service may not work correctly without cookies required for security or authentication.

We keep information for as long as needed to provide the service, maintain business and security records, resolve disputes, comply with legal obligations, and support merchants and payers. Retention periods can vary by record type, account status, transaction context, legal requirements, and security needs.

Depending on where you live, you may have rights to request access, correction, deletion, portability, restriction, or objection related to personal information. Some records may need to be retained for security, payment integrity, legal, tax, accounting, dispute, or compliance reasons.

Merchants can update many MakePay settings in the dashboard. Payers should contact the merchant first for order, refund, fulfillment, or store account questions because the merchant controls the customer relationship and order records.

MakePay is an online service and may process information in countries different from where a merchant or payer is located. We use reasonable administrative, technical, and organizational measures designed to protect information during that processing.

We may update this Privacy Policy as MakePay changes or legal, operational, or security requirements evolve. The effective date at the top of the page identifies the current version.