Trackeon Privacy Policy

Last updated: October 26, 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. Automatic failed-swing uploads are off unless you opt in under Account → Privacy. If enabled, the App can upload available short failed-swing videos and related diagnostics after you leave tracking, including recent failed captures saved while uploads were off (see Section 3). Camera and microphone permission is required for tracking and scan flows. The App does not intentionally send raw camera or microphone streams as analytics events, but exclusion of the native tracker preview from session recordings has not been independently verified.
• We store account information, club selections, calculated shot data, and aggregate stats so the App can provide your history and other features. We also process account-linked free-access and subscription information through RevenueCat and your device's store to check access, handle purchases and restores, and measure subscription activity.
• 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. The selected elevation is saved on your device and may be included in shot records stored with your account.
• 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 third-party services for hosting, authentication, email delivery, app updates, diagnostics, analytics, and our website. Their roles and the information they receive depend on the service and your choices.
• If you choose to connect the App to GSPro, OpenGolfSim, or Muni Golf, the App sends calculated shot data to that software over the local-network connection you configure. It does not intentionally send raw camera video or microphone audio through those simulator integrations.
• The Site displays an analytics choice banner. On an initial visit, PostHog is initialized only when the saved choice is Accept; Reject or no saved choice does not initialize it. If you change an earlier Accept to Reject after PostHog has finished loading, the Site saves Reject and calls PostHog's stop-recording and opt-out methods. If PostHog is still loading, those calls are skipped, so collection may begin despite the changed choice. You can reopen Privacy settings to change your choice. We have not determined whether the Site's consent setup meets every legal requirement in every region where it is accessible.
• We do not run ads, sell personal information, or share personal information for cross-context behavioral advertising.
• You can delete individual shots or request account deletion from inside the App. Account deletion removes active account and associated records when the relevant deletion steps succeed; uploaded capture-file cleanup is a separate best-effort step. See 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 intentionally sent as a live camera or microphone stream. Short swing-capture video files may be uploaded as described in Section 3. App session recordings are collected when enabled, but exclusion of the native tracker preview from those recordings has not been independently verified.
• Is held only in short-lived buffers used for detection and analysis, which are cleared during normal app operation.

The App can save a rolling set of up to ten recent failed-swing capture files on your device for diagnosis. Automatic failed-capture uploads are off unless you opt in under Account → Privacy, as described in Section 3. Putts and successful swings are not uploaded automatically, and the App has no screen for browsing or manually uploading local capture files. Apart from these optional uploads, we do not intentionally send raw camera video or microphone audio to our servers. The tracker preview's exclusion from session recordings has not been independently verified. The camera is used for swing tracking and scanning a companion-display QR code; the microphone detects impact. Camera and microphone access is required before tracking-related setup and QR scanning, and denying either permission blocks those flows. Approximate foreground location is optional and requested only for elevation lookup; manual elevation entry is available without location access.

The App also stores information locally on your device, such as authentication-session information, a random installation identifier, selected settings and preferences (including your elevation and whether it was entered manually or obtained from Google), and GSPro, OpenGolfSim, or Muni Golf host names or IP addresses and ports that you enter. It can retain up to ten recent failed-swing capture files for diagnosis, replacing older files as new failed captures are saved. There is no user-facing capture browser or manual-upload screen. Signing out or deleting your account does not itself remove these local files or all device settings. Removing the App may remove 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 may include timestamps, IP address, user-agent information, and similar security data. Backend security and operational audit records may include your account identifier, event source and message, timestamps, an associated session identifier, and limited event metadata. The database audit log is pruned daily for records older than 30 days; other Supabase or provider logs may have different retention periods that have not been verified.

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, launch angles, spin information, carry and total distance, simulated putting roll distance and time, putting trajectory summary information, 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 raw camera video or microphone audio. A shot record can include the elevation value used when calculating the shot. If you edit or delete an individual shot, cumulative lifetime stats are not currently recalculated. Deleting your account removes the associated cumulative-stat record when account deletion completes.

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.

Simulator integrations: GSPro, OpenGolfSim, and Muni Golf

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. The Muni Golf integration also sends supported calculated shot information to the Muni Golf software you select. The App does not intentionally send raw camera video or microphone audio through these integrations. We have not verified the current Muni Golf provider terms and downstream data practices for this App's local integration.

These integrations use provider-defined local-network protocols. Trackeon does not add transport encryption to the GSPro, OpenGolfSim, or Muni Golf local-network connections, so use them only on a network and with a destination device you trust. After information reaches a simulator, 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.

Optional failed-swing capture uploads

