Privacy Policy

Effective Date: November 8, 2026
Last Updated: November 8, 2026
Policy Version: 2026-11-08

Flighting Inc. ("Flighting," "we," "us," or "our") operates the Flighting mobile application and website (collectively, the "Service"). This Privacy Policy explains how we collect, use, disclose, and protect your personal information when you use our Service.

By using Flighting, you agree to the collection and use of information in accordance with this Privacy Policy. If you do not agree with this Privacy Policy, please do not use our Service.

1. Information We Collect

1.1 Information You Provide Directly

When you create a Flighting account and use our features, we collect:

• Account Information: Full name, email address, and password (stored using one-way cryptographic hashing)
• Phone Number: Optional. Used for account security, transactional notifications, and, only if you grant separate express consent through the in-app prompt or account settings, to send marketing and promotional SMS / text messages. Consent to receive marketing texts is not required to use the Service and may be revoked at any time
• USGA Handicap ID (GHIN Number): When you choose to link your official handicap
• Profile Information: Equipment details ("What's in the Bag"), club affiliation, home course, and other optional profile fields
• Member Experience Selection: Your selection of the Men's Experience or Women's Experience, which you can change in account settings. We use this product preference for feature access, individual rankings, and personalization. Members who have not saved a selection currently rank with Men's Experience members; Women's Experience rankings remain separate. We do not independently verify the selection as legal sex, gender identity, or eligibility under another organization's rules
• Shipping Address: When you make purchases, claim rewards, or redeem welcome offers
• Support Tickets: Content of support requests and in-app feedback (ideas, gear requests, bug reports) you submit through the platform
• Self-Reported Rounds: If you log a round manually, we store the course, tees, date, total and any hole scores you enter. Unless you turn off sharing when you log it, the round is shown in your activity feed according to your activity-visibility settings. Self-reported rounds may be reviewed by our staff for accuracy, and you can edit or delete them within 48 hours of logging. If the same round is later imported from the USGA, we link the two and hide the self-reported copy so the round is not counted twice
• Inquiries & Messages to Our Team: When you reach out through an in-app contact or inquiry form (such as the "Contact the founders" form), we collect the name, email address, subject, and message content you provide so we can respond. We also automatically record the IP address and browser user-agent associated with the submission, which we use for support, abuse prevention, and traceability (see Section 1.9). Submissions are stored in our database, and the messages are delivered to our team by email

1.2 USGA Handicap Data

When you provide your USGA Handicap ID (commonly called your GHIN number), you authorize us to retrieve and store the following information from the USGA:

• Official Handicap Index
• Score history and posting records
• Scoring statistics (fairways hit, greens in regulation, putts per round, etc.)
• Course names and locations where rounds were played
• Revision dates and trends
• Club affiliation (if applicable)
• Any other data available through the USGA API

Round and score data in Flighting is imported from the USGA's GHIN system, except for any rounds you choose to log yourself (see Section 1.1). Linking your USGA Handicap ID lets us retrieve your Handicap Index and publicly available scores. To import your full round details, such as course, tee, and hole-by-hole information, you approve data sharing with Flighting through the USGA: you give us the email address on your GHIN account, the USGA emails you an approval request, and you approve Flighting in that email. You can use Flighting without this approval, but some round-based features require it.

By entering your USGA Handicap ID, you explicitly consent to our retrieval and use of this official USGA data.

1.3 Financial and Transaction Data

When you use our payment and financial features, we collect:

• Purchase History: Records of items purchased, order details, and transaction amounts
• Personalized Pro Shop Access: Permanent entitlement records for products you earned or purchased through milestones, weekly or micro challenges, or completed purchases. We also use account and catalog information to show the base assortment
• Store Credit Activity: Credits, debits, member-to-member store-credit transfers, promo code redemptions, and game-bounty credit settlements. Historical payout requests, if any, may also be present in account-linked records; the current credit feature is not a general cash payout service
• Verified-USGA Hat Claims: If you seek the one-time complimentary designated hat, we record the linked member, designated offer, claim eligibility and status, reservation and checkout timestamps, Stripe checkout session identifier, and Shopify order identifier when fulfilled. Your GHIN verification status and claim history determine eligibility
• Stripe Customer and Checkout Data: The identifier linking your Flighting account to your Stripe payment profile, checkout session and payment status, amounts, shipping and applicable tax, and store-credit transactions for eligible purchases
• Shopify Customer and Fulfillment Data: The identifier linking your account to Shopify, product and order details, shipping information, fulfillment status, and Shopify order identifiers for applicable purchases or rewards

We do not store your complete credit card number, CVV, or full payment card details. Payment processing is handled entirely by Stripe.

1.4 Photos, Images, and Device Camera Access

When you use the AI Bag Scanner or AI Scorecard Scanner features, or add a profile photo:

• Photos you upload or capture using the device camera for Bag Scanner or Scorecard Scanner are sent to OpenAI's vision API for club identification (Bag Scanner) or hole-by-hole score extraction (Scorecard Scanner)
• The Flighting mobile application or your browser may ask for access to your device camera so you can take a photo within the app for scorecard scanning, bag scanning, or your profile photo. If you choose an existing photo instead, your device's photo picker lets you pick a specific image, and we receive only the image you pick
• Camera access is used only to capture images you choose to take for these features (Bag Scanner, Scorecard Scanner, and profile photo); we do not access or use the camera for any other purpose
• Images are compressed client-side before upload to reduce data transmission
• Bag Scanner photos are transmitted to OpenAI for processing and are not permanently stored in Flighting's database after the request is completed
• Scorecard Scanner photos are kept in private storage for up to 30 days so we can check scan accuracy and troubleshoot failures, and are then deleted automatically. The extracted hole-by-hole score data and scan results are stored in a scan log linked to your account so we can display results, investigate scan accuracy, troubleshoot failures, and support the feature. Authorized administrators may review these scan logs, and the photo while it is still stored, for those purposes
• Scorecard scan logs are removed from Flighting's active database when your account is deleted. A scan photo that is still within its 30-day period is deleted on that 30-day schedule, subject to the limited retention described in Section 4.3
• Profile photos: If you add a profile photo, the image you pick or take is resized on your device to a small image (about 512 pixels) before upload. It is stored in our cloud object storage and shown with your name to other members, for example on your profile, in leaderboards, and in messages. The stored image is served from a web address that does not require sign-in, so anyone who has that address can view it. Replacing the photo or deleting your account removes it from your profile, but the image file may remain in storage until it is cleaned up. Profile photos are not sent to OpenAI
• Monthly Wrapped images: If you export your Monthly Wrapped photo carousel, the images are created on your device and handed to your device's share sheet or saved as downloads. Where they go from there, such as your photo library or a social media app, is your choice and is governed by that app's or platform's terms and privacy practices
• You are responsible for verifying extracted results before saving
• OpenAI's data handling of transmitted images is subject to OpenAI's Privacy Policy

