Privacy Policy

PayBridgeNP is a product of Nepali Mind Private Limited, a company registered in Nepal. In this policy, "PayBridgeNP", "we" and "us" mean that company.

PayBridgeNP decides how merchant-account, website, support, checkout analytics, and PayBridgeNP ID data is used. For the customer data a merchant collects through their checkout, the merchant decides the purpose and PayBridgeNP processes it to provide the service. Payment providers (eSewa, Khalti, Fonepay) handle the payment itself under their own terms and privacy policies.

• Account data - name, email, contact phone number, password hash, sign-in and security settings, team roles, and support history.
• Business and project data - business name, live or test environment, webhook endpoints, API keys, branding, and provider configuration, including the business name a provider shows for your account on its own payment page (read when you save or test those details).
• Business profile - what the merchant sells, its category and website or selling page and, if the merchant adds them, its registered name, registration and PAN numbers, e-commerce listing number, business address, and support and complaint contacts. Used to understand and review the business, and printed on receipts only if the merchant turns that on. We do not ask for bank account details.
• Transaction data - amount, currency, provider, payment status, references, metadata, and records of callbacks and webhook deliveries.
• Payer details from the payment provider - when a provider reports them for a payment: the payer's name, mobile number, the bank or wallet they paid from, and any note they added. Kept with the payment record to confirm and support the payment. Full mobile numbers are encrypted when stored and shown masked in dashboards.
• Checkout steps - on the hosted checkout, which bank or payment app button a buyer taps, whether the checkout page then moves into the background and comes back, and how long it was away, linked to the checkout reference. Used to find payment options that are not working for buyers. It cannot confirm that a bank app opened, and it never includes the buyer's contact details or payment credentials.
• Customer contact data - when the merchant's checkout asks for it: name, email, phone number, and billing or shipping address. Used to complete the payment, show the receipt, and send transactional notifications. PayBridgeNP does not market to customers.
• Notification records - for SMS and email we send: recipient, message type and content, delivery status, and the provider's reference. Merchants can see their own message history in the dashboard.
• Feature requests - ideas you send from the dashboard: what you wrote, the area, which account and team member sent it, and our internal review notes. Used to plan the product. Other merchants never see them.
• Website and device data - IP address, browser and device details, and pages visited on our websites.
• Security signals - at merchant sign-up, sign-in, and API use, a protected form of the IP address and browser, used to prevent abuse.
• How you found us - if you arrive from an ad or a link with campaign tags, we store those tags with the referring page on your merchant record at signup, so we can see which campaigns bring merchants in. We do not sell it.

• To create and manage merchant accounts, sign users in, and keep accounts secure.
• To create checkouts, hand customers to their chosen provider, confirm payment outcomes, and keep records accurate.
• To provide dashboards, payment-tracking pages, refund records, webhook logs, message history, and reports.
• To send transactional notifications (receipts, refund confirmations, payment reminders) on behalf of the merchant.
• To improve checkout usability and reliability, and to understand which of our campaigns bring merchants in.
• To detect and prevent abuse and fraud, and to meet legal obligations.

We do not sell merchant or customer personal data. We share data only as follows.

• Payment providers (eSewa, Khalti, Fonepay) receive what they need to process, confirm, or refund a payment.
• Sub-processors listed below process data on our behalf to run the service.
• Advertising partners (Google and Meta) receive website visit data from our marketing site to measure our ads and to show our ads to people who visited it. They use this under their own terms. They never receive transaction data or the contact details customers enter at checkout.
• Merchants receive payment status, the customer data they collected, metadata, and webhook events for their own transactions.
• We may disclose information where the law requires it, or to protect the rights, safety, and security of PayBridgeNP, merchants, customers, or the public.

We use service providers that process personal data on our behalf, each under its own data-processing terms. We choose providers with reasonable security and privacy commitments. They fall into these groups:

