Overview
DriveLog is a record-keeping and audit compliance platform built for Australian driving schools. This Privacy Policy explains how we collect, use, store, and protect personal information in accordance with the Australian Privacy Act 1988 and the Australian Privacy Principles (APPs).
Who We Are
DriveLog is operated by Drive Log Australia, based in New South Wales, Australia.
- Website: drivelog.com.au
- Email: support@drivelog.com.au
- Jurisdiction: New South Wales, Australia
What We Collect
We collect only the information necessary to provide driving school management and compliance services.
| Category | Data Collected | Who Provides It |
|---|---|---|
| Identity | Full name, date of birth | Learner driver |
| Contact | Mobile number, email address, residential address | Learner driver |
| Licence | NSW licence number, licence expiry date, licence class | Learner driver (via OCR scan or manual entry) |
| Booking | Test date, test time, test centre, package selected | Learner driver |
| Booking Confirmation | Screenshot/photo of official RMS/Service NSW test booking confirmation | Learner driver (uploaded image) |
| AI Assistant Conversations | The messages you type to the optional AI assistant on our booking page, and the replies it gives you | Learner driver (only if you choose to use the assistant) |
| Lesson Records | Lesson dates, durations, notes, payment status | Driving instructor |
| Account | Instructor name, email, Google account (for login) | Driving instructor |
| WhatsApp Business Platform | WhatsApp Business Account ID, phone number ID, display phone number, customer phone numbers, WhatsApp profile name where provided, message IDs, message timestamps, message content, message type, delivery/read/error status, webhook event metadata, template/message audit logs, and onboarding/session records needed to connect an authorised WhatsApp Business account | Driving school/business account owner, Meta/WhatsApp Business Platform, and WhatsApp users who message the connected business |
| Consent | Timestamp and version of privacy policy accepted | Automatically recorded at registration |
How We Use It
Personal information collected through DriveLog is used solely for the following purposes:
- Creating and managing student records for the driving school
- Scheduling and tracking driving lessons and test bookings
- Generating audit-ready compliance reports required by transport authorities
- Sending notification emails to instructors when a new student registers
- Verifying test booking details against the uploaded confirmation screenshot
- Saving student contact details to the instructor's Google Contacts for easy access
- Creating calendar events for lessons and tests in the instructor's Google Calendar
- Answering questions asked through the optional AI assistant on the booking page, and reviewing those conversations afterwards to handle support enquiries and complaints, check the quality and accuracy of the answers given, and keep a record of what a learner was told
- Connecting an authorised driving school's WhatsApp Business account to DriveLog
- Receiving WhatsApp customer enquiries inside DriveLog
- Organising WhatsApp conversations as leads, students, bookings, or support records
- Sending booking, test-preparation, reminder, and support replies through the WhatsApp Business Platform
- Recording message delivery/status events and audit logs for troubleshooting and compliance
- Supporting WhatsApp Business App / Cloud API coexistence where enabled by Meta and authorised by the business
Google Services
DriveLog requests Google Calendar and Google Contacts access when an instructor connects their Google account. This access supports the driving school workflows described below:
| Google Service | Purpose | Data Accessed |
|---|---|---|
| Google Calendar | Read availability; create, update, reschedule and cancel lesson and test events | Event dates and times, titles, descriptions, locations and attendees needed for scheduling and synchronisation |
| Google Contacts | Search and synchronise the authorised contact directory; create, update and explicitly delete linked learner contacts | Contact names, phone numbers, email addresses, addresses and learner details saved with contacts |
| Licence OCR | Extract details from uploaded licence photos automatically | Uploaded image content processed through DriveLog’s server-side OCR service |
Calendar and Contacts access is authorised by the instructor and used for their driving school workflows. Calendar changes can be synchronised between Google Calendar and DriveLog’s linked lesson and booking records. When authorised staff explicitly choose Google removal while deleting a learner, DriveLog can also delete that learner’s linked Google Calendar events and Google Contact. Licence and test-booking image processing uses DriveLog’s server-side OCR service; it does not use the instructor’s Calendar or Contacts permissions.
Google data access, use and sharing
Raw data. Depending on the feature you use, DriveLog reads Calendar event identifiers, dates and times, status, titles, descriptions, locations, attendees and DriveLog linking information. Availability-only checks request busy start/end times, without event titles or descriptions. Contacts features read names, phone numbers, email addresses, addresses and metadata needed to find or update a linked contact. The synchronised contacts directory stores the contact's display name, valid phone numbers, Google resource identifier, version and update time; it does not copy every field in the Google address book.
Derived data. DriveLog derives free/occupied time slots, conflict and buffer decisions, linked booking status, contact-match results and operational counts from this information. Raw, derived and aggregated Google data are used to provide scheduling, learner/contact management, synchronisation, support, security and troubleshooting for the authorised school. They are not used for advertising, credit decisions, data brokerage or unrelated profiling.
Processing and recipients. Google data is processed by DriveLog's application and its hosting, database and storage providers, including Supabase and Vercel, to operate these features. Relevant lesson/contact information is shared with authorised school users. Creating or changing an event can send Google Calendar invitations or updates to its attendees. Google Calendar and Contacts receive the writes requested by the user. Service-provider access is limited to operating the requested service, security and support; DriveLog does not sell Google user data or transfer it to advertisers or data brokers.
Optional assistant. If the booking assistant is enabled, available time slots derived from Calendar availability may be sent to the configured Ollama-compatible AI service together with the conversation and the limited learner context described under Sharing & Disclosure. That scheduling pack does not include personal appointment titles, descriptions, attendees or the contact directory. AI inference used to answer a booking question is separate from training an AI model.
Limited Use. DriveLog's use and transfer of raw or derived data received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. DriveLog does not use this data to develop, improve or train general-purpose AI/ML models, and does not permit a service provider to use it for that purpose. Any AI processing of this data is limited to the authorised user-facing feature.
Access controls. Google account permissions and DriveLog school/instructor authorisation are separate checks. Connections, synchronisation records and backend credentials are access-controlled; requests use HTTPS/TLS. School Support access requires the applicable authorised support and Calendar-sharing context. Human access is limited to authorised school operations, a user's support request, security or legal requirements. We do not claim that a Google permission alone authorises access to another school's records.
Disconnecting and deleting. You can revoke DriveLog's Google access in Google Account connections. This stops future access under that grant; it does not by itself delete events or contacts in Google, copies already saved in DriveLog, or records the school must retain. Contact support to request removal of connection data or other Google-derived copies. The linked-learner deletion screen offers separate, explicit Google Contact and Calendar removal choices and reports incomplete external cleanup for review. Unselected Google copies remain in your Google account.
Google Maps (learner pickup addresses). If you ask us to pick you up, we collect and store the street address you choose, so your instructor knows where to go, together with the Google place identifier for it. We keep both with your booking record for the school's six-year lesson-record period and then delete them automatically, or sooner if you ask us to erase your data; sessions that were never completed are cleared automatically. Map coordinates for that place are kept for no more than 30 days and are then deleted. Travel times from Google Maps are used when we check the booking and when staff review it, and are not stored. When we work out the drive we send Google map coordinates or a place identifier, never your name, phone number or email; the text you type in the address search box is also sent to Google, to suggest addresses. Our booking service includes Google Maps features and content; their use is subject to the Google Maps End User Additional Terms of Service (maps.google.com/help/terms_maps/) and the Google Privacy Policy (policies.google.com/privacy).
WhatsApp Business Platform
DriveLog may integrate with the WhatsApp Business Platform to help driving schools manage customer conversations and booking enquiries.
When a business connects its WhatsApp Business account, DriveLog may receive and process WhatsApp Business Platform data, including WhatsApp Business Account IDs, business phone number IDs, customer phone numbers, WhatsApp profile names where provided, message IDs, message content, timestamps, message type, delivery/read/error statuses, template activity, webhook event metadata, and related audit logs.
DriveLog uses this data only to provide WhatsApp messaging, lead-management, booking-support, customer-service, troubleshooting, security, and audit functions for the authorised driving school.
DriveLog may use Meta Embedded Signup or related Meta Business tools to allow an authorised business owner to connect their WhatsApp Business assets. Any tokens or credentials used to access WhatsApp Business Platform APIs are stored server-side and are not exposed in the browser.
Where WhatsApp Business App and Cloud API coexistence is enabled, DriveLog may receive webhook events such as message history, contact sync events, message echoes, and account update events. These events are used only to display, store, audit, or synchronise the business's own WhatsApp conversations and related contact records inside DriveLog.
DriveLog does not:
- sell WhatsApp or Meta Platform Data
- use WhatsApp message content for unrelated advertising
- share WhatsApp message content with advertisers or data brokers
- use WhatsApp data to build unrelated user profiles
- access WhatsApp data unless authorised by the connected business account owner
Booking Confirmation Screenshots
When a learner selects a test package, they may upload a screenshot or photo of their official RMS / Service NSW test booking confirmation. This image is:
- Stored securely in a private Supabase Storage bucket — not publicly accessible
- Linked to the learner's profile in the driving school's records
- Accessible to authorised school staff and approved support personnel under the applicable access controls
- Used to verify and audit the test date, time, and centre details entered during registration
- Retained for 6 years in accordance with Australian business record-keeping obligations
Data Storage & Security Infrastructure
DriveLog uses Supabase for its application database and private file storage. Connected Google records remain in Google as well, and service providers can process operational data as described below. Key protections include:
- The learner-record database is hosted in the ap-southeast-2 (Sydney, Australia) region. This is a statement about where the database sits — it is not a claim that every service DriveLog uses stores or processes data only in Australia. See Sharing & Disclosure and the published provider disclosure.
- Row-Level Security (RLS) — each driving school can only access its own data
- All data transmitted over HTTPS/TLS encryption
- Storage buckets are set to private — no public URL access to uploaded files
- Ordinary instructor sessions use a 30-minute inactivity sign-out. Separately authorised, time-limited background operations can use an explicit temporary session-continuation lease; server authentication and authorisation checks still apply.
- Access logging on sensitive student profile views
Website and Booking Activity
Where the school enables first-party operational activity reporting, DriveLog automatically records minimized journey activity with a visible notice. This helps the school understand booking steps, failed validation categories and purchases. It records the type of page visited, identified buttons clicked, booking steps reached, and fixed validation field categories. These events do not include typed form values, licence images or numbers, addresses, email addresses, telephone numbers, message text, or Google Calendar/Contacts content.
A short-lived random identifier can connect a school-website visit to the booking page. It is not a device fingerprint. The school can review its own journey and conversion activity, including server-confirmed booking and payment outcomes; browser activity alone never proves payment. These minimized DriveLog journey records are retained for up to 14 days. Choose Stop first-party activity in the notice to stop collection in this browser and request removal of that journey. The choice persists in this browser and follows public booking links from the school website. We also respect Global Privacy Control. Stopping activity does not cancel bookings, erase required school/payment records, or affect your ability to book.
Masked Microsoft Clarity replay. Participating schools use Microsoft Clarity to review page interactions across their website and school-branded booking domain. Text, images and form details are masked before recording starts. Private uploads and sensitive outbound navigation stop replay; unsafe incoming URLs disable it. Named booking stages and a random journey reference help the school investigate unfinished bookings. Parents or guardians should make bookings for learners under 18. Activity preferences and Global Privacy Control also apply to replay. Microsoft processes replay under its own retention settings; the 14-day DriveLog event period does not describe Microsoft-held recordings.
Optional Google Analytics is separate. Where the school offers it, Google Analytics starts only after explicit opt-in. It follows Google’s own processing and retention settings; DriveLog’s 14-day period is not a promise about Google-held analytics. First-party operational reporting does not grant Google Analytics permission. Contact support@drivelog.com.au for help with a privacy request.
Data Retention
| Data Type | Retention Period |
|---|---|
| Student records & lesson logs | 6 years (Australian tax & business records obligation) |
| Booking confirmation screenshots | 6 years |
| Consent logs | 6 years |
| Instructor account data | Duration of active account + 2 years |
| AI assistant conversations | 90 days from the last message in that conversation |
| Error & access logs | Normally up to 90 days; shorter operational rules and longer consent, audit, security or legal exceptions can apply |
| WhatsApp messages and conversation records | Retained for the duration of the connected business account plus up to 6 years where required for business records, audit, dispute handling, or legal obligations |
| WhatsApp webhook/security/error logs | Normally retained for up to 90 days unless needed for security, troubleshooting, audit, or legal reasons |
| WhatsApp onboarding/session records | Retained while the integration is active plus a reasonable period for audit, support, and security |
These are DriveLog's retention periods for the stated record categories, not a claim that one automatic deletion job covers every table. Some operational logs are removed sooner; consent, audit, dispute and legal evidence can have different requirements. Cleanup may be scheduled, event-driven or performed after an authorised review, depending on the record type.
Google-linked copies and sync data. Linked lesson and learner/contact details form part of the applicable school record. Directory cache entries are reconciled when Google reports a deletion or a successful full sync no longer includes the contact; connection identifiers and sync cursors support the active integration. A revocation is not an automatic erasure of these copies. Contact us to request deletion or disconnection; we identify the affected records and any retention exception rather than promising that every copy disappears immediately. Provider-held originals and backups have separate retention and recovery processes.
Upon written request, we will delete personal information earlier where there is no legal obligation to retain it.
Your Rights
Under the Australian Privacy Act 1988, you have the right to:
- Access — request a copy of the personal information we hold about you
- Correction — request correction of inaccurate or outdated information
- Deletion — request deletion of your personal information (subject to legal retention requirements)
- Complaint — lodge a complaint with the Office of the Australian Information Commissioner (OAIC) if you believe your privacy rights have been breached
To exercise any of these rights, contact us at support@drivelog.com.au. We will respond within 30 days.
Businesses may request disconnection of their WhatsApp Business integration at any time by contacting support@drivelog.com.au. Individuals may request access, correction, or deletion of their personal information, including WhatsApp-related records, subject to legal retention requirements.
Data Deletion Requests
To request deletion of DriveLog account data, learner data, or WhatsApp-related records, contact support@drivelog.com.au with enough information to identify the relevant account or record.
Where legally permitted, DriveLog will delete or de-identify the requested information. Some records may be retained where required for business records, audit, dispute handling, fraud prevention, security, or legal compliance.
For Meta App Review and platform compliance, this page serves as DriveLog's public data deletion instructions.
Security
We take reasonable steps under APP 11 to protect personal information from misuse, interference, loss, unauthorised access, modification, or disclosure. Measures include:
- Encrypted data transmission (HTTPS/TLS)
- Private, access-controlled file storage
- Inactivity sign-out for ordinary sessions, with explicit time-limited continuation only for separately authorised background operations
- Access logging for sensitive student-profile workflows
- School-level data isolation — no cross-school data access
If you become aware of any security concern relating to your data, please contact us immediately at support@drivelog.com.au.
Contact Us
For any privacy-related questions, requests, or complaints: