Privacy Policy
Updated 10/22/2026
This Privacy Statement covers the following entities: Argyle Payments LLC. and Integrated Compliance, LLC referred to as “we,” “us,” and “our” throughout this statement.
Privacy Is Our #1 Priority
What types of nonpublic personal information do we collect?
What types of nonpublic personal information do we disclose?
- Information you provide online and on applications or other forms, such as your name, address, Social Security number, date of birth, business history and processing history.
- Information about your transactions with us, such as your processing history and banking history.
- Information about you from consumer-reporting agencies and business-reporting agencies.
To what types of entities (other than those companies used to process or service transactions) do we disclose nonpublic personal information?
To what other types of entities might we disclose nonpublic personal information?
How do we protect the confidentiality and security of nonpublic personal information?
Our employees (for example, customer service and compliance personnel) and third party service providers have access to your nonpublic personal information only on a “need to know” basis. We conduct regular internal audits of our business practices and procedures, examining confidentiality standards and information access in order to protect your personal information.
Cardholder Data Security Is Our Responsibility
This Cardholder Data Security Responsibility Statement covers Argyle Payments LLC, referred to as “we,” “us,” and “our” throughout this statement.
In the course of providing merchant non-cash processing products and services, we handle cardholder data on behalf of our merchant and partner customers. We protect that data under the Payment Card Industry Data Security Standard (PCI DSS). This statement is our security acknowledgement under PCI DSS Requirement 12.9, and it supports the security terms in our customer agreements.
What are we responsible for?
We are responsible for the security of all cardholder data and other account data that we possess, store, process or transmit on behalf of our customers. We are also responsible for the security of each customer’s cardholder data environment to the extent that we could affect it. We maintain PCI DSS compliance for the services we provide, and a qualified assessor validates that compliance at least once every twelve months.
How do we protect cardholder data?
- Minimal data: we keep only the account data our services need, mask card numbers, and never store sensitive authentication data (track data, card verification codes or PINs).
- Segmented network: systems that handle cardholder data sit in a restricted network segment with no public access to databases or key stores.
- Encryption: data is encrypted in transit (TLS 1.2 or higher) and at rest, with keys held in a managed key service.
- Access control: access is limited to staff who need it. Every user has a unique ID, and multi-factor authentication is required.
- Monitoring and testing: activity is logged and monitored, systems are patched and scanned every quarter, and independent penetration tests run every year.
- People and providers: our staff are trained in security every year, and our service providers must be PCI DSS compliant.
Who is responsible for what?
| Area | Our responsibility | Customer’s responsibility |
|---|---|---|
| Account data we handle for the customer | Responsible | None |
| Customer’s own terminals, websites, systems and staff | None, unless we provide them | Responsible |
| Sending data to us | Secure channels on our side | Securing its own systems and credentials |
| Our accounts given to customer staff | Securing the accounts | Giving access only to authorized staff and removing leavers promptly |
| PCI DSS validation | Our own annual assessment | The customer’s own compliance |
How can customers get our compliance information?
Customers can ask for our current Attestation of Compliance and a detailed matrix of PCI DSS responsibilities for their services. Email support@argylepayments.com. We may ask for a confidentiality agreement first.
What happens if there is a security incident?
If an incident affects a customer’s account data, we will notify that customer without undue delay, and within 72 hours of confirming the incident. We will contain it, cooperate with the customer, card brands and authorities, and fix its causes.
We ask customers to send account data only through the secure channels we provide, and to tell us promptly about any incident that could affect us.
Agreements and contact
If this statement conflicts with a customer’s signed agreement, the agreement controls. We review this statement at least once a year. Questions or security concerns: support@argylepayments.com. Please do not include card numbers in your message.
Have a question?
Email Us