• Hosting and databases - running the API, the store integrations, our websites, the merchant dashboard and PayBridgeNP ID, and storing account, transaction and notification records.
• Network, security and storage - DNS, network protection, content delivery, rate limiting, storage for uploaded logos, and custom checkout domains.
• Email delivery - sending transactional emails such as receipts, verification and account notices.
• SMS delivery in Nepal - receipts, refund notices, reminders, sign-in codes, and account notices to a merchant's own number. Receives the recipient number and the message.
• Sign-in, analytics and advertising - optional sign-in with Google (your Google email and basic profile); measurement and advertising tags on our marketing site only; product analytics and error monitoring for the dashboard, the merchant mobile app, the API and the hosted checkout, which receive your IP address, a device identifier and your merchant account ID. In the merchant mobile app we record which screens are opened, which buttons are tapped (by a fixed button name) and which setup and onboarding steps are completed, never payment amounts, customer details or what you type. In the dashboard we also count, per account and day, which pages are opened and which named buttons are used; these counts never include what you type or copy. On the checkout, only how the page is used is measured, never buyer contact details. Fonts on the hosted checkout are served by a font provider that receives the page request, including the IP address, without setting cookies.
• Support and monitoring - the support messenger in the dashboard (your name, email, account ID, plan and role; not used on the checkout), uptime monitoring and application logs (which can include a request ID, merchant ID or IP address), internal operational alerts to our team (which can include a merchant's account name and contact email, never a customer's contact details), and hosting for our documentation site.

The cookies these providers set are listed on our cookies page. Merchants and partners who need the named list of providers for their own compliance can request it from support@paybridgenp.com. We update this section when the kinds of providers we use change, and change the "Last updated" date above.

PayBridgeNP is operated from Kathmandu, Nepal, and processes personal data under Nepal's Individual Privacy Act, 2075 (2018). We collect it with notice and, where the law requires, consent; we use it only for the purposes on this page; and we do not sell it.

Some sub-processors operate outside Nepal, so providing the service involves transferring data across borders. Each receives only what it needs for its stated purpose. Where we rely on your consent, you can withdraw it by contacting us; this does not affect processing that already took place or processing we need to complete a payment or meet a legal obligation.

PayBridgeNP sends transactional SMS and email on behalf of merchants, for example a receipt to the customer who just paid, or a reminder to complete payment for an unpaid store order. We never send marketing messages to customers.

• What goes out - receipts, refund confirmations, payment reminders, invoice notifications, security alerts, and account emails such as verification and password reset. We may also text a merchant's own contact number about their PayBridgeNP account, for example a plan invoice that is due.
• Account summaries and alerts - account owners receive a monthly payment summary (a daily one is optional) and an alert when payment updates to their webhook keep failing. Summaries can be switched off or unsubscribed from at any time; failing-webhook alerts are part of running the account.
• Merchant controls - merchants choose which customer messages are sent. Customer SMS depends on the merchant's plan and SMS credits. No real messages are sent in test mode.
• Records - each message, sent or not, is recorded so the merchant and our support team can check delivery.

• Shopify - when a merchant installs PayBridgeNP for Shopify, the app reads the customer's name, email, phone number and, where needed, address from the order, to send the payment link and reminders and to fill in the checkout. These are used only for the payment, never for marketing or profiling. The app removes contact details from paid, cancelled, or expired order records once they are over 90 days old, and from unpaid orders 90 days after the payment window ends. Shopify privacy requests remove the matching customer's details, or the shop's records, held by the app. Checkout, payment and message records follow the Retention rules below.
• WooCommerce and WHMCS - the plugins send the order or invoice number, the amount, and the customer's name, email, phone number, and billing address where available, to fill in the checkout and process the payment. Payment updates sent back to the store can include these details.

PayBridgeNP ID (id.paybridgenp.com) lets buyers keep their details for faster checkouts and see their payment history. We store the details the buyer chooses to save, their confirmed phone and email, and their chosen language.

• Payment history - for each payment linked to your ID we show the store, amount, date, and references. For Fonepay payments we also show the bank or wallet app it was paid from and the bank's reference, taken from the merchant's Fonepay settlement report, and list the banks and wallets you have paid with. We do not show the paying mobile number, because the person who paid is not always the ID holder.
• Insights imports - buyers can upload eSewa or Khalti exports to build a combined spending view. We extract the transactions and keep them, including their descriptions and references, along with import details such as the file name, and sort them into categories using our own rules, without sending them to an AI service. The uploaded file itself is discarded after processing. Bank statements imported before bank uploads were removed stay in your view until you delete them; bank account numbers and balances were not kept.
• Control - imported data is private to the buyer's ID. You can delete an import and its transactions from the Insights page. Deleting your ID stops access immediately, and its profile and Insights data are permanently deleted after 30 days. Merchants keep their own records of payments you made to them, and anonymised audit or accounting records may remain.

