« Legal & Policies

Data Retention Policy

Last updated:
October 2026

If you or your practice are based in the United States, then the US version of our Terms of Service and the US version of our End User Terms apply to you.

If you or your practice are not in the United States, then the outside USA version of our Terms of Service and outside USA version of our End User Terms apply to you.

1. Introduction

1.1 This policy sets out the policies and procedures of Physitrack PLC, together with its subsidiaries Champion Health Limited and Champion Health Plus (collectively referred to as the "company"), with respect to the retention, archiving and deletion of data, whether in hard copy or digital form, and including personal data and Patient Data processed through the EMR and other company services.

1.2 The company is subject to a range of statutory obligations in relation to the retention of data. On the one hand, the company is obliged to retain some classes of data for a minimum period. On the other hand, it is a fundamental principle of data protection law that personal data should be only retained for so long as required. Moreover, the retention of some classes of data may represent an unnecessary security risk.

For these reasons, the company recognises the importance of formulating clear and specific policies in relation to data retention.

1.3 This policy is to be read with the applicable Terms of Service, End User Terms, Privacy Policy, DPA, BAA and Customer Contract. Mandatory law and the applicable DPA or BAA prevail over conflicting provisions of this policy. A different retention arrangement expressly agreed in the Contract applies only to the extent consistent with those requirements.

2. Definitions

2.1 In this policy:

(a) "appointed person" means the individual primarily responsible for handling data retention, archiving and deletion by the company, being the data protection officer of the company;

(b) "data controller" means the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data;

(c) "data processor" means a natural or legal person, public authority, agency or other body which processes personal data on behalf of the controller;

(d) "data subject" means an identified or identifiable natural person; an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person;

(e) "deletion" means the permanent and irreversible deletion of data from all relevant databases and storage media in the possession or control of the company, including, where necessary, destruction of the relevant storage media. Deletion is completed in accordance with the applicable live-system and backup deletion periods. Archiving, disabling access or pseudonymising information does not, by itself, constitute deletion;

(f) "personal data" means any information relating to a data subject, including personally identifiable information (PII) and identifiable health information protected under applicable law;

(g) "Customer" means the clinic, practitioner or other organisation obtaining services under a contract with the company (the "Contract");

(h) "EMR" means the company's electronic medical record and practice management services;

(i) "Patient Data" means personal data processed on a Customer's behalf about its patients, including information entered, imported or generated through the EMR. Depending on the enabled features, this includes clinical records, intake responses, attachments, appointments, communications, consents, patient billing information, recordings, transcripts, drafts and associated audit information;

(j) "Data Protection Legislation" means the privacy, data protection and health-information laws applicable to the relevant processing, including applicable national, federal, state, provincial and territorial requirements;

(k) "DPA" means the applicable data processing agreement between the company and the Customer;

(l) "BAA" means the applicable business associate agreement governing the company's handling of PHI; and

(m) "PHI" means protected health information, including electronic PHI, as defined under the US Health Insurance Portability and Accountability Act of 1996 and its implementing regulations, as amended ("HIPAA").

3. Data Retention, Archiving and Deletion

3.1 The company must archive and delete data in its possession and/or control in accordance with schedule 1 (Data retention periods), save as set out in this section 3 and subject to clause 1.3.

3.2 Subject to clauses 3.4 and 3.6, and notwithstanding the archiving rules set out in this policy, the company may retain non-archived copies of data to the extent that the data is reasonably required in non-archived form for:

(a) the fulfillment of any legal or contractual obligations of the company; and/or

(b) the establishment, exercise or defence of any legal claims.

3.3 Subject to clauses 3.4 and 3.6, the company must not delete data to the extent that:

(a) the company has a legal obligation to retain the data;

(b) the company has a contractual obligation to retain the data (providing that such contractual obligation is not overridden by any legal obligation to delete the data); and/or

(c) the retention of the data is reasonably required for the establishment, exercise or defence of any legal claims (providing that such requirement is not overridden by any legal obligation to delete the data).

3.4 For Patient Data, the Customer determines the purposes of processing and applicable record-retention requirements. The company acts on the Customer's documented instructions as data processor, business associate, service provider or equivalent role, as applicable. Instructions may be recorded in the Contract, DPA, DRP, or BAA, approved retention settings or other documented directions. The company must inform the Customer if it considers an instruction unlawful and must comply with any obligations that apply directly to it.