1.5 AI Conversation and Recommendation Data

When you use the Danny AI Caddie feature:

• Your conversations and messages are stored in our database linked to your account
• Conversation content is sent to OpenAI for response generation
• You can delete your conversation history at any time

When you use Flighting Intelligence in Round Analytics:

• Your Round Analytics questions and responses are stored in a separate conversation history linked to your account
• Your messages and a privacy-minimized, server-generated summary of your stored scores, valid hole-by-hole details, course history, Handicap Index or Flight Tier context, and any available anonymous flight comparison are sent to OpenAI to generate evidence-based answers
• The feature is limited to analysis of your own round-performance data and may state that the available sample is too small to support a reliable conclusion
• You can restart and remove the current Round Analytics conversation from the feature

When you use the AI Practice Recommendation feature:

• Your USGA round history, scoring statistics, hole-by-hole performance data, and player profile information are sent to OpenAI for analysis and personalized practice plan generation
• Generated weekly practice plans and drill completion progress are stored with your account so you can revisit them. Other AI-generated tips may also be saved for later display

1.6 Social and Community Data

• Follow Relationships: Records of who you follow and who follows you
• Game and Challenge Data: Participation records, game outcomes, bounty amounts, challenge results
• Weekly Challenge Data: Participation records, challenge results, and prize eligibility for community-wide weekly challenges
• Clubhouse Posts and Responses: Questions, discussion posts, and replies you submit in The Clubhouse forum, including post titles, body text, and response content
• Clubhouse Upvotes: Records of responses you upvote in The Clubhouse
• Clubhouse @Mentions: Records of users you tag using the @mention feature in Clubhouse posts and responses, and mentions of you by other users
• Notifications: In-app notification records and read status
• Activity Feed: Records of milestones, rounds, and achievements shared in the community activity feed with the audience you choose in your visibility settings
• Profile Performance Insights: Recent form, season highlights, and detailed achievement information derived from your rounds and milestones. We apply your activity visibility setting when deciding which other members may see these details
• Monthly Wrapped: A frozen monthly snapshot of selected golf, practice, challenge, follower, and community engagement statistics. Each snapshot has a unique share token. The snapshot becomes accessible to others when you choose to distribute its public link, as described in Section 3.1
• Direct Message Content: Text messages you send and receive in one-to-one and group conversations, including conversations associated with Host Network and Local Play. Each message is limited to 2,000 characters
• Pro Shop Reviews: Your product rating and review text, linked to your account and a qualifying order and order item used to check purchase eligibility. A review removed from public view has its text cleared, but its rating, order references, account association, and removal/moderation status may remain in a limited record for moderation, fraud prevention, and purchase-verification integrity.
• Messaging Metadata: Timestamps, sender/recipient identifiers, and message read status
• Block and Report Records: Records of users you have blocked or reported, and reports filed against your account. A report records the reason you choose, any details you add, and which message, Feed post, or comment it concerns. A report about a Feed post or comment also stores a short excerpt of the reported content so moderators can review it even if the content changes
• News Feed Comments: Comment text you post on news articles, timestamps, and the associated news article identifier
• Edit Timestamps: When you edit a news feed comment or a Clubhouse response, we store the timestamp of the edit (editedAt) alongside the updated content
• Activity Visibility Settings: Your chosen audience for activity feed posts and round-derived profile details (everyone, your Flight Tier, your club, your followers, or an empty audience selection), which we store and apply when deciding who can see that activity and those details. "Your club" means members who share a USGA/GHIN home club with you or who belong with you to the same private group on Flighting, such as The Stake Club
• Daily Trivia Participation: The answer you select for each daily trivia question, whether it was correct, and any store credit awarded for correct answers (credits are applied through Stripe as described in Section 1.3)
• Feed Engagement: Which feed posts you view and interact with (such as impressions and taps), used to measure engagement and improve feed content
• Club News Media: Images uploaded by authorized club staff for club news posts, together with the associated club, post content, publication timing, and object-storage path

1.7 Referral Program Data

When you participate in our referral program, we collect:

• Referral Code: A unique code assigned to your account for sharing with prospective members
• Referral Relationships: Records of which users you referred and who referred you
• Credit Activity: Referral credits earned and applied to your account balance
• Referral Link Visits: When someone opens a referral link, we temporarily record the referral code together with the visitor's IP address and browser user agent. This is used only to reconnect the referral code to the new account if the visitor installs our mobile app before signing up (since app store installs would otherwise lose the code). These records are short-lived and are used solely for referral attribution
• Fraud Prevention Signals: We process IP addresses and basic device information when you create an account, in hashed form that does not store your actual IP address, to detect and prevent fraud and abuse of our referral and rewards programs. This data is deleted after 180 days

1.7A Local Play Discovery

Local Play is an optional discovery feature available to signed-in adult Flighting members in beta. If you choose to opt in, we collect the ZIP code you voluntarily provide and use a ZIP centroid to make approximate matches within approximately 50 miles. We do not show your exact ZIP code, street address, or coordinates to other members, and Local Play does not use continuous GPS tracking.

You may pause your visibility at any time. You may revoke consent and delete your Local Play profile at any time; this stops future discovery matching. Local Play is currently included without a separate charge, but joining Flighting or buying another membership does not opt you into discovery. Profiles, identities, availability, and approximate locations are not guaranteed.

1.7B Host Network Membership

If Host Network is available to you, we process your GHIN verification status, private-club affiliation and supporting eligibility evidence, and your free Host Network opt-in status. Host Network is provided without a charge, so we do not process any subscription, checkout, renewal, billing, cancellation, grace-period, or pause data for it. Eligible active Hosts are visible in the Host directory to other eligible active Hosts. Directory entries may include name, profile image, club, Flight Tier, and Host status. Host messages use the direct-message data and safety records described in Section 1.6.

1.8 Content Interaction Data

• News Feed Activity: Interaction with aggregated golf news content sourced from third-party RSS feeds
• Weather Queries: To show local weather, you can enter a city or ZIP code or tap "Use my location" to let your browser or device provide coordinates through its location prompt. We ask for device location only after you tap that option; in a web browser where you allowed it before, the widget may refresh that location on a later visit until you clear the saved weather location. The location and coordinates are cached in your browser; weather requests also send coordinates to our server, which requests forecasts from Open-Meteo. City or ZIP searches are sent to our server for geocoding. The weather feature does not save these coordinates to your account profile. You can clear the cached weather location in the feature and manage device location permission in your browser or device settings
• Training Center Usage: Engagement with training content and educational materials

