PRIVACY & TRUST
DATA HANDLED WITH PURPOSE.
This policy explains the information the website may collect, why it is used, and the controls available to administrators and customers.
SCOPE
What this privacy policy covers.
This website supports product discovery, enquiries, registered customer accounts, orders, payment-reference submission and administrative analytics. The information collected depends on how a visitor uses the site. A person who only browses equipment pages may generate technical visitor records. A customer who submits an enquiry or creates an account provides additional contact information. A customer who places an order provides delivery and transaction-related information required to process that order.
The business should only request information that has a clear operational purpose. The website does not require customers to provide cryptocurrency private keys, wallet seed phrases or online-banking passwords. Manual payment methods may request a UTR, transaction reference, proof image or wallet transaction identifier so the administrator can review the submitted payment.
This policy is a configurable project document and should be reviewed by the business before production use. Legal requirements can differ by jurisdiction, customer type, payment method and data-processing arrangement. The administrator should ensure the final published wording accurately reflects actual practices.
The business should only request information that has a clear operational purpose. The website does not require customers to provide cryptocurrency private keys, wallet seed phrases or online-banking passwords. Manual payment methods may request a UTR, transaction reference, proof image or wallet transaction identifier so the administrator can review the submitted payment.
This policy is a configurable project document and should be reviewed by the business before production use. Legal requirements can differ by jurisdiction, customer type, payment method and data-processing arrangement. The administrator should ensure the final published wording accurately reflects actual practices.
INFORMATION COLLECTED
Account, enquiry, order and technical data.
Account information can include name, email address, phone number, password hash, account status and creation time. Passwords are stored as password hashes rather than readable plain text. Enquiry information can include contact details, country, state, city, pincode, requirement type, gym size, preferred series, referral source and the message submitted by the visitor.
Order data can include order number, linked user account, total amount, order status, selected payment method, payment status, shipping name, phone number, shipping address, notes and order date. Payment-review data can include method, amount, transaction reference, uploaded proof and verification status. Product and admin records may also be associated with operational changes made by authorized staff.
When visitor tracking is enabled, the site may record session identifier, IP address, browser user-agent string, broad device category, page path, page title, referrer and approximate geographic data returned by an IP-geolocation service. Such geographic data can include country, state or region, city, postal area and approximate coordinates. IP-based location is inherently approximate and can be affected by network routing or privacy services.
Order data can include order number, linked user account, total amount, order status, selected payment method, payment status, shipping name, phone number, shipping address, notes and order date. Payment-review data can include method, amount, transaction reference, uploaded proof and verification status. Product and admin records may also be associated with operational changes made by authorized staff.
When visitor tracking is enabled, the site may record session identifier, IP address, browser user-agent string, broad device category, page path, page title, referrer and approximate geographic data returned by an IP-geolocation service. Such geographic data can include country, state or region, city, postal area and approximate coordinates. IP-based location is inherently approximate and can be affected by network routing or privacy services.
HOW DATA IS USED
Operational reasons for processing information.
Information may be used to respond to enquiries, create and manage customer accounts, process orders, verify submitted payment references, coordinate delivery, provide product or service support and maintain the security of the website. Administrators may use order and enquiry information to understand project requirements and communicate with customers about quotations, availability or service needs.
Visitor analytics may be used to understand which pages attract interest, what device categories are common, where broad geographic demand appears to originate and which referrers send traffic. This can support content planning, inventory presentation and marketing analysis. Analytics should not be treated as a precise real-world location system.
Security-related processing can include session handling, CSRF protection, access-status checks and server logs. Administrators are responsible for limiting panel access to authorized personnel and keeping hosting credentials secure. Data should not be retained indefinitely without a business or legal purpose. A production deployment should establish retention periods for enquiries, analytics, transaction proofs and inactive accounts.
Visitor analytics may be used to understand which pages attract interest, what device categories are common, where broad geographic demand appears to originate and which referrers send traffic. This can support content planning, inventory presentation and marketing analysis. Analytics should not be treated as a precise real-world location system.
Security-related processing can include session handling, CSRF protection, access-status checks and server logs. Administrators are responsible for limiting panel access to authorized personnel and keeping hosting credentials secure. Data should not be retained indefinitely without a business or legal purpose. A production deployment should establish retention periods for enquiries, analytics, transaction proofs and inactive accounts.
SHARING & SERVICES
When third-party infrastructure may be involved.
The website may rely on hosting, content-delivery, mapping, analytics-support or communication services necessary to operate the platform. Visitor geolocation is designed to use an external IP-geolocation lookup when tracking is enabled, and the admin map loads OpenStreetMap map tiles through the Leaflet mapping library. Product pages may also display externally hosted images if an administrator chooses to configure external image URLs.
Payment processing described in the current build is manual-verification oriented. The site can display UPI, bank-transfer or USDT TRC20 instructions configured by the administrator, and customers can submit references or proof. Any future integration with a payment gateway, logistics provider, email service or CRM may introduce additional data sharing and should be reflected in this policy before launch.
The business should avoid selling or disclosing customer data in ways that are inconsistent with its public commitments or applicable law. Service providers should receive only the information necessary for their role and should be selected with appropriate attention to security and contractual obligations.
Payment processing described in the current build is manual-verification oriented. The site can display UPI, bank-transfer or USDT TRC20 instructions configured by the administrator, and customers can submit references or proof. Any future integration with a payment gateway, logistics provider, email service or CRM may introduce additional data sharing and should be reflected in this policy before launch.
The business should avoid selling or disclosing customer data in ways that are inconsistent with its public commitments or applicable law. Service providers should receive only the information necessary for their role and should be selected with appropriate attention to security and contractual obligations.
SECURITY & CHOICES
Controls for customers and administrators.
The application uses password hashing, CSRF tokens for form submissions, HTTP security headers and status-based access checks as part of its baseline security design. Administrators can block or unblock customer login access and can control which content blocks, products, categories, trainers and payment methods are visible. Website settings also include a visitor-tracking switch so analytics collection can be disabled at application level.
No internet service can guarantee absolute security. Production administrators should keep PHP and server software maintained, use HTTPS, restrict database permissions, maintain backups, rotate sensitive credentials, review administrator accounts and remove unused uploads or integrations. Access to transaction proof images and customer records should be limited to people who need that information for their work.
Customers may contact the business using the support details published on the website to ask questions about their account or submitted information. Requests for correction, deletion or other privacy rights should be handled according to applicable law and legitimate record-keeping requirements. Where records must be retained for accounting, fraud prevention, contractual or legal reasons, the business should explain the applicable limitation rather than silently ignoring a request.
No internet service can guarantee absolute security. Production administrators should keep PHP and server software maintained, use HTTPS, restrict database permissions, maintain backups, rotate sensitive credentials, review administrator accounts and remove unused uploads or integrations. Access to transaction proof images and customer records should be limited to people who need that information for their work.
Customers may contact the business using the support details published on the website to ask questions about their account or submitted information. Requests for correction, deletion or other privacy rights should be handled according to applicable law and legitimate record-keeping requirements. Where records must be retained for accounting, fraud prevention, contractual or legal reasons, the business should explain the applicable limitation rather than silently ignoring a request.