3.5 The Customer is responsible for identifying and complying with the retention requirements applicable to its practice and Patient Data in each relevant jurisdiction, including applicable national, federal, state, provincial and territorial laws and rules for children's records, professional recordkeeping, record integrity and pending access requests, complaints or proceedings. Before instructing deletion, the Customer must determine that disposal is lawful. The company's storage periods do not replace those requirements or relieve the company of its own obligations.

3.6 Clauses 3.2 and 3.3 do not authorise the company to retain or use Patient Data for independent business purposes contrary to applicable law, the DPA or the BAA. Where EU or UK data protection law applies, Patient Data must be returned or deleted at the Customer's choice when processing ends, and existing copies deleted unless applicable Union, Member State or UK law requires storage. For PHI, Schedule 1, clause 2.9 applies. Any retention exception must be limited to the necessary records and purpose, documented, protected by restricted access, reviewed and ended when its basis ceases. The Customer must be informed where required and legally permitted.

3.7 Patients should normally direct clinical-record retention, access and deletion requests to their healthcare provider. The company will promptly refer requests received in its processor role to the relevant Customer and assist it as required by law and the DPA or BAA. Direct legal duties of the company continue to apply. Deleting a user login, closing a patient portal account or marking a patient inactive does not by itself authorise deletion of the clinical record.

3.8 Records held by the company for its own account administration, tax, accounting or other lawful independent purposes follow the Privacy Policy and applicable retention schedules. Records containing Patient Data remain subject to the DPA or BAA. Required compliance documentation is retained for its applicable statutory period; this does not establish a corresponding period for all patient clinical records.

4. Default Archiving and Deletion Methods

4.1 Data must be archived by the company using documented storage procedures with access controls and security measures appropriate to the sensitivity of the data, save to the extent that specific archiving methods are provided for in schedule 1 (Data retention periods).

4.2 Data must be deleted by the company using secure erasure or destruction methods appropriate to the relevant storage medium, save to the extent that specific deletion methods are provided for in schedule 1 (Data retention periods). The company must maintain proportionate records of deletion instructions and completion, without retaining unnecessary copies of the deleted Patient Data.

4.3 Pending lawful expiry of backup copies, data awaiting deletion must be put beyond ordinary use and remain protected. If a backup is restored, prior deletion instructions must be reapplied before the affected data is returned to ordinary use. Backup retention must be justified and data deleted as soon as reasonably possible within the applicable schedule; a backup period is not a blanket exception to a legal deletion duty.

4.4 The company must impose applicable retention, return, deletion and continuing-confidentiality obligations on subprocessors and HIPAA subcontractors holding Patient Data on its behalf, and obtain evidence of compliance as required by the DPA, BAA and law. This includes copies held in support systems and by providers of enabled EMR features.

5. Reviewing and Updating this Policy

5.1 The Information Security Manager or its delegate, in consultation with the appointed person, shall be responsible for reviewing and updating this policy on an annual basis.

5.2 This policy must also be reviewed and updated on an ad hoc basis if reasonably necessary to ensure:

(a) the compliance of the company with applicable law, codes of conduct or industry best practice;

(b) the security of data stored and processed by the company; or

(c) the protection of the reputation of the company.

5.3 The following matters must be considered as part of each review of this policy:

(a) changes to the legal and regulatory environment;

(b) changes to any codes of conduct to which the company subscribes;

(c) developments in industry best practice;

(d) any new data collected by the company;

(e) any new data processing activities undertaken by the company, including EMR features, integrations, subprocessors and processing in additional jurisdictions; and

(f) any security incidents affecting the company.

5.4 Material changes to retention periods must be assessed against existing contractual commitments and applicable law, with notice to Customers and an opportunity to make necessary export arrangements where required. Retention or export enquiries may be directed to Physitrack support or dpo@physitrack.com.

Schedule 1 (Data Retention Periods)

1. Introduction

1.1 This schedule 1 sets out the methods to be used by the company when archiving and deleting Customer data (including PII and Patient Data) and the periods during which data must be archived and deleted by the company, subject to clauses 1.3 and 3 of this policy.

2. Customer Data: Retention, Archiving and Deletion

2.1 In this policy, "Customer data" means any Customers and Customers' Patients data including but not limited to customer identity details (PII), customer identity evidence, customer contact details and Patient Data, including data processed through the EMR. Customer data does not include Marketing and Communications Data as is referred to in our Privacy Policy which shall be retained in accordance with Data Protection Legislation and the Privacy & Electronic Communications Regulations as applicable. The distinction in clause 3.8 applies to records retained for the company's own purposes.

