Subprocessors
The companies Limozly uses to provide its service, what each one does and which data it receives. Last updated 2026-10-19.
| Company | Purpose | Data | Location |
|---|---|---|---|
| Supabase | Database, sign-in and private file storage | All account, booking, customer and driver data | United States |
| Vercel | Application hosting | All data in transit while pages and APIs run | United States |
| Stripe | Card payments, subscriptions and payouts | Payer name, email, card token, amounts | United States |
| Authorize.Net (Visa) | Card payments for operators who choose itOnly for: Operators who connect Authorize.Net | Payer name, card token, amounts | United States |
| Twilio SendGrid | Email delivery | Recipient email, message content | United States |
| Twilio | Text messages and masked calls | Phone numbers, message content | United States |
| Google Maps Platform | Address search, distances and maps | Addresses and coordinates | United States |
| Google Firebase | Push notifications to the driver and passenger apps | Device token, notification text | United States |
| Anthropic | AI assistant and document reading | Text and documents sent to the assistant | United States |
| AeroDataBox (via API.market) | Flight tracking for airport trips | Flight numbers and dates | European Union |
| Google Workspace and Microsoft 365 | Calendar and mailbox connectionsOnly for: Operators who connect a calendar or mailbox | Calendar events and emails the operator connects | United States |
| GNet | Ride network for farm-in and farm-outOnly for: Operators who join GNet | Trip details shared with the network | United States |
| HubSpot | Limozly sales and support records | Operator business contacts (not their customers) | United States |
Tell me when this list changes
We email you before a new subprocessor starts receiving data. One email per change; unsubscribe in any of them.
See also: Privacy policy, Security, Privacy request.