Privacy

Privacy that explains the flow, not just the policy.

PayBridge sits between merchants, customers, and Nepal payment providers. This page explains what information moves through the platform, why we need it, and where responsibility stays with the merchant or provider.

Last updated March 31, 2026

Who this applies to

Merchants using PayBridge, visitors to this website, and customers interacting with PayBridge-hosted payment flows.

Core principle

PayBridge does not hold customer funds. We process payment and operational data to route, verify, and report transactions.

Questions

For privacy questions or data requests, email support@paybridgenp.com.

What we collect

The data we collect depends on how you interact with PayBridge. Merchants provide account, business, project, API, and provider credential information. Customers may provide payment references, order identifiers, return URLs, and other checkout details supplied by the merchant’s integration.

  • Account data such as name, email address, password hash, authentication settings, and support history.
  • Business and project data such as merchant name, environment, webhook endpoints, API keys, branding settings, and provider configuration.
  • Transaction data such as amount, currency, provider, payment status, session IDs, reference numbers, metadata, and callback or webhook delivery logs.
  • Website and analytics data such as IP address, browser details, device information, pages visited, and cookie-derived analytics where enabled.

How we use data

We use data to operate the platform, secure accounts, confirm payment outcomes, deliver webhooks, troubleshoot merchant issues, and improve the reliability of the product.

  • To create and manage merchant accounts, authenticate users, and protect access with security controls such as email verification and optional 2FA.
  • To create checkout sessions, route customers to supported providers, verify provider callbacks, and keep payment state in sync.
  • To deliver dashboards, public tracking pages, refund records, webhook logs, and operational reporting.
  • To detect abuse, enforce rate limits, investigate fraud or suspicious behavior, and comply with legal obligations.

When we share data

PayBridge shares data only where it is needed to complete the payment flow or operate the service. We do not sell merchant or customer personal data.

  • Payment providers such as eSewa, Khalti, and ConnectIPS receive the information required to initiate, verify, or reconcile transactions.
  • Infrastructure and service providers may process data on our behalf for hosting, email delivery, monitoring, and analytics.
  • Merchants receive payment status, metadata, and webhook events for transactions created through their projects.
  • We may disclose information if required by law, court order, lawful request, or to protect the rights, safety, and security of PayBridge, merchants, customers, or the public.

Retention and security

We keep information for as long as it is needed to provide the service, maintain reliable payment records, resolve disputes, meet compliance obligations, and enforce our agreements.

Sensitive credentials are handled with access controls and encryption. Payment and webhook records are retained for operational visibility and auditability. Analytics data may be retained in aggregated form.

Your choices

Merchants can request updates or deletion of account information, subject to records we need to retain for legitimate business or legal reasons. Customers should generally contact the merchant first for questions about a specific purchase or payment context because the merchant controls the underlying transaction purpose.

You can also manage cookie preferences through your browser settings. For privacy requests, contact support@paybridgenp.com and include enough detail for us to verify the request safely.