Privacy Policy for Paymattic

Privacy Policy

The Privacy Policy describes information on how we collect, process, and share the personal data of external individuals to the paymattic.com website and the Paymattic WordPress plugin. We declare that Paymattic is a child concern of WPManageNinja. You can find WPManageNinja’s Privacy Policy here.

What data is being collected by Paymattic?

Paymattic requests data relevant to executing payment processing. But Paymattic does not store any credit card credentials.

Product users

When product users (website admins) deploy Paymattic on their WordPress website, they consciously agree to the terms or conditions regarding specific data accessible to third parties via their developer API. Note that, if the product users turned off the Auto Update or Auto Sync feature, still some data (previously cached) may be stored in the product user’s website database. However, Paymattic is not responsible for this cached data. This issue is described in detail below.

End-users

When end-users (payment gateway users) register with and complete transactions using the payment gateways, they consciously agree to the terms or conditions regarding specific data accessible to third parties via their developer API. Paymattic only forwards the data provided consciously by the end-users with users’ permission to make them accessible to third-party applications to process a payment. Moreover, all kinds of private data are excluded. Paymattic does not fetch/process/store any user data that are not permitted by users to be shared publicly. A detailed description of the personal data that Paymattic can display is given below:

Stripe access credentials

Paymattic will never receive any personal information about an individual user from Stripe. Stripe gateway works the same just as all payment gateway types. The only personal information provided by Stripe are the publishable key, and secret key. For more information, please refer to the Stripe privacy policy.

PayPal access credentials

Paymattic will never receive any personal information about an individual user from PayPal. PayPal gateway works the same just as all payment gateway types. The only personal information provided by PayPal are account email. For more information, please refer to the PayPal privacy policy.

Mollie access credentials

Paymattic will never receive any personal information about an individual user from Mollie. Mollie gateway works the same just as all payment gateway types. The only personal information provided by Mollie are publishable key. For more information, please refer to the Mollie privacy policy.

Razorpay access credentials

Paymattic will never receive any personal information about an individual user from Razorpay. Razorpay gateway works the same just as all payment gateway types. The only personal information provided by Razorpay are API key, and API secret. For more information, please refer to the Razorpay privacy policy.

Paystack access credentials

Paymattic will never receive any personal information about an individual user from Paystack. Paystack gateway works the same just as all payment gateway types. The only personal information provided by Paystack are API key, and API secret. For more information, please refer to the Paystack privacy policy.

Square access credentials

Paymattic will never receive any personal information about an individual user from Square. Square gateway works the same just as all payment gateway types. The only personal information provided by Square are access key, and location ID. For more information, please refer to the Square privacy policy.

Payrexx access credentials

Paymattic will never receive any personal information about an individual user from Payrexx. Payrexx gateway works the same just as all payment gateway types. The only personal information provided by Payrexx are instance name, and API key. For more information, please refer to the Payrexx privacy policy.

SSLCOMMERZ access credentials

Paymattic will never receive any personal information about an individual user from SSLCOMMERZ. SSLCOMMERZ gateway works the same just as all payment gateway types. The only personal information provided by SSLCOMMERZ are store key, and store password/secret. For more information, please refer to the SSLCOMMERZ privacy policy.

Billplz access credentials

Paymattic will never receive any personal information about an individual user from Billplz. Billplz gateway works the same just as all payment gateway types. The only personal information provided by Billplz are store key, and store password/secret. For more information, please refer to the Billplz privacy policy.

Moneris access credentials

Paymattic will never receive any personal information about an individual user from Moneris. Moneris gateway works the same just as all payment gateway types. The only personal information provided by Moneris are store ID, checkout ID, and API token. For more information, please refer to the Moneris privacy policy.

Xendit access credentials

Paymattic will never receive any personal information about an individual user from Xendit. Xendit payment gateway works the same just as all payment gateway types. The only personal information provided by Xendit is Secret Key. For more information, please refer to the Xendit privacy policy.

Flutterwave access credentials

Paymattic will never receive any personal information about an individual user from Flutterwave. Flutterwave payment gateway works the same just as all payment gateway types. The only personal information provided by Flutterwave is API Keys (Public Key, Secret Key, & Encryption Key). For more information, please refer to the Flutterwave privacy policy.

How does Paymattic use the data collected?

When Paymattic receives data from the submitted forms, it saves the submitted data on the plugin’s custom database.The admin can view the data in the entries page of the plugin.

Third-party APIs

