Privacy

Calculation happens where you are, not on a server

GolfVectorLab has no login and no server-side record of who used which engine or entered what value. A Handicap Index, a club carry distance, a course rating, whatever an engine asks for, is read by the JavaScript already loaded in your browser, used to produce that engine's result on your device, and then either discarded when you close the tab or kept only if you choose to save it, as covered next.

Why a second engine already knows your driver distance

A handful of values, club carry distances, Handicap Index, and similar bag or player facts, are reused by more than one engine. The first time you enter one, it is written to your browser's own local storage under this site's origin, so a different engine asking for the same fact later shows it pre-filled instead of blank. That is the entire mechanism behind the "connected" part of this site: no server round-trip, no sync service, just a value your browser already has being read by whichever page you open next. Editing it on any engine changes it everywhere it appears, and there is no dedicated profile page because every field where it shows up already doubles as the place to change it.

Your export, import, and clear controls

Everything saved this way belongs to you and stays removable at any time. The controls below export the current saved values to a JSON file you keep, load a previously exported file back in, or erase everything this site has stored in your browser in one action. Clearing your browser's stored site data for GolfVectorLab, or opening it in a private window, has the same effect as the clear control.

Export my data (JSON)Import dataClear all saved data

What an anonymous page visit does and does not include

Page-view analytics on this site counts things like which engine page loaded or whether a result was exported or printed, tagged only by an engine's name. It is structurally unable to include a Handicap Index, a club distance, a course name, or any other value you typed or any result those values produced, because the analytics call and the calculation logic never share data with each other in the code.

Visitors in the EU, EEA, UK, and Switzerland get analytics storage denied by default, without a cookie banner making that choice for them first. A Global Privacy Control signal from your browser overrides analytics on regardless of where you are. No advertising cookie, remarketing pixel, or ad-personalization signal exists anywhere on this site, in any region.

What the hosting layer sees

Because this is a static site with no backend, "hosting" here means a content delivery network handing out unchanging HTML, CSS, and JavaScript files. That layer keeps its own ordinary connection-level logs, the kind any web server keeps for abuse prevention and uptime, and GolfVectorLab has no separate process that reads, exports, or otherwise makes use of those logs beyond what the hosting provider does on its own. Questions about any of the above can go through the contact page.