Skip to main content
Outback WiFiCheck availability

Privacy Policy

Last updated 16 October 2026

Booking details, payment records and limited website measurement are used to operate the hire service.

Who to contact

Outback WiFi operates the hire service from Ourimbah, NSW 2258. Contact bookings@outbackwifi.com.au about this policy, your information or a privacy concern. This policy describes our handling of information; it does not assume a particular statutory exemption or registration status.

Booking and hire information

We collect your name, email, phone number and requested dates. Destination and booking notes are optional. We also keep the server-calculated quote, pricing version, accepted terms version and time, collection acknowledgement, booking status, agreed pickup time, return and inspection records.

A random submission reference and a fingerprint of the submitted booking fields help recognise retries without creating duplicate requests. These are operational records, not advertising identifiers.

Availability waitlist

If you join the waitlist, we store your name, email, optional phone number, preferred collection and return dates, contact permission and enquiry status. We use these details to contact you about availability for the requested hire. Joining does not create a booking, reserve dates or sign you up for general marketing.

Email bookings@outbackwifi.com.au if you no longer want to be contacted about a waitlist enquiry. We may retain the permission and handling record where needed to explain how your enquiry was processed.

Payments and accounting records

Card details are entered on Stripe's hosted checkout. This application does not receive or store a full card number. We retain provider event and Checkout Session identifiers, payment amounts and currency, status and review notes needed to reconcile a booking.

For payments or refunds completed outside this application, the owner records the type, amount, method, transaction reference and relevant note. Hire payments and refundable bonds are recorded separately. Do not put card details, account credentials or unnecessary personal information in booking or payment notes.

Notifications

We keep booking notification jobs and per-channel delivery records so a failed message can be retried without intentionally repeating a successful channel. These records can contain the booking and quote details required for the message, provider reference, status and a limited error description. Optional Telegram alerts are for the owner, not a public group.

Website measurement

Vercel Web Analytics, Speed Insights and PostHog help measure public page use, performance and the booking funnel. Application analytics exclude admin, API, payment-result and private booking routes and remove public URL query strings. Booking-funnel events are limited to public paths, button placement, broad duration or lead-time buckets, source and status categories and non-identifying flags.

We do not deliberately send customer names, emails, phone numbers, booking references, exact hire dates, destinations, notes or payment links in analytics events. Session storage supports deduplication and limited first-visit attribution such as a public landing path, referrer hostname and filtered campaign labels. It is not used by us for cross-site tracking.

When you submit a booking or waitlist enquiry, that filtered first-visit information and its random session reference may also be saved with the request. This lets us understand which pages or campaigns lead to enquiries and paid hires. The request record connects this information to your booking or enquiry; the separate analytics events do not contain your contact details.

PostHog uses that random per-tab session reference to connect public page and form events with a successfully reconciled deposit. It does not receive your contact details or payment reference. We disable PostHog session replay, automatic click and form capture, person profiles and location enrichment. Its identifier stays in memory and session storage rather than a persistent tracking cookie. A browser Do Not Track signal disables new session attribution and PostHog capture.

Providers and use

Information is used to manage requests, contact you, fulfil and reconcile the hire, handle disputes and meet applicable recordkeeping duties. We do not sell personal information.

Booking records are stored on our own database server in Australia, with encrypted backups. Providers used for those purposes include Vercel for hosting and limited measurement, PostHog US Cloud for limited booking analytics, Cloudflare for secure database transport, Stripe for payments, Resend for email and optional Telegram owner alerts. Provider infrastructure may process information outside Australia. Information may also be disclosed where required by law.

Retention and security

We retain records for the period needed to operate the service, resolve outstanding payments or disputes and meet applicable legal and tax obligations. Archiving a booking in the dashboard does not delete its payment or notification history.

Private administration is access controlled, and connections use encryption in transit. No online system is guaranteed perfectly secure. Access, backups and retention must be managed alongside the application; a dashboard status is not a substitute for those controls.

Access, corrections and concerns

Email bookings@outbackwifi.com.au to request access, correction or deletion where we are not required to retain the record. We may need to verify that the request relates to you. Tell us about a concern so we can investigate and respond.

Policy changes

The current policy is published here. Accepted hire terms and the original quote are stored with the booking and are not silently replaced by a later website version.

© www.outbackwifi.com.au · Terms · Privacybookings@outbackwifi.com.au