Security

CarrierCompass holds your carrier invoices and tracking data. This page describes how that data is kept separate, how people sign in, and how carrier access is stored.

Your data is yours alone

• Every company’s invoices, shipments, findings and settings are kept apart by the database itself, not only by the application. Each request can read only the rows of the company it is signed in to.
• A carrier account number belongs to exactly one company.

Signing in

• Passwords are stored only as a salted scrypt hash. We cannot see them.
• Two-factor sign-in with an authenticator app. Each company decides which roles must use it, and CarrierCompass staff always do.
• Single sign-on through your identity provider is available, and a company can require it.
• Sign in with Google still asks for your second factor.
• An account locks after repeated wrong passwords, and sign-in attempts are rate-limited per network address.
• Sessions use secure, HTTP-only cookies that expire after 14 days. Session tokens are stored only in hashed form.

Carrier access

• Carrier API secrets are encrypted with AES-256-GCM. The key is held outside the database, and each secret is bound to its company, so it cannot be opened under another.
• A secret is never shown again after it is saved.
• Carrier access is used for tracking and delivery commitments only, which are read-only.
• With Connect UPS, you sign in at ups.com. We never see or store your UPS password.

Staff access

• CarrierCompass support staff can open a company’s workspace to help, and every such access is logged.

Leaving

• When a company leaves, it gets an export of its data. Thirty days later the data is permanently deleted.

Hosting

• The application runs on Vercel and the database on Neon Postgres, in the United States.
• All traffic is encrypted in transit over HTTPS.

Found a security problem? Please tell us through Support, linked at the bottom of every page.