01Information We Collect
Information may include details you submit, information generated when you use account or service features, and limited technical or security information needed to operate the platform. The precise collection and retention practices should be confirmed by the business owner before publication.
02Account Information
Account information may include name, mobile number, email address, shop or business details, profile information, and other fields used by the existing account features. Login credentials are used for authentication and are not displayed in service pages.
03Transaction and Service Information
A service request may contain the selected service, operator or biller, plan or category, customer-entered mobile or account references, amount, and request status. The current flows store drafts for review and do not submit them to a service provider.
04Technical Information
Technical information may include session, browser, device, IP-address, and security-event details generated by login, OTP, or platform activity. Login OTP records can include request IP address and user-agent information when that feature is enabled.
05How We Use Information
Information may be used to authenticate accounts, display requested service flows, validate submitted details, maintain service and transaction records, respond to support requests, protect the platform, and meet applicable legal obligations.
06Payment Information
The current payment-method preview does not collect card numbers, CVV, UPI PIN, ATM or card PIN, internet-banking passwords, or payment OTPs, and it does not initiate payments. If a future hosted payment integration is introduced, payment data handling must be described according to the actual provider integration before it launches.
07Information Sharing
Information may be shared where reasonably necessary to operate, secure, support, or complete a requested service, or where disclosure is required by law. The current local catalog flows do not send service requests to external providers.
08Service Providers
If provider or payment integrations are added, relevant information may be shared with those providers to support the requested service, subject to the applicable requirements and updated disclosures. No provider is named or represented as currently connected by this draft.
09Data Security
PaySport uses reasonable technical and organizational measures designed to protect information against unauthorized access, alteration, disclosure, or destruction. No method of storage or transmission can be represented as completely secure.
10Data Retention
Information may be retained as needed for account operation, service records, security, dispute handling, and legal obligations. Specific retention periods and deletion procedures must be confirmed by the business owner before publication.
12User Choices and Rights
You may contact PaySport to ask about access to or correction of account information, subject to identity checks, applicable law, and records that must be retained. The process and response timelines should be confirmed by the business owner.
13Children's Privacy
PaySport is not designed for children to use independently. The business should confirm an appropriate age and guardian policy before publication.
14Changes to This Privacy Policy
This policy may be updated as the platform or its integrations change. The publication process, effective date, and user-notice requirements should be confirmed before launch.
15Contact Information
For privacy questions, use the existing PaySport Contact page. The contact details below are copied from that page and require owner confirmation before publication.
Paysport Linkventures Private Limited B-1363, First Floor, Office No. 2, New Ashok Nagar, Delhi - 110096 info@paysport-co.inThese details are reproduced from the existing Contact page and must be confirmed by the site owner before publication.