Security
Flodock Inc. is a young company. We do not paste fake certifications on the website. Here is what we do with your data, how integrations are secured, and how you can evaluate the connected yard platform safely.
Demo requests, accounts, sandboxes, and careers applications collect the information you submit. We use it to respond, provision sandboxes, evaluate hiring, and improve the product. We do not sell your personal information or contact details to third parties for their marketing.
See Privacy for retention, cookies, service providers, and contact details. See Terms for acceptable use of the site and sandboxes.
Production hosting uses encryption in transit and at rest, role-based access, and authenticated webhooks and API keys for ERP closeout. We document integration security, data handling, and access control during evaluation — ask us for the security brief.
Sandboxes are isolated trial yards for evaluation. Do not load production freight, driver PII, or regulated data you would not put in a test system. We can discuss production hosting, access control, and integration security during a sales walkthrough.
Security or privacy questions: hi@flodock.com
Security posture
Honest status — we do not display certifications we have not earned.
| Topic | Available today | Ask during evaluation |
|---|---|---|
| Encryption in transit | TLS for web and API traffic | Cipher suites, certificate policy |
| Encryption at rest | Production data stores encrypted | Key management details in security brief |
| Role-based access | Site-scoped roles for gate, yard, dock, admin | SSO / IdP integration roadmap |
| Webhook & API auth | Per-environment keys for closeout endpoints | Rotation policy, IP allow lists |
| SOC 2 / ISO | Not claimed on this page | Current audit status in walkthrough |