1.9 Usage and Performance Data

We automatically collect:

• Device Information: Device type, operating system, browser type, app version
• IP Address and Approximate Location: When you use the Service, our servers receive your IP address and request headers. We use these to derive an approximate location (such as country and region, for example, from a Cloudflare cf-ipcountry/cf-region-code header or a server-side IP lookup), which we use for jurisdictional compliance (such as determining whether GDPR or CCPA privacy notices apply to you) and for shipping and region context. This is coarse, network-level location and is not the same as the precise GPS coordinates described in Section 1.8
• Performance Metrics: Milestones achieved, progress tracking, leaderboard rankings
• Flight Tier Classification: Your automatically assigned skill-level tier (FT+ through FT5) derived from your current USGA Handicap Index, used for leaderboard segmentation, Strokes Gained peer comparisons, and competition grouping
• Activity Data: App usage patterns, features accessed, session duration
• Analytics Data: Page views, click patterns, and user flows (collected via Google Analytics)
• Session Replay and Heatmap Data: When analytics tracking is permitted, Microsoft Clarity may collect mouse movements, clicks, scrolls, page interactions, and session recordings to help us understand how people navigate the Service. Avoid entering sensitive information into fields not intended for it
• Marketing Attribution (Client-Side): When marketing tracking is permitted under the regional consent process in Section 8, conversion events, browsing activity, device and browser information, and ad performance data may be collected through the Meta (Facebook), X (formerly Twitter), Reddit, OpenAI advertising, TikTok, and AppLovin AXON pixels. Browser advanced matching may include your account identifier, email, phone, and, for Meta, available first and last name, city, state, ZIP, country, and date of birth. We do not collect date of birth solely for advertising. Identifiers passed to browser pixels are normalized, and the providers handle matching under their own practices
• Marketing Attribution (Server Side): When marketing tracking is permitted under the regional consent process in Section 8, we send selected conversion events to Meta, X/Twitter, Reddit, OpenAI advertising, TikTok, and AppLovin AXON. For Meta, available email, phone, first and last name, city, state, ZIP, country, date of birth, and Flighting account ID are normalized and SHA-256 hashed before server transmission; IP address, browser user agent, and Meta browser/click IDs are sent without that hashing. Other networks receive available identifiers and event/browser signals according to their integrations. Browser and server copies of eligible events use a shared event identifier for deduplication
• First Touch Attribution: When you first arrive, before advertising pixels load, we may read UTM campaign parameters, the referring website, the landing page variation, and supported Meta, X, or Reddit click identifiers from the page URL. We store that first touch information locally in your browser so it survives navigation, and we save it to your member record when you register. This local capture does not itself contact an advertising provider. Other provider click identifiers, including TikTok and AppLovin identifiers, may be retained in your browser after marketing tracking is permitted and used to attribute later conversion events
• Marketing Quiz Responses: If you complete our onboarding or marketing quiz (a short golf-preferences questionnaire), we collect the answers you provide. We use these responses to classify a "golfer type" and to personalize the signup experience. The quiz variation you saw is recorded as part of your signup attribution, and quiz completion and call-to-action events are recorded in our usage analytics. Subject to your consent, these conversion events may be shared with the advertising platforms described above for conversion attribution
• Ad Landing Page Analytics: When you arrive on one of our advertising landing pages, you may be assigned a page variation, and first-party analytics record page views, call-to-action clicks, and conversion steps to measure the performance of our advertising. These first-party records are separate from the third-party advertising pixels and conversion transmissions governed by the regional tracking choices in Section 8
• Blog View Analytics: When you read an article on our Blog, we record a page view to measure readership. For deduplication (so repeat views within an hour are not double-counted), we store a one-way cryptographically hashed (SHA-256) value derived from your IP address and browser user agent, along with your browser user agent and the referring page. We do not store your raw IP address with blog views
• First-Party Product Analytics: We record app usage events in our own database, such as page views, taps on features and buttons, and steps completed. Each event can include the event name, the page path, the feature or on-screen element involved, a few short coded properties (such as which screen or option), a random session identifier kept in your browser's session storage, your browser user agent, the time, and your account ID if you are signed in. These events are designed not to include your name, email address, or text you type, such as messages, comments, or searches. We use them to understand which features are used, measure onboarding and A/B tests, and improve the Service. They are kept in our own database, are not sent to advertising providers, and are not controlled by the cookie choices in Section 8. We automatically delete these records after 180 days, except a small number of records that note which trivia question was shown in the Feed, which we keep so each question stays attached to the same post. Events linked to your account are deleted when you delete your account (Section 4.1)
• Performance Monitoring: For a random sample of about one in four page loads, and only when analytics tracking is permitted under Section 8, your browser reports page-loading and responsiveness measurements (such as Core Web Vitals) and the page path. Our server converts the path to a general page type, notes a device class (for example, phone or desktop) and whether you are using an in-app browser from your user agent, and stores only daily counts, with no account ID, IP address, or other identifier. When you open a page that does not exist, your browser reports the page path (without any query string) and the referring website's domain, and we store daily counts of those pairs with no identifiers. Missing-page reports are not controlled by the cookie choices. Both kinds of monitoring records are deleted after 90 days
• A/B Testing: We sometimes test different versions of a page or feature to see which works better. When we use A/B tests, our server may set a first-party cookie named fg_aid that holds a random identifier, not your name or email. It is an httpOnly cookie, so scripts on the page cannot read it, it lasts up to 400 days, and it is used only to assign you consistently to a test version and measure results. Which version you saw is recorded in the first-party analytics described above. If you create an account in that browser, we link the random identifier to your new account so a test can be measured through signup; that link is deleted when your account is deleted. A/B testing is part of operating and improving our own Service, does not send data to advertising providers, and is not controlled by the cookie choices in Section 8
• Session Data: Authentication session tokens stored in secure cookies

1.10 Mobile Application Data

When using the Flighting mobile application (WebView-based):

