← Back to your workspace
PROPOSED SCHEDULE · RMW-DPA-2026-11-18

Customer data-processing agreement

Prepared for approval before paid launch

This proposed schedule describes the intended responsibilities between the customer company and Hunter Construction Ltd. It is not a claim that the hosting contract, transfer assessment or deletion process has already been verified. The launch review identifies the remaining evidence.

1. Roles, duration and instructions

The customer determines why and how its workforce, client and project information is used and acts as controller, or as an authorised processor for its own client where applicable. Hunter Construction Ltd, trading as Run My Works, processes that information to provide the configured workspace and acts as processor or subprocessor for that purpose.

Processing lasts for the service and the agreed return/deletion period. Documented instructions are the agreed contract, the customer's authorised configuration and actions in the app, and verified written support instructions. The operator will process only on those instructions unless law requires otherwise, and will inform the customer of such a requirement where permitted. It will tell the customer if an instruction appears to infringe applicable data-protection law.

2. Processing particulars

The purpose is to store, organise, display and exchange authorised construction records; manage access; record customer decisions; and deliver associated transactional notices. Operations include collection, storage, retrieval, authorised sharing, export, correction and agreed deletion.

People covered include company administrators, employees, contractors, site visitors, client contacts and invited customer representatives. Data may include names, contact details, roles, work assignments, time records, project communications, signatures, site photographs, plans, training and leave records, and location points deliberately submitted through supported features.

Incident or employment records may contain health information. The customer must identify the relevant lawful basis and additional condition, minimise the information and restrict access. Unnecessary medical details, identity documents and sensitive information must not be included in unrestricted notes, customer updates or email notifications. Equipment tracking must be authorised for the relevant company assets and vehicles and handled under the customer's workforce notice; it must not be used covertly to track a person.

3. Confidentiality and access

The operator will limit access to authorised personnel who need it for service or support and are bound by confidentiality. The customer controls membership, assignments, permissions and customer invitations. Individual sign-in is required; the customer must promptly remove access when it is no longer needed.

The implemented service separates company records and checks membership, role and job access. Sensitive categories have additional restrictions. Customer spaces and shared handovers expose records deliberately published to that project. The operator must maintain a record of support access and keep service credentials out of customer-facing pages.

4. Security measures

The proposed security schedule includes encrypted network transport, protected sessions, email verification, role and company access checks, least-privilege provider credentials, input and file validation, version and retry controls, audit records and review of material software changes. Payment access is granted from verified provider evidence. A browser redirect cannot by itself grant paid access.

Offline use requires a trusted-device choice. Prepared copies are bounded, expire after seven days and are revalidated before syncing; sign-out and a verified account change clear local records. Device access remains the customer's responsibility. Offline storage is not an encrypted vault or a substitute for server backup, and access revocation cannot instantly erase a disconnected device or an exported file.

These are descriptions of service controls, not an independent certification, an uptime guarantee or an assurance that every possible attack is prevented. The approved security schedule must include the actual hosting, backup and incident-response arrangements.

5. Subprocessors and transfers

The approved agreement would give general written authority for the disclosed subprocessors necessary to provide the service, with advance notice of additions or replacements and an opportunity to raise a reasonable data-protection objection. The operator would require equivalent data-protection obligations and remain responsible for its subprocessors' performance of those obligations.

The provider register must identify the managed hosting provider and underlying storage, Resend for transactional email, and any further service processing customer workspace data. Stripe and KashFlow/IRIS also process billing information under their applicable roles and agreements. External display fonts and map providers must be disclosed where used.

International access or transfers require an applicable lawful mechanism and any necessary assessment and supplementary measures. No UK-only or EU-only hosting promise is made. A generic supplier DPA or the availability of an EU region does not prove the arrangement for this specific deployment.

6. Requests, incidents and regulatory assistance

The operator will notify the customer of requests relating to customer-controlled records and assist, taking account of the nature of processing, with access, correction, erasure, restriction and portability. It will not decide employment-record requests on the customer's behalf unless instructed or legally required.

The operator will notify the customer without undue delay after becoming aware of a personal-data breach affecting its records, provide available information in stages and assist with investigation and required notifications. The customer remains responsible for deciding its notifications to individuals or the regulator. The parties will cooperate with relevant impact assessments and consultation obligations.

7. Return, deletion and retained records

On verified instruction at the end of service, the operator will return or delete customer-controlled personal data, including copies, unless law requires retention. Export format, collection window, active-data deletion and backup expiry must be agreed and supported by the actual platform before paid activation. Retained legal or financial records must be separated, restricted and used only for their retained purpose.

The customer must remove offline copies and exports from its own devices and recipients when appropriate. Removing a staff member from a workspace is an access change and does not erase their historical work records.

8. Evidence and audits

The operator will make information reasonably necessary to demonstrate these obligations available and cooperate with proportionate audits or inspections. Existing reports may be used where sufficient; confidentiality, security and other customers' information must be protected. An audit arrangement cannot remove a right required by applicable law.

9. Operator's separate records

For its own account administration, service security, support, invoicing and legal obligations, the operator may act as an independent controller. The privacy notice must set out its purposes, lawful bases, recipients, retention criteria and rights. This schedule does not replace the customer's workforce or client privacy notices.

References used in preparing this schedule

ICO guidance on controller–processor contracts · ICO international-transfer guidance · Resend DPA · Resend retention and GDPR information. Reviewed for this proposal on 18 November 2026. Supplier documents still need to be matched to the actual accounts and contract.