Skip to content
Par PocketSettings

Privacy policy

Learn how Par Pocket handles local golf records, optional account backup, analytics, permissions, course maps and data deletion.

Effective 20 September 2026

Jump to a section

You can score solo rounds on your device without an account. Account backup, online sharing and product analytics are optional. Some connected features and crash reporting send information as explained below. We do not sell your personal information or display third-party advertising.

This policy covers the Par Pocket website and apps. For privacy questions or an accessible copy, email hello@parpocket.com.

Your device stores rounds, notes, course choices, playing benchmark, preferences, notifications, recovery copies and shared-game access details. Personal course notes are stored only on this device and are excluded from account sync and round backup files. Saved mapped shots include precise locations and capture times. An optional Android widget keeps a private active-round copy until the round ends.

If you enable account backup, Supabase receives your email, account identifier, completed rounds, notes, saved shot locations and preferences. Active-round backup requires a separate choice in Account settings. Scoring works offline; check sync status before relying on a backup. You choose how to resolve conflicting copies. Pausing uploads leaves existing cloud copies in place.

Exports may contain your full golf history. You choose where backups and result images go; recipients and external services may keep or forward them.

Online scoring and course groups require an account; availability polls can be joined as a guest. Local group scoring needs no account. Supabase stores memberships, access identifiers and the information shared with your group: nicknames, handicaps, teams, course details, scores, results, changes, standings, proposed dates, votes and attendance.

Joining a course group automatically shares eligible past and future rounds at that course, including dates, scores, handicap and playing statistics. Each round does not get a separate sharing prompt. Invite holders can see a limited preview and may join; members can see the group record. Ask permission before entering another player’s information. Nicknames do not make attendance or scores anonymous, and removing access cannot recall copies already saved.

Safety reports include the reported name, reason, group and involved account identifiers. Blocks restrict access to groups shared with the blocked account.

You can decline permissions and still score manually. Location is used on your device for nearby courses and foreground hole GPS. Live GPS stops when you leave the screen, background the app or stop it. Readings are not saved or sent unless you explicitly save a mapped shot; saved locations, times, placement source and available accuracy then form part of your round and enabled backups.

Scorecard photos are read on device, not uploaded or stored with rounds. Temporary app-cache copies are deleted when replaced or when you finish or leave import. Par Pocket never deletes the original library photo. Android ML Kit may contact Google for model or compatibility updates. ML Kit automatically sends app/device details, a per-installation identifier and operational metrics—not photos or recognised text.

Voice entry requires on-device recognition; we do not retain audio. Notifications are optional. Group alerts send a push token and preferences to our service and pass through Expo and Apple or Google, with a general message and group identifier. Your lock-screen settings control visibility. Local reminders stay on device.

Adding a tee time shares event details with your chosen calendar. iOS uses add-only access; Android opens the system event editor. We do not read your calendar or request contacts, tracking or background location.

Website product analytics is on by default for page views, traffic sources and feature usage. Turn it off in Settings → Privacy; saved opt-outs and Do Not Track are respected. In the Android and iOS apps, product analytics stays off until you enable it in Settings; older default-on app settings require a fresh choice. PostHog receives usage events, with Google Analytics on web and Firebase Analytics in the app. Events describe screens, feature use and outcomes, session duration, selected options, round/import activity, hole counts, app version and device information. Web analytics also uses cookies or identifiers and approved campaign and broad referral categories. With analytics enabled, approved campaign labels are kept on this device for up to 30 days to recognise return visits. Android can read approved campaign labels from Google Play after you opt in; download links may pass those labels to Google Play. Turning analytics off clears the saved labels.

Events exclude scores, names, email, course identities, notes, GPS, photos, recognised text and audio. Web click details are masked; raw URLs and referrers are excluded, Do Not Track is respected, advertising consent is denied and session replay is off. Opting out stops new events but does not delete earlier data.

When configured, Sentry automatically receives crash type, technical error details, app version, OS/device information and limited diagnostic labels. Native apps also send session status, duration and SDK-generated session/install identifiers to measure crash-free releases; these are not linked to your Par Pocket account. User/request details, screenshots, attachments, activity trails and replay are removed or disabled. Turning off analytics does not stop these crash reports or Android ML Kit metrics.

Sending feedback shares your answer, optional comment, app version, platform and relevant course/tee identifiers with PostHog, separately from analytics consent. A random device identifier links submissions. Email, scores, notes and precise location are not automatically attached. Supabase and Resend deliver feedback and context privately to the operator; delivery receipts store a reference and status, not the comment. Unsent feedback retries while the app is open and connected.

You can turn off feedback prompts while keeping manual feedback; this preference is included in account backup. Keep the feedback reference for access or removal requests.

