Privacy Policy

2. Local records and sharing

Scoring does not require registration using a phone number, email address, password or Apple account. The app does not use iCloud or CloudKit to establish team identities. Local teams, player names and numbers, lineups, rules, pitch-by-pitch records, match dates and time zones, corrections, statistics and preferences remain on your device. Rosters and complete games are uploaded when you choose to share them. The optional voice and broadcast functions send the information described below.

Core scoring, statistics, rules and reports work offline. The app does not read contacts, GPS location or camera data. The microphone is used only for optional voice scoring in versions that offer it and with your consent. A ball landing position is a coordinate you select on a field diagram, not your device location. iPad and iPhone Duo layouts do not add location, audiovisual or biometric collection.

When you export PDF, TXT, match posters, complete local backups or team archives, the system share sheet sends files to the destination or recipient you choose; we do not automatically receive them. Files may contain player information. Local exports are not encrypted, so store and share them carefully. System backups and external services you choose operate under their own policies.

Optional voice scoring on Android

Android 1.0.0 supports enabling voice scoring with an activation code. During activation, the app sends the code and a random device identifier to our voice service to verify access. Each recording requires your consent and Android microphone permission. When you start recording, the app sends the current game situation to our voice service to obtain a temporary recognition connection. Audio streams directly to Tencent Cloud Speech Recognition. The app does not write the original audio to a file.

You can review and edit the transcript. In Android 1.0.0, tapping Analyze Situation sends the transcript and current situation for analysis. Starting with Android 1.0.1, after you consent to record, analysis begins automatically when recording ends. Clear single-pitch phrases are handled on the device. Other transcripts and the current situation are sent through our voice service to Tencent Cloud Hunyuan for a scoring suggestion. Games and practice use the same voice processing flow. The situation may include match identifiers, scores, inning, pitch count, outs, batter name and number, and fielder and runner identifiers. The transcript can also include personal information you speak. The app writes a suggestion to the game record only after you confirm it. You can cancel recording or revoke microphone permission in Android settings and continue manual scoring.

3. Launch screen network requests

After launch, the app may request branded launch screen text and settings from baseballmaster.cc, download a background image from the same domain if needed, and cache validated resources locally. These requests do not contain team rosters, match payloads, device authorization secrets or administrator recovery codes. They do not set launch screen cookies or redirect to other domains. Servers and network infrastructure still process connection information such as IP addresses, request paths, times and responses. Offline, the app uses valid local resources or its built-in screen. This does not enable sharing or broadcasting or prevent offline scoring.

4. Team collaboration data

When you create a shared team, confirm roster uploads, share games, upload historical games or submit corrections, the relevant data is sent over HTTPS to services we control for team synchronization, recording handoffs, recovery, access control and security:

• Team name, abbreviation and city; player names, English names, uniform numbers, stable identifiers and active/inactive status; and manually confirmed historical player mappings.
• Shared game rules, lineups, dates and time zones, pitch and plate appearance records, ball types and field coordinates, defensive plays and throws, runner outcomes, scores, statistics, revisions and submitted review drafts.
• Your chosen team nickname and device display name, member and device identifiers, roles, operation attribution and timestamps.
• Random identifiers, credential digests, revisions and operation receipts needed for synchronization, invitations, device pairing, administrator recovery, viewing authorization and duplicate-request protection.

Device authorization is held in the local system Keychain and is excluded from ordinary backup and team archive exports. The service stores digests of device credentials, invitation secrets and administrator recovery codes rather than their usable full secrets. Display names are identifiers for collaboration, not verified identities.

Bulk rosters are pasted or entered by you, one player per line in “name,English name,number” format. The app does not continuously read your clipboard. Previewing or cancelling does not add players; confirmation saves locally or submits one batch to the shared service. Necessary batch and retry state may be saved locally. Drafts remain available when a request fails or its result is unknown to help avoid duplicates. Player field charts use existing games you are entitled to access and do not infer missing coordinates.

Invited team members have role-based access. Each team can have up to three administrators. Administrators and recorders can add or edit player names and numbers; ordinary members are read-only, and administrators manage membership and permissions. Share player information only when authorized and avoid unrelated contact details or sensitive information.

5. Live links and historical viewing

Anyone with a valid live text broadcast link can view it without installing the app. It may show team names, player names and numbers, lineups, rules, timers, scores, batter/pitcher information and play text, but no live audio or video. Forwarding expands the audience. A temporary broadcast expires after successful closure, one hour after the game ends, or one hour without synchronization or an online heartbeat. Expiry does not delete the local game or a shared team archive.

In Android 1.0.0, a team's fixed broadcast links can display the score and pitcher, current batter, and each team's lineup. Once an authorized administrator or scorer selects a game, the app syncs broadcast data such as scores, batter and pitcher information, team names, player names and numbers, and lineups to our service. Anyone with a valid link can view it, including people outside the team. Administrators can rotate the code to invalidate older links. Fixed broadcasts display scoring information and do not transmit live audio or video. Confirm you have permission to publish the players' information before broadcasting.