When swing processing fails or finishes without usable launch metrics, the App can save a short swing video and diagnostic sidecar on your device and record it for a possible later upload. It retains a rolling set of up to ten recent failed captures even while uploads are off. Automatic uploads require an account-level opt-in under Account → Privacy. If you enable them, available retained failed captures, including captures saved while uploads were off, and future failed captures may upload after you leave tracking and while the App is in the foreground. No file search or upload runs while you are tracking. Putts and successful swings are not uploaded automatically, and the App does not provide a capture browser or manual-upload screen. You can turn automatic uploads off at any time under Account → Privacy. Your saved account-level choice remains in effect until you change it. Turning uploads off stops further automatic transfers where the App can apply that choice; it does not recall information already sent or delete local or uploaded files. You can request deletion of uploaded captures as described in Section 8.

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 and are intended for diagnosing tracking problems. They are not presented to other users, and the App has no user-facing download path. The current Supabase bucket has no configured automatic expiration rule, so we do not state a fixed retention period. Account-deletion cleanup is attempted separately and may fail; files left behind may require a separate deletion request.

Diagnostics and feedback

We use Sentry in release builds to diagnose crashes, handled errors, and performance problems. Crash reporting is on by default; you can turn it off under Account → Privacy in the App. Depending on the event and provider defaults, Sentry may process error data, technical context, request URLs, and console or network breadcrumbs:

• Error and crash details, code context, and breadcrumbs describing recent screens or app actions.
• Device, operating-system, app version, release, update, and performance information; network information such as IP address; request URLs; and technical breadcrumbs or log data associated with errors.
• Your internal Trackeon account UUID and limited session context, such as a session identifier and selected club. The App does not intentionally set your name or email as Sentry user fields, but error context and URLs may contain information supplied to or generated by the App.
• 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 release-build sampling rate is currently about 10% and may be adjusted. Some native crash reports already queued by the operating system may be sent before the App can load your saved reporting preference. Turning reporting off prevents later reports where the App can apply that choice; it cannot recall information already sent.

App product analytics

We use PostHog in release builds to understand how the App is used so we can improve it. App analytics is off unless you opt in after signing in, and the saved choice applies to your account. You can change it under Account → Privacy. PostHog event and session-recording capture requires a loaded, affirmative choice for the currently signed-in account; signed-out capture is disabled. Development builds can also send analytics if explicitly opted in. This PostHog setting is separate from RevenueCat's purchase, access-check, and paywall-view processing described above. If App analytics is on, 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, with text inputs and image views configured for masking. The tracker camera preview uses a native rendering surface whose exclusion from session recordings has not been independently verified, so we cannot promise that all camera imagery is excluded from recordings. The App does not intentionally send raw camera or microphone streams as analytics events.
• 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. Release builds send analytics when the preference allows it; development builds do not send by default, but an explicit opt-in can enable them.

Site, forms, and website analytics

If you use the Site, we may collect:

• When beta registration was open, we collected your email address, phone manufacturer and model, whether you had access to another launch monitor, and whether you had access to supported simulator software. Beta registration is now closed.
• 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 after you choose Accept, 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 may then be collected, 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 used beta-registration information to administer beta access and select testers with useful device or equipment combinations. Any retained registration records are handled under Section 8; closure of registration does not itself erase earlier submissions. We use contact submissions to respond to you and privacy-request submissions to verify and fulfill the request. Optional Trackeon updates remain subject to your communication choices.

Site analytics uses a separate choice from App analytics. The Site displays an analytics banner with Accept and Reject options and saves your choice in your browser's local storage. On initial load, the Site initializes PostHog only when the saved choice is Accept; Reject or no saved choice does not initialize it. A persistent Privacy settings control lets you reopen the banner. If you change an earlier Accept to Reject after PostHog has finished loading, the Site saves Reject and calls PostHog's stop-recording and opt-out methods, but it does not unload the SDK. If PostHog is still loading, those calls are skipped, so collection may begin despite the changed choice. The actual effect of the SDK methods on immediate cessation has not been verified. You can also use browser, content-blocker, or network settings to block or clear cookies and similar storage. We have not determined whether this consent setup meets every legal requirement in every region where the Site is accessible.

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.
• Request terrain elevation from Google's Elevation API when you ask for a lookup. The deployed backend verifies a signed-in, non-guest account, applies limits of 5 requests per minute and 100 per rolling 24 hours, then forwards your coordinates to Google over HTTPS.
• Send account confirmation, password-reset, service, 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.

