Claims Bridge

Security / privacy

Private case information belongs behind a protected account.

Claims Bridge is designed around authenticated access and server-side ownership checks. This page explains the product approach without exposing private infrastructure details.

The account boundary

Security is part of the client journey.

01

Authenticated access

Client claim information is designed to remain behind sign-in rather than a public reference lookup.

02

Ownership boundaries

Account routes resolve the signed-in client and verify ownership before returning claim information.

03

Private correspondence

Messages and notifications are presented inside the account rather than exposed through public pages.

04

Controlled document architecture

Document functionality is designed for private authenticated access; live file storage depends on separate configuration.

05

Data minimisation

Public pages avoid private claim details, storage internals and unnecessary personal information.

Document handling

Designed for private access, clear about availability.

The Document Vault and upload flow are designed to support private, authenticated access. File-storage activation is configuration-dependent, so this public explanation does not claim that every account currently has live document storage.

Next route

See the client route

Understand how secure account access fits into the broader Claims Bridge journey.