Privacy
Your plan is yours.
The separate first-party task counter is disabled. Public information pages load the owner-configured Google Tag Manager container GTM-WLX3R45M. Tags published there can measure visits, browser/device/referrer information and may use cookies; Google receives those requests. Private build, comparison, search, evidence/correction and measurement-control pages do not load this container. The site tools do not add stored build names, notes, contact details or private exports to the Google data layer. No remote font, visitor account or marketing subscriber service is configured. The static site does not create a visitor account or store personal information on an application server. Its host may retain ordinary access logs.
- This browser
- Chosen file
- No auto-upload
Original data-boundary diagram; private records never become public assets.
Control optional measurement preferences. That first-party counter requires an enabled same-origin service and your explicit Allow preference;DNT/GPC,local/owner preview and recognized automation override it. Those controls do not configure Google Tag Manager. cv-measurement-v1 stores the first-party preference;cv-event-keys-v1 and cv-owner-preview-v1 are tab-only dedup/preview controls. The collector stores daily category counters,not personal IDs,notes,query terms,URLs or orders. Blocked collection cannot block tools.
Named builds use the browser-local key cv-builds-v2. They contain names, vehicle scope, exact package IDs, quantities, owned/planned stages, notes, saved public-source observations and explicitly saved energy/water/dimension/mass scenarios with their assumptions. An earlier cv-build-v1 list can be copied locally and is retained until Clear all. Comparisons use cv-shortlist-v1 for explicitly saved public IDs. No background sync or account is configured. Clear all browser build data removes build keys; browser storage controls can also erase them. JSON exports are separate files containing your notes and cannot be recalled by the site. Import validates the file locally and adds copies; no upload occurs.
Shared comparison links include public package IDs, vehicle scope and row settings. Fit-finder/tool/lesson answers and standalone parts ownership overrides stay in page memory.
The structured evidence-packet form keeps exact IDs,source scope and optional consented contact email only in page memory until you download its private file. No online intake endpoint,mailing list or attachment upload is configured. Editors intake files explicitly into a separate private queue; no contact details enter public catalog candidates. The correction-note form processes your entries in this page’s memory. It sends nothing to a server, does not save to browser storage, and only downloads a file when you ask. Reload or reset clears the draft. A downloaded file is your separate copy and cannot be recalled by the site.
Merchant/source links take you to external sites with their own policies. Creator pages use local original markers and ordinary links; no video player loads before you click its explicit load control. That action contacts YouTube under its own policies; removing the player cannot erase provider data already received. Future measurement, account or notification features must describe their actual storage and consent controls when enabled.