Skip to content What we collect
Identity, booking, payment-reference, and support data needed to complete air travel transactions.
Volobase minimises stored personal data to what is needed for account access, traveller capture, booking fulfilment, receipts, support, and fraud or security review.
Who can access it
Internal access is separated by role, with finance-safe pseudonymised views where possible.
Finance views exclude customer-identifying information, while support tools are limited to roles that are explicitly authorised to view customer contact and booking records.
Service providers
Cloud infrastructure and travel providers are used only where needed to deliver the service.
Current or planned processors include Cloudflare, Stripe, Duffel, and the future production email provider stack.
Your rights
Customers can contact support@volobase.com.au about access, correction, or support questions.
Key topics
- What information is required to create an account, request a reset, or book a flight.
- How booking references, payment references, itinerary documents, and audit records are retained.
- When data is shared with airlines, payment providers, or support processors to complete a booking.
- How exports, finance dashboards, and operational tools are shaped to protect unnecessary PII exposure.
- How customers can contact support@volobase.com.au about access, correction, or support questions.