Skip to main content
Zemerc
Trust and security

Controls that can be examined, together with claims Zemerc does not make.

Industrial records must remain reliable, traceable and defensible throughout their lifecycle. This page explains the controls Zemerc applications use to protect those records, where control architectures differ between applications, and the claims Zemerc does not make.

7
Control areas
4
Published limits
None
Certifications publicly claimed
What a website enquiry passes through
  1. Identity

    Your authorised identity and role permissions

  2. Tenancy

    Which organisation’s data is in scope

  3. Row-level security

    Enforced at the data layer where applicable, not only through the user interface

  4. The record

    Immutable where required and superseded rather than overwritten

Each controlled change creates an append-only audit entry recording the change as it is committed.

The position

Four points this page establishes first.

  • Controls implemented in the application

    Segregation of duties, immutability and effective dating are implemented as application controls rather than relying solely on procedural instructions.

  • Architecture varies

    Architecture varies by application. Applicable organisation-isolation and deployment controls are confirmed for the product under consideration.

  • Your data remains under your control

    Applications provide governed export where supported, while access, approval and workflow rules are configured to reflect the organisation’s approved governance model.

  • No certifications claimed without supporting evidence

    Zemerc does not claim certifications, service levels, live integrations or AI capabilities unless they have been established and approved for publication.

How security is approached

Three principles governing the approach.

The controls and limitations described below follow from these principles.

  • Controls are implemented in the application, not left only to procedure

    Segregation of duties, immutability and effective dating are implemented as application controls rather than relying solely on working instructions.

  • Records remain traceable throughout their lifecycle

    Approved records are superseded rather than overwritten where the governing workflow requires preservation. Controlled changes retain append-only history to support reconstruction of prior positions.

  • Unverified claims are not presented as established facts

    Where no approved method exists for a figure, the application does not produce that figure and records the reason. The same principle applies to this page: claims are made only where the underlying capability can be demonstrated.

The controls

7 control areas, with limitations stated for each.

Where controls vary between applications, the applicable position is stated for the product concerned.

This website

What applies broadly, what varies and what is confirmed per application.

The controls described for Zemerc applications are distinct from the controls that apply to this public website. Application controls operate under the architecture and agreement for each product; this section addresses the website only.

  • Ordinary browsing does not by itself require users to submit personal data

    The current website states that ordinary browsing does not use analytics, advertising or tag-management technology, and typefaces are served from the Zemerc website. Consent-dependent third-party content is handled separately.

  • One published enquiry route

    Website submissions are validated before processing. Request-size and abuse controls are applied before an enquiry record is accepted.

  • Controls must operate in practice

    If an enquiry cannot be delivered, the website reports the failure and does not present a successful submission state.

Where this varies: The Zemerc website is hosted on Vercel. Details not independently verified by Zemerc are not stated here as established facts.

Where this varies: Online enquiry delivery is not currently active. Use the published contact details to contact Zemerc directly.

Identity and access

Access is governed by authorised identity rather than informal working practice.

Roles, organisation scope and approval authority are assigned to authorised users and enforced by the application.

  • Role-based access

    Users are assigned roles that determine what they may view, change and approve. Administrative actions are governed by explicit permissions.

  • Segregation of duties

    Where segregation of duties is required, authorship and approval are assigned to different authorised users. Draft records do not progress until the required approval has been completed.

  • Authority is explicit

    Where supported, approval limits, delegations and named approvers are maintained as governed configuration records, including signature references associated with management-of-change approvals.

Where this varies: Authentication arrangements are confirmed for the application being adopted.

Data isolation

Data separation is enforced at the applicable data layer.

Several Zemerc applications enforce organisation-level data isolation at the data layer, reducing reliance on application checks alone.

  • Organisation-level data isolation

    Where row-level security is used, organisation data isolation is enforced at database level rather than relying solely on interface filtering.

  • Reference data governed consistently

    Equipment, personnel, organisations and locations are maintained as governed reference data and referenced consistently where required.

  • Boundaries between applications

    Applications are not designed to require direct reads of another product’s internal tables. Where information passes between products, it does so through an explicit governed boundary.

Where this varies: Architecture and organisation-isolation controls differ across the portfolio and are confirmed for each application.

Auditability

Append-only audit history prior controlled changes.