2.2 Customer data is stored by the company in the following databases: for each geographical data centre where Physitrack application data is stored, Customer data will be stored in SQL-based database management systems, configured in a high-availability pattern, and in any additional storage used for enabled EMR features, attachments and associated records. This policy applies to all such copies and does not change the hosting or transfer arrangements in the DPA or BAA.

2.3 Customer data will be backed up daily in accordance with the company's documented recovery procedures. Backup copies and archived records remain subject to this policy; creating a backup or archive does not reset a retention period.

2.4 Subject to clauses 1.3 and 3 of this policy and clauses 2.6 to 2.9 of this schedule, Customer data in live systems will usually be deleted 30 days after Contract termination or expiry unless it is required to be retained in accordance with clause 3.3 above. Copies retained on back up storage (used for back up recovery and disaster planning) will be deleted within 12 months post Contract expiration or termination. These are default service-deletion periods, not medical-record retention periods. A lawful earlier deletion instruction or shorter applicable legal or contractual deadline takes priority.

2.5 During an active EMR subscription, clinical records are retained in accordance with the Customer's documented instructions and the applicable Contract, DPA or BAA. They are not routinely deleted solely because a patient is inactive or a record is old. Any automatic retention setting must reflect documented Customer instructions and be communicated before it operates, subject to applicable law.

2.6 Customers must arrange secure export or request return of Patient Data through available functionality or support before Contract termination or expiry, or promptly following notice of termination where advance arrangements are not possible, and complete the transfer before the notified deletion deadline. The company must verify the requesting person's authority and provide a usable copy of the records it is required to return, including retained treatment transcripts, attachments and associated information needed to preserve their meaning and integrity. Before scheduled deletion, the Customer must receive reasonable notice and an opportunity to obtain its records. A timely return request must be fulfilled before the requested records are deleted. The Customer must check that exported copies are complete, usable and accessible, and securely retain them for its applicable recordkeeping period, including after its Contract with the company ends.

2.7 At the end of processing services, the company must, at the Customer's choice, return or delete Patient Data and delete existing copies, subject to any storage required by applicable law and the BAA provisions in clause 2.9. The default schedule in clause 2.4 applies where it forms part of the Customer's documented instructions and no overriding lawful instruction applies. Cancellation, suspension or a payment dispute must not prevent access to, or return of, Patient Data where required by law or the DPA or BAA.

2.8 A Customer's obligation to retain medical records does not automatically require the company to host them after the Contract ends. The company does not undertake to retain Patient Data indefinitely or to provide post-termination storage for the Customer's applicable medical-record retention period. Any continuing storage service must be expressly agreed before deletion and remain subject to the DPA or BAA. The Customer must otherwise arrange lawful retention elsewhere, including on practice closure or transfer. Records that have been permanently deleted cannot be recovered.

2.9 Where HIPAA applies, on termination the company must return or destroy all PHI held on the Customer's behalf, including copies held by subcontractors, where feasible and in accordance with the BAA. If return or destruction is infeasible, the company must document the reason, continue the BAA's protections, and limit further use and disclosure to the purposes making return or destruction infeasible, for as long as the PHI remains. Clause 2.4 does not establish infeasibility or authorise retention contrary to the BAA or HIPAA.

2.10 Transcripts retained or used to inform patient care, including transcripts used by the EMR assistant to inform subsequent treatment, follow the clinical-record retention rules in clause 2.5 and the return and deletion rules in clauses 2.6 to 2.9. They must be included in patient-record exports and made available to support lawful patient-access requests. Such transcripts must not be automatically deleted merely because a summary or final note has been saved. Temporary audio recordings, intermediate AI outputs and other feature data that are not retained or relied on for patient care may have separate, purpose-based retention periods documented in the applicable feature documentation or processing instructions. Those periods must respect applicable recordkeeping, access and preservation requirements. A final note saved in the record follows the clinical-record rules. Retention under this policy does not authorise use of Patient Data or de-identified patient-record data to train AI models.

2.11 Beta, sandbox, demonstration and evaluation environments must not contain real Patient Data unless expressly approved for production clinical use under the applicable terms. Permitted test data and beta-user account information follow those terms and the Privacy Policy. If real Patient Data is entered contrary to the restrictions, it must still be protected and handled under the applicable incident-response and lawful deletion procedures.

Please note that if you are reading a translated version of this policy, the text of the English version of this policy prevails.