Where your data lives
SwiftTMS runs on Google Cloud infrastructure in the United States. Your loads, customers and carriers are kept in a PostgreSQL database. Uploaded documents such as rate confirmations, BOLs and PODs are kept in private cloud storage and open only for signed-in users who have access to that load.
Encryption
Every connection to SwiftTMS uses HTTPS. Credentials you save for integrations (EDI, accounting, ELD and similar) are encrypted separately for each company with AES-256 and are never shown again in full after you save them.
Passwords and sign-in
Passwords are stored only as Argon2 hashes, so nobody — including us — can read them. Password sign-ins are protected by a one-time code sent by email by default, and repeated failed attempts are rate-limited.
Each company sees only its own data
Every company on SwiftTMS is separate. Inside a company, access follows roles: an office sees its own customers, and an agent sees what their role allows. Owners and admins control who has access and can suspend an account at any time.
Backups
The database is backed up every day to separate private storage, and every backup is automatically restored as a test before it counts. Backups are kept for 12 months.
Audit trail and deletions
Important changes are recorded with who made them and when. Deleted loads and records go to a Recycle Bin with a full copy first, so they can be restored.
AI features
AI in SwiftTMS suggests; a person approves. We do not use your data to train AI models, and our AI provider's commercial terms do not allow training on customer content. AI features are an optional module.