Trackeon Privacy Policy

Last updated: September 8, 2026

This Privacy Policy explains how Trackeon Golf, LLC ("Trackeon," "we," "us") handles information when you use the Trackeon mobile app (the "App") or our website at trackeongolf.com (the "Site"). Trackeon Golf, LLC is the company responsible for the information described in this policy.

We wrote this policy in plain language on purpose. If anything is unclear, contact us at support@trackeongolf.com.

1. Quick summary

The App analyzes camera video and microphone audio on your device. During the beta, if you allow automatic failed-capture uploads, the App uploads the short swing-capture video and related metadata when a swing-processing attempt does not produce a successful tracking result. You may also choose to upload other swing captures manually (see Section 3). We do not otherwise receive or store raw camera video or microphone audio.
We store account information, club selections, calculated shot data, and aggregate stats so the App can provide your history and other features.
If you choose automatic elevation lookup, we use your device's approximate coordinates to request terrain elevation through Google's Elevation API. You can enter elevation manually instead. Either way, your selected elevation is saved on your device for future setup.
We use your account identifier and store purchase information to provide free access, subscriptions, purchase restoration, and subscription management.
Detailed shot records and aggregate stats are kept for the life of your account unless you delete a shot or your account. We do not automatically expire older shots.
We use service providers for hosting, authentication, email delivery, app updates, diagnostics, product analytics, and our website.
If you choose to connect the App to GSPro or OpenGolfSim, the App sends calculated shot data to that software over the local-network connection you configure. It does not send raw camera video or microphone audio.
The Site uses PostHog to measure visits and interactions. Unlike analytics in the App, which is opt-in, Site analytics currently begins when a Site page loads, subject to browser and network controls.
We do not run ads, sell personal information, or share personal information for cross-context behavioral advertising.
You can delete individual shots or delete your account from inside the App. Account deletion removes active account, bag, shot, and aggregate-stat records, subject to the limited log and backup qualifications in Section 8.

2. Information processed on your device

The App uses your phone's camera (at the frame rates supported by your device) and microphone to detect a golf swing and club/ball impact. Raw camera video and microphone audio:

Is processed on-device, in real time, to calculate shot metrics.
Is not uploaded to or stored on our servers, except the short swing-capture video files described in Section 3, which the App uploads for failed swing-processing attempts during the beta if you allow automatic uploads and which you may also choose to upload manually.
Is held only in short-lived buffers used for detection and analysis, which are cleared during normal app operation.

During the beta, the App also saves a short swing-capture file on your device for each detected swing. If you allow automatic failed-capture uploads and the App determines that the swing-processing attempt did not produce a successful tracking result (a "failed swing"), it automatically uploads that capture as described in Section 3. Captures from successful swings stay on your device unless you explicitly upload them. Apart from these uploads, we do not receive the raw video or audio and cannot access or recover it.

The App also stores information locally on your device, such as authentication-session information, an installation identifier, selected settings and preferences (including your elevation and whether it was entered manually or obtained from Google), GSPro and OpenGolfSim host names or IP addresses and ports that you enter, and temporary app state. Removing the App may remove this local information, although information already stored on our servers remains associated with your account until it is deleted as described below.

3. Information we collect

Account and profile information

Depending on how you sign in, we process:

Your name, email address, password-related authentication data, and account identifier when you create an email/password account. Passwords are handled by our authentication provider; we do not have access to your plain-text password.
Your name, email address, and Google account identifier if you choose Google Sign-In.
Your Apple account identifier and identity-token information, which may include your email address or Apple private relay address, if you choose Sign in with Apple. Apple may provide a name during the sign-in flow, but the current App does not save that Apple-provided name.
Authentication events and technical records used to secure and administer your account, which may include timestamps, IP address, user-agent information, and similar security data.

Golf, shot, and session information

We store:

