Data Processing Agreement

Parties and acceptance

This agreement sets out how Dentavector handles patient and staff data on behalf of a dental practice. It is version 1.4, dated 15 November 2026, and replaces version 1.3. It takes effect for a practice when that practice accepts it.

It is made between Dental Performance Analytics Limited, trading as Dentavector, a company registered in England and Wales under number 17467092, whose registered office is 24a Watling Street, Llanrwst, Conwy LL26 0LS, registered with the Information Commissioner's Office under number ZC257563 ("Dentavector", "we", "us"), and the dental practice named at acceptance ("the Practice", "you").

It applies whenever we process personal data for the Practice through the Dentavector service, during the free trial and afterwards, until that data is deleted under clause 10. It sits alongside the Dentavector terms ("the Terms"). If the two conflict on anything to do with personal data, this agreement prevails.

How it is accepted. A person with authority to bind the Practice accepts it, by signing this document, by confirming acceptance by email, or by accepting it on the agreement page of the Dentavector app. A practice accepts it before its Dentally API key is saved, and we read nothing from that practice's Dentally account before acceptance.

Several practices can accept together. One person with authority to bind each of them may accept this agreement and the Terms in a single confirmation that names each practice. That acceptance is recorded separately for each practice named.

We keep a record of each acceptance: the Practice's legal name, the name, email address, phone number and role of the person accepting, the date and time (UTC), the version number, a fingerprint of the exact text accepted, and, for acceptance in the app, the network address used. The Practice receives a copy of the text it accepted.

1. Roles and scope

1.1 The Practice is the controller of the personal data described in Annex 1 ("Practice Data"). Dentavector is its processor. "Data Protection Law" means the UK GDPR, the Data Protection Act 2018 and the Privacy and Electronic Communications Regulations 2003.

1.2 We process Practice Data only to provide the service and, as clause 2A sets out, to improve it. Providing the service means reading the Practice's data from Dentally, calculating its NHS Wales contract figures, showing them to the Practice's authorised users and, where they are in use for the Practice under clause 2C.1, the AI features in clause 2C: suggesting the Practice's setup and answering its users' questions. Annex 1 sets out the subject matter, duration, nature and purpose of the processing, the types of personal data and the people it is about.

1.3 The Practice is responsible for having a lawful basis to let us process Practice Data, for telling its patients and staff how their data is used, for the Dentally API key it gives us, and for deciding which of its staff have access to Dentavector.

1.4 Dentally is the Practice's own supplier. We read from it on the Practice's instruction, using the Practice's key. Dentally is not our sub-processor, and this agreement does not cover what Dentally does.

2. Instructions

2.1 We process Practice Data only on the Practice's documented instructions. Those instructions are this agreement, the Terms, the way the Practice configures the service (its settings, mappings and users), and anything further the Practice tells us in writing. Email is enough.

2.2 If the law requires us to process Practice Data in any other way, we will tell the Practice before we do so, unless the law forbids it.

2.3 If we believe an instruction breaks Data Protection Law, we will tell the Practice promptly.

2.4 We will not:

2.5 Records about the running of the service itself, such as sync timings and error counts, contain no personal data and are ours to keep and use to operate and improve the service.

2A. Improving the service

2A.1 In this clause:

2A.2 The Practice instructs us, in addition to providing the service, to:

2A.3 When we act under clause 2A.2:

2A.4 De-identified data is deleted with the rest of Practice Data under clause 10. Aggregate statistics, and models that have passed the check in clause 2A.3, contain no personal data and are ours to keep.

2A.5 The Practice may withdraw the instruction in clause 2A.2 at any time, by email. Within 30 days we then stop using its data for that purpose and delete its de-identified data. Aggregate statistics and models made before then are not affected. Withdrawing does not change the service or its price.

2B. How the service is used

2B.1 The service records how the Practice's users use it. These records may include when they sign in, the pages and features they open, what they click, how often and for how long, and the type of device and browser. It does not record what users type or make recordings of their screens.

