11 November 2026 / additive edition
Private organisation records
The existing Holdwright privacy notice continues. This page explains the additional corrective-action records and access model.
Records retained
We retain account and organisation identity, source finding references, supplied classifications, containment/correction, human investigation, exact adopted policy and plan versions, assigned owners and dates, actual implementation, later human review decisions, closure/reopen snapshots and actor/time histories. Supplied original files retain names, hashes, observation dates, provenance and coverage limits.
Records and file payloads are encrypted on the server with the application’s retained encryption secret. This is not end-to-end encryption: authorised operators can decrypt records. Case IDs, ownership, version numbers, timestamps, file sizes, account lookup keys and existing billing/delivery metadata support service operation.
People and isolation
Sign in and recover access through a matching-email, single-use link. The owner invites named colleagues and can revoke access. Every member can read the organisation’s cases and evidence. These organisation workspaces are separate tenants; they do not provide client-by-client partitions inside one organisation. Advisers should join separately owned client organisations where that separation is required.
Public sample content is fictional. The local working demo is isolated from production and excluded from the production package. No customer/supplier contact list or third-party records are imported.
Copies, exports and recovery
Exports identify exact stored versions. A selected ZIP includes only selected permitted originals, alongside its manifest and actual PDF/CSV report. Original files can also be downloaded by authorised organisation members. Downloaded copies are outside the app’s revocation controls.
The release supplies consistent private database/configuration backups and a restoration check. Its existing scheduled maintenance can create daily snapshots after installation. Host-specific backup operation, off-host copies and geography require operator verification; this page makes no UK-only processing or backup-location guarantee.
Immutable record history remains until a deliberate authenticated whole-workspace erasure/retention process is completed. Contact [email protected] for an access or erasure request. Independent source copies and lawful retention remain the organisation’s responsibility.
CAPA terms and allowances · Return to workspace
Connected QMS records and private backups
Process scope, exact external document/calibration references, audit observations, reviewed change plans, named training evidence and frozen management reviews are retained with encrypted originals and immutable versions. All active organisation staff can read these records; named assignment and server roles restrict decisions. Source links do not share source-system permissions or fetch draft bytes. QMS/CAPA history remains after subscription lapse; the original material-workspace erase does not delete it. Contact support for an erasure request. Private daily backups retain the latest 30 recognised snapshots by default; provider-hosted backups have their own retention. These local private copies are not an off-host recovery guarantee. Verified consent and billing obligations remain separate.