Privacy
What SmartVision processes, why it needs that information, and the choices you have.
Updated September 10, 2026
Current service notice. SmartVision access is limited to approved accounts. These terms and the privacy notice describe the service as operated on the date above.
Service operator
JR Learning Plus LLC
A Pennsylvania limited liability company, United States.
support@tennis-smartvision.appTraffic and performance statistics
Vercel Web Analytics and Speed Insights help us understand visits and improve page performance. They process page views, referrers, approximate location, browser/device information and page-performance measurements. We remove URL queries and fragments, allow only named application pages and disable custom analytics events. We do not send recording contents, filenames, profile details or sign-in tokens as analytics event data.
Profile and video defaults
Account settings store your chosen display name, playing hand and default video preferences on the processing server to personalize your workspace and initialize new recordings. You can correct these details in Account settings. These details do not change your sign-in identity; playing hand does not drive automated analysis.
Information processed
Firebase Authentication verifies your identity with the Google or Apple account you choose. It processes a Firebase user identifier, the provider account identifier, email and profile details the provider releases, and short-lived Firebase ID tokens. SmartVision stores recordings you submit, filenames, playback copies, analysis results, manual edits, player names, court calibration, and exports. Recordings may contain faces, voices, locations, or other personal information. Service and hosting logs may contain network addresses, request details, timestamps, and errors. Support email contains the information you choose to send.
Why it is used
Information is used to authenticate access, import and process recordings, save corrections, play and export videos, recover completed work, troubleshoot failures, and respond to requests. Where data protection law requires a lawful basis, processing requested by the account holder supports providing the service; necessary security and troubleshooting support the legitimate interest in operating a secure service; legally required handling supports compliance with legal obligations. Those interests must be balanced against affected individuals’ rights.
Your videos and analysis
The application processes recordings for the analysis you request. The current shot helper can learn from reviewed examples within that same recording. The current implementation does not send recordings to a general-purpose generative AI service or use them to train a shared model. Human corrections are stored with the recording and take priority over automatic proposals.
Service providers and access
The hosted service uses Vercel to deliver the website, Firebase Authentication to manage sign-in, Google Cloud for video processing and storage, and Google or Apple as identity providers. Support email is received through Resend, which processes the sender and recipient addresses, message headers, body, and any attachments. SmartVision creates a support issue in a private GitHub repository containing the sender and reply-to addresses, received time, message body, and attachment filename and type metadata. Attachment contents are not copied to GitHub, and support messages are not forwarded to Gmail. A limited delivery record is stored in Google Cloud to prevent duplicate issues. Workspace administrators may access stored information to operate, troubleshoot, and recover the service. These providers process information under their own applicable terms and privacy notices. The app does not create public recording pages or offer public sharing links. Exported files that you download and share are under your control.
Location and transfers
Your browser sends information to the configured hosting, authentication, and processing services, which may process it in countries other than your own. Provider agreements and transfer safeguards apply as required by applicable law. Local mode stores and processes recordings on the machine running SmartVision; importing a Drive file still contacts Google.
Retention and deletion
SmartVision currently retains recordings, derived files, edits, and completed-work backups until the administrator removes them. There is no automatic recording deletion schedule or self-service recording/account deletion flow. Signing out or clearing your browser does not delete server recordings. Backups are retained separately and may still contain material removed from live storage. Ask the administrator about removal from both live storage and backups before submitting sensitive material.
Your choices and rights
You can decide which recordings to submit, correct annotations, download an MP4 or analysis JSON, and sign out. Depending on applicable law, you may also have rights to access, correct, erase, restrict, object to processing, or receive a portable copy of personal information. Use the contact page to make a request; identity or authority may need to be verified. Where applicable, you may complain to your data protection authority. Rights may have legal exceptions.
Browser storage and security
Firebase Authentication uses browser storage to keep you signed in and refresh expiring ID tokens. SmartVision keeps the current ID token in memory while the page is open; the language preference and last-opened recording reference use local storage. See the cookie policy for details. The hosted service uses authenticated requests and expiring media access links. No system can promise absolute security. Avoid sending credentials or private recordings in a support request.
Children and changes
SmartVision is not offered directly to children. The uploading adult is responsible for permission to process footage involving children or other players. Contact the administrator if material has been submitted without appropriate permission. This notice will be updated when processing practices change; the date above identifies the current version.