Data Processing Agreement#
This agreement is part of the Terms of Service between [Company legal name] ("we", the processor) and the business that holds a Payment Cascade account ("you", the controller). It applies whenever we process personal data on your behalf, and it meets the requirements of Article 28 of the GDPR, the UK GDPR, and the service provider rules of the California Consumer Privacy Act and similar US state laws. If this agreement and the Terms contradict each other on data protection, this agreement wins.
1. What we process#
Purpose and nature. We receive checkout requests from you, pass customer and order data to the payment providers you have connected, store the result and report it back to you. That is the only purpose.
Data subjects. Your customers, and the people whose details your customers enter (for example, a different recipient in the shipping address).
Personal data. Name, email address, phone number, billing and shipping address, order items and amounts, your order ID, provider references and statuses, and the IP address and browser information of customers who pass through our payment pages. We don't ask for special categories of data under Article 9 GDPR, and you must not send them.
Duration. For as long as your account is open, plus the deletion period in section 8.
2. Your instructions#
We process the data only on your documented instructions. Those instructions are the Terms, this agreement, your API requests, and the settings in your account, including which providers to try and in which order. Sending a checkout to a provider you have connected is processing on your instructions. The provider receives the data as your partner under your contract with it; it is not our sub-processor.
If we believe an instruction breaks data protection law, we will tell you. We may refuse to follow an instruction until it is confirmed or changed. If the law requires us to process data in another way, we will tell you first unless the law forbids it.
3. US state law terms#
We act as your service provider or contractor. We will not sell or share the personal data, use it for cross-context behavioural advertising, or keep, use or disclose it for any purpose other than providing the service to you, or outside our direct business relationship with you. We will not combine it with personal data from other sources, except as those laws allow. We will tell you if we can no longer meet these obligations, and you may then take reasonable steps to stop unauthorised use.
4. Confidentiality#
Everyone at our company who can access the data is bound to keep it confidential.
5. Security#
We take the technical and organisational measures listed in the annex, and update them as technology and risks change, without lowering the overall level of protection.
6. Sub-processors#
You give us general authorisation to use sub-processors. Our current sub-processor is:
| Sub-processor | What it does | Location |
|---|---|---|
| [Hosting provider, country] | Hosts the servers and database | As stated |
We will email you at least 30 days before adding or replacing a sub-processor. You may object on reasonable data protection grounds within that period. If we can't address the objection, you may close your account, and we will refund unused purchased credits. Each sub-processor is bound by data protection terms at least as protective as these, and we remain responsible for it.
7. Helping you#
Taking into account what we can reasonably do, we will help you to:
- answer requests from data subjects. If a request reaches us, we forward it to you and don't answer it ourselves unless you tell us to;
- meet your duties around security, breach notification, data protection impact assessments and prior consultation with authorities.
Breaches. If we become aware of a personal data breach affecting your data, we will notify you without undue delay, and in any case within 48 hours. We will tell you what happened, which data and roughly how many people are affected, the likely consequences, and what we are doing about it, and keep you updated as we learn more.
8. Deletion and return#
While your account is open, you can read each checkout through the API, and on request we export all your checkout data in a machine-readable format. Within 30 days after your account is closed, we delete the personal data we processed for you, unless the law requires us to keep it. Data in backups is overwritten as part of the normal backup cycle.
9. Audits#
We will make available the information you need to show that we meet these obligations. You may audit us, or have an independent auditor bound to confidentiality audit us, once a year with at least 30 days' notice, or at any time after a breach or a request from a supervisory authority. Audits take place during business hours and must not disrupt the service or expose other customers' data. Each party bears its own costs.
10. Transfers outside the EEA#
We transfer data to countries outside the European Economic Area that lack an EU adequacy decision only with appropriate safeguards under Chapter V GDPR, usually the European Commission's Standard Contractual Clauses (module 2 or 3, as applicable). By accepting this agreement, the parties agree to those clauses where they are needed.
11. Liability#
Liability under this agreement follows section 8 of the Terms, unless the law does not allow it to be limited.
Annex: technical and organisational measures#
- Encryption in transit. All connections use HTTPS, with HSTS enabled.
- Encryption at rest. API keys and provider credentials are encrypted with a key kept outside the database. API keys are looked up by a hash. Passwords are stored only as salted hashes.
- Access control. Merchants see only their own checkouts. Server and admin access is limited to the people who run the service and requires authentication.
- Abuse protection. Rate limits on registration, login and the API, and automatic blocking of IP addresses that exceed them.
- Integrity. Webhooks from payment providers are checked by signature and timestamp. Webhooks we send to you are signed with your API key.
- Payment safety. A checkout can be paid only once. An abandoned attempt with one provider is closed before the next provider is tried.
- Data minimisation. Server logs exclude URL query strings and are kept for 14 days.
- Separation. Each merchant's provider credentials are separate. No card data passes through our systems; customers pay on the providers' own pages.