Your selected clubs, bag-onboarding status, and any custom club names you enter.
Calculated shot, swing, and putting data, including ball speed, club speed when available, launch angles, spin information, carry and total distance, simulated putting roll distance and time, putting trajectory summary information, smash factor and measurement provenance where available, the selected club, tracking mode, timestamps, shot number, app version, and related calculated values, including the full underlying analysis result produced for each shot.
A random per-installation device identifier, your account identifier, and a session identifier associated with a shot.
Cumulative stats such as lifetime shot count and total distance.

This is calculated or account-linked data, not the raw camera video or microphone audio. If you edit or delete an individual shot, cumulative lifetime stats are not currently recalculated. Deleting your account removes the associated cumulative-stat record.

Free access, purchases, and subscriptions

We store the date when you choose to start Trackeon's seven-day free-access period. This period is tied to your Trackeon account, does not require payment information, and is separate from any trial or introductory offer administered by Apple or Google.

When you view, buy, restore, or manage a subscription, we and our subscription-management provider, RevenueCat, may process your Trackeon account UUID, store and product identifiers, transaction and receipt metadata, purchase and expiration dates, renewal and cancellation status, entitlement status, whether the purchase occurred in a sandbox or test environment, and technical request information. Apple or Google processes your store account and payment method; Trackeon and RevenueCat do not receive your full payment-card number. We use this information to show available products, complete and restore purchases, determine whether your account has paid access, provide subscription management, prevent abuse, and troubleshoot purchase problems.

Optional elevation lookup

Our only Google Maps Platform API integration is the Elevation API. It returns an estimate of terrain elevation above sea level for a pair of latitude and longitude coordinates. Google Sign-In is a separate authentication service described above.

When you tap the location button during tracking setup, the App checks your device's location permission and requests permission if needed. With permission, it obtains approximate latitude and longitude and sends them to Trackeon's backend hosted by Supabase. Our backend verifies your signed-in, non-guest account, checks your request allowance, and sends the coordinates to Google's Elevation API. Google returns the terrain elevation for that location. We use the coordinates for this requested lookup, not continuous location tracking, and do not request precise or background location for this feature.

Google receives the coordinates and technical information associated with the API request from our backend. We do not include your Trackeon name, email address, account identifier, or authentication token in the request to Google. Google may use and retain the information it receives to provide and improve its products and services under the Google Privacy Policy. Use of the Google-provided elevation feature and content is subject to the then-current Google Maps/Google Earth Additional Terms of Service and Google Privacy Policy.

The App saves your selected elevation and its source locally, whether you enter the value manually or obtain it through the lookup. The value is shared across the App's elevation inputs and restored after restarting the App. Saving this setting does not create a location history or automatically update the value when you move. The lookup coordinates are not saved in local settings, shot records, or analytics, and the lookup handler does not maintain a database of coordinates or elevation results. To enforce request limits, our backend retains your account identifier and a limited set of lookup-attempt timestamps. Requests may also generate the infrastructure and security records covered elsewhere in this policy.

Location access and automatic lookup are optional. You can enter, replace, or clear elevation manually without granting location permission, and you can revoke location permission in your device settings at any time. Revoking permission stops future device-location access but does not clear an elevation already saved or withdraw information already sent to Google. Clear or replace the elevation input to remove or change the saved value.

Companion display sessions

The App lets you link to a companion display by scanning a QR code so calculated shots can stream to that display in real time. We process the session identifier, selected club, session status, and the same calculated shot data described above to provide this feature. Raw camera video and microphone audio are not sent to the companion display.

GSPro and OpenGolfSim integrations

The App lets you connect to supported golf-simulator software running on a computer or other device on your local network. You choose the integration and enter the destination host name or IP address and port. The App stores that endpoint on your device so you do not have to re-enter it each time. We do not store simulator endpoint information in your Trackeon account or intentionally send it to PostHog.

While connected, the App sends calculated shot measurements needed by the simulator, including ball speed, vertical and horizontal launch angles, total spin, and spin axis. It may receive connection status, acknowledgements, errors, selected-club information, handedness, and simulator player or result information. OpenGolfSim messages can include a player identifier or name and position information; the App processes this information transiently to keep the experience synchronized and does not add it to your Trackeon account. Raw camera video and microphone audio are not sent to either integration.

