Request the DPA PDF
Get the current DPA, IDTA, and SCC annexes.
We return a signed PDF and the Standard Contractual Clauses / UK International Data Transfer Addendum as a single package, together with our Annex I–III (processing details, technical and organisational measures, sub-processor list).
Email legal@markst.com →1. Who needs a DPA?
You do if your organisation is a data controller and Verus will process personal data (user identifiers, portfolio company personnel, borrower contacts, or any personal data embedded in deal documents) on your instructions. Under UK and EU GDPR the DPA is not optional — it is a statutory requirement for every controller / processor relationship.
2. What it covers
- Subject matter and duration of the processing.
- Nature and purpose — operating the Verus valuation platform under the master service agreement.
- Types of personal data and categories of data subjects.
- Obligations and rights of the controller and processor, including confidentiality, sub-processor engagement, audit rights, and termination.
- Technical and organisational measures (Annex II) — encryption, access controls, tenant isolation, logging, incident response.
- International transfers — UK IDTA Addendum and the EU Standard Contractual Clauses (module 2: controller to processor) attached as annexes.
- Assistance with data-subject rights, breach notification (within 72 hours where required), and DPIAs.
- Return or deletion of personal data on termination.
3. Annexes
- Annex I — processing details (parties, subject matter, nature, purpose, categories, retention).
- Annex II — technical and organisational measures (aligned with the posture described at /trust).
- Annex III — authorised sub-processors (kept in sync with /legal/subprocessors).
- UK IDTA Addendum — ICO-approved template.
- EU SCCs (module 2) — 2021/914 as updated.
4. Turnaround
We target a one-business-day response. If you have a preferred DPA template, include it with your request and we will mark it up against our standard terms. Material deviations may require sign-off from the master services agreement, so plan for a longer loop if you are early in a procurement cycle.
5. Who can sign
On the MARKST LTD side, the DPA is executed by an authorised signatory at the company's registered office (45 Albemarle Street, Floor 3, London W1S 4JL). On your side, it should be signed by whoever has authority to bind the controlling legal entity.
6. Related documents
- Privacy Notice — personal data we hold as a controller (your account data).
- Data Protection (GDPR) — how we meet UK / EU GDPR obligations.
- Subprocessors — the list referenced in Annex III.
- Trust & Security — posture and compliance roadmap that back Annex II.
7. Contact
DPA and procurement: legal@markst.com. Data protection queries: dpo@markst.com.
DATA PROCESSING AGREEMENT
This Data Processing Agreement (the "DPA") is entered into between MARKST LTD, a company incorporated in England and Wales under company number 17164595 with registered office at 45 Albemarle Street, Floor 3, London W1S 4JL, United Kingdom (the "Processor"), and the customer identified in the Principal Agreement (the "Controller"). The Controller and the Processor are each a "Party" and together the "Parties".
This DPA is entered into in connection with the master service agreement, order form, terms of service or other written agreement between the Parties that governs the Controller's use of the Verus platform operated by the Processor (the "Principal Agreement"). This DPA supplements and, to the extent of any conflict on matters of data protection, prevails over the Principal Agreement.
The Parties intend for this DPA to satisfy the requirements of Article 28 of the UK General Data Protection Regulation and Article 28 of Regulation (EU) 2016/679 (together, "GDPR"), and to incorporate by reference the European Commission's Standard Contractual Clauses (module 2: controller to processor) set out in Commission Implementing Decision (EU) 2021/914 (the "EU SCCs") and the UK International Data Transfer Addendum issued by the Information Commissioner's Office (the "UK IDTA"), as applicable.
IT IS AGREED as follows.
1. Definitions and interpretation
Capitalised terms used but not defined in this DPA have the meanings given in the Principal Agreement or, where not so defined, in the GDPR. For the avoidance of doubt:
- (a) "Personal Data" means any personal data, as defined in the GDPR, that the Processor Processes on behalf of the Controller in connection with the Principal Agreement.
- (b) "Process", "Processing" and "Processed" bear the meaning given in Article 4(2) of the GDPR.
- (c) "Sub-processor" means any third party engaged by the Processor to Process Personal Data on behalf of the Controller, other than the Processor's own employees.
- (d) "Data Subject Request" means a request by a Data Subject to exercise any right under Chapter III of the GDPR.
- (e) "Personal Data Breach" bears the meaning given in Article 4(12) of the GDPR.
- (f) "Supervisory Authority" bears the meaning given in Article 4(21) of the GDPR; in the United Kingdom this is the Information Commissioner's Office ("ICO").
2. Scope, subject matter and duration
The subject matter, nature and purpose of the Processing, the categories of Personal Data and of Data Subjects, and the duration of the Processing are as set out in Annex I to this DPA.
This DPA takes effect on the later of the Effective Date of the Principal Agreement and the date this DPA is signed by both Parties, and continues in force for so long as the Processor Processes Personal Data on behalf of the Controller, together with any survival periods expressly provided for in this DPA.
3. Status of the parties
In respect of the Personal Data described in Annex I, the Controller is the controller and the Processor is a processor. Each Party will comply with the obligations that apply to it under the GDPR and any other applicable data protection laws.
The Processor Processes Personal Data only for, and on behalf of, the Controller, and only for the purposes set out in Annex I. The Processor has no independent right to use or disclose the Personal Data for any other purpose.
4. Processing on documented instructions
The Processor will Process Personal Data only on the documented instructions of the Controller. The Principal Agreement (including configuration options selected by the Controller, any statement of work, and reasonable ad-hoc instructions given in the ordinary course of operating the Verus service) constitutes the Controller's documented instructions.
If the Processor is required by applicable law to Process Personal Data otherwise than on the Controller's instructions, the Processor will (unless prohibited from doing so by that law on important grounds of public interest) inform the Controller of that requirement before carrying out the Processing.
If the Processor considers that a Controller instruction infringes the GDPR or other applicable data protection law, the Processor will inform the Controller without undue delay and is entitled to suspend performance of the instruction until it is amended or confirmed.
5. Confidentiality
The Processor will ensure that any person authorised to Process the Personal Data (including the Processor's employees, contractors and Sub-processors) is subject to binding obligations of confidentiality — whether by contract, professional or regulatory duty — and has received appropriate data-protection training.
6. Security of Processing (Article 32)
The Processor will implement and maintain appropriate technical and organisational measures to ensure a level of security appropriate to the risk, taking into account the state of the art, the costs of implementation, and the nature, scope, context and purposes of the Processing, as well as the likelihood and severity of the risks to the rights and freedoms of natural persons.
The technical and organisational measures applied by the Processor as of the Effective Date of this DPA are set out in Annex II. The Processor may update those measures from time to time without the Controller's consent provided the updates maintain or improve the level of protection; the Controller may request an up-to-date statement at any time.
7. Sub-processors
The Controller authorises the Processor to engage the Sub-processors listed in Annex III to this DPA, as published and updated from time to time at https://markst.com/legal/subprocessors, subject to the conditions of this clause.
The Processor will give the Controller prior notice of any intended addition or replacement of Sub-processors, by updating the Sub-processor register and emailing the Controller's designated contact, at least thirty (30) calendar days before the change takes effect, save where a shorter notice period is strictly required by security, legal or force-majeure circumstances (in which case the Processor will explain the shorter window in writing).
The Controller may object in writing to the proposed change on reasonable grounds relating to data protection within the notice period. The Parties will discuss the objection in good faith; if the objection cannot be resolved, the Controller may terminate the affected part of the Principal Agreement without penalty and receive a pro-rata refund of pre-paid fees for the unused period.
The Processor remains fully liable to the Controller for the acts and omissions of its Sub-processors as if they were the Processor's own, and will impose on each Sub-processor data-protection obligations substantially equivalent to those in this DPA by written contract.
8. Data subject requests
The Processor will, to the extent technically possible and taking into account the nature of the Processing, assist the Controller by appropriate technical and organisational measures in fulfilling the Controller's obligation to respond to Data Subject Requests under Chapter III of the GDPR.
If the Processor receives a Data Subject Request directly from a Data Subject and the request relates to Personal Data Processed on behalf of the Controller, the Processor will (i) not respond to the request other than to acknowledge receipt and direct the Data Subject to the Controller, and (ii) notify the Controller without undue delay.
9. Assistance with Controller compliance (Articles 32–36)
The Processor will provide reasonable assistance to the Controller, taking into account the nature of the Processing and the information available to the Processor, in ensuring compliance with the Controller's obligations under Articles 32 to 36 of the GDPR, namely:
- (a) the security of Processing (Article 32), by maintaining the measures set out in Annex II and making up-to-date information about them available on request;
- (b) notifying Personal Data Breaches to the Supervisory Authority (Article 33) and to affected Data Subjects (Article 34) in accordance with clause 10 below;
- (c) conducting Data Protection Impact Assessments (Article 35), by providing reasonable information about the Processing on request; and
- (d) consulting the Supervisory Authority prior to Processing where required (Article 36).
10. Personal Data Breach notification
The Processor will notify the Controller without undue delay and in any event within forty-eight (48) hours of becoming aware of a Personal Data Breach affecting Personal Data Processed on behalf of the Controller. The notification will include, to the extent known at the time of the notification and updated as further information becomes available:
- (a) a description of the nature of the Personal Data Breach, including the categories and approximate number of Data Subjects and records affected;
- (b) the name and contact details of the Processor's Data Protection Lead or other point of contact from whom further information can be obtained;
- (c) a description of the likely consequences of the Personal Data Breach; and
- (d) a description of the measures taken or proposed to be taken by the Processor to address the Personal Data Breach and mitigate its possible adverse effects.
11. International transfers of Personal Data
The Processor will not transfer Personal Data outside the United Kingdom or the European Economic Area without the Controller's prior written consent, unless such transfer is to a country in respect of which the UK or the European Commission has adopted an adequacy decision, or unless the transfer is protected by one of the safeguards listed in Article 46 of the GDPR.
The Parties incorporate by reference into this DPA the EU SCCs (module 2, controller-to-processor) and, where the Controller is a UK-established controller or the Personal Data originates from the United Kingdom, the UK IDTA, in each case as amended or replaced from time to time. Annex I of this DPA serves as Annex I of the SCCs; Annex II of this DPA serves as Annex II of the SCCs; Annex III of this DPA serves as the list of authorised Sub-processors under the SCCs.
The Processor will provide the Controller, on request, with a Transfer Impact Assessment in respect of any Sub-processor located outside the UK/EEA.
12. Return or deletion at end of Processing
On termination or expiry of the Principal Agreement, or at any earlier date on written request of the Controller, the Processor will, at the Controller's written choice, return all Personal Data to the Controller or delete all Personal Data in its possession, together with all existing copies, and certify the deletion in writing on request, except to the extent that applicable law requires storage of the Personal Data.
The Processor may retain Personal Data to the extent required by applicable law or for legitimate back-up or record-keeping purposes, in which case the Personal Data will remain subject to the obligations of confidentiality and security under this DPA for the residual retention period.
13. Audits and demonstration of compliance
The Processor will make available to the Controller all information necessary to demonstrate compliance with this DPA, including by providing (on reasonable written request and subject to reasonable confidentiality protections) copies of relevant policies, the Sub-processor register, incident-response runbooks, pen-test summary reports, and any third-party audit or certification reports then in force.
The Controller may, no more than once in any twelve-month period and on at least thirty (30) days' prior written notice, conduct an audit of the Processor's compliance with this DPA, either itself or through a reputable independent third-party auditor bound by appropriate confidentiality obligations. Audits will be conducted during normal business hours, without unreasonable disruption to the Processor's operations, and will make use of any third-party audit or certification reports already available wherever reasonably possible. The Controller is responsible for its own costs of such audits; the Processor bears its own.
If a Personal Data Breach or a material regulatory concern reasonably requires earlier or more frequent audit activity, the Processor will cooperate in good faith to facilitate the necessary investigation.
14. Liability
Each Party's liability under this DPA is subject to the limitations and exclusions of liability in the Principal Agreement, except to the extent that those limitations or exclusions would be prohibited by applicable law.
Nothing in this DPA limits or excludes either Party's liability for (i) death or personal injury caused by negligence, (ii) fraud or fraudulent misrepresentation, (iii) any liability that cannot be excluded or limited under applicable law, or (iv) a Party's own infringement of Article 82 of the GDPR.
15. General
Precedence. This DPA prevails over any conflicting provision of the Principal Agreement on matters of data protection. In all other respects, the Principal Agreement continues in force unchanged.
Amendments. Any amendment to this DPA must be in writing and signed by both Parties, save that the Processor may update Annex II and Annex III unilaterally in accordance with clauses 6 and 7.
Severability. If any provision of this DPA is held to be invalid, illegal or unenforceable, the remaining provisions continue in full force and effect.
Notices. Notices under this DPA will be sent to the data-protection contacts notified by each Party from time to time. For the Processor, notices may be sent to dpo@markst.com.
Governing law and jurisdiction. This DPA is governed by the laws of England and Wales, and the Parties submit to the exclusive jurisdiction of the courts of England and Wales in respect of any dispute arising out of or in connection with it, without prejudice to any right of a Data Subject or a Supervisory Authority to bring proceedings under applicable law.
Annex I — Description of Processing
This Annex forms part of the DPA and, where applicable, serves as Annex I of the EU SCCs (module 2) and the UK IDTA.
Part A — List of parties
Controller: as identified in the Principal Agreement. Controller's Data Protection contact: as notified in writing to the Processor and updated from time to time.
Processor: MARKST LTD, 45 Albemarle Street, Floor 3, London W1S 4JL, United Kingdom. Company no. 17164595. Processor's Data Protection Lead: dpo@markst.com. General legal contact: legal@markst.com.
Part B — Description of transfer
| Item | Detail |
|---|---|
| Categories of Data Subjects | Authorised users of the Controller's Verus tenant; personnel of portfolio companies and borrowers whose information the Controller uploads or enters; contact persons of the Controller's counterparties. |
| Categories of Personal Data | Professional identifiers (name, work email, job title, organisation); authentication data; usage data (pages viewed, actions taken, valuations run, timestamps, IP address); any Personal Data incidentally contained in deal documents, financial statements or assumption sets uploaded by the Controller. |
| Special categories of Personal Data | None processed intentionally. Any special-category data incidentally present in uploaded content is Processed only on the Controller's documented instructions and is subject to the measures in Annex II. |
| Nature of the Processing | Storage, organisation, structuring, consultation, use, retrieval, combination, restriction, erasure and destruction, in each case in connection with the provision of the Verus private-credit valuation platform under the Principal Agreement. |
| Purpose of the Processing | Performance of the Verus service, including account administration, audit logging, valuation computation, reporting, and (where the Controller has enabled them) optional AI-assisted deal extraction and summarisation features. |
| Frequency of the Processing | Continuous, for the duration of the Principal Agreement. |
| Duration of the Processing | The term of the Principal Agreement plus any post-termination period during which the Processor retains Personal Data under clause 12. |
| Competent Supervisory Authority | United Kingdom Information Commissioner's Office (ICO) where the Controller is established in the UK or where Personal Data originates from the UK; otherwise the lead Supervisory Authority determined under Article 56 of the EU GDPR. |
Annex II — Technical and organisational measures
This Annex forms part of the DPA and, where applicable, serves as Annex II of the EU SCCs. Measures are reviewed at least annually and updated as the Processor's security posture evolves; a current version is always available at https://markst.com/trust, with the disclosures at https://markst.com/legal/bcdr and https://markst.com/legal/data-residency as supporting documents.
1. Encryption and transport security
- TLS 1.3 at the edge (TLS 1.2 accepted as legacy-browser fallback on the public marketing surface); AES-256 at rest for application databases and object storage.
- Separate KMS keys per environment; backup-encryption keys distinct from production keys.
2. Access control
- Role-based access control (RBAC) with least-privilege defaults; separation of duties for administrative actions.
- Multi-factor authentication enforced for all administrative and privileged access.
- Optional SSO (SAML / OIDC) for customer tenants.
- Tenant-scoped data-access middleware enforcing per-organisation access on every query.
- Access reviews at least quarterly; immediate de-provisioning on personnel departure.
3. Logging, monitoring and audit trails
- Audit logging of privileged actions, authentication events, and administrative changes.
- SHA-256 content-addressed version-ids for every deal, assumption set, and valuation run so that historical runs remain verifiably reproducible.
- Structured application logs retained per the retention policy in the Privacy Notice; security-relevant logs retained in accordance with incident-response requirements.
4. Resilience, backup and continuity
- RDS multi-AZ in the primary region with automated backups and point-in-time restore; backups encrypted with distinct KMS keys.
- S3 cross-AZ versioning for object storage.
- Recovery Point Objective (RPO): 1 hour. Recovery Time Objective (RTO): 4 hours. See /legal/bcdr for detail.
- Annual DR drill; restore-from-backup tested at least quarterly.
5. Incident response and breach notification
- Documented incident-response runbook covering detection, triage, containment, eradication, recovery and post-incident review.
- Personal Data Breach notification within 48 hours of becoming aware (clause 10 of this DPA).
- Post-mortem issued within 5 business days for Sev-1 incidents.
6. Sub-processor controls
- Written data-processing agreements with every Sub-processor that Processes Personal Data; obligations substantially equivalent to those in this DPA.
- 30-day advance notice of material Sub-processor changes (clause 7).
- Current register at https://markst.com/legal/subprocessors.
7. Physical security
- Personal Data is Processed on AWS infrastructure (eu-west-2 by default; EU / US available). AWS data centres operate under ISO 27001, SOC 2 Type II, ISO 27017 and ISO 27018 attestations; the Processor relies on AWS for physical-security controls at the data-centre layer.
8. Personnel
- Pre-employment background checks where permitted by law.
- Signed confidentiality and acceptable-use agreements at onboarding.
- Annual data-protection and security-awareness training; on-hire and role-change training for staff with privileged access.
9. Secure software development and change management
- Version-controlled source in Git; pull-request review with required approvals before merge.
- Automated dependency vulnerability scanning on every commit; critical CVEs patched within 7 days.
- Separated development, staging, and production environments.
- Infrastructure-as-code for reproducible rebuilds during DR events.
- Golden-number CI harness blocks merges that perturb canonical valuation output beyond a configurable tolerance.
10. Vulnerability management and penetration testing
- Scheduled annual independent penetration testing (WebApp + API + infrastructure); redacted reports available under NDA.
- Responsible-disclosure programme at https://markst.com/trust#responsible-disclosure with a 48-hour acknowledgement target.
11. Data minimisation and retention
- Retention defaults per the Privacy Notice §6. Controllers may configure tenant-specific retention where the service supports it.
- Deletion of Personal Data on request or on termination in accordance with clause 12.
12. Certifications (roadmap)
- Cyber Essentials Plus — target Q3 2026.
- SOC 2 Type I — observation begins Q3 2026; report Q4 2026.
- SOC 2 Type II — report Q2 2027.
- ISO/IEC 27001 — gap assessment Q4 2026; certification target 2027.
Annex III — Authorised Sub-processors
The Processor maintains an up-to-date list of authorised Sub-processors at https://markst.com/legal/subprocessors. That list is incorporated into this DPA by reference and forms Annex III for the purposes of this DPA and, where applicable, Annex III of the EU SCCs. Material changes are notified to the Controller in accordance with clause 7.
The Processor engages Sub-processors to provide the underlying infrastructure and operational services that support the Verus platform. Each Sub-processor is bound by a written data-processing agreement imposing obligations substantially equivalent to those set out in this DPA. Sub-processors that Process Personal Data outside the UK / EEA are bound by appropriate transfer mechanisms (SCCs, UK IDTA) as described on the Sub-processor register.