Draft for legal and owner review — not approved for acceptance. This page is a working draft, not a final contract or legal advice. The agreement must not be accepted until the parties, legal roles, processing details, suppliers, transfers, security commitments and other review points below are confirmed.
Data Processing Agreement
Draft cover schedule draft-1 for review. This is not the agreement's standard terms and does not create a contract. The signup flow will link the exact approved agreement during account activation.
Agreement source — standard terms not yet attached
The contract body must be taken from the current UK/EU oneDPA standard template, with any edits limited to approved variable fields. The exact template release and permitted use must be verified and archived before activation can be enabled. Do not accept this schedule on its own.
oneDPA source and product information
Parties and roles — confirmation required
- Customer legal entity: not supplied; each customer must provide its registered name and address.
- Service provider legal entity: ANUASSURE LTD (company number 17535135), 66 Paul Street, London EC2A 4NA.
- Roles: confirm controller/processor or other roles separately for customer care/workforce records and AnuAssure account/security operations.
- Contacts: confirm operational, privacy and breach-notice contacts for both parties.
Processing schedule — draft, requires owner/DPO completion
- Subject matter: provision and support of AnuAssure workforce, compliance, rota, visit and care-coordination software; confirm exact product scope.
- Duration: service term, post-termination return/deletion, backups and legal holds are not yet approved.
- Nature and purpose: confirm the exact operations, permitted purposes and documented-instruction channels.
- Data subjects: expected categories include customer representatives, staff and service users; confirm exact scope.
- Personal data: may include identity/contact, employment/compliance, rota/visit/attendance, care, attachment and optional staff duty-location data. Confirm the categories and minimisation boundaries.
- Special-category data: care data may include health information. Confirm the applicable safeguards and customer responsibilities.
- Security schedule: deployed technical and organisational measures, backups and assurance evidence need verification; source code alone is not evidence of deployment controls or certification.
- Subprocessors and transfers: production suppliers, services, locations, contracts and transfer mechanisms are not verified; attach an approved list and process.
- Assistance, incidents, audit and deletion: insert reviewed response channels, times, limits and end-of-service handling.
Required review before signup acceptance
Confirm the legal parties, roles, schedule facts, production suppliers and transfers; attach the exact standard terms; review liability and service-term precedence; and obtain qualified privacy/legal approval. Until then, account activation remains paused and no DPA acceptance is recorded. A demo workspace is synthetic-only; do not enter real care or staff records there.