Subprocessors
Third parties that process personal information for floDock Inc. and floDock Labs LLC to run flodock.com and the floDock Partner, Yard and Go apps.
Each provider processes data only on our instructions. None may use it for their own marketing. We do not sell or rent personal information. See the Privacy Policy and Data Processing Addendum.
Current list
| Subprocessor | What it does for us | Data involved | Location | Applies to |
|---|---|---|---|---|
| Cloudflare | Hosting and delivery of flodock.com (Pages), bot protection on forms (Turnstile), secure tunnel in front of the website API | Website traffic metadata (IP address, request headers), form submissions in transit | United States and global network | Website |
| Infrastructure hosting provider | Servers, databases and backups for the floDock service and website API | All account data and Customer Data stored in floDock | United States | Website, apps, platform |
| Website analytics (Google Analytics 4, IP anonymised), Google Sign-In for website accounts only, Firebase Cloud Messaging for Android push notifications, font delivery | Website usage data; Google account details when you choose Google Sign-In on the website; Android push tokens and the notifications we send | United States | Website, Android apps | |
| Apple | Apple Push Notification service for iOS, App Store distribution | iOS push tokens and the notifications we send | United States | iOS apps |
| Expo | Delivery of app updates (EAS Update) and relay of push notifications to Apple and Google | Push tokens, the notifications we send, app and device metadata | United States | Apps |
| Sentry | Crash and error reporting for the apps and services (when enabled for a build) | Stack traces, device and app version metadata; no name or email by default; secrets scrubbed before send | United States | Apps, platform |
| Brevo | Transactional email (confirmations, sandbox logins, notices) and marketing email where you have opted in | Email address, name, email content, delivery and open metadata | European Union | Website, platform |
| Chatwoot | Live chat on the public website | Chat messages; account email, name and company if you are signed in | United States | Website |
Changes to this list
We will update this page before we start using a new subprocessor for Customer Data. Customers with a Customer Agreement may ask to be notified of changes by emailing hi@flodock.com with the subject “Subprocessor notices”, and may object to a new subprocessor as described in the Data Processing Addendum.
Not subprocessors
Your own company or facility, which controls its floDock workspace, is not a subprocessor. floDock’s own trial infrastructure, which provisions isolated evaluation sandboxes, is run by floDock and is not a third party.
Services a company turns on
A company can connect its floDock workspace to outside services. These run under the company’s own instructions and, where a key is needed, the company’s own account with that provider. They are not on by default.
- FMCSA (U.S. government). Carrier checks look up a carrier’s public DOT or MC number against FMCSA records.
- SafeCube. Container tracking sends container numbers to SafeCube and receives status events back.
- AI providers for documents. If a company switches on AI help for documents, the document content goes to the AI provider the company has configured (for example Google Gemini or an OpenAI-compatible provider). floDock sends only what the feature needs.