Par PocketYour golf, in your pocket.
Privacy policy
Learn how Par Pocket handles local golf records, optional account backup, analytics, permissions, course maps and data deletion.
Effective 19 September 2026
Optional in-app feedback
Sending feedback shares your answer, optional comment, app version, platform and relevant course or tee identifiers with PostHog, independently of optional usage analytics; it does not enable analytics. A random identifier links feedback from this device. Your account email, scores, notes and precise location are not automatically attached. Feedback is private. Supabase and Resend email it and course/platform context to the ParPocket operator. Delivery receipts store a reference and status, not your comment. Unsent feedback stays on this device and retries while the app is open and connected; clearing site data or uninstalling may remove it. Settings lets you disable proactive questions while retaining manual feedback. Feedback preferences are backed up with account preferences. Contact support with your feedback reference for access or removal.
About this policy and how to contact us
This policy covers the Par Pocket website, web app and mobile app. It explains personal information handled through local scoring, optional accounts, shared games and connected services. Par Pocket is the product name. For privacy enquiries, requests or complaints, contact the person responsible for Par Pocket at hello@parpocket.com with “Privacy” in the subject. You can request a copy of this policy in an accessible format.
Your choices and why information is used
You can keep solo scores without an account or providing a real name. An email address is needed for optional account sign-in and recovery; online shared games require an account and can use a nickname; local group scoring does not require an account. Declining a permission prevents the feature needing it from working, but manual scoring remains available. We use information to provide the features you choose, restore records, coordinate shared play, answer support requests, understand usage through the analytics described below, diagnose faults and protect the service. Information may also be handled where required or authorised by law. The privacy policy itself is not consent to every optional collection or a waiver of your rights.
What Par Pocket stores
Par Pocket stores your rounds, hole entries, course choices, personal playing benchmark, preferences, notification inbox, read status, and a small rolling set of recovery snapshots on this device using native SQLite or browser storage. Saved mapped shots can include precise coordinates and capture times. Shared-game records and guest-session credentials are also stored locally. On Android, a private active-round snapshot keeps an optional home-screen widget current and is cleared when the round ends.
What leaves your device
When you deliberately export or share a JSON backup or result image, you choose which app or destination receives it. Optional account backup sends your email address, account identifier, completed rounds, round notes, saved shot coordinates and preferences to Supabase for sign-in and restoration. Publishing or joining a shared game sends group information to Supabase even without an account; this is described separately below. Active-round solo scoring works locally. If you separately enable active-round backup in Account settings, your active scores, notes and saved shot coordinates are also sent to your private account. Conflicting versions require your choice; pausing uploads retains the existing cloud copy until account deletion. Connected services receive network information such as your IP address when contacted. Optional product analytics and separately configured crash diagnostics are described below. On Android, Google ML Kit automatically sends limited app/device information, a per-installation identifier, and OCR operational metrics to Google; it does not send the scorecard image or recognized text.
Shared games, groups and invitations
When you publish or join an online game, course group or recurring group, Supabase holds the shared record, account-linked membership and session identifiers. Safety reports record the reported player name, reason, group and involved account identifiers for moderation. Blocks prevent access to groups shared with the blocked account. Depending on the feature, the record includes player nicknames, playing handicaps, teams, course and round details, hole scores, results, change history, shared personal-round summaries, season standings, proposed playing dates, votes and attendance. Joining a course group can automatically share existing and newly completed eligible rounds for that course, including dates, scores, handicap and playing statistics; it is not a separate opt-in for each round. Hosts or scorers may enter information about other players. Tell those players and obtain their permission before sharing their information. A nickname does not make scores or course attendance anonymous. People with a valid invitation can see a limited preview and may join; members can see the shared record. Only send invitations to intended participants. Removing a member or changing an invitation cannot recall copies already seen or saved.
Group alerts and external sharing
If you enable online group alerts, Par Pocket stores your push token and alert preferences with your guest membership. Notifications pass through Expo and the applicable Apple or Google push service. The payload contains a general update or result message and a group destination identifier; device lock-screen settings control what is visible. These alerts are separate from on-device reminders. Result cards and achievements are generated for you to share; review the preview and course/date controls before sending. Recipients and destination services can retain or forward copies. Adding a tee time to a calendar may send event details to the calendar provider you select.
Support messages and information about others
If you email hello@parpocket.com, the support mailbox receives your email address, message and any attachments you choose to send, and retains correspondence needed to respond and resolve the issue. Do not send passwords, sign-in codes or guest-session credentials. Avoid including health information, identity documents or another person’s private information in notes, imports or support messages unless necessary and you have authority to do so. If we receive unnecessary personal information, we will assess whether it should be deleted or de-identified where lawful and reasonable.
Optional product analytics
Analytics stays off until you explicitly enable it in Settings. Older default-on preferences do not count as consent; those installations need a fresh choice. You can withdraw your choice in Settings. PostHog receives usage events on all platforms; Google Analytics also receives web events and Firebase Analytics receives native events. These include app opens, screen names, feature attempts and outcomes, game sessions and duration, approved lesson and filter labels, round/import events, hole count, strategy, environment, app version, platform and SDK identifiers/device information. Page views use safe screen names; automatic web clicks have text and attributes masked. Raw URLs and referrers are excluded and Do Not Track is respected. After opt-in, web analytics includes approved campaign labels and coarse search/social referral sources to understand how people find the app. Feedback analytics includes fixed sentiment, screen context and dismissal choices, without feedback IDs or free text. Events exclude scores, names, email, courses, notes, GPS, photos, OCR text and audio. Advertising consent is denied and replay is off. Opt-out stops new events without deleting earlier provider data.
Crash diagnostics
Some releases automatically send scrubbed crash diagnostics to Sentry when crash reporting is configured. These reports retain crash type, stack information, app version, OS/device information, and limited diagnostic labels. User and request details, screenshots, attachments, breadcrumbs, and session replay are disabled or removed. Crash diagnostics are separate from the Help improve Par Pocket setting: turning off product analytics does not disable configured crash reporting or Android ML Kit operational metrics.
Browser storage, hosting and marketing
Browser storage keeps golf records, preferences and account or guest-session state. Enabled web analytics also uses local storage and Google Analytics cookies or identifiers. You can opt out of product analytics in Settings and manage cookies through your browser. Clearing site data can remove rounds, sign-in state and your saved analytics choice; export important records first. Vercel hosts the website and may process requested URLs, IP addresses, device/browser details and operational logs to deliver and secure it. This hosting traffic is separate from analytics. Par Pocket does not display third-party advertising or sell your personal information. Account codes and service messages are not marketing subscriptions. Optional ParPocket emails use separate consent for the monthly note and getting-started or return reminders. Marketing is limited to two emails in any 30 days, at least seven days apart. We store your email, topic choices, verification and consent history, and delivery/suppression records. Resend delivers email and processes delivery, bounce and complaint events; Supabase stores preferences and schedules eligible sends. Reminder selection uses reliable account activity and synced-round information; unknown or stale activity is skipped. You can change choices in Email preferences or unsubscribe without signing in using an email link. Account deletion turns off linked marketing subscriptions. We retain the minimum suppression and consent evidence needed to respect opt-outs and prevent accidental re-enrolment. Confirmation links expire after 48 hours; email preference links expire after 180 days.
Tee-time searches and external services
Tee-time searches send your selected search filters, such as region, date, player count and number of holes, to the configured Par Pocket availability service. The service and its hosting provider receive ordinary network information, including your IP address. Search results link to external clubs or booking providers. Opening a link contacts that provider, whose privacy policy applies to information you enter there. Par Pocket does not take booking payments or receive your payment-card details through this search feature. If you choose an available Support Par Pocket link, contributions are handled on Ko-fi’s website under its privacy policy and payment-provider arrangements; Par Pocket does not collect card details in the app.
Account backup and JSON export
Account backup is optional. Completed rounds and preferences are validated before upload or restore, and scoring continues locally when offline. JSON backup files may contain your complete golf history and preferences; you choose where exported files are saved or which app receives them.
Retention and deletion
Local golf data remains until you clear it in Settings, choose Sign out and remove device data, clear browser site data, or uninstall the native app. Copies in exported files, device backups or other people’s devices are separate. Account deletion removes your cloud account and associated personal round/preference records; ordinary sign-out does not. After cloud account deletion, the app removes that account’s data from the device used to delete it; interrupted device cleanup is retried when the app opens. Other devices, exported files and external backups may retain copies. For shared memberships linked to the account, deletion removes the membership and redacts identifying player information; anonymised score facts can remain for other participants, and hosting may transfer to another member. A game with no other member is deleted. Separate, unlinked guest memberships and their shared records are not automatically removed by account deletion or clearing your device. Invitation expiry does not delete the shared record, and there is currently no automatic shared-game expiry. Contact hello@parpocket.com to request removal or correction of shared information, identifying the group and your nickname without sending a private session token. We will consider other participants’ rights when responding. Opting out of analytics or deleting an account does not automatically delete provider analytics, diagnostics or support correspondence. Provider logs, backups and analytics have separate retention schedules; previously sent data may not be identifiable from your email address. Contact us for help with those requests. We will retain personal information we control only while needed for the stated purpose or a legal obligation, and take reasonable steps to delete or de-identify it when no longer needed.
Service providers and overseas handling
Par Pocket uses Supabase for accounts, shared play and email preferences; Resend for email delivery; PostHog and Google Analytics/Firebase for configured analytics; Sentry for configured diagnostics; Vercel for web hosting; Microsoft Outlook for the support mailbox; Expo, Apple and Google for enabled push notifications; and the map and weather providers below. These services and their infrastructure or support teams may handle information outside Australia. MET Norway keeps forecast access logs in Norway. Other processing locations depend on the provider and the project region; Australian-only storage is not promised. Provider privacy information is linked below. Contact us for information about the locations and safeguards relevant to your request. Where Australian privacy law applies, overseas handling does not remove our obligations under that law.
Google privacy (including Firebase and ML Kit)
Access, correction and privacy complaints
You can view and edit local records and export a JSON backup in Settings. To request access to, correction of, or deletion of personal information we hold, or to complain about our handling of it, email hello@parpocket.com. Describe the information or concern and the outcome you seek. We may need proportionate identity or authority checks to protect you and other players; do not send identity documents unless we arrange a suitable method. We aim to respond within 30 days and will explain if more time is needed. Making a request or complaint is free. If access or correction is refused, we will explain the reason where lawful and how you can challenge it. If you are not satisfied after giving us an opportunity to respond, you can contact the Office of the Australian Information Commissioner (OAIC); it can consider complaints within its jurisdiction. These choices do not limit any rights you have under applicable law.
Security and data incidents
Configured account and group services use HTTPS, account access controls and restricted guest-session credentials. No storage or transmission method is completely secure. Protect your device, mailbox, backups and invitation links. If you suspect unauthorised access, contact support promptly. We will investigate suspected data incidents, take reasonable containment and remediation steps, and notify affected people and the OAIC where required by the applicable Notifiable Data Breaches scheme. We will explain practical steps affected people can take.
Younger players
Younger players should review this policy with a parent or guardian, particularly before enabling an account, online sharing or analytics. An adult entering a child’s details should consider their understanding and privacy, use a nickname where appropriate, and avoid sharing information more widely than needed. We do not verify age through the current sign-up flow. A parent, guardian or young person can contact support about information they believe has been collected or shared inappropriately; we will consider the young person’s capacity and the requester’s authority when responding.
Permissions
Location is requested when you choose Find Nearby or Use GPS. Find Nearby uses a single position on device. Optional hole GPS uses precise foreground location while its hole screen is open; it stops when you leave the screen, put the app in the background or choose Stop GPS. Ordinary GPS checks are not saved or transmitted. If you explicitly save a mapped shot, its start and finish coordinates, capture times, placement source and available device accuracy are stored with the round and included in round backups and enabled account sync. Camera or photo access is requested only for scorecard import; text recognition runs on device and images are not uploaded or stored with rounds. On Android, ML Kit may contact Google for fixes, model or hardware-compatibility information and sends the limited operational metrics described above. Temporary app-cache copies are deleted when you replace the image, finish import, or leave the import screen; Par Pocket never deletes the original library photo. Microphone and speech-recognition access are requested only for optional voice entry; on-device recognition is required and Par Pocket does not retain audio. Notification permission is requested when you enable reminders or group alerts; local reminder schedules can be changed in Settings. On iOS 17 and later, add-only calendar access is requested only when you choose Add tee time; Par Pocket cannot read your calendar. Android opens the system event editor without calendar permission. Par Pocket does not request contacts, tracking, or background location.
Course maps
The course map loads OpenStreetMap tiles over the internet. The tile provider receives your IP address, browser or app identification, and the map area viewed. Your GPS fix, scores, account details and notes are not sent to the map provider. Course selection and scoring remain available when map tiles cannot load.
Course weather
Round setup requests a forecast from MET Norway using the selected course’s coordinates, not your GPS position. MET Norway receives your IP address, app or browser identification, and the requested course coordinates, and stores access logs in Norway. Scores, notes and account details are not sent. A small forecast cache is kept on this device; forecasts are reused for at least an hour and cached results older than six hours are not shown. Native cache files may be cleared by the operating system; browser caches can be removed by clearing site data. Weather is optional for scoring, and manual conditions remain available offline.
Weather data credits
Weather data from the Norwegian Meteorological Institute (MET Norway), licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). Par Pocket converts wind speeds, rounds displayed values and summarises forecast conditions. Rain amounts are estimates for each hourly interval. UV is a cloud-free forecast estimate, not a measured reading or a cloud-adjusted forecast. Times use the course’s time zone where known.
Hole GPS and map data
GPS green distances use bundled OpenStreetMap geometry and are calculated on device without sending your location to a map provider. Supported courses are labelled GPS available. Distances are approximate, depend on phone and mapping accuracy, and do not locate today’s flag. Stale or imprecise readings are hidden. The derived course geometry is available under ODbL 1.0, © OpenStreetMap contributors. It is bundled for offline use and updated with app releases. Selected courses also include aerial hole guides and optional layup planning. Aerial tiles are loaded from MapTiler; the provider receives your IP address, app/browser identification and the selected map area, but not your GPS fix. Tiles are held in memory for display and are not bundled for offline redistribution. Imagery may be older than current conditions. If imagery fails, a bundled coordinate-drawn outline remains available. Planning targets are temporary, stay on device and are cleared when you leave the guide. Explicitly saved shot locations remain with the round; replay connects recorded endpoints by straight lines and does not measure ball flight. They show geometric distances, not safe landing recommendations. Missing features are not inferred. Opening source or download links uses your internet connection.
Nearby facilities and data credits
Nearby facility data © OpenStreetMap contributors, available under the Open Database Licence (ODbL) 1.0. Par Pocket filters, groups and rounds distances from mapped features within 1.2 km of the course pin. Nearby facilities may be outside the course, restricted or closed; missing map data does not mean a facility is absent. A dated snapshot is bundled for offline use. The app checks Par Pocket’s website for an updated snapshot at most once a day. The website receives your IP address and app/browser identification; selected course coordinates, GPS, scores and account details are not included in that request. Opening a facility link sends you to OpenStreetMap. Maintainers refresh the shared snapshot from OpenStreetMap; app installations do not query Overpass.
Daylight calculations and software credit
Sunrise and sunset are calculated entirely on device using the course location and date. They are approximate astronomical times; terrain and local conditions can affect usable daylight. No external request is made. Calculations use SunCalc 2.0.2, distributed under the BSD 2-Clause licence. Copyright (c) 2026, Volodymyr Agafonkin All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Changes and contact
We will keep this policy up to date and show its effective date. For material changes to how we handle personal information, we will provide a prominent notice in the app or website before the change where practicable, and obtain consent where required. Updating this policy does not itself authorise a new use of previously collected information. Questions can be sent to hello@parpocket.com.