Privacy

The public website loads these third-party scripts in the browser.

Vercel Web Analytics. Pages load Vercel's analytics script, which records page views. Vercel's documentation says this product does not use cookies.

Meta pixel. Meta's pixel, id 1981072442446647, loads from connect.facebook.net and sends a page view only when the hostname is exactly southernlifts.com.au or www.southernlifts.com.au. A vercel.app address does not load it.

Google Analytics. Google Analytics 4, measurement ID G-208F1BS0YY, loads only when the hostname is exactly southernlifts.com.au or www.southernlifts.com.au. That check also applies on a production deployment, so a vercel.app address does not load the tag. The script runs after the page becomes interactive.

Google reCAPTCHA. Every page loads Google's reCAPTCHA script. The contact, home-lift enquiry, brochure, and change-of-ownership forms use it.

Mapbox. The contact page loads a Mapbox map. The map library requests tiles and a style from Mapbox.

YouTube. The home-lifts page embeds a video from youtube.com. Project pages embed videos from youtube-nocookie.com. A blog post can include a YouTube video.

When you submit an enquiry or a brochure form, your IP address is passed to Southern Lifts' enquiry system for spam and abuse prevention.

What they store

The times below are the vendors' published defaults. They are not a setting read from the Southern Lifts accounts.

Google Analytics. Google's tag records on-site activity, device and browser details, and a random identifier in a first-party cookie. Google says the tag uses the IP address to run the service and to estimate location, and that Analytics does not log or store the IP address. The default cookies are _ga (to tell users apart) and _ga_ followed by the measurement id (to keep the session). Google's cookie list gives both a default expiry of 2 years, refreshed on a later visit. The same page says a browser may shorten that if the person does not come back: up to 400 days in Chrome and 7 days in Safari. This site's tag does not set a custom cookie lifetime. For data kept on Google's servers, Google's Explorations help says a property retains 2 months of data by default. That limit applies to user-level and event-level data in explorations and funnels. Standard aggregated reports are not cut off by it. Age, gender, and interest data are kept for 2 months whatever that setting is. A standard property can be changed to 14 months. To stop Analytics measurement in this browser, Google publishes an opt-out add-on.

Meta pixel. The pixel sends the page view. Meta's cookie settings default is to use both first-party and third-party cookies. The pixel can store a first-party _fbp cookie, a browser identifier, and an _fbc cookie when the visit includes a Meta click id. When a site sets _fbc itself, Meta's developer note recommends a 90-day expiry. That page does not publish one retention period for events stored on Meta's servers, so none is stated here.

Vercel Web Analytics. Vercel's privacy note says the product does not use cookies. A visitor is identified by a hash of the request, and that hash is discarded after 24 hours. With a page view Vercel may store the time, the URL and route, the referrer, filtered query parameters, an approximate location, the operating system, the browser, the device type, and the script version. Vercel says the record is not tied to an IP address. How long those records are guaranteed to stay available is the plan's reporting window, from Vercel's pricing page: 1 month on Hobby, 12 months on Pro, and 24 months on Pro with Web Analytics Plus and on Enterprise. Vercel says it may keep the data longer than that window. This page does not state which plan this project uses.