Privacy policy

Who this information is for

Australian Chauffeurs Group (ACG) provides booking and operations services for customers, chauffeurs, corporate users and office staff. The final policy must identify the responsible legal entity and its privacy contact.

Information in the platform

Depending on the service used, platform records can include names, email addresses, telephone numbers, account details, pickup and destination addresses, trip dates, stops, passengers, luggage, flight details and booking notes.

Other records can include saved places and routes, corporate membership and billing information, payment references and invoices, trip feedback, support requests and notification delivery history. Chauffeur and vehicle records can include contact details, availability, registrations and compliance documents.

Avoid placing unnecessary sensitive information in booking notes or support messages.

Bookings and access

Booking information supports trip organisation, dispatch, customer communication, invoicing and support. Customer and chauffeur access is separated: chauffeur services are restricted to information needed for assigned trips, while office services require staff permissions.

The final policy must explain the purposes of collection and use, disclosures to chauffeurs and corporate administrators, and any additional uses. This page does not authorise marketing use of personal information.

Location and flight information

The platform supports recorded chauffeur locations and booking flight updates. Location records may be used for trip tracking and dispatch where the relevant tracking features are connected.

The final policy must specify when location collection starts and stops, whether background collection occurs, the permissions required and retention periods. Native device tracking has not been verified here. Flight updates do not automatically change a booking’s pickup time.

Payments and external providers

Stripe payment services are designed to process card payments, with payment status and provider references recorded against the booking. Stripe secret credentials are not supplied to customer or chauffeur applications.

ACG’s integration setup includes Twilio for SMS, Firebase for messaging and FlightStats for flight information. Availability depends on configuration and device registration. The final policy must confirm which providers receive information, what is shared, overseas processing and applicable provider privacy notices.

Notifications and preferences

The platform records booking and payment alerts and notification delivery attempts. Depending on configuration, messages may be delivered in the app or through email, SMS or push notifications.

Device notification permissions and service communication preferences are not the same as deleting an account. The final policy must explain available preferences and distinguish operational messages from any optional marketing.

Storage, security and retention

ACG uses authenticated services and role-based access controls to restrict private records. No online system can be represented as entirely risk-free.

Approved retention periods, backup handling, cross-border disclosures, cookie and analytics details, and incident response information are still pending. No specific retention period or security certification is claimed on this page.

Access, correction and deletion

The final policy must explain how to request access to or correction of personal information, how identity is checked, and how privacy complaints are handled. The designated privacy contact and response timeframes await approval.

See Account deletion below for the current deletion information. Visiting that page or uninstalling the app does not delete an account.