UR Cricket Video Analysis: Umpire
Features How to use Support

effective May 17, 2026

Privacy, disclaimers, and disclosures.

Cricket Video Analysis: Umpire is built as a local-first cricket video review tool. It records delivery clips, supports frame-by-frame review, can coordinate co-umpire and observer access, and can submit selected clips for optional AI trajectory support. This page explains what data is used, when it leaves the device, and what the app does not claim to do.

Operator and contact

Cricket Video Analysis: Umpire is provided by teJai Technologies LLC. Contact support@tejai.tech, www.teJai.tech, or +1-520-369-2026. Privacy, deletion, support, billing, and legal requests should be sent to support@tejai.tech.

Age, permission, and venue responsibility

You must be 18 years or older to use this app. The app is intended for adults acting as umpires, match officials, coaches, analysts, or authorized match helpers. Do not use it if you are under 18.

Cricket clips may show or record players, umpires, coaches, spectators, voices, uniforms, venue surroundings, timestamps, team names, and match context. You are responsible for following all recording, privacy, child/minor consent, venue, school, club, tournament, and league rules before recording or sharing clips.

Decision-support disclaimer

ICC describes the Decision Review System as a technology-based process for assisting match officials, not replacing them. This app follows the same philosophy: it is an evidence and review aid. It is not an official DRS system, not a certified ball-tracking system, and not a substitute for an umpire.

MCC Law 36 and ICC DRS protocols show why LBW review is not a single calculation. Pitching, first interception/impact, whether the ball touched the bat, genuine attempt to play the ball, no-ball status, and whether the ball would have hit the wicket all matter. Our app can help organize and estimate evidence, but it does not know every legal or match-context fact automatically. The umpire always makes the final decision.

Accuracy limits

Technical and AI analysis can be affected by shaky body-worn video, single-angle evidence, missed ball detections, low light, motion blur, occlusion by the batter or fielders, inaccurate calibration, missing post-bounce frames, phone overheating, dropped frames, network delays, or incorrect manual marks.

Confidence scores, projected paths, 3D reconstructions, and AI summaries are advisory. They should be reviewed together with the actual video, frame stepping, match laws, and the umpire's own judgement. A high confidence score is not a decision. A low confidence score does not decide the appeal either.

Local-first data model

By default, match clips, trial clips, calibration clips, timing sidecar files, match setup details, review records, local clip protection status, and app preferences are saved on the device. No match video automatically leaves the device.

The app stores local metadata such as match name, team names, date, stadium, umpire names, match ID, co-umpire/observer codes, over and delivery labels, role selection, start/stop timing, clock offset, frame duration, readiness results, calibration status, and whether a clip is protected from automatic cleanup.

Camera, microphone, storage, and network permissions

Camera access is used to record cricket delivery clips and calibration clips. Microphone access may be used if the device video recorder includes audio. Storage/media access is used to save, pick, review, share, export, and analyze video clips. Network access is used for Firebase match/session records, optional AI/cloud features, website links, activation code validation, and selected clip upload.

The app asks for platform permissions where required. If a permission is denied, related features may be unavailable or limited.

Optional AI analysis and cloud backup

AI analysis and complimentary 30-day cloud backup are optional paid match add-on features. They are not required for local recording and frame-by-frame review.

If enabled, selected clips, selected calibration videos, timing sidecar data, match metadata, and the analysis request payload may be uploaded to Firebase/Google Cloud and processed through Vertex AI or another configured AI service. Upload is user-triggered; it is not automatic during live match recording. This is intentional to protect battery, mobile data, thermal performance, and recording reliability.

AI analysis is designed for a match-limited analysis window. Saved AI reports and selected uploaded clips may remain available for the stated cloud-retention period, currently up to 30 days, unless a longer period is needed for security, fraud, support, accounting, dispute, or legal reasons.

Co-umpire and observer access

The app can create match, co-umpire, and observer codes. A co-umpire code can allow another umpire device to participate in the same match workflow. An observer code is intended for view-only access to live preview or saved review clips where enabled. Share codes only with people authorized for that match. Anyone with a code may be able to access the permitted match view until the code or match expires.

Payments and activation codes

Payment checkout may be handled by Dodo Payments or another payment provider. The app does not store payment card details. We may store payment metadata, activation code status, product type, buyer email if supplied by the payment provider, match activation status, timestamps, and audit records needed for support, accounting, fraud prevention, abuse prevention, dispute handling, and legal compliance.

Service providers and data sharing

Depending on the features you use, data may be processed by Firebase/Google Cloud services such as Authentication, Firestore, Storage, Hosting, Cloud Functions, and Vertex AI. Payment checkout may be processed by Dodo Payments. We do not sell personal or sensitive user data.

Data may also be disclosed if required by law, to protect users or the service, to investigate abuse or fraud, or as part of a business transfer with appropriate notice.

Security and retention

Off-device communication uses HTTPS or Firebase/Google Cloud transport security. Local clips remain under the security of your device. You should protect your phone, match IDs, co-umpire codes, observer codes, and activation codes.

Local clips remain on the device until you delete them, clear app data, uninstall the app, export them, or the app removes older unprotected clips under storage pressure. Clips marked "Protect" are excluded from the app's automatic cleanup and require manual deletion. Optional cloud clips are intended to be retained for up to 30 days. Payment and audit records may be retained longer where required for business, tax, security, support, dispute, or legal needs.

Your choices and deletion

You can use core local review without purchasing AI/cloud. You can choose whether to upload selected clips. You can delete local clips from the app or device storage, avoid sharing pairing codes, protect important clips from automatic cleanup, and contact support for cloud deletion or privacy questions.

For deletion requests involving cloud records, include the match ID, activation code, or other information needed to locate the records. Do not send unnecessary sensitive information.

Google Play disclosure alignment

Google Play requires developers to accurately disclose data access, collection, use, sharing, security practices, and third-party SDK behavior. Because this app uses camera, optional microphone, storage, Firebase, optional cloud upload, optional AI processing, and optional payment activation, the app includes an in-app prominent disclosure gate before the main screen and this public policy page for Play Console and users.

Reference context

  • ICC Decision Review System overview
  • MCC Laws of Cricket, Law 36: Leg Before Wicket
  • Google Play User Data policy
  • Google Play Data safety section guidance