• Device Identifiers: Device type, operating system version, and app version
• App Usage: Session data, feature usage, and interaction patterns within the mobile wrapper
• App-Open Activity: When your authenticated mobile app starts or returns to the foreground, we record the server time of a recent app open, no more often than once every 15 minutes. This timestamp may be shared with our authorized CRM integration for engagement and inactivity communications. It is not inferred from ordinary website browsing, and an empty timestamp means we have not recorded a mobile app open for that account
• Push Notification Permission: After onboarding, the app may ask whether you would like notifications before your device shows its own permission prompt. We store your answer and when you gave it. Your device decides whether notifications are allowed, and you can change that at any time in your device settings
• Push Notification Tokens: When you enable push notifications, we collect and store a device token linked to your account. We route iOS notifications through Apple Push Notification service (APNs) and Android notifications through Firebase Cloud Messaging (FCM). The token and device platform are used to deliver notifications to the correct device. Invalid tokens may be removed automatically, and account deletion removes tokens associated with the account. You can disable push notifications at any time using the push notifications toggle in your account settings or through your device settings
• Push Notification Delivery: Notification delivery status, timestamps, and read/open status
• Saved Sign-In on iOS (Face ID): When you sign in or create an account in the iOS app, the app saves your email address and password in your device's iOS Keychain. When the sign-in screen appears later, the app may offer to fill them in, but only after you confirm with Face ID or Touch ID; nothing is filled without that confirmation, and you can decline. The app also keeps a sign-in token in the Keychain to restore your session. These items stay on your device and are removed when you sign out in the app. Face ID and Touch ID are handled by iOS; Flighting never receives your face or fingerprint data

1.10A Information Stored on Your Device

To make the app fast and usable with a weak signal on the course, some information is stored in your browser or app on your device:

• Offline App Shell: Our service worker stores the app's code, styles, and Pro Shop product images so the app can open without a connection. It does not store your account data
• Offline Copy of Your Data: A limited copy of your own account data (your profile, rounds and handicap scores, known courses, milestones, and weekly challenge progress) is kept in your browser's storage so the app can show it without a signal. It is tagged to your account, is shown only to that account, expires after 24 hours, and is deleted when you sign out or a different account signs in on the device
• Unsent Drafts: Text you have typed but not yet sent in a direct message or comment is saved on the device so it is not lost. It is removed once sent, and all of these drafts are deleted when you sign out. Unsaved scorecard edits are kept on the device until you save or discard them, for up to 30 days; they are not currently removed at sign out
• Other Preferences: Items such as your cookie choices, saved weather location, sign-in recovery token, and the first-touch attribution described in Section 1.9. The sign-in recovery token is removed when you sign out; you can clear the saved weather location in the weather widget

Information stored on your device is not shared with other members. Anyone with access to your unlocked device or browser profile may be able to see it, so sign out on shared devices.

1.11 Information We Do NOT Collect

We do not collect:

• Continuous or background GPS location tracking. The optional weather feature uses device coordinates when you grant permission and sends them through our server to request forecasts (see Section 1.8). We also derive approximate network-level location from request information for compliance and region context (see Section 1.9). Local Play uses a ZIP code you choose to supply, not background GPS
• Golf course check-ins
• Biometric data
• Photos or images from your device camera roll or photo gallery beyond the specific photo you select or capture for a scanning feature or your profile photo; we do not browse, index, or access your photo library

2. How We Use Your Information

2.1 Core Service Functions

• Account Management: Creating and maintaining your Flighting account, authenticating your identity
• Milestone Tracking: Monitoring your progress and achievements based on USGA handicap data
• Leaderboards: Displaying your performance compared to other users across multiple categories
• Member Experience: Grouping individual rankings and standings by experience, with members who have not selected one included in Men's rankings and Women's rankings separate. Full Pro Shop access, commerce-linked rewards, store-credit issuance and transfers, and related commerce notifications currently require an explicit Men's Experience selection. A member without that selection who already has permanent access to a particular product may have limited catalog and checkout access to that product, without opening the rest of the Pro Shop
• Reward Fulfillment: Processing and delivering eligible apparel, gear, member benefits, and the one-time verified-USGA complimentary hat claim via Stripe checkout and Shopify order fulfillment where applicable
• Personalized Pro Shop: Showing the base assortment and maintaining permanent account-level access to products earned through milestones and challenges or retained through completed purchases
• Top 100 Tracking: Matching your played courses against the Top 100 course list for milestone progression
• Flight Tier Assignment: Automatically classifying your skill level into a Flight Tier (FT+ through FT5) based on your Handicap Index for leaderboard segmentation and peer grouping
• Strokes Gained Analytics: Comparing your scoring performance against players within your Flight Tier to provide peer-relative performance insights

2.2 Financial Services

• Payment Processing: Processing purchases and recording eligible store-credit activity through Stripe, including checkout for the verified-USGA hat's shipping and any applicable tax
• Member Credit Transfers: Recording transfers of eligible store credit between members, not cash transfers to external accounts
• Game Bounties: Recording eligible store-credit debits or awards when a game result is settled. We do not hold game credits in cash escrow or make cash bounty payouts
• Promo Code Redemption: Validating and applying promotional codes and credits

2.3 AI-Powered Features

• Bag Scanning: Processing uploaded photos to identify golf club brands and models using OpenAI's vision capabilities
• Scorecard Scanning: Processing uploaded scorecard photos to extract hole-by-hole scores using OpenAI's vision capabilities
• Danny AI Caddie: Generating personalized golf advice, rules guidance, and course strategy using OpenAI's language models
• AI Practice Recommendations: Analyzing your USGA round history, scoring statistics, hole-by-hole performance, and player profile data using OpenAI to generate and save personalized weekly practice plans in the Training Center

2.4 Social and Community Features

• Following System: Enabling users to follow others and receive activity updates
• Direct Messaging: Facilitating private text-based communication between users, including message delivery, read receipts, and conversation management
• Messaging and Community Safety: Processing block and report records, including reports about direct messages, Feed posts, and comments, to enforce our Code of Conduct and protect users from harassment, spam, and prohibited conduct
• News Feed Comment Moderation: Reviewing and moderating comments posted on news articles to enforce our Code of Conduct, including removing inappropriate comments and taking enforcement action (up to account suspension or permanent ban) against users who violate community standards
• Notifications: Sending in-app notifications about milestones, game updates, follower activity, challenge invitations, and new messages
• Feed Engagement Emails: Sending email when another member reacts to or comments on your Feed activity when your Feed Activity email preference is enabled. Not every in-app or push notification generates an email
• Games and Challenges: Facilitating multiplayer games, head-to-head challenges, and competition management
• Weekly Challenges: Administering community-wide weekly challenges, tracking participation, determining results, and distributing prizes
• Clubhouse Forum: Facilitating community Q&A and discussion through The Clubhouse, including post and response management, upvote tracking, @mention notifications, and content moderation to enforce our Code of Conduct
• Activity Visibility: Applying your chosen audience settings to activity feed posts and round-derived profile details, including recent form, detailed season highlights, and individual achievement details
• Monthly Wrapped: Creating a monthly snapshot for your own review and providing a unique token link that you may choose to distribute. Anyone who receives that link can view the limited data described in Section 3.1
• Daily Trivia: Recording your trivia answers, determining correctness, and applying store credit rewards to your account balance through Stripe
• Community Fact Cards ("Flighting Facts"): Generating daily community insight cards shown in the activity feed. Practice-insight cards use a rolling 90-day window and may show aggregate counts or percentages by practice focus and Flight Tier. We suppress a practice aggregate when fewer than three distinct members contributed to that group. Other cards may highlight aggregated community statistics or notable achievements and information already publicly visible on the platform (such as leaderboard standings, milestones, or "What's in the Bag" equipment). We do not include private information such as messages or hidden activity in fact cards
• Club News: Determining whether you are affiliated with a participating club so news, announcements, and images posted by that club's authorized staff appear in your feed
• Local Play: Using voluntary ZIP-centroid matching to provide approximate local discovery for consenting adult members; applying visibility, revocation, deletion, block, report, and conduct protections
• Host Network: Verifying GHIN and private-club eligibility, recording your free Host Network opt-in, displaying eligible active Hosts to one another, and authorizing cross-club messages

2.5 Communication

• Transactional Emails: Password resets, order confirmations, security messages, and other essential account communications sent via SendGrid
• Onboarding and Engagement Emails: A limited welcome sequence for new members and activity-based emails, including eligible Feed reactions and comments. These communications use your account status, onboarding progress, Member Experience, feature activity, and email preferences to avoid irrelevant messages and may be managed through applicable account settings or unsubscribe links
• Setup Reminders: If you have not finished setting up your account, meaning you have not linked your USGA Handicap ID or turned on push notifications, we may send one reminder about two days after you sign up and one about six days after, so no more than two in total. If linking your handicap is still missing and you already receive push notifications from us, the reminder may come as a push notification. Otherwise it comes by email, and only if your Product Updates email category is on and you have not unsubscribed. We do not remind you to turn on push notifications if you have switched them off in your account settings. Reminders are sent between 10 a.m. and 8 p.m. in your device's last known time zone (Eastern Time if we do not know it), and each email includes an unsubscribe link
• Marketing Emails: Promotional emails about new features, collections, and offers managed through our customer relationship system (you may opt out at any time using the unsubscribe link in any email)
• SMS / Text Messages: If you have provided your mobile number and granted express consent through the in-app prompt or account settings, we may send marketing texts (new product drops, exclusive offers, reward and milestone notifications, weekly challenge updates) and transactional texts (order updates, security alerts) through our own customer relationship system. Message frequency varies. Message and data rates may apply. Reply STOP to opt out of marketing texts at any time, or toggle SMS off in your account settings. Reply HELP for help. Consent to receive marketing texts is not a condition of using the Service
• Customer Support: Responding to your support tickets and questions

2.6 Platform Improvement

• Analytics: After analytics tracking is permitted under the regional consent process described in Section 8, understanding user behavior through Google Analytics and Microsoft Clarity to improve features and experience. First-party usage and engagement records may be collected separately from these third-party trackers
• Marketing Optimization: After marketing tracking is permitted under the regional consent process described in Section 8, using the advertising pixels and server-side conversion services listed in Sections 1.9 and 3.2 to measure attribution and advertising effectiveness
• Admin Analytics: Generating aggregated platform metrics for internal operations
• Performance Monitoring: Ensuring the app functions properly across devices, using the sampled page-speed measurements and missing-page reports described in Section 1.9
• A/B Testing: Comparing versions of pages and features using the first-party testing identifier and usage events described in Section 1.9

2.7 Legal and Safety

• Fraud Prevention: Detecting and preventing fraudulent handicap data, score manipulation, financial abuse, and game collusion
• Code of Conduct Enforcement: Monitoring compliance with our integrity standards
• Legal Compliance: Fulfilling legal obligations and protecting our rights

3. How We Share Your Information

3.1 Public Information

Flighting profiles are visible to other Flighting users. The following profile and aggregate information may be publicly visible within the Service:

