Skip to content

Data

How we use data, and what we never do

ParHard runs on three kinds of data. Two are about courses. One is about you, and it stays yours.

Last updated . This page is a draft pending counsel review.

Three kinds of data

  • Course facts we can publish. Hours, policies, walkability, holes, yardages, what a course has. Every fact is stored with its source, how we learned it and the date we last checked. These power the course pages, the public API and the MCP server, and they are the only data that ever leaves the service in bulk.
  • Licensed data from partners. Some maps, imagery and course details come under contracts that limit where they can show. They stay inside the surface they were licensed for, are never traced or copied into our own data, and never go into any AI pipeline.
  • Your data. Your account, rounds, scores, marked shots, bag, crews, outings, messages and photos. Private by default. Shown only to you and the people you choose. Never on the public web, never in the API or MCP server, never in any open download, and never used to train a model.

Every public boundary checks which kind of data it is handling before anything leaves. That check is a test in the code, not a policy someone has to remember.

Your rounds

  • A round is a list of events, added to and never edited. A correction is a new event. Nothing is lost when a phone dies or a signal drops.
  • Anyone in a group round can record scores. Each entry says who recorded it, and you confirm your own.
  • Rounds feed your history, your stats and your crew's standings. They never feed anything public unless you share a card or a round yourself.

Location

  • Precise location is read only during a round or practice session you started, and only while the app is open. Never in the background.
  • Raw GPS tracks stay on your phone. Only the shots you mark are sent, and only when you mark them.
  • Near me uses an approximate spot, rounded on the phone before anything is sent. We do not keep it.
  • Photos have their location data stripped on the phone before upload, and again on the server.
  • Analytics and error reports never carry coordinates, and we turn off any lookup of where your network address is.
  • No feature ever shows other people where you are, and we never build maps from player positions.

What we do with your data

  • Run your rounds, crews, outings and standings.
  • Sync your account between the web, the app and your watch.
  • Send the outing invites, reminders and account emails you or your organizer asked for.
  • Charge for a plan, if you bought one, through Stripe, the App Store or Google Play.
  • Learn which features are used and where people get stuck, through analytics that carry no names and no location.
  • Fix crashes, through error reports scrubbed of personal data.
  • Answer you when you write to us.

What we never do

  • Sell your data, or share it for advertising.
  • Show ads or run any ad tracking.
  • Track you across other sites or apps.
  • Hold, move or settle money for a game. Every game is points only.
  • Send your private data to an AI model without your opt-in, per feature, in plain words.
  • Train any model on your data, even with opt-in.
  • Use face recognition.
  • Record your screen. Session replay is off everywhere.
  • Keep raw GPS tracks on our servers.
  • Guess a course fact or a yardage. Unknown stays blank.

Analytics

We use PostHog for product analytics and Sentry for crash reports. Here is exactly what that means:

  • Events are screen views, taps and form submits, page speed and errors. Never what you typed, never a score, never a position.
  • Events carry an internal account id, not your name or email, and only once you are signed in.
  • No cookies and no browser storage are used, so there is no cookie banner and nothing follows you between visits.
  • Search terms, codes, tokens, contact details and coordinates are stripped from any URL before it is recorded.
  • On screens that show your own data, text on the page is masked before an event is sent.
  • Every event we send is listed in a registry in our code before it ships. The app store privacy labels are generated from that list.

AI

No feature today sends your private data to an AI model. When one does, such as a recap of your round or an assistant that drafts an organizer's reminder, it is off until you turn it on for that feature, and you will see what data goes where before you do. Only your own data goes, or group data that every member opted into; a member who did not is left out. Providers must keep nothing after the response. Nothing is ever used for training. Every use is logged where you can see it, and you can turn it off at any time. Licensed partner data never goes to any model, with or without opt-in.

Where you control it

  • Profile visibility and search visibility: in the app under Profile, and on the web at /me. Both off by default.
  • Whether your crews can see your rounds, outing and crew notifications, and product email: in Settings. Product email is off unless you turn it on.
  • Location permission: in your phone's settings. The app works without it; you lose yardages and shot marking.
  • Who can see each feed item, photo or review: chosen per item when the social features ship.
  • Delete your account: in the app under Account, or on the web at /account.

Where it lives

Your data is stored in the United States with Supabase, and the service runs on Vercel. The full list of companies that process data for us, and what each one gets, is in the privacy policy. Public course data and weather come from USGS, NOAA and the National Weather Service, and no personal data goes to them.

Questions

Write to support@parhard.com. The privacy policy has your rights and the terms have the rules.