The legal basis for processing depends on the purpose and the law that applies. We use account, shot, and session information to provide requested App features; process optional device location for a lookup you request; use diagnostic, security, and operational data to maintain and protect the Services; and use App analytics based on your choice. On initial Site load, PostHog is initialized only when the saved choice is Accept. If you change the choice using Privacy settings, the Site records Reject. When PostHog has finished loading, it calls the SDK's stop-recording and opt-out methods; if the SDK is still loading, those calls are skipped, so collection may begin despite the changed choice. The SDK methods' effect on immediate cessation has not been verified. We have not determined whether this consent setup meets every legal requirement in every region where the Site is accessible. Where processing relies on consent, you may withdraw it for future processing 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 Trackeon's backend forwards a lookup. The deployed function sends the selected coordinates over HTTPS, without your Supabase key or user access token. Applicable Maps Platform terms and Google's account-level logging and retention settings remain under review.
• 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, OpenGolfSim, or Muni Golf, or choose a third-party sign-in method.

The listed services can act as service providers, independent controllers, or platform providers depending on the service and processing. We do not claim that every provider is contractually restricted to our instructions or that every transfer safeguard has been confirmed. Contact us if you need information about a provider's role or transfer safeguards for a particular service.

6. Service providers and platforms

The services that may process information for Trackeon include:

• Supabase — Database, backend, account authentication, file storage, rate-limit records, and related security logs. The current project is configured in Supabase's us-east-1 United States region. It processes account and profile data, authentication data, bag data, shot data, sessions, aggregate stats, account-linked elevation request timestamps, limited backend audit events, private free-access eligibility and grant records, and swing-capture files uploaded with your permission, including retained earlier uploads. The captures bucket is private and has no configured automatic expiration rule. The database audit log is pruned daily for records older than 30 days. Other provider log and backup retention settings have not all been verified.
• Google Maps Platform — Elevation API only — Provides terrain elevation for coordinates submitted through the location button. The App sends those coordinates to Trackeon's Supabase-hosted backend. Its deployed get-elevation function verifies a signed-in, non-guest account, enforces per-account request limits, and forwards the coordinates to Google's Elevation API over HTTPS without sending your Supabase key or user access token. The function writes account-linked rate-limit timestamps through a database RPC but does not write lookup coordinates to the database or explicitly log them; infrastructure logs and Google account settings remain unverified. Google's applicable Maps Platform terms require confirmation for this integration. This is separate from Google Sign-In, Google Play, and device-level services.Google Privacy Policy
• 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. See Sentry's privacy policy (https://sentry.io/privacy/) and data-collection documentation (https://docs.sentry.io/platforms/react-native/data-management/data-collected/). Production project settings, provider retention, and the account's DPA status have not been independently verified.Sentry Privacy PolicySentry Data Collection
• PostHog — App product analytics, App session recordings, Site analytics, and Site session recordings. For the App, PostHog can process usage events, shot-metric event properties, device and app information, account UUID, and screen recordings as described in Section 3. Inputs and image views are configured for masking, but exclusion of the custom native tracker camera preview has not been verified. For the Site, it processes the website analytics data described above. See PostHog's privacy policy (https://posthog.com/privacy) and data processing addendum (https://posthog.com/dpa); whether Trackeon's account has an executed addendum and which provider options are enabled have not been verified.PostHog Privacy PolicyPostHog DPA
• 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.
• Account email delivery — Supabase Auth sends account confirmation, verification, and password-reset email. The deployed SMTP provider and its tracking settings have not been verified. If this route uses Resend, it may process the recipient email address, message content and subject, and delivery metadata that may include open or link activity and related IP address, device, browser, or email-client information depending on account configuration.
• 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 contact and deletion-request submissions and standard website/request data described in Section 3, and may retain submissions made while beta registration was open.
• Cloudflare — Bot protection and abuse prevention through Turnstile on the Site's forms, including contact and deletion-request forms. It also protected beta registration while that form was available. It processes IP address, browser and device environment, and interaction signals from visitors who load a page containing a protected form. Cloudflare states that Turnstile does not receive the contents entered into the protected form fields.
• Apple App Store and Google Play — App distribution 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, OpenGolfSim, and Muni Golf are user-selected third-party integrations, not service providers that process information on Trackeon's behalf. The App sends data to the local-network destination you specify. These products 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.

RevenueCat; Apple App Store and Google Play — RevenueCat processes account-linked access, promotional-entitlement, purchase, and subscription information and paywall-view events as described in Section 3. Apple and Google process store purchases, renewals, cancellations, and refunds. Their own privacy policies apply to their handling of this information.

7. International processing

Trackeon is operated from the United States. The Supabase backend project is configured in the us-east-1 region in the United States. Other third-party services may process information in the United States or other countries. The App is not yet listed in app stores; intended distribution regions and other provider-specific processing locations are still being determined. Where we have confirmed applicable transfer safeguards, we can provide information on request.

8. Retention and deletion

