Fortis Tech Limited · Private review draft · 15 November 2026
Practice data-processing agreement
Private review draft for personal data handled on a practice’s instructions. Complete the processing and security schedules for the actual service before signing or uploading client files.
Who gives instructions
For the processing described here, the practice determines the purposes and acts as controller. Fortis Tech Limited acts as processor. Where the practice itself acts for another controller, identify that controller’s instructions and authority to appoint Fortis in the order. Fortis handles its own business contacts separately under the applicable privacy notice.
Processing schedule
Subject matter: the agreed practice workspace. Duration: the service term and agreed exit period. Purpose: organise and deliver the practice’s instructed client work. Operations may include collecting, storing, linking, retrieving, sharing selected items, exporting and deleting records. Record which operations and Apps the practice enables.
People and records
The schedule may cover practice staff, clients, directors, beneficial owners and client contacts. Data may include contact and relationship details, deadlines, time records, correspondence, source documents, financial records and AML evidence. Identify any special-category or criminal-offence data, its purpose and safeguards before enabling that processing.
Documented instructions and transfers
Fortis will process data only on documented instructions from the practice, including instructions for international transfers. If law requires other processing, Fortis will inform the practice before processing unless the law prohibits disclosure. Fortis will immediately tell the practice if it considers an instruction contrary to applicable data protection law.
Confidentiality and security measures
Fortis will ensure authorised personnel are bound by confidentiality and will implement appropriate technical and organisational measures under Article 32. Before signature, attach the verified controls for practice isolation, privileged access, encryption, logging, backup restoration and security testing, including responsibility and review frequency.
Sub-processors
Fortis must obtain the practice’s prior written authorisation before appointing a sub-processor. For general authorisation, Fortis will give advance notice of additions or replacements and an opportunity to object before they process data. Fortis will impose equivalent written obligations and remain responsible to the practice for the sub-processor’s performance. The schedule must name each provider, purpose, processing location, transfer mechanism where relevant and notice period.
Requests from individuals
Fortis will promptly pass rights requests concerning practice records to the practice. Taking account of the processing, it will assist through appropriate technical and organisational measures, insofar as possible, with searches, correction, restriction, export or deletion needed for the practice’s response.
Incidents and assistance
Fortis will notify the practice without undue delay after becoming aware of a personal data breach. It will provide the available facts and updates on the records and people affected, likely consequences and containment action. Taking account of the processing and information available, Fortis will assist with security obligations, breach notifications, impact assessments and prior consultation with the regulator. Record both parties’ monitored incident contacts before activation.
Assurance and audit
Fortis will make available information needed to demonstrate compliance and allow and contribute to audits and inspections by the practice or its appointed auditor. The parties will agree practical arrangements that preserve other customers’ confidentiality.
Return, deletion and backups
At the practice’s choice on termination, Fortis will return or delete personal data and delete existing copies unless applicable law requires retention. The exit schedule must specify the export method, deletion and backup expiry periods, how retained copies are protected, and how completion is confirmed.
Schedules requiring sign-off
The parties must complete the processing inventory, security controls, supplier and transfer register, incident contacts and retention and exit schedule against the deployed service. A pilot integration alone does not authorise disclosure to an AI, ledger or identity-check provider. Read the accompanying practice subscription terms.