Privacy Policy

php-encryption =============== ![Build Status](https://app.travis-ci.com/defuse/php-encryption.svg?branch=master) [![codecov](https://codecov.io/gh/defuse/php-encryption/branch/master/graph/badge.svg)](https://codecov.io/gh/defuse/php-encryption) [![Latest Stable Version](https://poser.pugx.org/defuse/php-encryption/v/stable)](https://packagist.org/packages/defuse/php-encryption) [![License](https://poser.pugx.org/defuse/php-encryption/license)](https://packagist.org/packages/defuse/php-encryption) [![Downloads](https://img.shields.io/packagist/dt/defuse/php-encryption.svg)](https://packagist.org/packages/defuse/php-encryption) ```terminal composer require defuse/php-encryption ``` This is a library for encrypting data with a key or password in PHP. **It requires PHP 5.6 or newer and OpenSSL 1.0.1 or newer.** We recommend using a version of PHP that [still has security support](https://www.php.net/supported-versions.php), which at the time of writing means PHP 8.0 or later. Using this library with an unsupported version of PHP could lead to security vulnerabilities. The current version of `php-encryption` is v2.4.0. This library is expected to remain stable and supported by its authors with security and bugfixes until at least January 1st, 2024. The library is a joint effort between [Taylor Hornby](https://defuse.ca/) and [Scott Arciszewski](https://paragonie.com/blog/author/scott-arcizewski) as well as numerous open-source contributors. What separates this library from other PHP encryption libraries is, firstly, that it is secure. The authors used to encounter insecure PHP encryption code on a daily basis, so they created this library to bring more security to the ecosystem. Secondly, this library is "difficult to misuse." Like [libsodium](https://github.com/jedisct1/libsodium), its API is designed to be easy to use in a secure way and hard to use in an insecure way. Dependencies ------------ This library requires no special dependencies except for PHP 5.6 or newer with the OpenSSL extensions (version 1.0.1 or later) enabled (this is the default). It uses [random\_compat](https://github.com/paragonie/random_compat), which is bundled in with this library so that your users will not need to follow any special installation steps. Getting Started ---------------- Start with the [**Tutorial**](docs/Tutorial.md). You can find instructions for obtaining this library's code securely in the [Installing and Verifying](docs/InstallingAndVerifying.md) documentation. After you've read the tutorial and got the code, refer to the formal documentation for each of the classes this library provides: - [Crypto](docs/classes/Crypto.md) - [File](docs/classes/File.md) - [Key](docs/classes/Key.md) - [KeyProtectedByPassword](docs/classes/KeyProtectedByPassword.md) If you encounter difficulties, see the [FAQ](docs/FAQ.md) answers. The fixes to the most commonly-reported problems are explained there. If you're a cryptographer and want to understand the nitty-gritty details of how this library works, look at the [Cryptography Details](docs/CryptoDetails.md) documentation. If you're interested in contributing to this library, see the [Internal Developer Documentation](docs/InternalDeveloperDocs.md). Other Language Support ---------------------- This library is intended for server-side PHP software that needs to encrypt data at rest. If you are building software that needs to encrypt client-side, or building a system that requires cross-platform encryption/decryption support, we strongly recommend using [libsodium](https://download.libsodium.org/doc/bindings_for_other_languages) instead. Examples --------- If the documentation is not enough for you to understand how to use this library, then you can look at an example project that uses this library: - [encutil](https://github.com/defuse/encutil) - [fileencrypt](https://github.com/tsusanka/fileencrypt) Security Audit Status --------------------- This code has not been subjected to a formal, paid, security audit. However, it has received lots of review from members of the PHP security community, and the authors are experienced with cryptography. In all likelihood, you are safer using this library than almost any other encryption library for PHP. If you use this library as a part of your business and would like to help fund a formal audit, please [contact Taylor Hornby](https://defuse.ca/contact.htm). Public Keys ------------ The GnuPG public key used to sign current and older releases is available in [dist/signingkey.asc](https://github.com/defuse/php-encryption/raw/master/dist/signingkey.asc). Its fingerprint is: ``` 2FA6 1D8D 99B9 2658 6BAC 3D53 385E E055 A129 1538 ``` You can verify it against Taylor Hornby's [contact page](https://defuse.ca/contact.htm) and [twitter](https://twitter.com/DefuseSec/status/723741424253059074). Due to the old key expiring, new releases will be signed with a new public key available in [dist/signingkey-new.asc](https://github.com/defuse/php-encryption/raw/master/dist/signingkey-new.asc). Its fingerprint is: ``` 6DD6 E677 0281 5846 FC85 25A3 DD2E 507F 7BDB 1669 ``` A signature of this new key by the old key is available in [dist/signingkey-new.asc.sig](https://github.com/defuse/php-encryption/raw/master/dist/signingkey-new.asc.sig).

At NFC Pay, your privacy is of utmost importance to us. This Privacy Policy outlines how we collect, use, share, and protect your personal information when you use our services, including our website and mobile applications.
1. Information We Collect

Personal Information: We may collect personal information such as your name, email address, phone number, date of birth, and payment card details when you register for an account, make payments, or engage with our services.
Transaction Data: Information related to your transactions, including the amount, date, time, and merchant details.
Device Information: Data such as IP addresses, device type, operating system, and unique device identifiers.
Location Information: We may collect your geolocation data when you use our app for location-based services.
Usage Information: Information about how you interact with our services, including access times, pages viewed, and links clicked.

2. How We Use Your Information
We use the information we collect for the following purposes:

To Provide Services: To facilitate payments, manage your account, and deliver customer support.
To Improve Our Services: To enhance the performance and functionality of our app and website, and to develop new features.
To Communicate with You: To send you updates, security alerts, and support messages.
For Security and Fraud Prevention: To monitor, detect, and prevent fraud, unauthorized transactions, and other security issues.
To Comply with Legal Obligations: To fulfill our legal, regulatory, and compliance obligations.

3. Sharing Your Information
We may share your personal information in the following circumstances:

With Service Providers: We may share information with third-party service providers who perform services on our behalf, such as payment processing, data analysis, and customer support.
For Legal Reasons: We may disclose information to comply with applicable laws, regulations, legal processes, or governmental requests.
Business Transfers: In the event of a merger, acquisition, or sale of all or a portion of our assets, your information may be transferred as part of that business deal.

4. Security of Your Information
We take the security of your personal information seriously and implement a variety of security measures, including encryption, secure servers, and access controls, to protect your data from unauthorized access, disclosure, alteration, or destruction. However, no method of transmission over the internet or electronic storage is completely secure, and we cannot guarantee its absolute security.
5. Your Privacy Rights
Depending on your location, you may have certain rights regarding your personal information, such as:

Access and Correction: You may request access to or correction of your personal information.
Deletion: You can request that we delete your personal information, subject to certain exceptions.
Opt-Out: You may opt out of receiving promotional communications from us by following the instructions in those messages.

6. Third-Party Links
Our services may contain links to third-party websites or services. We are not responsible for the privacy practices or the content of these third-party sites. We encourage you to review the privacy policies of those third parties.
7. Children’s Privacy
Our services are not intended for individuals under the age of 13. We do not knowingly collect personal information from children under 13. If we become aware that we have collected personal information from a child under 13, we will take steps to delete that information.
8. Changes to This Privacy Policy
We may update this Privacy Policy from time to time to reflect changes in our practices or for other operational, legal, or regulatory reasons. We will notify you of any significant changes by posting the new Privacy Policy on our website and updating the effective date.
9. Contact Us
If you have any questions or concerns about this Privacy Policy or our data practices, please contact us at:
Email: support@nfcpay.com

Useful Links

Subscribe