2.9 ORDER AND PAYMENT SECURITY; SECURE CHECKOUT POLICY.
(a) When you place orders on our Website or through our Mobile Web App, your order information, including without limitation your payment card number, payment address, delivery address, and other information (including without limitation personally identifiable information) is transmitted through the internet to Navore and to certain third party payment processors. Such information is transmitted utilizing the security functions implemented or required by the applicable payment processor, which has been represented to Navore as including the use of secure sockets layer technology (a technology which, assuming your browser is properly functioning and has properly implemented such technology, causes your browser to encrypt your order information before transmitting it). Such technology is industry standard and is designed and intended to prevent someone other than you from capturing and viewing your personal information.
(b) Although Navore has (and our payment processors have represented that they have) implemented and use secure sockets layer technology and/or other industry standard means to protect your information, our Website, and our Mobile Web App, no communication methods are perfectly secure, and any communication is susceptible to interception and de-encryption (or capture via nefarious means prior to or following transmittal). While the security measures Navore uses (and its payment processors have indicated they use) are appropriate based on the nature and type of information, no guaranty can be provided that use of our Website or Mobile Web App, or transmittal of any information, will be completely safe. It is important that you use strong credentials to protect your personal information and use caution with respect to: (i) the software that is run (whether intentionally or unintentionally) on your device; (ii) the personal security and protections in place with respect to your device; and (iii) your transmittal of information and use of the internet.
Comments
0 comments
Please sign in to leave a comment.