Privacy Policy

Information you provide

When you use the planner, you may provide starting-point addresses, player labels, course filters, and reports about missing or incorrect facilities. Addresses and coordinates are used to find locations and compare travel to golf facilities. You do not need an account to use Bridge Golf.

Browser storage

Bridge Golf uses local storage to remember your theme, whether you have seen the About dialog, and recently selected addresses. Session storage remembers the current planner state and latest results for the browser session. This information stays in your browser and can be removed by clearing site data.

Shared plans

If you create a share link, Bridge Golf stores the plan's labels, addresses, coordinates, filters, and settings so the link can reopen it. Anyone with the link may be able to view that information, so only share it with people you trust. Shared-plan pages are marked so search engines should not index them, but that instruction cannot make a publicly shared link private.

Analytics

Bridge Golf keeps privacy-conscious first-party product events for completed searches, created share links, affiliate-link clicks, and submitted catalog reports. These events contain only limited operational properties such as the number of starting points, number of results, planning mode, affiliate placement, or report reason. They do not contain street addresses, player names, raw IP addresses, analytics cookies, browser identifiers, share tokens, or user-agent strings. Reports created from these events use aggregate counts. Product analytics are retained for approximately 13 months.

Security and operational data

An essential, anonymous session cookie and a salted one-way representation of the request IP address are processed in memory to limit abusive API traffic. Correction reports may retain a salted reporter token to help moderate repeated submissions; Bridge Golf does not store the raw IP address with the report. Operational logs may include the request path, response status, timing, and infrastructure request ID, but are configured not to include query strings, addresses, raw IP addresses, or user-agent strings.

Caches

Confirmed geocoding responses and route calculations may be cached to improve speed and avoid repeated provider charges. Geocoding cache entries can include provider-supplied address labels and coordinates. Route-cache entries contain rounded coordinates, course identifiers, travel time, and distance rather than the typed street address. Cache entries expire after their configured retention period, and expired database rows are removed during normal cache activity.

Service providers

Bridge Golf currently uses Cloudflare for DNS and network protection, Render for application hosting, Neon for PostgreSQL hosting, Stadia Maps for address search and route calculations, and OpenFreeMap for map tiles. Information needed to provide a feature, such as an address, coordinates, or a normal web request, may be sent to the relevant provider. Those providers handle information under their own terms and privacy policies.

Affiliate links

Bridge Golf includes links to retail partners and may add links to tee-time booking partners. Bridge Golf records that an affiliate link was clicked, along with its partner and placement, but attribution after leaving Bridge Golf is handled by the partner. Partners may use cookies or similar technology under their own policies. As an Amazon Associate, Bridge Golf earns from qualifying purchases.

Your choices

You can avoid creating shared plans, clear locally stored site data, or contact us about information submitted through a correction report or shared plan. Email contact@bridgegolf.net.