Skip to main content

Security

Separate data for every business, encrypted credentials, and signed webhooks by default

Security controls that are already implemented and enforced, described factually — no certifications are claimed unless verified.

Security capabilities

Separate data for each business

FleetBridge identifies your business from your verified sign-in, never from anything the browser sends, and applies that separation to every data query.

Encrypted integration credentials

Order source and delivery provider credentials are encrypted at rest with a versioned envelope that supports key rotation without breaking existing records.

Multi-factor authentication

TOTP-based MFA is available for accounts and can be required for sensitive roles.

Signed, replay-protected webhooks

Outbound and inbound webhooks are HMAC-SHA256 signed, with rotation support and protection against replayed or out-of-order events.

Durable idempotency

Order creation and background job processing use database-backed idempotency, so retries and at-least-once delivery never duplicate work.

Least-privilege infrastructure

Runtime credentials and network access follow least-privilege scoping, with outbound webhook calls validated against internal and unsafe address ranges.

Authentication model

Short-lived JWT access tokens with rotating refresh tokens, issued and stored through a cookie-based backend-for-frontend — access and refresh tokens are never placed in browser local storage.

FleetBridge does not claim SOC 2, ISO 27001, or any other third-party security certification at this time.

Have a security question before you integrate?