These integrations use the simulator providers' local-network TCP protocols. Trackeon does not add transport encryption to those local connections, so use them only on a network and with a destination device you trust. After information reaches GSPro or OpenGolfSim, that software may store, use, or transmit it under its own settings, terms, and privacy practices. Trackeon Golf, LLC does not control that downstream processing.

Beta swing-capture uploads

During the beta, the App saves a swing-capture file on your device for each detected swing. The App asks whether you want to allow automatic failed-capture uploads, and you can change that choice in Account. If you allow them, when the App determines that a swing-processing attempt did not produce a successful tracking result, it automatically sends the corresponding capture to us after you leave tracking so we can diagnose and improve swing tracking. No file search or upload runs while you are tracking. The Account screen also includes an "Upload swing captures" option on iOS and Android that lets you manually send other selected captures.

Each swing-capture file contains:

A short encoded video clip of the moments around your swing, recorded by your phone's camera. The clip may incidentally include your surroundings and any people in the frame.
Camera and capture metadata, such as camera intrinsics, lens-calibration information, the camera height you entered in the App, device orientation and gravity data, and the region of the frame used for tracking.
The on-device tracking results for that swing.

Swing-capture files do not contain microphone audio.

Uploaded captures are stored in a private storage area under your account identifier, are used only to reproduce and fix tracking problems, and are not visible to other users. There is no user-facing download path; captures are diagnostics for the development team, not a backup of your swings. This feature exists only during the beta and will be removed before general release.

Diagnostics and feedback

We use Sentry in production builds to diagnose crashes, handled errors, and performance problems. Crash reporting is on by default; you can turn it off at any time under Account → Privacy in the App. Depending on the event, Sentry may receive:

Error and crash details, code context, and breadcrumbs describing recent screens or app actions.
Device, operating-system, app version, release, update, and performance information.
Your internal Trackeon account UUID and limited session context, such as a session identifier and selected club, but not your name or email as Sentry user fields.
A feedback message you voluntarily submit through the in-App bug-report form. The form does not request your name or email and does not attach a screenshot, but you may choose to include identifying information in your message.

Performance monitoring is sampled rather than collected for every transaction; the production sampling rate is currently about 10% and may be adjusted as needed to operate the App.

App product analytics

We use PostHog in production builds to understand how the App is used so we can improve it. Product analytics runs only if you choose to share usage analytics: the App asks for this choice when you first sign in, and you can change it at any time under Account → Privacy. If you have not opted in, no usage events or session recordings are collected. If you opt in, PostHog may receive:

Usage events, such as the screens you view, buttons and features you use, settings you change, sign-in attempts and outcomes (by method, without your credentials), and companion-display session activity.
Calculated shot metrics attached to usage events, such as ball speed, launch angles, spin, and estimated carry, together with the selected club and whether the shot saved successfully.
Session recordings of App screens, in which all text inputs and all images are masked before capture. Recordings show masked screen layouts and interactions, not your camera video, and never include the raw camera or microphone data described in Section 2.
Device, operating-system, app-version, locale, and app-lifecycle information (such as when the App is opened or backgrounded), and device capability information such as whether your device supports high-speed camera capture.
Your internal Trackeon account UUID, but not your name or email as analytics identity fields.

Analytics events are batched on your device and may be stored briefly on-device before sending. Production builds send analytics; local development builds do not.

Site, forms, and website analytics

If you use the Site, we may collect:

Your email address, phone manufacturer and model, whether you have access to another launch monitor, and whether you have access to supported simulator software when you register interest in the beta.
Your name, email address, selected topic, and message when you submit a contact form.
Your email address, request type, platform, optional details, and confirmation when you submit a deletion or other privacy request.
Standard website and security data processed by our hosting provider, such as IP address, browser/device information, requested pages, timestamps, and similar request logs.
Website analytics data processed through PostHog, such as a persistent visitor identifier, page URLs and titles, referrer, page views and exits, clicks and other interactions, browser and device information, operating system, IP address and associated approximate location, and cookies or similar local-storage identifiers. Site session recordings are enabled, and PostHog masks input fields in those recordings by default. We do not intentionally use Site analytics to collect the contents you type into form fields.