• Shot records and aggregate stats are retained for the life of your account unless you delete a shot or your account. We do not automatically expire older shots. 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. The backend removes ended sessions with no players or shots after seven days; this cleanup does not apply to every session. When an account is deleted, its player/viewer references in retained session rows are set to null, but rows and session identifiers, timestamps, or information about other participants may remain.
• Elevation settings and shot elevation values are saved on your device and may also be stored with shot records until the shot or account is deleted. The App stores elevation returned by Google's Elevation API; Google's current Elevation API policies may restrict this storage, which remains under review. The backend stores account-linked recent lookup timestamps to enforce 5-per-minute and 100-per-rolling-24-hour limits; account deletion removes these records, and timestamps older than 24 hours are trimmed on a later successful budget reservation. The deployed function writes those rate-limit timestamps but does not write lookup coordinates to the database or explicitly log them; provider infrastructure logging has not been verified. Google's retention of information sent to its API is governed by applicable Google terms and policies.
• Earlier beta-registration and current contact information are kept as long as reasonably necessary to address earlier beta participation, communicate with you according to your choices, respond to requests, or maintain appropriate business records, subject to applicable deletion rights and legal requirements.
• Uploaded swing captures have no configured automatic expiration rule in the current Supabase storage bucket. Account-deletion cleanup is a separate best-effort step and may fail, so files may remain after account deletion. You can request earlier deletion of uploaded captures at any time by contacting support@trackeongolf.com.
• App and Site analytics events and recordings are subject to provider settings. Current account-level retention settings have not been verified, so we do not state a fixed period. Analytics identifiers may remain until they expire or are cleared from the device or browser. App diagnostics, provider security logs, form submissions, and email-delivery records may have different retention schedules that have not been fully verified.

You can delete an individual shot in the App. You can also start account deletion from the Account screen or request it at https://www.trackeongolf.com/delete-account without installing the App or signing in. Account deletion removes the active account and associated profile, bag, shot, and aggregate-stat records when the database deletion succeeds. In retained session rows, references to the deleted user as a player or viewer are set to null; the session row and its identifiers, timestamps, or information about other participants may remain. Ended sessions with no players or shots are automatically removed after seven days; other sessions may remain. Uploaded-capture cleanup is separate and best-effort, so some files may remain after account deletion. Limited security, authentication, diagnostic, and legal-compliance records may remain for applicable periods, and residual copies may remain in backups until those backups cycle out. The web request page says requests are confirmed within 7 days and completed within 30 days; this processing promise should be checked against current operating practice. Information submitted to verify a privacy request is intended to be used to verify and process it.

Free-access and subscription records. We retain private free-access eligibility and grant records for access administration and to prevent repeated grants. RevenueCat and the stores may retain customer, entitlement, transaction, support, and legally required records under their own retention practices. We have not verified a fixed retention period for every such record. Deleting your Trackeon account does not cancel a store subscription and does not automatically erase RevenueCat customer or purchase records or store billing history. Cancel a subscription through the store that processed the purchase. Contact support@trackeongolf.com for a related privacy request; requests remain subject to applicable legal and recordkeeping requirements.

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: App product analytics through PostHog requires your opt-in. You can change your choice at any time under Account → Privacy. Turning it off disables PostHog events and session recordings; it does not turn off separate RevenueCat purchase, entitlement, and paywall-view processing.
• Site analytics controls: Site analytics does not use the App setting. On initial load, PostHog is initialized only when the saved Site choice is Accept; Reject or no saved choice does not initialize it. You can choose Reject or reopen Privacy settings at any time. After an earlier Accept, Reject is saved. If PostHog has finished loading, the Site calls its stop-recording and opt-out methods, but does not unload the SDK; if it is still loading, those calls are skipped, so collection may begin despite the changed choice. The SDK methods' effect on immediate cessation has not been verified. You can also use browser, content-blocker, or network controls to block or clear Site analytics cookies and similar storage.
• Crash reporting: Crash reporting is on by default. You can turn it off under Account → Privacy. Some native crash reports already queued before the preference loads may still be sent.
• Communications: You can withdraw from optional Trackeon 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, OpenGolfSim, and Muni Golf integrations use local-network 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

Trackeon Golf, LLC reserves the right to amend, modify, or replace this Privacy Policy at any time, in its sole discretion, subject to applicable law. The revised Policy will be posted on the Site and will take effect on the effective date stated with the revisions or, if no effective date is specified, upon posting, except where applicable law requires otherwise. We will provide notice of material changes and obtain consent before implementing a change where required by applicable law. No amendment authorizes a materially different use or disclosure of previously collected personal information unless all applicable notice, consent, and other legal requirements have been satisfied. Continued use of the Services does not constitute consent where applicable law requires affirmative consent. The "Last updated" date identifies 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 | 267 Timber Dr PO Box 1202, Garner, NC 27529