Layered infrastructure protection across edge, access, and data.
Bohus Global Ltd · Platform Security Measures
Last updated: 4 April 2026
1.1 This page sets out the technical and organisational security measures applied by Bohus Global Ltd (No. 17126389) to protect Customer Data across edge protection, authentication, access control, tenant isolation, object storage, credential management, audit logging, and incident response.
1.2 These measures form part of the Data Processing Addendum and describe the Platform’s security architecture.
2.1 The Platform is deployed behind Cloudflare's global edge network, providing layered protection before traffic reaches the application origin.
2.2 Cloudflare acts as an infrastructure subprocessor for network-layer security, traffic routing, and related edge services.
3.1 Internal and administrative platform surfaces are protected by Cloudflare Access, a Zero-Trust access control gateway.
3.2 Cloudflare Access enforces identity verification before protected administrative requests reach the application layer.
3.3 Sessions established through Cloudflare Access are time-limited, cryptographically signed, and revocable by the platform operator.
4.1 Data in transit is protected using HTTPS/TLS 1.2 or higher.
4.2 Data at rest is protected using provider-managed encryption for Cloudflare R2 object storage and Supabase/Postgres database storage. Backups inherit the applicable storage-layer encryption configuration.
4.3 The Platform is not marketed as end-to-end encrypted or zero-knowledge encrypted unless expressly stated in writing.
5.1 Platform sessions are authenticated, time-limited, and revocable.
5.2 Role-based access controls restrict platform capabilities to the permissions granted to each account type, including standard user, admin, and developer roles.
5.3 Entitlement checks, workspace-capacity controls, and case-level permission gates are enforced by the backend before protected resources are returned.
5.4 Admin and developer accounts are limited to operational and diagnostic functions. Access to a specific customer's case data by a platform operator requires a controlled break-glass action with a stated reason, which is recorded in the audit log.
5.5 Break-glass access is time-limited and logged with the actor identity, stated reason, resource accessed, and timestamp.
6.1 Records within the Platform are associated with the relevant customer account, workspace, or authorised user context.
6.2 Postgres Row-Level Security (RLS) is enforced at the database layer as an additional isolation boundary, separate from and additive to application-layer access controls.
6.3 The Platform is designed to prevent unauthorised cross-workspace or cross-customer access through both application-layer controls and database-layer isolation.
7.1 User-uploaded documents and generated outputs are stored in Cloudflare R2 object storage.
7.2 Storage objects are scoped to the relevant customer account, workspace, or authorised user context and are not exposed to other customers through the Platform.
7.3 Pre-signed URLs used for document access are short-lived and require an authenticated platform session.
8.1 Customer Data is not used to train Bohus Global models or to develop or refine any machine learning system operated by Bohus Global Ltd.
8.2 Where third-party AI providers are used to process Customer Data for a requested Platform function, processing is governed by the applicable provider configuration, data processing terms, and contractual controls. Relevant providers are identified in the Subprocessor Register.
9.1 Production secrets, API keys, and credentials are stored outside the codebase and injected through environment configuration at runtime.
9.2 Secret-scanning controls are used to reduce the risk of accidental credential inclusion in the version-controlled codebase.
9.3 Secrets are not intentionally logged, echoed, or included in application error output.
10.1 Third-party dependencies are tracked and assessed as part of platform maintenance.
10.2 Known vulnerabilities in direct and transitive dependencies are assessed as part of release, maintenance, and security-management activity.
10.3 Security advisories affecting platform dependencies are prioritised according to severity, exploitability, and relevance to the Platform's runtime environment.
11.1 The Platform applies browser-facing security headers to reduce common web application risks.
12.1 The Platform records security and operational events with a timestamp, actor identity where applicable, and outcome.
12.2 Audit log retention is described in the Retention page.
12.3 Audit logs are designed not to be modifiable by the actors whose actions they record.
13.1 Bohus Global Ltd maintains an incident response process covering detection, containment, investigation, remediation, and notification.
13.2 Where a personal data breach is confirmed and notification is required under applicable data protection law, Bohus Global Ltd will notify the affected Controller without undue delay, with a target notification window of 72 hours from confirmation.
13.3 Notifications will include, where available, the nature of the breach, the categories and approximate number of records affected, likely consequences, and the measures taken or proposed to address it.
14.1 The Platform relies on third-party infrastructure providers acting as processors or subprocessors. Current infrastructure providers include:
14.2 A separate Subprocessor Register identifies the infrastructure providers used by the Platform.
15.1 Security measures are maintained as part of the Platform’s operational governance framework.
15.2 The Platform maintains layered security controls appropriate to its architecture, operating model, and customer-data processing activities.
Structured Intelligence Systems. Not legal advice. Not professional representation.