ClientBridge

Security and trust

Your business is yours. Your information deserves protection.

ClientBridge handles business and customer information, so security is an operating requirement rather than a marketing badge. We describe implemented practices without claiming certifications not earned.

Private business workspaces
Authenticated access
Protected client files
Accountable administration

1 / Your business is yours

These controls are designed to prevent one business from accessing another business’s customers, documents, reports, invoices, or operating history.

Your workspace is private to your business.

ClientBridge checks that a signed-in user belongs to the active business workspace before allowing access to protected tenant pages. When tenant databases are enabled, workspace records load within that tenant context, while central platform administration remains separate.

  • User accounts matched to the active workspace
  • Workspace records loaded in tenant context
  • Super Admin access separated from tenant routes
  • Protected tenant-only application routes

2 / Your information is protected

We do not claim encryption at rest or a backup certification here because those controls require separate verification and documented operating procedures.

Business information is protected while it moves through ClientBridge.

In production, ClientBridge redirects application traffic to HTTPS. Client-uploaded files are stored as private, and a client file cannot be downloaded or deleted unless the signed-in client matches the file owner.

  • HTTPS enforced for production requests
  • Client uploads stored on private storage
  • Ownership checked before client file access
  • Upload, download, and deletion activity recorded

Identity and permissions

A protected URL is not enough on its own; the request must come from an authenticated account with permission for that action.

Protected work requires a verified identity and the right permissions.

ClientBridge supports Google sign-in and standard authenticated sessions. Roles, policies, and route protection limit access to workspace administration, billing, support tickets, customer portals, and Super Admin operations.

  • Google and standard account sign-in
  • Role-aware protected areas
  • Policies around support records and attachments
  • Separate Super Admin authorization

3 / We take responsibility

Visibility does not prevent every issue, but it gives the platform team a record to investigate, communicate, and improve from.

Monitoring and accountability make important activity visible.

ClientBridge publishes component status, provides administrative diagnostics, records sensitive platform actions, and logs selected client-file activity. Security monitoring is designed to observe failures without exposing internal exception details publicly.

  • Public component-level service status
  • Administrative health diagnostics
  • Audit records for sensitive platform changes
  • Incident and error review tools

Straight answers

Questions people ask before they commit.

Does ClientBridge have SOC 2 or ISO 27001 certification?

ClientBridge does not currently claim SOC 2, ISO 27001, or another formal security certification. We prioritize implementing and maintaining practical controls as the platform develops.

Can other businesses access my information?

Business workspaces are logically separated. ClientBridge matches signed-in users to the active workspace, loads tenant records within that workspace context when tenancy is enabled, and checks ownership before protected client-file access.

How do I report a security concern?

Contact the team through the Support page and identify the request as security-related. Do not include passwords, credentials, or customer data in the first message.

Where can I review your privacy practices?

The Privacy Policy explains how ClientBridge collects, processes, stores, and handles personal and business information. It is linked from every public page footer.

Continue exploring

Contact ClientBridge support