Historical viewing for shared games is separately set to permanently open, approved viewers only, or closed. Open links may be viewed by anyone who has them and may later be restricted by an authorized person. Closed web viewing does not remove authorized in-app team access. Restricted viewing processes the applicant’s chosen name, request identifier, random viewing session and authorization result. A necessary Secure, HttpOnly browser session cookie maintains viewing authorization; it is not used for advertising or cross-site tracking. Clearing cookies or switching browsers may require reauthorization.

Viewing pages offer no public game directory and ask search engines not to index them. Revocation stops subsequent access but cannot retrieve screenshots, exports, external caches or offline copies already saved by others.

6. Retention, backups and deletion

• You control local data and can export or delete it. The app maintains available local automatic backups and upgrade recovery copies; these are not remote cloud backups. Deleting the app may remove its documents. External exports must be removed separately.
• Shared team archives remain until an authorized administrator deletes games or dissolves the team. Closing historical web viewing, ending a game, leaving a team or uninstalling the app does not delete shared games for the team.
• Deleted cloud games have a 30-day recovery period. Dissolving a team immediately closes member access and sharing; recovery within the original permission scope is available for 30 days. Recovery does not automatically restore old memberships, invitations or viewing access. Game content is purged after expiry.
• The shared service creates encrypted daily backups. Routine team backups follow a 30-day retention period. The deletion recovery period and daily-backup expiry operate separately. Restores continue to apply deletion and revocation records rather than reviving revoked access.
• Complete data and configuration backups made for migration verification, rollback and recovery are managed separately from routine team backups and currently have no automatic expiry. Access is restricted to necessary personnel. Copies will be cleaned up to the necessary scope as migration closeout is completed; the routine retention period does not mean every copy is cleared within the same period. Contact the operator on this page to clarify the scope of a personal-data deletion request.
• Necessary operation attribution, objects and timestamps are kept for security and audit. Names are cleared after dissolved-team expiry. Deletion markers, revocation digests and operation identifiers that cannot be used to view or reconstruct game content may remain to prevent stale devices or backups from restoring access.
• Legacy and local-only temporary broadcasts are removed on expiry or successful closure and are not backed up as long-term team archives. Service restarts may end these temporary broadcasts earlier; their removal does not delete the local original.

Recovery cannot guarantee zero data loss. Keep important complete archives outside the app. Restoring a local backup does not overwrite the entire shared service; reconnect and verify shared state afterward.

7. Providers, regions and security

The website, online services and independent backups use Tencent Cloud infrastructure. The provider processes requests as needed for hosting, networking, storage and security. Current production online services and primary business data are located in Shanghai, China. Routine team backups use independent private object storage in the Shanghai region. Old data, journals and backup copies in Hong Kong, China, remain for migration verification, rollback and recovery, with restricted access; they are not a separate externally writable primary service. These migration copies currently have no automatic expiry and will be cleaned up to the necessary scope as migration closeout is completed. We will update this policy if regions or processing arrangements change.

Transfers use HTTPS, access is controlled by member/device permissions, and backups are encrypted with keys held separately. IP addresses and other connection information are processed to respond to requests and apply rate limits. Operational information is limited to service operation and security troubleshooting. We do not intentionally record rosters, game payloads, link secrets or credentials in logs. No security measure eliminates every risk. Protect your devices and administrator recovery card.

We use no advertising SDK, cross-app tracking, third-party behavioral analytics or additional crash collection SDK, and do not sell game or player data. Apple’s store, TestFlight diagnostics, system sharing, email and other services you select have their own policies.

8. Access, correction, revocation and deletion

Within your permissions, you can view or export records, correct games, deactivate players, revoke members or devices, leave a team, delete cloud games or dissolve a team. Deactivating a player preserves historical results. Disabling synchronization, leaving or uninstalling is not a substitute for a deletion confirmed by the server.

Use mutually confirmed device pairing or a new invitation when changing devices. Administrators should save their recovery card in advance. A team name or nickname alone cannot restore management rights without a valid device or recovery card. There is no personal phone/email registration account to close using a login password; team exit, revocation, authorized deletion and privacy requests remain available.

Contact us to request access, correction, deletion, limits on public availability or withdrawal of relevant authorization. We verify the requester’s relationship to the information and permissions before acting. We do not need device secrets or a complete database. We cannot restore local information that was never uploaded or backed up.

9. Minors, support and updates

The app is a match recording tool without a public community or chat. A parent, guardian or authorized team representative should obtain appropriate authorization before entering, sharing or publishing a minor’s information. Prefer display-appropriate nicknames and uniform numbers. If information is inappropriately exposed, stop forwarding it and contact the team administrator and us.

If you contact support, we receive the contact information, messages and attachments you provide solely to resolve the request, and delete them when no longer needed, except where retention is legally required.

When processing changes, we update this page’s date and explain the applicable changes. New upload or public sharing features describe their scope before activation. Upgrading does not automatically share local games. See the support page for operating instructions.