Privacy Policy
Last Updated: July 5, 2026
Pay2Bulk Platform ("Company", "we", "us", or "our") is completely committed to protecting the privacy and security parameters of our merchants and users. This Privacy Policy describes how we collect, use, process, store, and safeguard your operational data elements when you utilize our transaction services, dashboard terminal, and automated UPI & IMPS Payout Gateway systems (collectively, the "Services").
By registering or using our processing infrastructure, you explicitly agree to the collection and data handling practices described in this policy framework. If you do not agree with these operations, please do not access our terminal environment.
1. Information We Collect
To safely handle balance routing and ensure network security, we collect the following sets of data parameters:
A. Merchant Account Profile Information
Full Name of account managers, authorized business entity names, valid corporate types, business registration documents, Permanent Account Number (PAN), and regulatory national identification parameters required to clear your initial onboarding state from Pending status.
B. Technical & Security Logs
Merchant server IP addresses configured for IP Whitelisting protection, hardware specifications, operating system versions, access log timestamps, browser identifiers, and security handshake patterns.
C. Payout & Transaction Data
Detailed parameters required to execute balance distribution commands, including beneficiary full names, matching bank account numbers, IFSC routing codes, virtual payment addresses (UPI IDs), specific transfer volumes, time-stamps, Retrieval Reference Numbers (RRN), and Unique Transaction References (UTR).
2. How We Use Your Information
We process your data strictly to run financial distribution channels under clean, transparent rules:
- To safely run, process, and track your instant UPI and IMPS business payouts.
- To maintain active security walls by checking whitelisted server IP records against incoming API requests.
- To complete merchant identity checks and clear accounts out of the default pending verification queue.
- To issue instant system alerts, text notifications, and transaction updates regarding wallet balances.
- To track platform performance and optimize transfer delivery speeds across bank paths.
- To isolate security environments and block fraud, balance abuses, or malicious script attacks.
3. Sharing of Information
Pay2Bulk functions as an independent routing core. We do not sell or lease profile metrics or transaction structures to ad tracking companies or third-party marketing groups. Information is only exposed to trusted financial bodies to process your explicit payout requests:
- Banking Operations & Processing Nodes: To pass balance distribution payloads securely and verify recipient routing endpoints.
- Regulatory & Legal Officers: When demanded under active Indian financial laws, tax reporting mandates, or formal audit requests by national law authorities.
4. Data Retention Limits
We store information logs for as long as your merchant profile remains operational. According to standard Indian financial, tax, and anti-fraud reporting guidelines, core transaction records and audit journals are safely retained for a period ranging from 5 to 10 years, even after profile closing request completion.
5. Structural Security Actions
We isolate all database instances and execute standard financial data protection routines. Active sessions use strict HTTPS/SSL configurations during network transmissions. Pre-funded merchant account assets and keys are heavily secured via AES-256 bit encryption protocols. No web framework is 100% immune, but we monitor and log core terminal nodes continuously to block data leaks.
6. Policy Amendments
We update this policy structure as our routing tools evolve. Material modifications are notified via merchant email prompts or alert highlights inside the main terminal dashboard panel. Continued use of our payout tools indicates structural agreement with the updated documentation updates.