2B.2 We use these records for the Practice, as its processor: to support its users, and to show its administrators how the service is used.

2B.3 We also use them for our own purpose: to understand how Dentavector is used and to improve it. For that purpose we are a controller, not a processor. Our privacy notice explains this use to the Practice's users, and each user may object to it by writing to us. We use these records in aggregate wherever we can, and never to judge or report on any person's work.

2B.4 Records that identify a user are kept for 12 months.

2B.5 The Practice tells its users that the service records how it is used.

2C. AI features

2C.1 The service includes two optional features that use an AI model running on Amazon Bedrock (Annex 3):

Setup suggestions are on for a practice that accepts this version before it first connects to Dentally. An administrator may turn them off at any time, and the Practice then sets up the service itself. For any other practice, setup suggestions are used only if an administrator turns them on. The Assistant is used only if an administrator turns it on, and an administrator may turn it off at any time. A practice that accepted an earlier version of this agreement cannot use either feature until it has accepted this version and the 30 days' notice under clause 5.2 has ended.

2C.2 For setup suggestions, we send the model only:

2C.3 For the Assistant, we send the model only:

2C.4 For either feature, we do not send Dentally patient identifiers, dates of birth, clinicians' names or any record about an individual patient, and we never send one practice's data, settings or mappings in a request made for another practice.

2C.5 Treatment names and questions are text written by people. Users are told not to type patient details into the Assistant. We check all such text before sending it and stop what looks like a date of birth, an NHS number or a name. This check cannot catch everything. Anything it misses is sent to the model as written, is processed under this agreement and is handled as clause 2C.6 sets out.

2C.6 Except for the record of setup suggestions in clause 2C.7, we do not store the text of requests to the model or of its answers. For the Assistant, we keep only the date and time of each question, the user who asked it and the part of the service used, under clause 2B.4. If the Assistant reads patient-level data to answer a question, that reading is logged under clause 9.2 in the name of the user who asked.

2C.7 A setup suggestion is a proposal. It takes effect only when an administrator of the Practice confirms the setup, and the service shows which suggestions were less certain. Confirmed settings and mappings are the Practice's instructions under clause 2.1. For each suggestion we keep what was suggested, the figures it was based on, how certain it was, the model used, and what the administrator confirmed or changed. The Practice can see and undo any of them.

2C.8 We use Amazon Bedrock on these terms:

2C.9 AWS may run automated checks on requests and answers to detect abuse of its service. Its terms allow it to store and review images that its checks flag as apparent child sexual abuse material. We do not send images to the model.

3. Confidentiality

3.1 Only people who need access to provide or improve the service may access Practice Data. At the date of this version, that is the two directors of Dentavector. Each is bound by a written duty of confidentiality that continues after they leave.

3.2 We look at identifiable Practice Data only to support the Practice, to fix a fault, or because the law requires it.

3.3 If anyone else is given access, they will be bound by the same duty before they get it, and the Practice will be told.

4. Security

4.1 We keep Practice Data secure with appropriate technical and organisational measures, as Article 32 UK GDPR requires. Annex 2 describes the measures in place at the date of this version.

4.2 We may change those measures as the service develops, but never in a way that lowers the overall level of protection.

4.3 The Practice keeps its own Dentavector accounts secure: it chooses who has access, keeps passwords private and removes a person's access when they leave.

5. Sub-processors

5.1 The Practice authorises us to use the sub-processors listed in Annex 3.

5.2 Before we add or replace a sub-processor, we will email the Practice at least 30 days in advance. The Practice may object on reasonable data protection grounds. If we cannot resolve the objection, the Practice may end the service, and its data will be deleted under clause 10, with nothing to pay for the notice period, and we refund the unused part of any month or year already paid.

5.3 Each sub-processor is bound by a written contract that protects Practice Data to the standard of this agreement. We remain responsible to the Practice for what our sub-processors do.

6. Where the data is, and transfers outside the UK