• Your name
• Your current Handicap Index (sourced from USGA)
• Your aggregate milestone count and other profile achievement information permitted by your visibility setting
• Your leaderboard rankings and scores
• Your inclusion in individual rankings grouped by Member Experience (members without a saved selection currently rank with Men's Experience members), from which a selection or ranking group may be apparent to other members
• Your equipment information ("What's in the Bag")
• Your game and challenge participation and results
• Product ratings and review text you choose to submit, displayed with your member name on the product page unless the review is hidden or removed
• Your follower and following lists
• Any other information you choose to display on your profile

We do not currently offer fully private profiles. However, your activity visibility setting controls who can see your activity feed posts and round-derived profile details such as recent form, detailed season highlights, and individual achievement details. You may select everyone, members in your Flight Tier, members of your club, your followers, or leave the audience selection empty so no other member qualifies through that setting. Aggregate profile information, current Handicap Index, Flight Tier, leaderboard results, and aggregate achievement counts remain visible as described above.

Public Monthly Wrapped links: A Wrapped snapshot is assigned a unique share token, but Flighting does not distribute its public link for you. If you choose to share the link, anyone who has it can view the frozen snapshot without signing in. The public snapshot may include your first name, month label, rounds and holes played, scores, pars, birdies, eagles, holes in one, course highlights, practice totals, challenge and follower activity, community interactions, and a generated golf personality. It does not expose your account record, contact information, full round records, full course list, private messages, or other profile data through that public endpoint. Treat the link as public and share it only with people or services you want to view the snapshot.

3.2 Third-Party Service Providers

We share your information with trusted third-party service providers who assist us in operating our Service:

• Stripe: Checkout, payment and tax processing, customer and store-credit records. Stripe receives checkout information such as your name, email, payment details, items, amounts, shipping charges, and applicable tax. Verified-USGA hat checkout carries offer-related information used to identify the claim and payment session. See Stripe's Privacy Policy.
• Shopify: Catalog, order fulfillment, customer management, and gift card processing. For orders including the verified-USGA hat, Shopify receives the order and shipping information needed for fulfillment; Shopify order identifiers are linked to the claim record. See Shopify's Privacy Policy.
• OpenAI: AI-powered features (bag scanner, scorecard scanner, Danny AI caddie, Flighting Intelligence in Round Analytics, and AI practice recommendations). OpenAI receives photos you upload for scanning, your AI conversation messages, the privacy-minimized round-performance context used to answer Round Analytics questions, and your golf performance data used to generate practice plans. We also use OpenAI to generate system content such as daily trivia questions, news digest summaries, training tips, and blog articles; generating this content does not involve sending your personal information to OpenAI beyond what is described above. See OpenAI's Privacy Policy.
• SendGrid: Transactional email delivery. SendGrid receives your email address for sending password resets and notifications. See SendGrid/Twilio's Privacy Policy.
• Google Analytics: Usage analytics and behavior tracking through cookies and tracking scripts when analytics tracking is permitted. See Google's Privacy Policy.
• Microsoft Clarity: Session replay, heatmap, and interaction analytics, including mouse movements, clicks, and scrolls when analytics tracking is permitted. Do not enter sensitive information into fields that are not intended to receive it. See Microsoft's Privacy Statement.
• Meta (Facebook) Pixel & Conversions API: Client-side browsing and conversion measurement and server-side conversion transmission. When available and marketing tracking is permitted, browser advanced matching passes normalized email, phone, first and last name, city, state, ZIP, country, date of birth, and Flighting account ID to Meta's Pixel. Server-side matching hashes these fields with SHA-256 before transmission; IP address, user agent, and Meta browser/click identifiers are not hashed in this way. After GHIN verification, the custom GHINVerified conversion carries a verification status, not your GHIN number or Handicap Index. See Meta's Privacy Policy.
• X (formerly Twitter) Pixel & Conversions API: Client-side conversion tracking (Pixel) and server-side conversion data transmission (Conversions API). The Conversions API sends hashed user data (email, phone number) from our servers to X for ad measurement and optimization. See X's Privacy Policy.
• Reddit Pixel & Conversions API: Client-side conversion tracking (Pixel) and server-side conversion data transmission (Conversions API). The Conversions API sends hashed user data (email, phone number) from our servers to Reddit for ad measurement and optimization. See Reddit's Privacy Policy.
• OpenAI Advertising Pixel & Conversions API: Client-side conversion tracking (Pixel) and server-side conversion data transmission (Conversions API) for advertising measurement. The Conversions API sends hashed user data (email, phone number) from our servers to OpenAI for ad measurement and optimization. This advertising use is separate from the AI processing described elsewhere in this policy. See OpenAI's Privacy Policy.
• TikTok Pixel & Events API: Client-side and server-side advertising measurement, attribution, and conversion tracking. TikTok may receive event information, provider cookies or click identifiers, device and browser data, and normalized identifiers such as email, phone number, and account identifier for advanced matching. Server-side identifiers are hashed using SHA-256 before transmission. See TikTok's Privacy Policy.
• TikTok Content Posting API: Flighting may use TikTok's publishing tools to upload and publish Flighting-created, administrator-approved organic content to Flighting's authorized official TikTok account. TikTok processes the official account identifier, authorization credentials, content files, captions, and publication status needed for that purpose. This administrative integration is separate from advertising measurement and does not collect Flighting members' TikTok account data or allow members to connect personal TikTok accounts through the Service. See TikTok's Privacy Policy.
• AppLovin AXON Pixel & Conversions API: Client-side and server-side advertising measurement, attribution, and conversion tracking. AppLovin may receive event information, provider cookies or click identifiers, device and browser data, and identifiers such as email, phone number, and account identifier. Server-side email, phone number, and account identifiers are normalized and hashed using SHA-256 before transmission. See AppLovin's Privacy Policy.
• Apple Push Notification service (APNs): Delivery of push notifications to iOS devices. APNs receives your device token for notification routing. See Apple's Privacy Policy.
• Google Firebase Cloud Messaging (FCM): Delivery of push notifications to Android devices. FCM receives your Android registration token and notification delivery data needed to route the notification. See Google's Privacy Policy.
• Open-Meteo: Weather forecast and location geocoding requests made through our server, including coordinates used to request the forecast.
• Cloud Hosting and Object Storage (Replit): Servers that host our database and application infrastructure and store uploaded club-news media. Club-news images may remain in object storage after a post is removed while we complete operational cleanup, preserve backups, address security or abuse, or meet legal obligations

Providers process information for the purposes described here and may retain records under their own obligations and policies. For details about their processing, consult the linked provider privacy notices.

3.2.1 External API Data Sharing

Flighting provides authenticated external API endpoints that share data with Flighting's authorized CRM, email operations, and partner systems. We use these integrations to manage member communications, create weekly recaps, segment audiences, administer rewards, and support authorized partner operations. Data shared through these endpoints may include:

• Member identifiers, names, contact information, and club affiliations
• Handicap Index, Flight Tier, scoring data, round summaries, and practice activity
• Leaderboard rankings, milestones, challenge activity, discounts, rewards, and personalized product access
• Weekly recap fields, engagement segments, recorded mobile app-open timestamp (if any), and aggregated or individual performance statistics

We also support outbound member-update webhooks to an authorized CRM when that integration is configured. These updates can include member contact details, GHIN verification and performance fields, club affiliation, and email preferences. The mobile app-open timestamp is included in the protected member API export described above; it is not part of the member-update webhook payload.

Access to these API endpoints is restricted to authenticated integrations authorized by Flighting. Recipients may retain synchronized data under their own documented retention practices and contractual obligations. You can opt out of marketing messages as described in Sections 7 and 8, although operational or transactional processing may continue where necessary to provide the Service.

3.3 Other Users

When you use social and community features:

• Users you follow (and who follow you) may see your activity updates
• Activity and profile-detail visibility is member-controlled: You can choose who sees your activity feed posts and round-derived profile details (everyone, your Flight Tier, your club, your followers, or an empty audience selection) in your account settings. "Your club" includes members who share a USGA/GHIN home club with you and members of a private group you belong to on Flighting, such as The Stake Club. Aggregate profile and leaderboard information remains visible as described in Section 3.1
• Blocking: If you block a member, or a member blocks you, each of you stops seeing the other's Feed posts and comments, and neither of you can comment on, reply to, or react to the other's Feed content. You cannot exchange one-to-one messages, and a new group conversation cannot include two members when one has blocked the other. In a group conversation that already exists, a blocked member's messages are hidden from you and do not notify you
• Wrapped sharing is initiated by you: If you distribute a Monthly Wrapped link, anyone with that token link may view its limited public snapshot, including people who are not Flighting members
• Club staff: If you are affiliated with a participating club, authorized staff at that club may see aggregate engagement with the club news they post. Club staff do not gain access to your private information
• Game and challenge participants can see your performance data relevant to the competition
• Members receiving store-credit transfers see your name associated with the transfer
• Direct messages are not public: Message content is available to conversation participants, including group-chat participants. Flighting administrators may review reported messages and nearby conversation context for safety and moderation, or access content where required for compliance or legal purposes

3.4 Future Marketing Partners

We may share aggregated, anonymized data with marketing partners in the future. We will update this Privacy Policy and notify you before sharing identifiable personal information with any marketing partners. You will have the option to opt out.

3.5 Legal Requirements

We may disclose your information if required by law, court order, or governmental authority, or if we believe disclosure is necessary to:

• Comply with legal obligations
• Protect the rights, property, or safety of Flighting, our users, or the public
• Detect, prevent, or address fraud, security, or technical issues
• Enforce our Terms of Service or Code of Conduct
• Investigate potential financial fraud related to store-credit balances, transfers, and checkouts

3.6 Business Transfers

In the event of a merger, acquisition, bankruptcy, or sale of assets, your information may be transferred to the acquiring entity. We will notify you via email and/or prominent notice on our Service before your information is transferred and becomes subject to a different Privacy Policy.

4. Account Termination and Data Retention

4.1 User-Initiated Account Deletion

You may delete your Flighting account at any time through the app settings or by using our account and data deletion page. Upon deletion:

• Your Flighting account and profile will be permanently removed from our active account database
• Your profile will no longer be publicly visible
• We will stop sending account-based communications, although legal or transactional notices and records already synchronized to external providers may remain subject to the limits described in Section 4.3
• Your account-linked rounds, messages (including messages you sent in group conversations), activity, progress, entitlements, scan logs, AI conversation history, saved practice plans, first-party usage events linked to your account, the link between your account and any A/B testing identifier, and other account-linked application records will be removed from our active database. Conversations shared with other members and records of those members' activity may remain
• Your Monthly Wrapped snapshots and their public share links will be deleted and will no longer be accessible
• If you have remaining store credit or an outstanding payment dispute, contact support before deletion. Store credit is not generally withdrawable as cash

4.2 Company-Initiated Account Termination

Flighting reserves the right to suspend or permanently remove any user account at any time, with or without notice, for violating our Code of Conduct or integrity standards, including but not limited to:

• Submitting fraudulent or falsified handicap information
• Manipulating scores or USGA data
• Financial fraud or abuse (promo codes, store-credit transfers, or checkout manipulation)
• Posting inappropriate, offensive, or harassing comments
• Uploading or capturing inappropriate, explicit, obscene, or illegal imagery through the camera or photo upload features
• Engaging in behavior that violates our Terms of Service
• Any activity that compromises the integrity of the platform

We may provide a warning before permanent removal, but we are not obligated to do so. Our decision to remove a user is final.

4.3 Data Retention After Deletion

When you delete your account, Flighting removes the account-linked records described in Section 4.1 from its active application database. We may retain limited information for only as long as reasonably necessary or legally required for the following purposes:

• Legal, tax, accounting, regulatory, fraud-prevention, security, dispute-resolution, and agreement-enforcement obligations
• Temporary backups and system logs that cannot immediately be isolated from routine backup cycles, after which they are deleted or overwritten under our operational retention practices
• Records maintained independently by service providers such as Stripe, Shopify, SendGrid, OpenAI, analytics providers, advertising providers, and authorized CRM systems under their own legal obligations and retention practices
• Aggregated or de-identified information that no longer reasonably identifies you

Deleting your Flighting account does not automatically erase records that a third-party provider is independently required or permitted to retain. We will evaluate verified privacy-rights requests and direct them to applicable providers where required by law.

If you have questions about data retention, please contact us at privacy@flightingapp.com.

5. Data Security

We implement reasonable administrative, technical, and physical security measures to protect your personal information from unauthorized access, disclosure, alteration, or destruction. Specific measures include:

• Passwords stored using bcrypt one-way hashing (we cannot access your plain-text password)
• Secure session management with server-side session storage
• HTTPS encryption for all data in transit
• Secure cookie handling with appropriate flags (httpOnly, secure, sameSite)
• Rate limiting on sensitive endpoints (authentication, AI features)
• Role-based access control separating member and admin functions

However, no method of transmission over the internet or electronic storage is 100% secure. While we strive to protect your information, we cannot guarantee absolute security.

You are responsible for maintaining the confidentiality of your account credentials. Do not share your password with anyone.

6. Children's Privacy

Flighting is intended for users aged 18 and older. We do not knowingly collect personal information from individuals under 18 years of age. If we become aware that a user is under 18, we will terminate their account and delete their information.

If you believe a minor has created an account, please contact us immediately at support@flightingapp.com.

7. Your Privacy Rights

7.1 Access and Correction

You may access and update your account information at any time through the app settings, including your profile details, equipment information, and notification preferences.

7.2 Opt-Out of Marketing

You may unsubscribe from marketing emails by using the unsubscribe link in a promotional email, the applicable email preference in your account, or contacting us at support@flightingapp.com. Account email settings include separate categories; switching off Feed Activity emails alone does not switch off every other category. Switching off the Product Updates category also stops setup reminder emails. You may revoke marketing SMS consent through account settings or by replying STOP. Email, SMS, push, and cookie/advertising preferences are separate controls. Essential service-related communications, such as password resets, order confirmations, and security alerts, may continue.

7.3 Data Deletion

You may request deletion of your account and personal data through our account and data deletion page. Note that certain data may be retained as described in Section 4.3.

7.4 AI Data

You may delete your Danny AI caddie conversation history at any time through the app and restart the current Flighting Intelligence Round Analytics conversation from that report. Bag Scanner photos are processed in real time and are not permanently stored in Flighting's database. Scorecard Scanner photos are deleted automatically after 30 days. Scorecard scan logs are retained as described in Section 1.4 and are removed from our active database when your account is deleted.

7.5 California Residents (CCPA)

If you are a California resident, applicable law may give you rights to:

• Know what personal information we collect, use, and share
• Request deletion of your personal information (subject to legal exceptions)
• Opt out of certain sales or sharing of personal information or use for targeted advertising where applicable
• Non-discrimination for exercising your privacy rights

To exercise these rights or ask about advertising data sharing, contact us at privacy@flightingapp.com. The cookie controls in Section 8 manage our browser marketing and analytics tools; marketing email and SMS preferences are separate.

7.6 European Residents (GDPR)

If you are located in the European Economic Area, you may have additional rights under the General Data Protection Regulation (GDPR), including the right to access, correct, delete, restrict processing, data portability, and object to processing of your personal information. Contact us at privacy@flightingapp.com to exercise these rights.

8. Cookies and Tracking Technologies

8.1 Cookies We Use

Our consent process is region based. In regions where our regional check identifies a prior-choice jurisdiction, analytics and marketing tools remain off until you make the applicable choice. In other regions, including when the server cannot determine a region, those tools may be enabled automatically. If the browser cannot complete the regional check, we ask for a choice before loading those tools. Your preference is stored for return visits; you can change it through the cookie controls. Essential storage and the local first-touch attribution capture described in Section 1.9 may occur before advertising pixels load. The A/B testing cookie, first-party usage events, and missing-page reports described in Section 1.9 are not controlled by these choices; sampled page-speed measurements are sent only when analytics tracking is permitted.

• Essential Cookies: Session cookies required for authentication and security, including a persistent "remember me" cookie (up to 90 days) that maintains your login session across visits. These are necessary for the Service to function and cannot be disabled.
• A/B Testing Cookie (fg_aid): A first-party, httpOnly cookie set by our server when we use A/B tests. It holds a random identifier, lasts up to 400 days, and is used only to show you a consistent version of a page or feature under test and to measure results, as described in Section 1.9. It is not used by advertising providers. You can delete it through your browser settings; a new random identifier may then be assigned.
• Analytics Cookies: After analytics tracking is permitted through the regional process above, Google Analytics cookies help us understand how users interact with the Service. These collect usage data.
• Session Replay Cookies: After analytics tracking is permitted through the regional process above, Microsoft Clarity cookies are used for session recording, heatmap generation, and user interaction analytics. These help us understand how users navigate the Service and identify usability improvements.
• Marketing Cookies and Local Storage: After marketing tracking is permitted through the regional process above, the Meta, X, Reddit, OpenAI advertising, TikTok, and AppLovin AXON tools may set or read cookies, local storage, browser identifiers, and provider specific click identifiers for conversion tracking, deduplication, advanced matching, and advertising attribution.

8.2 Managing Cookies

You can change analytics and marketing choices through the Service's cookie controls or control cookies through your browser settings. Disabling essential cookies may prevent you from using the Service; disabling analytics or marketing cookies will not affect core functionality. First-party usage and engagement events may still be recorded by our server independently of third-party tracking choices.

8.3 Do Not Track

Some browsers offer a "Do Not Track" (DNT) setting. We currently do not respond to DNT signals, but you can manage your tracking preferences through the cookie controls described above.

9. Third-Party Links

Our Service may contain links to third-party websites or services, including:

• USGA websites
• Shopify checkout and order tracking pages
• Stripe payment pages
• External golf news sources (aggregated via RSS)
• Weather data providers

We are not responsible for the privacy practices of these third parties. We encourage you to review their privacy policies before providing any personal information.

10. International Data Transfers

Your information may be transferred to and maintained on servers located outside of your state, province, country, or other governmental jurisdiction where data protection laws may differ. By using Flighting, you consent to the transfer of your information to the United States and other jurisdictions as necessary to provide the Service.

Third-party processors, including Stripe, Shopify, OpenAI, SendGrid/Twilio, Google, Apple, Microsoft, Meta, X/Twitter, Reddit, TikTok, AppLovin, and our hosting providers, may also process your data in jurisdictions outside your country of residence.

11. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. We will notify you of any material changes by:

• Posting the updated Privacy Policy on this page
• Updating the "Last Updated" date at the top of this policy
• Sending you an email notification (if you have provided an email address)

This November 8, 2026 update does not require existing authenticated members to complete a blocking re-acceptance step. New registrations expressly accept the current Terms and Privacy Policy. If applicable law requires a different notice or consent process for a future change, we will provide that process at that time. Otherwise, continued use after notice may constitute acceptance to the extent permitted by law.

12. Social Media and Public Marketing

Flighting maintains official social media accounts (including Instagram, Facebook, TikTok, and other platforms) to promote the Service and engage with the community. In connection with our social media presence:

• Aggregated Achievement Data: We may publicly share aggregated, anonymized statistics about the Flighting community (e.g., total milestones completed, total rounds logged) on social media or marketing channels. No individual user data is identifiable in aggregated posts.
• User Testimonials and Spotlights: We will not feature any identifiable user information, name, profile data, or achievements on our social media channels without obtaining your prior express consent.
• Social Media APIs: We use the Instagram Graph API, TikTok Content Posting API, and other platform APIs to manage official Flighting accounts and publish Flighting-created content approved by an authorized administrator. These administrative integrations process official-account credentials and publication content, not Flighting members' personal social media account data. Members cannot connect personal TikTok accounts or publish through the Service.

13. Contact Us

If you have any questions, concerns, or requests regarding this Privacy Policy, please contact us:

Flighting Inc.
3802 S. Jessamine Dr
St. George, UT 84790
Email: privacy@flightingapp.com
Support: support@flightingapp.com

14. Consent to USGA Data Retrieval

By using Flighting and entering your USGA Handicap ID, you explicitly authorize Flighting Inc. to:

1. Retrieve your official handicap information from the USGA database
2. Store and display your Handicap Index, score history, and scoring statistics
3. Use your USGA data for milestone tracking, leaderboards, games, challenges, Top 100 course tracking, and other platform features
4. Continue accessing updated USGA data associated with your USGA Handicap ID for as long as your account is active

You may revoke this authorization by deleting your account or removing your USGA Handicap ID from your profile settings.

15. Consent to AI Data Processing

By using Flighting's AI-powered features, you explicitly consent to:

1. The transmission of your uploaded or camera-captured photos to OpenAI for club identification (Bag Scanner) and score extraction (Scorecard Scanner)
2. The app requesting access to your device camera for the purpose of capturing photos for AI scanning features
3. The transmission of your conversation messages to OpenAI for response generation (Danny AI Caddie)
4. The transmission of your Round Analytics questions and a privacy-minimized server summary of your stored scores, valid hole-by-hole details, course history, profile performance context, and available anonymous flight comparison to OpenAI for Flighting Intelligence responses
5. The transmission of your USGA round history, scoring statistics, and player profile data to OpenAI for personalized practice plan generation (AI Practice Recommendations)
6. The storage of your AI conversation history in our database

You may stop using AI features at any time and revoke camera access through your device settings. You can delete Danny conversation history through the app and restart your current Round Analytics conversation. Saved practice plans are removed when your account is deleted.

By using Flighting, you acknowledge that you have read, understood, and agree to be bound by this Privacy Policy.