Paymattic uses several third-party APIs for payment gateways. Data retrieved using these APIs is strictly confined to the site on which our product (WordPress plugin- Paymattic) is installed. This data is used by the website where the product is installed and stored in the MySQL. We make sure that Paymattic doesn’t reveal, send or process any such data. Moreover, no attempts should be taken to extract any further data from it, whether it can be personally identifiable or otherwise. We (Paymattic) do not store any data for the connected API services.

As we stick to this policy, any third-party APIs used by our products may collect usage data. You can visit the Data Policy pages to know how these APIs may gather and use the data for more information.

How can users request to delete their data?

Depending on access, users can be categorized into two types. The product users, those who directly use the Paymattic plugin to collect payments and donations. And the end-users, those who use the Paymattic forms to give payments and donations. So, based on the category of users, the process of deletion is also divided into two types.

Product users

To delete the configuration and credentials, from your WordPress website’s admin panel (product user) go to Paymattic > Payment gateways and open the configuration. Next, you can remove the data and Save Settings. 

End-users

End-users can request to delete their data. Request admin, only admin can delete.

How Paymattic website handles user data?

User data is a sensitive topic, and so the following questions, and answers arise on the topic.

Is any data forwarded to third parties?

Paymattic doesn’t collect any third-party data. We retrieve data directly from the users, which is stored only in the plugin’s custom database. If the admin (product user) wishes to send user data to third-parties, they can do so. But in such instances, Paymattic takes no responsibilities for such data sharing.

Does Paymattic track data?

Paymattic website itself doesn’t track any user data. We only collect some relevant user information through subscription forms which is used to make the customer journey more smooth. However, to ensure a better user experience and to provide better service, Paymattic website uses third-party tracking tools like Google Analytics. Learn more about them here.

Third-party connections

If the product user needs to send, forward, or provide any data to third-party connections, they are free to do so with Zapier or webhooks. But the Paymattic plugin doesn’t collect or distribute any user data on its own.

Does Paymattic use cookies to store personal data?

No, the Paymattic WordPress plugin does not use cookies to store personal data. However, the website (paymattic.com) assigns cookies to the visitors to make their browsing experience smoother. Users can accept or decline cookies by modifying the settings on the browser or by using the options.

Support and contact forms

When you click on the Support or Contact Form on our website, you may be asked to provide your name and email address to get back to your queries and requests. The information and your public IP address have been stored in the Paymattic website’s database. Moreover, we forward the support ticket submission to the WPManageNinja Support team. All the support and contact forms are managed by WPManageNinja.

Paymattic demos

Paymattic offers demo pages of each prebuilt form containing all the input fields to try before our users make a purchase. Due to these requests, your IP address is visible to the Paymattic team, which may be used following their data privacy policies.

External links

The affiliate websites may contain links to other websites. The Paymattic team is not responsible for the privacy practices or the content of such websites.

Linked content from other websites

Published blogs on our website may contain embedded content such as videos, images, articles, etc. However, this embedded content from other websites performs the same on our site as how website visitors have visited the other website.

Moreover, suppose you are logged in to the related account. In that case, these websites may collect data, use your cookies, embed additional third-party tracking, and monitor your action and interaction with that embedded content.

Product purchase

Users buying a product from our websites enables us to collect personal data associated with purchases and the transaction process. This includes:

• Name
• IP address
• Billing address (Credit Card)
• Please note that we don’t store credit card information. For payment operations, we have been using Stripe and PayPal. Both of the operators store information securely on their encrypted servers (Stripe privacy policy) and (PayPal privacy policy)

Above mentioned information is sent to Stripe/PayPal, and they process the transaction and store the information securely. The moment you purchase a product from us, we will send transactional emails related to your purchase or attempted purchase, such as purchase confirmation receipt, account login information, checkout recovery email, and license renewal reminder emails. When logged into your account on our website, a cookie is set in your browser for allowing you to remain logged into your account. All the product purchases are directly managed by WPManageNinja.

Data

For better performance, a smooth user experience, and product improvement, we need to collect usage data from the website visitors. We use analytics tools such as Google Analytics to collect general browsing information and IP address and location data. Check out the Google Analytics privacy policy from the link. To understand better how our website has been used, we track the page history of visitors on our site. Moreover, for your data deletion request, contact us at any time.

Website contact

You can contact us if you have any queries about our privacy policy, the practices of this site, or your dealings with this website; contact us on paymattic.com. For support, please contact our support team.

Report security vulnerabilities

In case you want to report a possible data security vulnerability, report to us immediately through WPManageNinja product support team. You can report any data vulnerability/probability of data breach here.