Data Processing Agreement — Calmony DD
DRAFT FOR LEGAL REVIEW — NOT FOR USE. Prepared 29 September 2026. Items marked [TO CONFIRM] need a decision before publication.
Effective Date: [TO CONFIRM on publication]
1. Parties and scope
This Data Processing Agreement ("DPA") forms part of the Terms of Service for Calmony DD between agentOS Proptech Group Ltd, trading as Calmony (company number 05409547, 13 Lambourne Crescent, Cardiff Business Park, Llanishen, Cardiff CF14 5GF) ("we", "the Processor"), and the business using Calmony DD ("the Customer", "the Controller").
It applies whenever we process personal data about the Customer's payers on the Customer's behalf in providing Calmony DD. It is intended to meet Article 28 of the UK GDPR. If this DPA and the Terms conflict on data protection, this DPA prevails.
2. Roles
- The Customer is the controller of personal data about its payers. It decides why that data is processed: to collect payments from its customers by Direct Debit.
- We are the processor of that data, and process it only to provide Calmony DD.
- For personal data about the Customer's own staff and users of Calmony DD, we act as a controller, as described in our Privacy Policy. This DPA does not cover that data.
- Modulr FS Limited provides the Customer's Modulr account and the Direct Debit and payment services under its own agreement with the Customer, and processes payer data under that agreement. [TO CONFIRM: that Modulr is treated as an independent provider to the Customer, not as our sub-processor.]
3. Details of the processing
- Subject matter: providing Calmony DD, a service for setting up and managing Direct Debits under the Bacs Direct Debit Scheme.
- Nature of processing: collection, recording, storage, transmission to Modulr, retrieval, display to the Customer, and deletion.
- Purpose: inviting payers to set up Direct Debits; verifying payers (identity-verification video and account-name check); lodging mandates and requesting collections through Modulr; sending Bacs advance notices, confirmations and variation notices; recording and alerting on returns, cancellations and indemnity claims; and keeping the related records.
- Data subjects: the Customer's payers (its customers) and people invited to become payers.
- Personal data:
- payer email address, payment reference and amounts or schedule; - account holder name, sort code, account number, UK mobile number and address, which are passed to Modulr and not stored in Calmony DD's own systems; - an identity-verification video of the payer reading a phrase, the phrase, and when it was recorded; - the account-name-check result; - mandate, collection, notice, return, cancellation and indemnity-claim records; - authorisation evidence: the wording and Direct Debit Guarantee shown, the time of authorisation, and the payer's IP address and browser details.
- Special category data: none intended. The identity-verification video is not used for biometric identification: no face matching is carried out.
- Duration: for as long as the Customer uses Calmony DD, and afterwards for the retention periods in section 9.
4. Our obligations as processor
We will:
- process payer personal data only on the Customer's documented instructions, which are these Terms, this DPA and the Customer's use and configuration of Calmony DD, unless the law requires otherwise. In that case we will tell the Customer first unless the law forbids it;
- tell the Customer promptly if we believe an instruction breaks data protection law;
- make sure everyone we authorise to process the data is bound by confidentiality;
- put in place the security measures in section 7;
- use sub-processors only as set out in section 6;
- help the Customer, taking account of the nature of the processing, to respond to requests from payers exercising their rights (section 8);
- help the Customer meet its obligations on security, breach notification, data protection impact assessments and prior consultation with the ICO, using the information available to us;
- delete or return data at the end of the service as set out in section 9;
- make available the information reasonably needed to show we comply with this DPA, and allow audits as set out in section 10.
5. The Customer's obligations
The Customer is responsible for:
- having a lawful basis for collecting from each payer and for the processing it instructs;
- giving payers the information data protection law requires; Calmony DD shows payers our Privacy Policy and the Direct Debit Guarantee during set-up;
- the accuracy of the data it enters;
- deciding whether to require identity-verification video;
- handling payer requests and complaints as controller.
6. Sub-processors
The Customer gives general authorisation for us to use sub-processors. Our current sub-processors for payer data are:
- Vercel Inc.: application hosting (London and Paris regions);
- Neon Inc.: database hosting (UK/EU region);
- Temporal Technologies Inc.: background processing of mandate and collection jobs [TO CONFIRM region];
- Resend: email delivery of payer notices (EU region);
- file storage for identity-verification videos [TO CONFIRM provider and region];
- SaaS Factory, our software platform provider, for platform services including error monitoring and audit logging [TO CONFIRM legal entity, services and regions].
We keep this list up to date in our Sub-processors document. We will give the Customer at least 30 days' notice of a new sub-processor, and the Customer may object on reasonable data protection grounds. If we can't resolve the objection, the Customer may stop using Calmony DD. We will impose data protection terms on each sub-processor that are no less protective than this DPA, and we remain responsible for their performance.
7. Security
We keep appropriate technical and organisational measures in place, including:
- encryption of data in transit;
- payer bank details are passed to Modulr and not stored in our systems;
- access controls, and separation of each Customer's data by organisation [TO CONFIRM: whether database row-level security is enforced for the application role];
- a restricted, least-privilege database role for the application;
- logging and monitoring of access and errors;
- regular automated security, dependency and quality reviews of the codebase;
- documented incident response.
[TO CONFIRM: backup and disaster-recovery arrangements, and penetration testing.] Our Security Policy describes these measures in more detail.
8. Data subject requests
If a payer asks us directly to exercise their rights, we will pass the request to the Customer without undue delay and not respond ourselves, unless the Customer authorises us to. Calmony DD lets the Customer view, export and cancel a payer's mandates and records to help it respond.
9. Retention, deletion and return
We apply these retention periods on the Customer's behalf:
- mandate, collection, notice, return and indemnity-claim records, the payer's email, the identity-verification video and the authorisation evidence: 6 years after the mandate ends or the claim is closed, in line with Direct Debit Scheme and HMRC record-keeping requirements;
- invites that are never completed, including any identity-verification video: deleted 30 days after the invite link expires;
- outbound webhook records and provider call logs: 90 days.
When the Customer stops using Calmony DD, it can export its records. We will then delete payer personal data, except where the law or the Direct Debit Scheme requires records to be kept, in which case we keep them only for the periods above and then delete them. [TO CONFIRM: export window after termination, e.g. 30 days, matching the Terms.]
10. Audits
We will make available information reasonably needed to demonstrate compliance, such as our security documentation and summaries of independent assessments where available. The Customer, or an auditor it appoints who is bound by confidentiality, may audit our compliance once a year, or after a personal data breach, on at least 30 days' notice, during business hours, and at the Customer's cost.
11. Personal data breaches
We will notify the Customer without undue delay, and in any case within 48 hours, after becoming aware of a personal data breach affecting payer data [TO CONFIRM: 48 hours]. We will give the information the Customer reasonably needs to meet its own obligations, including notifying the ICO within 72 hours where required, and we will take reasonable steps to contain and remedy the breach.
12. International transfers
We aim to keep payer personal data in the United Kingdom and the European Economic Area. We will not transfer it outside the UK/EEA without an adequacy decision or appropriate safeguards, such as the UK International Data Transfer Addendum. [TO CONFIRM: once every sub-processor's region is confirmed.]
13. Liability and term
Each party's liability under this DPA is subject to the limitations in the Terms of Service. This DPA lasts for as long as we process payer personal data for the Customer.
14. Governing law
This DPA is governed by the laws of England and Wales. The courts of England and Wales have exclusive jurisdiction.