Skip to content
Trust & security The data architecture

Evidence,
built to be believed.

Every reading is hashed with SHA-256 the moment it arrives. Every treatment is GPS-stamped and sealed into the chain. The data sits in AWS London. None of it can be edited after the fact, including by us.

How the chain works

Three steps. One signed record.

The chain of custody is not blockchain hype — it's a sequence of cryptographic hashes that makes after-the-fact editing detectable.

01

Read & sign

Each sensor reading arrives at the platform with a timestamp and source ID. The platform writes a deterministic input string and computes its SHA-256 fingerprint — a 64-character hex digest unique to that input.

sha256(site+ts+payload) → a9f4…c4d8
02

Append

The new fingerprint is appended to the previous block's fingerprint and hashed again, producing the next link. Any retroactive change to a previous block invalidates every block after it. Tampering becomes visible by definition.

sha256(prev_hash+new_hash) → 1b2e…8e0c
03

Export & verify

On audit, the chain exports as a portable record. Any auditor with a SHA-256 implementation can replay the inputs and verify each fingerprint independently. We do not need to be in the room.

verify(chain) → all blocks valid
Architecture

Data resident in UK. End-to-end.

No US-resident processors in the path. No third-party SaaS storing your treatment record. Where the data sits and how it's protected.

Data residency

All client data — readings, treatment records, compliance packs — resides in AWS London (eu-west-2). DSPT v14-aligned. No replication outside the UK without your written consent.

Regioneu-west-2 · London
DSPTv14 alignment
UK GDPRCompliant · DPA registered

Encryption

AES-128 over LoRaWAN from sensor to gateway. TLS 1.3 from gateway to platform. Hashed-at-rest for treatment records. Encryption keys rotate quarterly.

In transit · radioAES-128 · LoRaWAN
In transit · webTLS 1.3
At restSHA-256 · KMS

Access & audit

SSO via SAML 2.0 or OIDC. Role-based access (FM, operator, technician, auditor). Every human action in the platform is logged into the same chain as sensor data.

AuthSSO · SAML 2.0 / OIDC
Roles4 default · custom available
Audit logHashed · append-only

Data ownership

Your data, your export. Full portable export available within fourteen days of request. We retain a processing licence only while the contract is active — terminate, and the licence ends.

OwnershipClient retains
Export formatCSV · JSON · PDF
TerminationWithin 14 days
Certification roadmap

Stated transparently.

We list what we hold today, what's in progress, and what's a target. No "ISO-aligned" hand-waving.

Live
Cyber Essentials

UK government baseline. Annual renewal.

In progress
Cyber Essentials Plus

Independent technical audit. Q3 2026 target.

In progress
SOC 2 Type I

Trust services controls — 2026.

Target
ISO/IEC 27001

Information security management system. 2027.

Incident response

If something goes wrong.

Our commitment to you, written down. The contract carries the same wording.

Notification window

If we believe a security incident affects your data, we will notify your registered contacts within 24 hours of confirmation, with a written summary inside 72 hours.

Coordinated disclosure

Independent security researchers can report vulnerabilities to security@greentech.co.uk. Responsible disclosure window: 90 days.

Sub-processors

List of sub-processors (AWS, ThingsBoard, Make.com, GoCardless) is published in the security pack and updated within 14 days of any change.

Penetration testing

Annual third-party pen test against the platform and sensor-to-platform path. Summary results sharable under NDA at the contract stage.

Note Certification statuses listed above are accurate as of the page's last review date. The platform does not currently market itself as "ISO 27001 certified" or "SOC 2 audited" — those are roadmap items. We will list them as Live only once the certification has been issued and is verifiable.

Trust is verifiable. Or it isn't trust.

Book a 30-minute security brief. We'll walk through the architecture, the certification roadmap, and the data-processing terms with your security or DPO function.