CourtBeam Mobile App and White-Label Distribution Addendum

1. Definitions

• App means the CourtBeam mobile application or a Club-specific branded application that CourtBeam builds, configures, operates or supports.
• App Source Code means source code, build configuration, native projects, signing configuration, deployment scripts, templates, reusable components, SDK integrations, documentation and technical materials used to create or maintain the App.
• Club Materials means the Club’s name, trademarks, logos, colors, images, copy, policies, waivers, URLs, support information and other materials the Club supplies or authorizes for use in the App or its store listing.
• App Configuration means tenant identifiers, brand settings, feature flags, store metadata and other configuration that CourtBeam uses to connect an App to a Club. App Configuration is not App Source Code.
• Store Account means an Apple Developer, App Store Connect, Google Play Console or comparable distribution account used for the App.
• Player Data means club-controlled personal data covered by the Data Processing Addendum, including account, booking, membership, payment-reference, waiver, device and notification information processed for the Club.

2. Service and scope

CourtBeam may provide a shared CourtBeam App, an App configured for one Club, or an App published under the Club’s name and branding. The App is a delivery surface for the hosted CourtBeam service. It does not make CourtBeam the Club, venue operator, coach, event host, payment processor, insurer or provider of the Club’s sporting services.

The Club is responsible for its facilities, staff, coaches, rules, prices, waivers, taxes, refunds, safety, accessibility, customer support and legal compliance. CourtBeam is responsible for the technical operation of the App to the extent stated in the order form and Platform Terms.

3. Ownership of software and Club Materials

CourtBeam and its licensors retain all right, title and interest in and to:

• the App Source Code and all object code, binaries, builds and deployment systems;
• the CourtBeam service, architecture, user interfaces, designs, templates, documentation, APIs, SDK integrations and infrastructure;
• App Configuration schemas, generic features, generic analytics, security controls, fixes, improvements, derivative works and know-how; and
• CourtBeam names, logos, trademarks and other CourtBeam brand assets.

No individual owner, director, employee, staff member or contractor of the Club receives ownership of or a right to possess the App Source Code merely because that person requested, paid for, administered, or appears in the name of the App. CourtBeam will maintain appropriate confidentiality and work product assignment agreements with its personnel and contractors.

The Club retains its rights in Club Materials and Player Data, subject to the licenses and processing rights in the Platform Terms and Data Processing Addendum. The Club grants CourtBeam a non-exclusive, worldwide, royalty-free license during the relationship to host, reproduce, adapt, display, publish and distribute Club Materials as reasonably necessary to build, configure, submit, operate and support the App and its authorized store listing. Use in unrelated advertising, customer endorsements or a case study requires separate permission. This license is limited by the content permissions in the Platform Terms and does not authorize unrelated use of Player Data.

This Addendum does not transfer ownership of a Club trademark, domain name, Club Materials, Player Data, App Source Code, or generic CourtBeam technology. Third-party and open-source software remains subject to its applicable license.

4. Limited App license

During the applicable subscription term, CourtBeam grants the Club a limited, non-exclusive, non-transferable, non-sublicensable license to identify the App as the Club’s member application and to permit the Club’s authorized members, guests and staff to use the App solely to access the CourtBeam services made available for that Club.

The Club must not, and must not permit another person to:

• obtain, disclose, sell, license, copy, modify, translate or create derivative works from the App Source Code or App;
• reverse engineer, decompile, disassemble, extract or attempt to discover the source code or underlying structure of the App, except where mandatory law or an applicable open-source license permits it;
• remove proprietary notices or CourtBeam attribution required by the order form, store rules or law;
• use the App to create a competing product or provide access for an unrelated club or third party; or
• represent that the Club owns the CourtBeam platform, App Source Code or generic technology.

5. Store accounts and publishing

The preferred arrangement is a separate Store Account owned by the Club’s legal entity, not by an individual owner. The Club may grant CourtBeam managed technical access needed to create identifiers, configure signing, submit builds, respond to reviews and maintain the App. Store-account ownership does not change ownership of the App Source Code.

If CourtBeam uses a CourtBeam-owned Store Account, CourtBeam is the developer of record and the Club receives only the license in Section 4. The order form must identify this arrangement and the Club’s rights to its Club Materials, store listing content and data.

The Club is responsible for approving the App name, description, screenshots, privacy disclosures, age rating, support contact, legal notices and other Club-specific store content. CourtBeam may reject or delay a submission that contains inaccurate, infringing, unlawful or misleading material. Neither party guarantees approval, continued availability, ranking or review outcomes because Apple, Google and other stores may change their rules or make independent decisions.

The parties will use an account and submission structure reasonably intended to comply with applicable store rules for template-based and white-label apps. CourtBeam may require a single shared App or aggregated club-picker model when multiple substantially similar Club Apps would create store-policy or account risk.

The Club must not share personal passwords or personal developer credentials with CourtBeam. Access must be granted through the store’s organization roles, and access must be removed when no longer required.

6. Club warranties and branding

The Club represents that it owns or is authorized to use every Club Material and that the App’s name, icon, screenshots, descriptions, policies and content will not infringe another person’s rights or violate applicable law. The Club is responsible for obtaining permissions for photographs, logos, testimonials, club names, participant images and other third-party materials.

