DiamondPilot Privacy Policy
Effective date: October 30, 2026
Who DiamondPilot is for
DiamondPilot LLC operates DiamondPilot for adult baseball and softball coaches and team administrators. Accounts are intended for people age 18 or older. Players entered on a roster are records managed by coaches, not player account holders.
Information we process
- Account information: email address, authentication identifiers and information needed to sign in, confirm an email address or recover account access. Authentication is handled through Supabase, which processes your sign-in credentials, retains a password verifier and session records, and supports confirmation and password recovery. Do not send your password or access tokens to support.
- Team, player and Guest information: team names and age groups, player and Guest names, roster membership, availability, position preferences, pitching/catching eligibility and limits, lineup preferences, player roles, development priorities and batting assessments entered by a coach. These include coach-entered athletic traits such as contact, power and speed; supported game history records participation and playing opportunities. The app does not ask for medical or injury information.
- Game and season information: opponents, game dates, seasons, plans, batting orders, defensive assignments, substitutions, restrictions, inning records and completed history. Season History and Opportunity features use supported game and roster information to present summaries and analysis.
- Account access and subscription information: your DiamondPilot account identifier, plan and access status, including administrative or promotional access where applicable. Apple and RevenueCat process purchase and subscription information such as product and transaction identifiers, purchase and expiration times, renewal status, applicable refund or revocation information, and Sandbox or Production environment. DiamondPilot uses RevenueCat's trusted subscription information to determine account access. RevenueCat receives a stable DiamondPilot account identifier so purchases and restores can be associated with the original account; it is linked to your identity through DiamondPilot's authentication records. Apple handles payment details; DiamondPilot does not receive your full payment-card number through this purchase flow.
- Preferences and feature activity: saved coaching settings, setup-guide status, completed or dismissed onboarding steps, game-operation history and subscription activity needed to operate the application and remember your choices.
- Support communications: messages and contact information you send to support. Please avoid sending unnecessary player information or sensitive access links.
Local device and browser storage
The application uses browser or device storage for authentication sessions, remembered navigation, drafts, preferences and recovery of some operations. The web/PWA version also uses cached application resources. Clearing storage, changing browsers or moving to another website origin can remove local information or require you to sign in again. Local drafts are not a substitute for successfully saving information to the service.
On iOS, RevenueCat's SDK stores the subscription identity and cached purchase or access information on the device. This is separate from DiamondPilot's authentication sessions, drafts and coaching data. Cached information alone does not establish current server-authorized Pro access. Changing the DiamondPilot sign-in account does not transfer a subscription to the new account.
Diagnostics and security information
The application processes technical diagnostics such as request/correlation identifiers, operation stages, timing, build information and errors to help troubleshoot failures. Operational records may include account or game identifiers. Public share access uses IP addresses for rate limiting. Hosting and authentication providers may also process IP addresses, request metadata and security logs while operating the service. Supabase session records can retain IP addresses and user-agent information for authentication and security. Feature-operation records can be linked to the signed-in coach or owned team and game. Startup failure reports include error classifications, build and route information and timing; service logs can include errors and stack traces. These records support troubleshooting, performance and security, rather than advertising. The app does not request GPS or device location access. RevenueCat documents using a network IP address to derive a country for customer information and analytics; it says it drops that IP address after determining the country. Supabase's retained authentication IP records are separate from this RevenueCat behavior. Retention depends on the kind of record and the applicable provider configuration.
Youth-player information and children's privacy
DiamondPilot is intended for adult account holders, not for children to create accounts. Youth-player names and other roster information may still be personal information. Coaches and administrators are responsible for having appropriate authority to enter and share this information and for limiting it to what is needed. The current player records do not ask for player birth dates or player contact details; do not put unnecessary sensitive information into names or other fields. Contact us with questions or concerns about a child's information.
How information is used
Information is used to provide team and roster management, generate and adjust plans, operate Game Day, present history and supported analysis, manage account access, tailor plans and supported insights to the coach-entered preferences and game history, remember setup-guide choices, understand subscription performance, respond to support requests and maintain the reliability and security of the service.
Shared Game Plans
A coach can create a Shared Game Plan link. Anyone with a valid bearer link can view its supported plan information without signing in, including team name, opponent and game date, player and Guest names, availability, batting orders, defensive assignments and supported reserve, designated-hitter and pitching/catching plan information. Recipients can forward links, copy information or take screenshots of what is displayed. Share only with people who should have access.
Links have an expiration and can be revoked through the sharing controls. Expiration or revocation stops future access through that link but cannot retrieve copies, screenshots or information already received. Do not send bearer links to support. Changing the product name does not invalidate existing links.
Service providers
Supabase supports authentication and database services. Render hosts the application and backend. Namecheap Private Email supports our support mailbox. The web version also obtains its Supabase JavaScript library through jsDelivr; requests for externally delivered software may expose ordinary request metadata to that delivery provider. The bundled native version uses a locally packaged library.
Apple handles purchase confirmation, billing, subscription management and test transactions under its own terms. RevenueCat provides subscription processing, purchase verification, subscription history and subscription analytics. Its SDK communicates with RevenueCat, and DiamondPilot's backend reads trusted subscription state and receives authenticated subscription-event notifications to update access. The integration uses your DiamondPilot account identifier rather than your email as its subscription identity; it does not send RevenueCat your sign-in password, team rosters or game plans. Subscription communications can also include app and SDK versions, device/platform information, device identifiers, locale and network request metadata. RevenueCat records connection activity such as last-seen time for customer information and activity metrics, and country information may be derived from an IP address. These are subscription-service communications, not an advertising integration. See RevenueCat's privacy policy and Apple's App Store privacy information.
The DiamondPilot TestFlight beta uses Apple's Sandbox environment; test purchases in that environment do not incur real charges. This statement does not apply to Production App Store purchases. Provider processing locations and retention depend on the service and its configuration; this policy does not promise a single processing location or a uniform retention period.
Advertising, tracking and sale
DiamondPilot does not currently use advertising networks or use subscription information to track people across other companies' apps and websites for advertising. We do not sell account or player information for advertising purposes. RevenueCat subscription analytics, necessary authentication, local storage and service diagnostics are distinct from advertising tracking.
Retention
Team, game and history information remains available according to the service's supported storage and deletion behavior. Archiving information is not the same as deleting it. Local drafts and recovery information may have their own cleanup behavior. Support messages are kept separately from application account records and are not automatically removed by deleting an application account. Provider logs and backups may persist separately after application records are deleted, according to the applicable service, plan and configuration. We do not promise a fixed deletion deadline for every provider system. Contact us about information you have sent to support or other retention questions.
Deleting a DiamondPilot account does not cancel an Apple subscription or automatically delete purchase history held by Apple or RevenueCat. Historical subscription records, provider logs and backups may remain separately from the active DiamondPilot account. Contact support with subscription-data or privacy requests; we may need to verify your authority and coordinate with the provider. We do not promise automatic provider-wide deletion or recovery of a deleted account's subscription association.
Account deletion and privacy requests
Signed-in users can request account deletion in Settings using the confirmation workflow. A successful account deletion removes the authentication account and related owned application records through the supported deletion and database relationships. A network interruption or later verification failure can leave the outcome uncertain: an error does not necessarily mean that nothing was deleted. Contact support if the result is unclear; recovery of deleted information is not guaranteed. If you cannot access the account or need help with a privacy request, email support@diamondpilot.app.
Deletion does not promise immediate removal from every provider backup or log, or from information independently copied by recipients of shared plans. We may need to verify that a request comes from an authorized person before acting on it.
Security
The service uses encrypted network connections and account-access controls. No service can guarantee absolute security. Protect your password and devices, and do not disclose authentication tokens, reset links or Shared Game Plan bearer links to people who should not have them.
International use
DiamondPilot LLC operates from Missouri, United States. Service providers may process information in other locations. This statement does not promise that all information is stored only in the United States. Contact us with privacy requests or questions about processing outside your location. The rights and requirements that apply can depend on your circumstances and applicable law.
Policy changes
Updates will be posted with an updated effective date. We will provide additional notice or obtain consent when required by applicable law.
Contact
DiamondPilot LLC — Missouri, United States
Privacy contact: support@diamondpilot.app