Built for procurement questions.

This page summarises the technical and operational controls used by Article 50 Hub. Runtime legal operator details, hosting region and subprocessors are published from configuration on the Privacy Policy and DPA pages.

Access and authentication

• Email verification for new accounts in production
• bcrypt password hashing and password reset flows
• Optional TOTP MFA with one-time recovery codes
• HttpOnly session cookies with SameSite controls
• Role-based access for owners, admins, reviewers and viewers

Application security

• Helmet security headers and Content Security Policy
• Rate limiting on authentication and public endpoints
• Origin checks for browser mutations
• Upload allowlists, size limits and file-signature validation
• Required ClamAV scanning and readiness verification in production
• Tenant relationship validation on systems, assets and evidence

Integrity and evidence

• Cryptographically chained audit events per organisation
• Immutable numbered Evidence Packs with per-file SHA-256 manifests
• HMAC-signed backups and integrity-checked restore
• Versioned disclosure templates and regulatory rule snapshots

AI assistance controls

• AI Copilot is disabled by default and uses server-side API keys
• Only records explicitly selected for the chosen workflow enter model context
• Structured outputs are validated against server-owned schemas
• Regulatory references map back to the official source register
• AI drafts require item-level confirmation before governed writes; publication approval and historical Evidence Packs remain deterministic
• Per-item Accept, Edit or Reject decisions and output hashes are audited

Hosting and privacy posture

• Production requires HTTPS APP_URL and fail-closed secrets
• Configurable hosting region and subprocessor register
• Organisation data export and deletion with password confirmation
• First-party product analytics only — no advertising pixels by default
• Customer content is not used to train foundation models

Operational notes

The default deployment is a single SQLite instance suitable for controlled production. Horizontal scaling requires a managed PostgreSQL migration. Target availability for paid service is 99.5%, excluding planned maintenance and events outside reasonable control.