CourtBeam may resize, crop, format, translate or technically adapt Club Materials for device screens, app icons, store metadata and accessibility. Any material change to the Club’s brand identity or legal content requires the Club’s approval where reasonably practicable.

7. Data, privacy and notifications

The Club controls Player Data used to operate its club and is the controller or business where applicable. CourtBeam is the processor or service provider to the extent described in the Data Processing Addendum and processes Player Data to provide the service, follow documented Club instructions, maintain security, prevent fraud, provide support, send transactional communications and comply with law.

The App may process device identifiers, app version, operating-system details, crash diagnostics, approximate network information and push-notification tokens. Enabled player analytics also records coarse screen activity, opens and sessions, including guest use. Signed-in activity can be linked to an account for distinct-player reporting; the Club receives aggregate reports. Native usage reporting currently has no in-app opt-out. CourtBeam uses Firebase Cloud Messaging to deliver requested push notifications, with Apple Push Notification service for iOS delivery; any additional provider is subject to the DPA disclosure process. Push notifications may contain booking confirmations, reminders, club announcements, security notices and other messages permitted by the Club’s notices and applicable law.

The App’s privacy notice, store privacy labels and Club privacy notice must accurately describe these practices. The Club remains responsible for its own purposes, notices, marketing choices, member communications and responses to requests about Club-controlled data.

8. Booking payments and store billing

Bookings, lessons, events and memberships that provide access to the Club’s physical courts, facilities, coaches or in-person activities are Club services. Where the payment flow uses the Club’s Stripe connected account, the Club is the seller and is responsible for the price, tax display, refunds, chargebacks, receipts and customer-facing obligations. CourtBeam currently charges zero application/platform commission on these Club payments; payment-provider fees and taxes remain separate. Processing-fee deductions for player cancellations, full refunds for Club cancellations and restored Club credit follow the disclosed transaction policy and mandatory law; see the Cancellation and Refund Policy.

The App may use a traditional card flow, Apple Pay, Stripe Checkout, a secure external browser flow, or another approved payment method for those physical Club services. CourtBeam will not represent a browser return as payment confirmation; the server records a booking only after the payment provider’s verified webhook or other authoritative result.

The Club must not use this section to sell digital content, digital features, or an app-only subscription without a separate store-policy review. If a purchase unlocks digital content or functionality consumed in the App, the parties must determine whether Apple In-App Purchase or Google Play Billing is required before enabling that purchase. CourtBeam’s B2B subscription and platform fees are not sold to players through the App.

9. Updates, configuration and security

CourtBeam may update the App for security, compatibility, legal, store-policy and product reasons. CourtBeam may use remote App Configuration for branding, tenant routing and feature availability, but remote configuration does not transfer App Source Code or give the Club a right to create its own build.

CourtBeam may suspend an App, a Club configuration, a notification capability or a Store Account workflow when reasonably necessary for security, fraud, non-payment, legal compliance, store compliance or protection of users. Where reasonably safe and practical, CourtBeam will notify the Club and provide a path to resolve the issue.

10. Termination and app-store exit

On termination, the Club’s license to use a CourtBeam-branded or Club-specific App ends except for any continued access expressly stated in the order form. CourtBeam may disable the Club configuration, request delisting, or convert the App to a shared CourtBeam experience where permitted by the Store Account and store rules. The Club may export its Club Materials and Player Data subject to the Platform Terms, Data Processing Addendum and legal retention duties.

An app-store transfer, if available and approved by both parties, transfers the store listing or app record only as described by the applicable store. It does not transfer App Source Code, generic CourtBeam technology, CourtBeam trademarks, or ownership of Player Data. The parties must document any source, signing, push-notification, analytics, payment, domain and user-account steps before agreeing to a transfer.

11. Order-form decisions

Each Club App order should state:

• whether the App is shared, aggregated, or Club-specific;
• the developer-of-record and Store Account owner;
• the Club Materials and store listings CourtBeam may use;
• setup, support, update, store-account and delisting fees;
• notification, analytics, payment and third-party SDK configuration;
• which party responds to store reviews, legal requests and support tickets;
• the termination, export, delisting and app-transfer process; and
• any Club-specific features that are configuration rather than bespoke code.

12. End-user terms

Players and staff use the App under the CourtBeam Player Terms, the applicable Club terms, waiver, cancellation policy and privacy notices. The Club’s branding in the App does not make the Club the owner of CourtBeam technology, and CourtBeam’s operation of the App does not make CourtBeam the operator of the Club’s facilities or sporting activities.

13. Deletion, continuity and scope of commitments

The App must provide the supported account-deletion path and accurate links to the Privacy Notice, Player Terms and Account Deletion Guide. App removal alone does not cancel memberships or delete an account. Before a material change to SDKs, tracking, notification content or data use, the parties must reconcile notices, lawful consent requirements and store declarations with the actual release.

The Club must approve its customer-facing policies and communications. CourtBeam must provide the technical information needed for accurate disclosures. A published notice or an app-store privacy label does not itself establish consent, execute an international transfer agreement or replace a required security control.