6.1 Practice Data, including its backups and de-identified data, is stored and processed on servers in London, United Kingdom. Requests to the model behind the AI features in clause 2C are processed in the same London Region.

6.2 Our directors may access Practice Data remotely from the United Kingdom and from Portugal, in the European Economic Area. UK law treats the EEA as giving adequate protection. The data itself is stored on the UK servers.

6.3 Our email runs on Google Workspace, which may store messages outside the United Kingdom. We ask the Practice not to send patient data by email. If patient data reaches us by email, we delete it from email once the matter it relates to is dealt with.

6.4 We will not transfer Practice Data outside the United Kingdom in any other way without the Practice's prior written instruction.

7. Helping the Practice

7.1 If a patient or anyone else asks us directly to exercise their data protection rights over Practice Data, we will pass the request to the Practice within 5 working days and will not answer it ourselves.

7.2 We will help the Practice answer such requests, for example by exporting the records Dentavector holds about a patient. Most requests are best answered from Dentally, which holds the original records.

7.3 Taking into account what we know about the processing, we will give the Practice reasonable help with its security obligations, data protection impact assessments and any consultation with the Information Commissioner's Office. This help is free during the trial.

8. Personal data breaches

8.1 We will tell the Practice about any personal data breach affecting Practice Data without undue delay, and in any case within 48 hours of becoming aware of it, by email and by phone to the contact given at acceptance.

8.2 We will tell the Practice what happened, which data and roughly how many patients and staff are affected, the likely consequences, and what we have done and will do about it. If we do not know everything at first, we will send what we know and follow up as we learn more.

8.3 We will help the Practice notify the Information Commissioner's Office, within its 72-hour deadline, and the people affected. We will not notify them on the Practice's behalf unless the Practice asks us to or the law requires it.

9. Information and audits

9.1 On request, we will give the Practice the information it reasonably needs to show that this agreement is being met, including the current sub-processor list and a description of our security measures.

9.2 A Practice administrator can see, in the service, a log of who opened patient-level records. The log is kept for 12 months.

9.3 The Practice, or an auditor it appoints who is bound by confidentiality, may audit our compliance with this agreement once in any 12 months, and also after a personal data breach or at the request of the Information Commissioner's Office. The Practice gives us 30 days' notice and pays its own costs. An audit never gives access to another practice's data. We may first offer written answers, and the Practice may accept them instead of an audit.

10. End of service: return and deletion

10.1 The service ends when the Practice cancels, when either side ends it under the Terms, or when we stop providing it.

10.2 If we can no longer read from Dentally, for example because the Dentally API we use is withdrawn, we stop reading at once and tell the Practice. What happens to the service then is set out in the Terms.

10.3 Practice Data is a copy: the originals stay in the Practice's Dentally account, untouched. If the Practice asks within 30 days of the end, we will first export its settings, mappings and figures as CSV files.

10.4 Within 30 days of the end, we delete the Practice's database, its de-identified data, its Dentally API key and its user accounts. Backups containing Practice Data expire within a further 35 days. On request, we confirm the deletion in writing.

10.5 We keep the record of the Practice's acceptance of this agreement for 6 years after the end, as evidence of what was agreed. It contains no patient data.

10.6 Aggregate statistics and models under clause 2A.4 are not deleted.

11. General

11.1 This agreement runs from acceptance until the deletion under clause 10 is complete.

11.2 Each party's liability under this agreement is as under the general law, subject to any limit agreed in the Terms, and only to the extent the law allows such a limit.

11.3 We may publish a new version of this agreement, with at least 30 days' notice by email. A change that lowers the protection of Practice Data applies only if the Practice accepts it. If the Practice does not, it may end the service, and clause 10 applies. A change required by law may take effect sooner.

11.4 A practice that accepted an earlier version is asked to accept this version in the app. Until it does, the version it accepted continues to apply to it. If that is version 1.0, clauses 2A and 2B.3 do not apply.

11.5 Notices go by email: to support@dentavector.co.uk for Dentavector, and to the contact given at acceptance for the Practice. Each party keeps its contact up to date.

