Last updated: 26 October 2026
To run Volo we rely on a small number of other companies. Where one of them handles personal data on our behalf, it is a sub-processor and it is listed here.
We give at least 30 days' advance notice by email before a new sub-processor starts handling personal data, to the administrator contact on each account. If you object on reasonable data-protection grounds within that period, we will work with you to find an alternative; if we cannot, you may stop using the affected part of the service without penalty.
Currently handling personal data
| Sub-processor | What they do for us | What they handle | Where |
|---|---|---|---|
| SupabaseUnited States | Runs our database, sign-in, file storage and backend services. | Everything you store in Volo: accounts, pilot and aircraft records, schedules, documents, billing records and safety reports. | United States |
| VercelUnited States, with a global content network | Hosts and serves the Volo web application, and counts visits to its public marketing pages, without cookies. | Connection data needed to serve pages, including IP address, browser type and the pages requested. Not the contents of your records. | United States, with a global content network |
| Google Cloud (Vertex AI)Google Cloud (Vertex AI) | Reads documents you upload — certificates, medicals, registrations, maintenance logbooks and meter photographs — so the details printed on them do not have to be typed. Also drafts a lesson-prep brief or a debrief when an instructor asks for one. | The document or photograph itself, the filename, and — where a school uploads on a pilot's behalf — that pilot's date of birth, used to calculate medical expiry. For a lesson-prep brief or debrief: the student's lesson history and syllabus progress and the instructor's typed notes, sent as written (so a name typed there is sent), but not the student's name or contact details from their profile. Processed under a Google Cloud Data Processing Addendum and not used to train any model. Vertex AI is the only Google AI service we use; it runs the Gemini models. | Google Cloud (Vertex AI) |
| AnthropicUnited States | Planned, not yet in use. No data is sent to Anthropic today. We will update this page, and give the notice described above, before we start. | None today. | United States |
| AssemblyAIUnited States | Used only when lesson recordings are enabled for an instructor. Converts lesson recordings to text (speech-to-text) so a debrief can be drafted from them. | The lesson audio recording. We ask the provider to delete its copy of the audio and transcript as soon as transcription finishes. | United States |
| ResendUnited States | Delivers our transactional email: invitations, welcomes, booking notices, expiry reminders, account deletion notices and training records. | Recipient name and email address, and the contents of that message. | United States |
| DropboxUnited States | Only where an organisation chooses to connect a Dropbox account. No data is sent unless that connection is made. | The connection itself: Dropbox returns the connected account's email address to us, and we store encrypted access tokens. Volo does not currently send files to Dropbox. | United States |
| Intuit Inc. (QuickBooks Online)United States | Only where an organisation chooses to connect its QuickBooks Online company. No data is sent unless that connection is made. | Once connected, copies of the organisation's billing records from the start date it chose: customer names, email addresses, phone numbers and billing addresses, and the invoices, payments and credit notes issued to them with their amounts and descriptions. We store the connection's access tokens encrypted and never in the browser. An administrator can disconnect at any time, and the tokens are then erased. Records already in QuickBooks stay there. | United States |
| Google LLC (Google Calendar API)United States | Only where a user chooses to connect their Google Calendar. No data is sent unless that connection is made. | To Google: for each of the user's reservations, an event with a title ("Flight: <aircraft>" or "Lesson"), the start and end times, the aircraft, the organisation or practice name and, only for the pilot or student, the instructor's name. No notes, phone numbers, email addresses or attendees. Volo creates a separate calendar for these events. From Google: only the busy start and end times of the user's primary calendar, never event titles or details. We store the connection's access tokens encrypted. Disconnecting stops syncing. | United States |
| Google LLC (Firebase Cloud Messaging)United States | Delivers push notifications to Android devices and, through browser push services, to web browsers, where a user has turned notifications on. | The device token or browser push address, and the text of the notification. Web push messages are encrypted for the receiving browser. | United States |
| Apple Inc. (Apple Push Notification service)United States | Delivers push notifications to iPhones and iPads where a user has turned notifications on. | The device token and the text of the notification. | United States |
| StripeUnited States | Payment processing: Volo's own subscriptions, and card payments to organisations through Stripe Connect where an organisation has enabled them. | Subscriptions: the account holder's email, the organisation or practice's internal ID and the plan. Payments to an organisation: the amount, invoice and organisation IDs and the payer's email for the receipt. Card numbers are entered on Stripe's own forms and never reach Volo. | United States |
Not sub-processors
We request public aviation data from the FAA's weather and temporary flight restriction services. Those requests contain airport identifiers only — no personal data — so those services are not sub-processors.
Our fonts are served from our own systems rather than a third-party font service, so loading Volo does not disclose your IP address to a font provider.