Record history forms part of the governed record and is preserved rather than edited retrospectively where auditability is required.

  • Immutable where it matters

    Readings, approved assessment revisions and audit entries are preserved as immutable records where required. Corrections are made through governed substitution or supersession so the original record remains available.

  • Supersession, not editing

    Approved engineering records are superseded rather than overwritten. Where other records depend on a superseded record, those dependencies are identified for reassessment.

  • Effective dating

    Where calculation methods are effective-dated, historical periods can be reproduced using the method that applied at the relevant time.

Data ownership

Client records remain under client control, including at exit.

Operational data remains under the organisation’s control, supported by governed export where applicable so authorised records can be retrieved in usable form.

  • Governed data export

    Applications provide controlled import, migration and export functions appropriate to their governed record types so authorised data can be moved through defined processes.

  • Client governance rules enforced through configuration

    The organisation defines who may change a record, what constitutes a valid entry and who may approve it. The application enforces those approved rules.

  • Provenance retained

    Migrated records retain their provenance, and the approved cut-over point identifies when the application became the system of record.

Application independence

No application requires another Zemerc application to remain operational.

Application independence can also limit the potential for an issue in one product to create mandatory dependency effects in another.

  • Independently operable applications with separate users, data and release lifecycles

    Each application retains its own controls and release lifecycle. No Zemerc application requires another product in order to remain operable.

  • No shared database

    There is no mandatory portfolio-wide data store. Where information passes between products, it crosses an explicit governed boundary rather than requiring databases to be merged.

  • Independently replaceable without mandatory portfolio-wide change

    Each application is independently operable and can be replaced without requiring changes to other Zemerc applications.

Deployment

Deployment options are agreed for the specific application.

Supported deployment modes vary by application and may include Zemerc-hosted, customer-managed cloud or private-network deployment.

  • Zemerc hosting is optional where alternative deployment modes are supported

    Zemerc-hosted deployment is available for applicable applications and is not a universal condition of use.

  • Deployment within a customer-controlled environment

    Where an application supports deployment within the client network, the client’s existing infrastructure and security controls continue to apply.

  • Confirmed per application

    Deployment options vary by application and are confirmed for the product and engagement under consideration.

Where this varies: Availability, continuity and recovery arrangements are defined in the agreement for the relevant application and deployment. No generic commitment is published here.

What Zemerc does not claim

Four claims this page deliberately does not make.

This page states both the controls Zemerc implements and the claims it does not make, so the boundaries are explicit rather than left to assumption.

  • No unverified certifications

    Zemerc does not claim security or compliance certifications for its applications unless such certification has been independently established and approved for publication.

  • No generic service-level commitments

    This website does not publish generic uptime, availability, response-time or severity commitments. Applicable commitments belong in the agreement for the relevant application and deployment.

  • No unverified live integrations

    Integration catalogues do not by themselves represent validated production integrations. Governed import and export remain the current controlled data-movement mechanisms unless a specific external integration has been configured and tested.

  • No unsupported AI capability claims

    Zemerc does not describe an application as AI-powered unless implemented capability supports that claim. Assistive features are described according to their actual production status.

  • No penetration-testing claim without supporting evidence

    Zemerc does not claim an independent penetration test or security assessment for this website or its applications unless supporting evidence is available and approved for publication. Any future assessment will be described by scope and date.

  • No generic availability or recovery figures

    No generic uptime percentage, recovery-time objective, recovery-point objective or backup-retention period is published. Applicable commitments are defined in the agreement for the specific application and deployment.

  • Public website hosting

    The Zemerc public website is hosted on Vercel. Application deployment is determined separately for each product and engagement.

Reporting a security concern

If you believe you have found a vulnerability

Report the issue through the website contact route, describing what you found and how it can be reproduced. The report will be directed to the team responsible for the relevant application or website service.

Do not test against a live customer deployment, access data without authorisation, or disclose vulnerability details before Zemerc has had a reasonable opportunity to investigate and respond.

  • Zemerc does not currently publish a dedicated vulnerability-disclosure mailbox or bug-bounty programme.
  • No generic response-time or severity commitment is published on this website.
  • Reports about a specific application are addressed in the context of that application’s architecture and deployment.
The rest of this section

Trust and legal

Need a person

A security question about a specific application?

Organisation isolation, access control and deployment are confirmed against the architecture of the application under consideration.

Bring application-specific security questions to a working session.

Questions about organisation isolation, access control or deployment are answered for the specific application and its actual architecture.