We use beta-registration information to administer beta access, select testers with useful device or equipment combinations, and send relevant Trackeon updates. We use contact submissions to respond to you and privacy-request submissions to verify and fulfill the request.

Unlike product analytics in the App, Site analytics currently starts when a Site page loads and does not use the App's analytics-consent setting. The Site does not currently offer a separate control that prevents PostHog from loading. Your browser, content blocker, or network settings may allow you to block or clear cookies and similar storage.

4. How we use information

We use information to:

Create, authenticate, secure, and support accounts.
Calculate, store, display, edit, and delete shot history, bag data, sessions, and stats.
Connect the App to companion displays.
Connect the App, at your direction, to supported simulator software on your local network.
Obtain terrain elevation through Google's Elevation API when you request it, save your selected elevation for setup, and enforce lookup limits to prevent abuse.
Send account confirmation, password-reset, service, beta, and support communications.
Diagnose errors, monitor performance, prevent abuse, and improve reliability.
Understand how the App and Site are used, measure where flows succeed or fail, and prioritize improvements.
Comply with law and protect users, Trackeon, and our service providers.

Where applicable law requires a legal basis, we generally process account, shot, session, and requested-integration data to perform our contract with you; device-location access for optional elevation lookup with your consent; narrowly scoped security, diagnostics, fraud-prevention, and service-improvement data for our legitimate interests in operating a safe and reliable service; App product analytics with your consent; optional beta communications with your consent; Site analytics based on consent where we obtain it and, only where applicable law permits, our legitimate interests in understanding and improving the Site; and information as necessary to comply with legal obligations. You may withdraw consent for future processing at any time, without affecting earlier processing.

5. When we disclose information

We do not sell personal information or share it with advertisers or data brokers. We disclose information only as described here:

To the service providers listed in Section 6 so they can perform services for us.
To Google through the Elevation API when you request automatic elevation lookup, as described in Section 3. Google's own privacy policy governs its processing of the information it receives.
If reasonably necessary to comply with law, legal process, or enforceable governmental requests; protect rights, safety, and security; or investigate abuse or fraud.
In connection with a merger, financing, acquisition, reorganization, or sale of all or part of the service, subject to appropriate confidentiality and notice where required by law.
At your direction, such as when you link a companion display, connect to GSPro or OpenGolfSim, or choose a third-party sign-in method.

We require service providers acting on our behalf to use personal information only to provide the contracted services and to provide the same or equivalent protection described in this policy and required by applicable law. We review provider terms and safeguards and remain responsible for explaining our own data practices.

6. Service providers and platforms

The services that may process information for Trackeon include:

Supabase — Database, backend, account authentication, file storage, and related security logs. It processes account and profile data, authentication data, bag data, shot data, sessions, aggregate stats, and, during the beta, swing-capture files the App automatically uploads with your permission after failed swing-processing attempts or that you choose to upload manually.
Google Maps Platform — Elevation API only — Provides terrain elevation for the coordinates you choose to submit through the location button. Supabase hosts the lookup service and processes the coordinates, account verification, and request-limit records. Google receives the coordinates through that backend and processes them and associated API-request information under the Google Privacy Policy, including to provide and improve Google products and services. This is separate from Google Sign-In, Google Play, and device-level services.
RevenueCat — Subscription offering, purchase, entitlement, restoration, and customer-management infrastructure. It processes the purchase and subscription information described in Section 3, linked to your Trackeon account UUID.
Sentry — Crash and handled-error reporting, sampled performance monitoring, and user-submitted bug reports. It processes the diagnostic and feedback data described in Section 3.
PostHog — App product analytics, masked App session recordings, Site analytics, and Site session recordings, hosted in the United States. For the App, it processes the consent-gated usage events, shot-metric event properties, masked recordings, device and app information, and account UUID described in Section 3. For the Site, it processes the website analytics data described above. PostHog states that it may use customer content in aggregated or de-identified form for product and model development unless that use is disabled in the customer's service settings.
Google Sign-In — Optional authentication. Google authenticates you and provides the account information described in Section 3 when you choose this method.
Sign in with Apple — Optional authentication on supported Apple devices. Apple authenticates you and provides the account information described in Section 3 when you choose this method.
Resend — Delivery of account confirmation, verification, and password-reset email through our authentication system. It processes the recipient email address, message content and subject, and message-delivery metadata. Depending on our email configuration, delivery metadata may include open or link activity and related IP address, device, browser, or email-client information.
Expo / EAS Update — Delivery of App updates and supporting App infrastructure. It may process technical information such as operating-system and app/update versions, a randomized update identifier, IP address, and request metadata.
Webflow — Hosting and form processing for the Site. It processes the beta, contact, and deletion-request submissions and standard website/request data described in Section 3.
Cloudflare — Bot protection and abuse prevention through Turnstile on the Site's forms, including the contact, beta-registration, and deletion-request forms. It processes IP address, browser and device environment, and interaction signals from visitors who load a page containing one of those forms. Cloudflare states that Turnstile does not receive the contents entered into the protected form fields.
Apple App Store and Google Play — App distribution, payments, subscription billing, and platform-level services. Apple and Google process information under their own privacy policies when you use their stores, devices, and operating-system services.