11.6 This agreement is governed by the law of England and Wales, and the courts of England and Wales have exclusive jurisdiction.

Annex 1 — Details of the processing

Subject matter Analysis of the Practice's NHS Wales General Dental Services contract
Duration From acceptance until deletion under clause 10
Nature Reading from Dentally through its API (read-only); where the Practice sets them up in Dentally, receiving Dentally's notices that an appointment has changed (webhooks); receiving and at once discarding the fields listed at the end of this Annex, storing, organising, calculating, displaying, de-identifying, aggregating, backing up and deleting; where they are in use for the Practice under clause 2C.1, sending the data in clauses 2C.2 and 2C.3 to a model, to suggest its setup or to answer its users' questions
Purpose Showing the Practice its contract position: value per care package, contract value per hour per clinician, forecast of contract delivery, under-claiming checks, and recall and booking lists; setting up the service for the Practice, including setup suggestions where they are in use; supporting the Practice's users, including seeing when each account last signed in and which parts of the service it uses; where the Practice has turned it on, answering its users' questions through the Assistant; and improving the service, as clause 2A sets out
Frequency One full read when the Practice connects, then frequent updates and a weekly full check, for as long as the service runs
People Personal data
Patients Dentally patient identifier; date of birth; appointments (date, time, length, clinician, status, and the reason from Dentally's fixed list); treatment plans and items (treatment codes, teeth, dates, values, NHS or private); NHS claims (status, value, codes, dates, the NHS patient category and the flags recorded on the claim); invoices and payment plans (amounts and dates); recall dates, interval and method; assigned dentist; consent to share accounts; account and payment plan references; active or archived status
Clinicians and other practice staff in Dentally Name; Dentally identifier; GDC number; rota and sessions; chair time; the figures the service calculates for each clinician
The Practice's Dentavector users Name; email address; role; password (stored only as a hash); sign-in times; record of patient-level pages opened; how they use the service, as clause 2B.1 describes; if the Assistant is on, the text of their questions (sent to the model and not stored) and the record in clause 2C.6; for setup suggestions, which administrator confirmed or changed each one (clause 2C.7)

Treatment and claim data about patients is health data, a special category under Article 9 UK GDPR.

Fields received and discarded. Dentally's API returns whole records and does not let us choose the fields. Some records therefore include fields we have no use for: patients' names, contact details (email, phone or address, including postcode, town and county), NHS number, ethnicity, medical alerts, free-text notes, the comments recorded on NHS claims and the reason a patient's record was archived. Ethnicity is special category data under Article 9 UK GDPR, and medical alerts and notes may be too. Our service discards these fields as each record arrives. They are held only in memory while the record is processed, and are never stored, displayed, written to our logs or used in any calculation. Receiving them is still processing, and this agreement applies to it. Notices of change also name the member of the Practice's staff who made the change; we discard those details in the same way.

Annex 2 — Security measures

These are the measures in place at the date of this version.

Annex 3 — Sub-processors

Sub-processor What it does for us Where Practice Data involved
Amazon Web Services EMEA SARL Hosts the service, its database and its backups London, United Kingdom All Practice Data
Amazon Web Services EMEA SARL (Amazon Bedrock) Runs the model behind the AI features in clause 2C, only for a practice for which they are in use under clause 2C.1 London, United Kingdom (eu-west-2, within the Region only) The data in clauses 2C.2 and 2C.3
Google (Google Workspace) Email for support and account messages Region not guaranteed; may be outside the UK Names and email addresses of Practice staff; patient data only if the Practice sends it, which we ask it not to

Not sub-processors: Dentally, which is the Practice's own supplier (clause 1.4); Anthropic, which supplies the model that AWS runs on Amazon Bedrock and has no access to requests or answers; Stripe, which takes our payments and handles only the Practice's billing details, which are ours, not Practice Data; GitHub, which holds our source code and no Practice Data; Google Analytics, which runs only on our public website, only with a visitor's consent, and never in the service.