Documentation Index
Fetch the complete documentation index at: https://docs.fitmyvehicle.com.au/llms.txt
Use this file to discover all available pages before exploring further.
Minimal footprint
The embed script (fmv.js) runs on your page but has an extremely limited scope:
- No DOM access — Does not read page content, forms, user inputs, other scripts, or any merchant DOM elements. It reads only its own
<script>tag attributes and click targets withdata-fmv-open-widget. - No cookies or storage — Sets zero cookies and does not touch
localStorageorsessionStorageon your domain. - No data transmission — The embed script sends no data anywhere. It’s purely a UI shell that creates an iframe.
- Creates exactly 2 elements — A
<div>overlay and an<iframe>. Nothing else.
Inside the iframe
The iframe runs oncdn.fitmyvehicle.com.au — a completely separate origin from your site. Inside the iframe:
- No cookies or storage either — The Supabase client is explicitly configured with
persistSession: falseandautoRefreshToken: false, so no cookies or storage are used even on the iframe’s own domain. - Data only goes to FMV — All data submitted inside the iframe goes exclusively to
*.fitmyvehicle.com.audomains over HTTPS. - Font providers are iframe-only — Adobe Fonts and Google Fonts are loaded inside the iframe only. They never touch your page.
- Customer data — Names, emails, phone numbers, and vehicle selections entered in the widget are submitted exclusively to
api.fitmyvehicle.com.auover HTTPS.
No third-party tracking
No analytics pixels, ad trackers, or third-party scripts are loaded on your page by the FMV widget. The only external requests from the iframe are to FMV’s own domains and font providers. The widget does emit structured analytics events (such asfmv_started and fmv_quote_submitted) via postMessage to the parent page. These events are designed for you to use with your own analytics setup if you choose — see Analytics events. FMV itself does not send this data to any third party.