Support email includes your address, message and attachments. We retain correspondence needed to resolve the issue. Do not send passwords or sign-in codes; avoid unnecessary sensitive information or other people’s private details. We assess unnecessary personal information for deletion or de-identification where lawful.

Connected services receive network details such as your IP address and app/browser information. OpenStreetMap and MapTiler receive the map area viewed, not your GPS fix, scores, notes or account details. Hole distances and temporary planning targets are calculated on device; targets are cleared when you leave the guide. Saved shots remain with the round.

MET Norway receives the selected course’s coordinates, not your GPS location, and keeps access logs in Norway. Forecasts are cached on device. Daylight calculations stay on device. Facility-data updates contact our website without sending selected course coordinates, GPS, scores or account details.

Tee-time searches send filters such as region, date, players and holes to our availability service. Booking providers and optional Ko-fi contributions use their own websites and privacy policies. We do not collect payment-card details through these features. Opening a source, facility or download link contacts that external service.

Ko-fi privacy

Browser storage keeps your golf records, preferences and sign-in or guest access. Clearing it may erase records and your analytics choice; export important data first. Vercel processes requested URLs, IP addresses, browser/device information and hosting logs to deliver and secure the website, independently of analytics.

Marketing emails require separate consent from account and service messages. You choose the monthly note and/or getting-started or return reminders, limited to two emails per 30 days and at least seven days apart. Supabase stores email preferences, consent and verification history, and delivery records; Resend sends emails and handles delivery, bounce and complaint events. Reminder selection uses account activity and synced-round information, skipping unknown or stale activity.

Change Email preferences or use the unsubscribe link without signing in. Account deletion stops linked marketing. We retain minimum consent and suppression records to honour opt-outs. Confirmation links expire after 48 hours; preference links after 180 days.

Local records remain until you clear them, choose Sign out and remove device data, clear browser storage or uninstall. Account deletion removes cloud account and personal-round data and starts cleanup on the current device; interrupted cleanup retries when the app opens. Signing out alone does not delete your account. Other devices, exports, device backups and recipients may retain copies.

Account deletion removes linked group memberships and identifying player details; anonymised scores may remain for other players and hosting may transfer. Groups with no other member are deleted. Unlinked guest records need separate removal; invitation expiry does not delete a group, and shared records do not automatically expire. Contact hello@parpocket.com with the group and nickname, never a private access token. Other participants’ rights may affect removal.

Account deletion or analytics opt-out does not automatically erase provider analytics, diagnostics or support correspondence. Provider logs and backups follow separate schedules, and some records cannot be found using your email. Contact us for help. We keep personal information we control only as needed for its purpose or a legal obligation, then take reasonable steps to delete or de-identify it.

We use Supabase for accounts, shared play and email preferences; Resend for email; PostHog and Google Analytics/Firebase for analytics; Google ML Kit for Android text recognition; Sentry for diagnostics; Vercel for hosting; Microsoft Outlook for support; and Expo, Apple and Google for notifications. Map and weather services are described above.

Providers and their support teams may handle information outside Australia. MET Norway’s access logs are kept in Norway; other locations depend on the provider and project region. We do not promise Australian-only storage. Contact us about relevant locations and safeguards. Overseas handling does not remove our obligations where Australian privacy law applies.

Supabase privacy

Resend privacy

PostHog privacy

Google privacy (including Firebase and ML Kit)

Sentry privacy

Vercel privacy

Microsoft privacy

Expo privacy

Apple privacy

OpenStreetMap Foundation privacy

MapTiler privacy

View, edit or export local records in Settings. For access, correction, deletion or a privacy complaint, email hello@parpocket.com with the issue and outcome you want. Requests are free. We may check your identity or authority; do not send identity documents unless we arrange a suitable method. We aim to respond within 30 days and explain delays.

If we refuse access or correction, we will explain why where lawful and how to challenge it. If unresolved, you can complain to the Office of the Australian Information Commissioner (OAIC), within its jurisdiction. Your rights under applicable law remain.

OAIC privacy complaints

We use HTTPS, account access controls and restricted guest credentials, but no system is completely secure. Protect your device, email, backups and invitations. Report suspected unauthorised access to support. We investigate incidents, take reasonable steps to contain them and notify affected people and the OAIC when required.

Younger players should review privacy choices with a parent or guardian, especially before accounts, sharing or analytics. We do not verify age at sign-up. Adults entering children’s details should consider their understanding and privacy. Contact support about inappropriate collection or sharing; we consider the young person’s capacity and the requester’s authority.

We use information to provide chosen features, restore records, coordinate play, respond to support, understand opted-in usage, diagnose faults and protect the service, or where required or authorised by law. This policy is not blanket consent or a waiver of rights.

We show the effective date and give prominent notice of material privacy changes before they take effect where practicable. We seek consent where required; updating this policy does not itself authorise new uses of previously collected information.