GSPro and OpenGolfSim are user-selected third-party integrations, not service providers that process information on Trackeon's behalf. The App sends data directly to the local-network destination you specify. GSPro and OpenGolfSim may process information under their own terms, privacy policies, and software settings.

The App and Site use PostHog for first-party analytics as described above. They do not contain advertising SDKs or general-purpose advertising trackers, and analytics information is not used for cross-context behavioral advertising.

7. International processing

Trackeon is operated from the United States, and our service providers may process information in the United States and other countries. Those countries may have privacy laws that differ from the laws where you live. Where required, we and our providers use safeguards for international transfers required by applicable law. Contact us if you would like more information about the safeguards applicable to your information.

8. Retention and deletion

Shot records and aggregate stats are retained indefinitely for the life of your account. A shot remains until you delete that individual shot or delete your account. Deleting an individual shot does not currently reduce previously accumulated lifetime stats.
Account, profile, bag, and session data are retained while your account exists and as needed to provide the service.
Elevation settings are saved on your device until you replace or clear the value or remove the App's local data. This includes elevations returned by Google's Elevation API. Revoking location permission or signing out does not automatically remove this device-level setting. Elevation request-limit records contain an account identifier and a bounded set of attempt timestamps; old timestamps are pruned during later lookups, and the records are removed when the account is deleted. Google's retention of information sent to its API is governed by its privacy policy.
Free-access and subscription records are retained while needed to provide access, restore purchases, prevent repeated use of one-time offers, resolve billing issues, and meet legal and accounting obligations. Apple, Google, and RevenueCat may retain transaction records under their own policies even after you delete your Trackeon account.
Beta-registration and contact information are kept as long as reasonably necessary to administer the beta, communicate with you, respond to the request, maintain appropriate business records, or until you ask us to delete it, subject to legal requirements.
App and Site analytics events in PostHog are subject to a configured 12-month event-retention period. App and Site session recordings are subject to a configured 30-day retention period. A changed PostHog replay-retention setting applies prospectively, so an older recording may keep the retention period assigned when it was captured, and deletion after expiry may not be immediate. Analytics cookies or local-storage identifiers remain until they expire, you withdraw consent, or you clear them. The separate Site consent-choice record is kept in your browser for up to 180 days.
Beta swing-capture uploads are kept only as long as reasonably needed to diagnose tracking problems and are deleted when the beta ends at the latest. They are deleted when you delete your account, and you can request earlier deletion of your uploaded captures at any time by contacting support@trackeongolf.com. Capture deletion runs as a separate step immediately before the account record is deleted, because deleting the account removes our ability to reach the files; if that step fails, account deletion still proceeds and the capture files can remain in storage after the account is gone. Most such failures are reported to our diagnostics provider, and we will delete any file left behind this way once we know about it; you can contact support@trackeongolf.com to ask us to check.
App analytics, diagnostics, provider security logs, form submissions, and email-delivery records are retained under the applicable provider configuration and retention schedule. Some Trackeon operational event logs are retained for up to 30 days.