Merchants can connect an AI assistant to their PayBridgeNP account with a token they create and can revoke at any time. The assistant can see and do only what the token allows, its tool calls are logged against the merchant's account, and the merchant is responsible for the assistant they connect and the data they share with it.

In the document generators and QR poster maker, your document and QR contents stay in your browser. If you tick "Remember my business", your own business details are kept in this browser so you do not retype them; customer details, items, and amounts are never kept, and unticking it deletes them. The pages are measured with Google Analytics like the rest of the site, and we count when a tool is used (for example, a PDF downloaded or a calculation made). That event names only the tool and the action, alongside the visitor and page information described in our Cookie Policy, and never includes what you type, upload, or create. The webhook tester sends your test request through our server to the address you enter and does not keep it.

• Accounts - kept while the account is open. When you delete your account, you can cancel within 30 days. After that we erase your account data within 60 days of your request: login and profile details, team members, connected wallet and provider credentials, API keys, webhooks, settings, payment links and buttons, email and SMS logs, and analytics linked to you.
• Transactions - payment and refund records are kept for 5 years from the date of each payment or refund, then deleted. They include what we need for disputes, fraud prevention, accounting and questions from payment providers, banks or regulators: amounts, dates and references, the payer's name, mobile number and bank or wallet, and the provider's merchant name, terminal and settlement details. They are not deleted on request before then.
• Our invoices to you - invoices we issued for your PayBridgeNP plan, with the business name and tax details on them, are kept unchanged for 5 years from their date because tax law requires it, then deleted.
• Checkout steps - our own records are kept for 24 months, then reduced to monthly totals per merchant. The copy sent to our product analytics service is kept under that service's retention settings.
• Shopify app order records - contact details are removed as described above.
• Uploaded logos - publicly viewable so they can appear in emails, and stored under random names. When you replace or remove a logo, we unlink it from your account and delete the stored file; deletion is attempted once and is not retried.
• Test-mode data - kept while the account is open; test messages are never delivered.
• Dashboard usage counts - daily page and button totals per account, kept for 400 days and then deleted.

The owner of a PayBridgeNP merchant account can close it at any time, in any of these ways:

• PayBridgeNP Merchant app - More, then Security, then Delete account, and confirm with your password.
• Web dashboard - Settings, then Account settings, the Security tab, then Close account.
• Email - write to support@paybridgenp.com from the account's email address. We check the request and reply within 30 days.

Closing archives every project at once: API keys stop working, webhooks are switched off, and payment links and buttons are cancelled. You are signed out everywhere. Live customer subscriptions must be cancelled and refunds in progress finished before the account can close. Team members cannot close the account; ask its owner. PayBridgeNP never holds your money, so payments already settled to your eSewa, Khalti or Fonepay accounts are not affected.

If you change your mind, email support@paybridgenp.com within 30 days from the account's email address, and we reopen the account as it was. After 30 days the deletion is permanent, and we erase your account data within 60 days of your request. Payment and refund records, and our invoices to you, are kept for 5 years and then deleted, as described under Retention. Deleting your merchant account does not delete a separate PayBridgeNP ID account.

We encrypt sensitive credentials, store passwords only as secure hashes, separate each merchant's data, and restrict and log staff access. We also keep a history of changes to merchants' provider credentials, without the secret values, to investigate security issues. More detail is on our security page.

Merchants, customers, PayBridgeNP ID users, and website visitors can ask us to access, correct, or delete personal data we hold about them, or to withdraw consent, by emailing support@paybridgenp.com with enough detail for us to find and verify the request. We may keep records we need for payments, accounting, disputes, fraud prevention, or the law. Merchants can close their account themselves; see Deleting your account.

If your question is about a specific purchase, the merchant you paid may be able to help faster, because they decide how their customer data is used; we will work with them where needed. We respond within 30 days, or tell you why we need longer. You can also manage cookies in your browser; see our cookies page.

We update this policy when what we collect, why, or who receives it changes, and show the date at the top. Questions and requests: support@paybridgenp.com.