Subprocessors
These are the services that handle customer data on FleetReform's behalf, and what each one receives.
The list
| Service | Used for | Data it receives | Location |
|---|---|---|---|
| Clerk | Sign-in, workspaces, and invitations | Name, email address, avatar, session, and workspace membership | Not yet confirmed |
| Vercel | Hosting for the web app and this site | Request metadata, including IP address | Not yet confirmed |
| Fly.io | Hosting for the API | All application data in transit | Frankfurt, Germany |
| Managed Postgres database | Primary datastore | All application data at rest | Provider and region to be named here before this list is final |
| Google Cloud Storage | Receipt photos and workspace logos | Uploaded images | Not yet confirmed |
| Resend | Email alerts | Recipient email address and the content of the alert | Not yet confirmed |
| Expo | Push alerts to the mobile app | Push token, and the title and text of the alert | Not yet confirmed |
| Mapbox | Map tiles on web and mobile | The map area being viewed and vehicle marker coordinates | Not yet confirmed |
| Sentry | Crash reporting in the mobile app | Crash and error details from the device | Not yet confirmed |
What this list is not
It names services, not the contractual terms with them. Locations marked "Not yet confirmed" have not been recorded here, and we would rather say so than guess. To ask about a specific service, a transfer mechanism, or to be told when this list changes, email support@tsunava.com.