You can delete an individual shot in the App. You can also delete your account from the Account screen. When account deletion completes, the active account record and associated profile, bag, shot, aggregate-stat, and uploaded swing-capture records are removed, subject to the swing-capture qualification above. Some session records may remain only in de-identified form. Limited security, authentication, diagnostic, and legal-compliance records may remain for their applicable retention periods, and residual copies may remain in disaster-recovery backups until those backups cycle out. We do not restore deleted account data from backup for ordinary use. You can also request account deletion, or deletion of only your uploaded captures, waitlist email, or contact messages, at https://www.trackeongolf.com/delete-account, without installing the App or signing in. We email you within 7 days to confirm that a request is really yours, and we complete requests within 30 days. Information you submit to verify a deletion or other privacy request is used only to verify and process that request and is then deleted.

Deleting your Trackeon account does not cancel a subscription administered by Apple or Google. Cancel it through your store account if you do not want it to renew.

9. Your rights and choices

Access: You can view shot history, stats, profile information, and bag information in the App.
Correction: You can edit supported profile, bag, and shot information in the App.
Location and elevation: Automatic elevation lookup is optional. You can revoke location access in device settings, enter elevation manually, and clear or replace the saved elevation in any tracking setup screen. Clearing the setting or revoking permission does not recall data already processed by Google.
Shot deletion: You can delete individual shot records in the App. As explained above, this does not currently recalculate aggregate lifetime stats.
Account deletion: You can delete your account from the Account screen in the App, or request deletion at https://www.trackeongolf.com/delete-account without installing the App or signing in.
Analytics choice: The App asks whether to share usage analytics when you first sign in. You can change your choice at any time under Account → Privacy; when off, no usage events or session recordings are collected.
Site analytics controls: Site analytics does not use the App setting, and the Site does not currently offer a separate analytics-preference control. You can use browser, content-blocker, or network controls to block or clear Site analytics cookies and similar storage.
Crash reporting: Crash reports are on by default to keep the App reliable. You can turn them off at any time under Account → Privacy.
Communications: You can withdraw from optional beta communications by using an unsubscribe method provided in the message or contacting us.
Other requests: Use https://www.trackeongolf.com/delete-account or contact support@trackeongolf.com to request a copy of your data or exercise a privacy right that is not available in the App.

Depending on where you live, you may have rights to access, correct, delete, or receive a copy of personal information; restrict or object to certain processing; withdraw consent; and appeal or complain to a regulator. These rights are subject to applicable exceptions and may not apply in every circumstance. We do not discriminate against you for exercising an applicable privacy right.

10. Children's privacy

Trackeon is not directed to children under 13, and you must be at least 13 — or the minimum age required to consent to data processing in your country, if higher — to create an account. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided personal information, contact support@trackeongolf.com so we can investigate and delete it as appropriate.

11. Security

We use reasonable administrative and technical safeguards intended to protect information, including encrypted connections to Trackeon's Internet services and database access controls. The optional GSPro and OpenGolfSim integrations use local-network TCP protocols without transport encryption supplied by Trackeon. No system is completely secure, and we cannot guarantee that information will never be lost, accessed, or disclosed improperly.

12. Language

This Privacy Policy is currently available in English only, even though the App's interface is localized into other languages. In case of a conflict between translations, the English version governs to the extent permitted by law.

13. Changes to this policy

We may update this Privacy Policy as the App, Site, providers, or legal requirements change. If we make material changes, we will provide notice in the App, on the Site, or by other reasonable means as required by law. The "Last updated" date shows the most recent revision.

14. Governing law

This Privacy Policy is governed by the laws of the State of North Carolina, USA, without regard to conflict-of-law principles. This does not limit privacy or consumer rights that cannot be waived under the law where you live.

15. Contact us

If you have questions about this Privacy Policy or how we handle information, contact:

support@trackeongolf.com

Trackeon Golf, LLC