OperiQBusiness Software
Sign inReturn to setup

UK GDPR processor terms

Data Processing Agreement

This draft shows the agreement that would govern OperiQ’s processing of personal data on behalf of a merchant customer.

Prototype version 0.1 · 9 October 2026

Working draft—not a live DPAThe final document must identify the legal parties, production hosting, sub-processors, transfer safeguards, security controls and retention periods, and receive professional legal approval.
CustomerUsually acts as controller and decides why business data is processed.
OperiQActs as processor and follows documented customer instructions.
ScopeOperational records used to provide the contracted OperiQ service.
ScopeInstructionsConfidentialitySecuritySub-processorsIndividual rightsIncidentsReturn & deletionAuditsTransfersProcessing schedule

1. Scope and roles

This DPA forms part of the agreement between the Customer and Equipment Zone Limited, company number 15211047, registered office 124 City Road, London, EC1V 2NX, trading as OperiQ. It applies where OperiQ processes personal data on the Customer’s behalf in providing the service.

The Customer is the controller and OperiQ is the processor unless the parties’ actual activities require a different classification. Each party remains responsible for its own obligations under applicable data-protection law.

2. Documented instructions

OperiQ will process personal data only on documented instructions from the Customer, including the agreement, configured product use and support requests, unless UK law requires otherwise. OperiQ will inform the Customer before legally required processing unless the law prohibits that notice.

If OperiQ reasonably believes an instruction infringes applicable data-protection law, it will notify the Customer and may pause the affected processing while the parties clarify the instruction.

3. Confidentiality and personnel

OperiQ will ensure that people authorised to process Customer personal data are subject to confidentiality obligations and receive access only where necessary for their role.

4. Security measures

OperiQ will implement appropriate technical and organisational measures proportionate to the risks of processing. The final security schedule should include verified controls for:

  • tenant isolation and role-based access;
  • authentication, session security and privileged access;
  • encryption in transit and appropriate encryption at rest;
  • logging, monitoring and incident response;
  • backups, restoration testing and business continuity;
  • vulnerability management, secure development and change control;
  • staff security and controlled support access.

Security descriptions must reflect the deployed service and must not claim certifications or controls that have not been independently verified.

5. Sub-processors

The Customer gives general or specific written authorisation—choose final model for OperiQ to use approved sub-processors. OperiQ will maintain a current list, give advance notice of relevant changes, provide a reasonable objection process and impose equivalent data-protection obligations on each sub-processor.

OperiQ remains responsible for its sub-processors’ performance of those obligations to the extent required by law and the final agreement.

6. Assistance with individual rights

Taking account of the nature of processing, OperiQ will provide reasonable technical and organisational assistance so the Customer can respond to requests for access, correction, erasure, restriction, objection and portability. If OperiQ directly receives a request concerning Customer-controlled data, it will direct the requester to the Customer unless legally required otherwise.

7. Compliance assistance

OperiQ will reasonably assist with security obligations, personal-data-breach assessments, data-protection impact assessments and prior consultations, taking account of the information available to OperiQ and the nature of processing.

8. Personal data breaches

OperiQ will notify the Customer without undue delay after becoming aware of a personal data breach affecting Customer personal data. The notice will provide available information about the nature of the incident, likely consequences, affected records and individuals, mitigation and a contact point. Information may be supplied in phases as the investigation progresses.

The final agreement must state the operational notification channel and any agreed target notification time without promising a deadline the production incident process cannot meet.

9. Return and deletion

At the Customer’s choice and subject to applicable law, OperiQ will return or delete Customer personal data after the service ends and delete remaining copies according to the agreed retention and backup lifecycle. The final schedule must define the export window, active-system deletion period and backup expiry period.

10. Information and audits

OperiQ will make available information reasonably necessary to demonstrate compliance with this DPA and permit proportionate audits or inspections. The final procedure should prioritise current independent reports and written evidence, protect other customers’ confidentiality, require reasonable notice and address costs for exceptional customer-specific audits.

11. International transfers

OperiQ will not make a restricted transfer of Customer personal data unless an applicable UK transfer mechanism and required safeguards are in place. The final DPA and sub-processor list must identify relevant processing locations and safeguards.

Schedule 1 — Details of processing

Subject matter and duration

Provision, support, security and termination of the OperiQ service for the term of the customer agreement and approved retention period.

Nature and purpose

Hosting, organising, retrieving, displaying, calculating, backing up, transmitting and deleting operational records as instructed through use of the service.

Categories of people

Customer users and staff; the Customer’s customers and contacts; supplier contacts; delivery recipients; and other individuals whose information the Customer lawfully enters.

Types of personal data

Names, contact details, delivery and billing addresses, user identifiers, role and access data, transaction records, quotations, invoices, account references, delivery information, support communications and security logs. Payment-card data should be handled by an approved payment provider and not stored by OperiQ unless a separately approved scope says otherwise.

Special-category data

Not intentionally required for ordinary use. The Customer must not enter special-category or criminal-offence data unless expressly agreed with suitable safeguards.

Schedule 2 — Security and sub-processors

Complete before launch: attach the verified technical and organisational measures, approved sub-processor register, hosting regions, transfer mechanisms, incident contacts, deletion timetable and audit contact.

Privacy contact: support@operiqsoftware.com.