OperiQBusiness Software
Sign inBack to website

Privacy, security & data

Clear data boundaries and responsibilities

This page explains the intended privacy and data model for OperiQ, including tenant isolation, customer responsibilities and the information collected through the website.

Draft for pre-launch review · Updated 12 November 2026

Website enquiriesOperiQ acts as controller for contact and demonstration requests.
Merchant recordsThe merchant is generally controller; OperiQ acts as its processor.
Separate workspacesThe platform is designed around an isolated data boundary for each customer organisation.
Overview Tenant isolation Website data Product data Retention Your rights Sub-processors Launch checklist

1. Who is responsible for the data?

For website enquiries, demonstration requests and direct sales conversations, Equipment Zone Limited, company number 15211047, registered office 124 City Road, London, EC1V 2NX, trading as OperiQ, is the data controller. Before publication, complete the remaining contact detail: privacy email to be confirmed.

When a merchant uses OperiQ to store information about its customers, suppliers, staff and transactions, that merchant will generally be the controller of that information and OperiQ will act as its processor under a separate Data Processing Agreement.

2. Tenant isolation and data separation

Proposed contractual clause: OperiQ is designed so that each customer organisation operates within a separate data boundary. Requests and authorised users are associated with a specific organisation, and access controls are intended to prevent one customer from accessing another customer’s records. Production safeguards—including hosting, encryption, backups, monitoring, retention and controlled support access—are documented in the applicable security information and Data Processing Agreement.

How the platform is intended to operate

  • Each merchant is resolved to a specific tenant before business data is accessed.
  • Unknown or inactive tenants are refused rather than falling back to another company.
  • Browser sessions, application storage and workspace identity are scoped to the merchant’s origin.
  • Support access should require merchant authorisation, be time-limited and be recorded.
  • Private demonstrations use separate disposable workspaces containing fictional information.

This describes the application design. Final public claims about encryption, hosting location, backup recovery objectives, certifications and availability must match the production infrastructure after deployment and testing.

3. Website and demonstration enquiries

When someone requests a demonstration or makes a custom-software enquiry, OperiQ collects their name, email address, company and business type. A custom-software enquiry also records the selected development route and the requirement description supplied by that person. If they request a meeting, OperiQ also records the requested date, time and time zone. These details are used to respond to the request, assess product fit, prevent abuse and arrange access or a conversation.

Lawful basis

The proposed basis for responding to a requested demonstration is legitimate interests and, where the request concerns steps before entering a contract, taking steps at the individual’s request. Optional product marketing must remain separate and should rely on a clear opt-in where required.

Marketing choice

Submitting a demonstration request does not automatically enrol someone in general marketing. The optional marketing checkbox is separate and unticked by default. Consent must be as easy to withdraw as it is to give.

4. Data processed in the product

Depending on the merchant’s use, OperiQ may process customer contact details, delivery addresses, quotations, invoices, account balances, payment references, supplier details, staff accounts, audit events and other operational records entered by authorised users.

The merchant decides why this information is used and is responsible for ensuring it has an appropriate lawful basis and gives relevant notices to its own customers, staff and suppliers. OperiQ must process that data only on documented instructions, subject to the service agreement and Data Processing Agreement.

5. Security approach

  • Role-based access and least-privilege permissions.
  • Controlled, expiring and auditable support access.
  • Secure transport and production encryption appropriate to assessed risk.
  • Backups, restoration testing and documented recovery procedures.
  • Security logging, vulnerability management and incident response.
  • Regular testing of tenant boundaries and common web-application risks.

These are required production outcomes, not a certification statement. They must be verified during the deployment and security-review process.

6. Retention, export and deletion

The current technical default keeps website enquiries while sales follow-up is active. After an enquiry is marked won or closed, its contact details and internal notes are automatically erased when it has been inactive for 365 days. A non-identifying record of that erasure is retained for accountability. The period is configurable only within a bounded operational range and remains subject to the pre-launch legal review identified below.

Disposable demo workspaces expire automatically. Contracted merchant data should follow documented retention, export and deletion rules, including any post-termination export period and legally required accounting retention. Before launch, publish exact periods for application logs, backups, support records, expired demos and closed customer accounts.

7. Individual rights

People may have rights to access, correct, erase, restrict or object to processing of their personal data, and to data portability where applicable. Where processing relies on consent, consent can be withdrawn. Individuals may also complain to the UK Information Commissioner’s Office.

Requests concerning data held by a merchant should normally be directed to that merchant as controller. OperiQ will assist the merchant as required by the Data Processing Agreement.

8. Hosting and international transfers

The final notice must identify the production hosting region and any processing outside the UK. Where data is transferred internationally, it must identify the relevant adequacy regulation or contractual safeguards and explain how a copy can be obtained.

9. Cookies and device storage

Strictly necessary cookies or local storage may be used for authentication, security and essential preferences. Non-essential analytics or advertising technologies must not run before any consent required by UK law has been obtained. The production cookie notice should list every technology, provider, purpose and duration.

10. Sub-processors

The production sub-processor register should name every supplier that may process customer data—for example hosting, email delivery, error monitoring, support and backup providers—along with its purpose, processing location and transfer safeguard. No providers are listed here until the deployment architecture is final.

11. Required before launch

  • Confirm the legal entity, controller contact and ICO registration requirements.
  • Complete the data inventory, processing records and lawful-basis assessment.
  • Finalise the customer Data Processing Agreement and service terms.
  • Record production hosting, sub-processors and international transfers.
  • Approve exact retention, deletion, backup and recovery periods.
  • Complete security and tenant-isolation testing.
  • Publish incident, rights-request and support-access procedures.
  • Obtain UK legal review before treating this draft as the final privacy notice.