Khel Vision
Privacy policy
What Khel Vision collects, what happens to a match you give it, what stays on your phone, and how to have any of it deleted.
We use the recordings, frames or selected sources you provide to find rallies, build a server reel when you request one, and operate and support the service. That is all we use them for. The Android app builds reels on your phone; Studio can build them in your browser or on the service. Section 9 explains Studio.
1What this policy covers
Khel Vision is operated by Avi Dullu. This policy covers the Khel Vision Android app (com.khelvision.app), Khel Vision Studio and this website.
Where a section describes one of those in particular, it says which and applies to that one: the diagnostics in section 2 are what the Android app sends, and section 5 is about this website at khelvision.com — not about Khel Vision Studio, which runs at app.khelvision.com and loads Google’s own sign-in code to sign you in. Section 9 describes Studio’s browser storage and requests. Your account and the data we hold for it are the same whether you reach them from the app or from Khel Vision Studio, which is why deleting your account from either one deletes the same account.
It is written to be read, not to be survived. Section 4 is the part most people are actually asking about.
2What we collect
| What | Why |
|---|---|
| Your email address, and the identifier of your sign-in account | You sign in with your Google account. Google confirms it is you through Firebase Authentication, a Google service that handles sign-in for us, and we link the account it confirms to your Khel Vision account. We receive your email address and the identifier Firebase gives that account, never your Google password. We use them to sign you in, to keep your matches with your account, and to reach you about your access to the alpha. |
| The match recording you give us | To analyse it and return the rallies in it; in Khel Vision Studio, to build a reel you ask for; and to operate and support the service (section 3). |
| Technical details of a match and its analysis | File name, size, duration and format; the identifiers of the upload and the analysis; timestamps; and whether it succeeded. Needed to resume an interrupted upload and to tell you what went wrong when something does. |
| Server logs | Ordinary request records, including an IP address, kept for security and for diagnosing faults. |
Android app diagnostics
The Android app reports how it is being used and how failures end, so faults can be found without asking you to reproduce them. This is on by default, and you can turn it off at any time in Settings → Diagnostics → Share diagnostics. Turning it on takes effect the next time you open the app.
| What | Why |
|---|---|
| Which steps you reach, and how each one ends | Steps such as signing in, switching accounts, preparing a file, uploading, analysis, browsing the rallies, editing and export each report that they started and how they finished — completed, cancelled, or failed with a category of failure. This is how we find out that, say, uploads on a particular network are failing at the same point. An upload also reports which of the app’s ways of sending a match it took: in parts, whole, as frames taken from it, or through a live session. Recording a match live reports the same way, and in more steps than any other part of the app: opening the session, waiting for it to be ready, each piece of the recording as it is sent and acknowledged, keeping the session alive while you record, the rally updates that come back, and how the match ended — finished, cancelled, or added to your library. What those reports add are counts and the sport you picked: how many pieces the recording was sent in, which piece a report is about, and how many rally updates arrived. What is in the recording is never among them. A live session also says whether it came from the camera or from a video you picked; a picked video sent through a live session reports the same steps as one recorded live. |
| Technical detail about a failure | The stage it happened at, a category for the cause, the HTTP status where a request was involved, and how many attempts were made. Where the app showed you an error code, such as KV-S15, that code is reported too, so a failure can be counted by the code you would quote to us. |
| Requests the app makes to us | Which endpoint was called — as a route, never the populated address — the response status, and which attempt it was. Most are recorded for only a sample of requests; a request that fails, and any request belonging to signing in or to a live recording session, is always recorded. When the app starts it also reports which version of our service and of our analysis engine answered it. |
| Technical detail about a file or a reel, never either | Its duration, its resolution and a size band — not the file, not the file name, and not a thumbnail. A reel you are assembling reports its length in the same way, before there is any file to measure. The same kinds of detail describe a match you record live, measured on their own subjects: its resolution and frame rate come from the finished recording, which is the only place either can be read; the duration is how long the session ran rather than how long the finished file is; and the size band is one per piece sent, not one for the whole recording. |
| How long a step took | Steps report their own elapsed time: starting the app, preparing a file, transcoding, uploading, analysis, a search, opening your moments, showing the first frame of one, and an export. A live recording adds how long it waited to become ready, how long it took to open, how long each piece took to send, how far behind the rally updates were, and how much of its recording permit remained when it was renewed. Where our server asks the app to wait before trying again, that interval is reported too. For transcoding and export we also report how that time compared with the length of the video itself, which is what tells a fast phone from a slow one. These are how long something took; what Google’s own services record about your sessions is separate, and described below. |
| How many of something there were | How many pieces an upload or a live recording was sent in and which piece a report is about, how far a cancelled upload had got, where a resumed one restarted, how many rallies came back and how many a filter left, how many you picked for a reel and how many were exported, and how many rally updates a live recording received. How many sections of a match our server had finished analysing when the app checked on it. Also how much of what a screen needed was already on your phone. Counts, never what was counted. |
| Choices you made, and what was already in progress | How you sorted your moments and how you reordered a reel; which sign-in method you chose and which sport; whether your video needed converting and whether a reel was built from the converted copy; whether you were signed in when the app started, whether the app was in the foreground when it checked on a job, and whether an upload or an analysis was running when you switched accounts. |
| What the app did about a problem | When an upload is interrupted the app has several ways to pick it back up, and it reports which one it chose — waiting and retrying, asking you, signing you in again, or stopping. When you submit a match it reports whether we analysed it fresh, served a result we already had, or recognised it as one already done. |
| How our server said it received each piece of a live recording | For each piece of a match recorded live, the server’s own word for what it did with it, passed on unchanged rather than interpreted. |
| Whether a finished live match reached your library | Added, still to be retried, or no longer possible — usually because the recording your phone kept has since been reclaimed. This one is our app’s own verdict on your device, not anything our server said. |
| How far your phone’s clock is from ours | Measured once each time a live recording asks permission to send a piece. A phone running a second ahead of our server is enough to have that permission refused, and that shows up in no error count — only in this number. |
| Identifiers that let one action’s events be read together | The upload, analysis and session identifiers our own service issued, plus an identifier generated for each thing you do in the app. |
| Which app you send a reel to | If you share a finished reel, the name of the app package you picked from the share sheet — never the reel, and never anything in it. |
| A pseudonymous identifier for your install | Created by Google Analytics for Firebase. It is not your email address, and it is not derived from your account. |
| Crash reports | If the app crashes or stops responding, the error and the stack trace are reported. |
What diagnostics never include. Your videos or any frame of them; your email address; file names; sign-in codes, passwords or access tokens; or anything you type as a player label. No diagnostic event carries an account identifier, and where one refers to a recording it carries a reference derived on your own phone that we cannot turn back into the recording. This paragraph is about diagnostics alone — what the app sends us in order to analyse a match is the table above and section 3.
Diagnostics are processed on our behalf by Google Analytics for Firebase and Firebase Crashlytics. Those services collect a surface of their own that the app does not choose and cannot filter: your device model, operating system version, app version and language, an approximate location derived from your IP address, and a set of automatic events that Google defines and adds to — among them the app being opened for the first time, a session starting, time spent in the app, and the app being updated, cleared or removed. Crashlytics also captures uncaught errors and app-not-responding events by itself. None of that can be switched off while diagnostics are on; turning diagnostics off stops it.
The list of what diagnostics never include is a rule the app applies to everything it sends itself. A crash captured by Crashlytics is the exception: its message is whatever the code that failed put there, and the app never sees it before it is sent. We write that code to keep such values out of error messages, but we cannot promise it there the way we can for the rest.
If you turn it off. Analytics stops immediately. Crash reporting stops when you next open the app — it cannot be stopped in the middle of a running session — and any crash reports still held on the device are deleted rather than sent. This does not erase diagnostics already sent to Google or ordinary service requests and logs needed to operate your account.
We do not ask for, and have no use for, your date of birth, your contacts or your device’s advertising identifier — the app requests no advertising permission and the analytics SDK is configured not to read one. It asks for no location permission and never reads your device’s location. The only location involved is the approximate one Firebase derives from your IP address while diagnostics are on, described above.
3What happens to a recording you give us
Whether you record the match live in the Android app, record it with Record on this phone, or pick an existing file, the app converts the recording into a format that can be uploaded and sends it to us. A match recorded with Record on this phone is sent automatically, in the background, once you are connected; you agree to that before you start recording it.
On our side it is stored and analysed to find the rallies in it. Doing that produces further copies and processed versions, and those are covered by this policy in the same way as the recording itself. The analysis returns a list of rallies, which comes back to your phone and is stored there. Studio can instead submit a recording, extracted frames, or a link or library selection from which the service obtains the recording. It can also ask the service to build and store a reel from your selections.
Your recordings are not used to train models or evaluate models, and they are not sold, rented or used for promotion or advertising. We use them only to provide your requested analysis and reels, and to operate and support that service. Operator access is limited to that purpose. The service uses Google Cloud for hosting and storage and RunPod for GPU analysis. These providers process data to provide the service to us; Gemini is not used to process Khel Vision uploads.
4What stays on your phone in the Android app
In the Android app, two things stay on your phone:
- The reel you make. Reels are cut and exported on the device. No reel is ever uploaded to us, and we never see one.
- Everything you do after the rallies arrive. Watching, picking, trimming, reordering and exporting all happen locally, with no further request to us.
A match you record with Record on this phone is kept as an original in the app’s own storage, not in your photo library, and is also sent to us as section 3 describes. The reel the app builds from it is made on the phone like any other. The original stays when you sign out, and when you delete the match from your library. Removing this account’s data from the phone, or deleting your account from the app on this phone, removes it. Deleting your account anywhere else, such as in Khel Vision Studio, signs this phone out the next time the app reaches us and leaves the original on it. Clearing the app’s storage or uninstalling the app removes it.
A reel leaves your phone only when you send it somewhere — a share sheet, your gallery, a message, a social platform. That is your act, and what follows from it is covered by section 7.
5This website
This site sets no cookies, and loads its fonts and its scripts from its own domain.
It counts visits without a script. Cloudflare, the company that hosts this site, serves every page. To deliver and protect the site it processes each request — including your IP address, the page asked for, the time, the address of the page that linked you here if there was one, and the browser and device details your browser sends with it. From those requests Cloudflare gives us aggregate counts, such as requests, visitors and the countries they come from. We see totals, not people. Nothing runs in your browser to collect this, so blocking scripts does not change it.
Cloudflare also keeps its own operational and security logs of requests, under its policies.
6How long we keep things, and how to have them deleted
The Android app keeps a match and its analysis with your account until you delete the match or account. Studio’s friend-beta policy is to remove uploads and derived results within 72 hours. That ordinary expiry is separate from the cleanup target after account deletion below. Deleting a match in the Android app removes the device copy and requests removal of our copy, except that the original of a match recorded with Record on this phone stays in the app until this account’s data is removed from the phone (section 4); deleting a video in Studio requests removal of the service-held copy, not a file you saved separately.
Server-log retention varies by destination; the deletion page distinguishes configured Cloud Logging periods from journals and destinations whose maximum is not established. Account records — your email address, the identifier of your sign-in account and the fact that you have access — are kept while your access lasts.
Diagnostics events and crash reports are held by Google Analytics for Firebase and Firebase Crashlytics under those services’ own retention. Our diagnostic events omit the Khel Vision account identifier; installation identifiers remain pseudonymous data.
Where a diagnostic event refers to one of your recordings, it carries a reference derived on your phone from a key that never leaves it and that belongs to the signed-in account alone — not the recording, and not a value we can turn back into one. Removing your account data destroys that key, so references produced before and after a removal cannot be connected, and the same recording under a different account on the same phone produces a different reference. The pseudonymous install identifier Google Analytics for Firebase creates is separate, and removing your account data does not remove it. Turning diagnostics off stops new Analytics collection; it does not delete that identifier or records already held by Google. Uninstalling the app does not erase records already sent either. Provider retention is described on the deletion page.
You can ask us for a copy of what we hold about you, or ask us to correct it, by writing to privacy@khelvision.com. We will answer within 30 days.
To delete your account, use Delete account in the Android app or in Khel Vision Studio, or write to hello@khelvision.com. Delete your account gives the steps for each. Account deletion covers all data associated with your account: the information we hold for it, whether you supplied it or it was created through your use of Khel Vision in the Android app or Khel Vision Studio, including copies our service providers hold on our behalf. The Android app also removes its local confirmation records under section 7. Studio can leave browser entries behind, as explained in section 9. It does not delete your Google account.
Deletion is permanent and cannot be undone. Once we accept the request your account is closed and permanent deletion begins; there is no period in which it can be cancelled or the data recovered, and cleanup continuing in the background is not such a period. We aim to finish deleting your data within seven days of accepting a request — a target rather than a guarantee, for the reasons set out on that page, which also lists the limited exceptions that remain afterwards and for how long.
The Android app’s other account actions are not deletion. Sign out and Sign out everywhere end sessions and keep your data on the phone; Remove from this phone clears the account’s data from that phone only. After any of the three, your account and the data we hold for it remain.
7Your responsibilities for the footage you provide
The same two conditions as Terms section 6, stated here because they are as much a privacy matter as a contractual one: they are about other people’s faces.
- A source you give Khel Vision must be a recording you personally own or are authorised to provide.
- Every identifiable person in it must be an adult who agreed to being recorded.
Footage involving minors must never be submitted, on any plan, for any purpose.
The Android app asks you to affirm both conditions for every recording, and asks you again before a reel leaves it. It records what you affirmed — the sentences as they were shown to you, and when — in a record on your device. That record is not sent to us. It is kept so that a later rewording of this page cannot change what an older confirmation appears to have claimed.
We cannot inspect footage to check who owns it or how old the people in it are. We ask, we state the rule, and we record the answer. That is the whole of what we can honestly do.
8Changes, and how to reach us
When this policy changes, the date at the top of the page changes with it. A change that affects what we collect or what we do with a recording will be described here before it takes effect, not after.
Privacy questions and requests: privacy@khelvision.com.
9Khel Vision Studio in your browser
Studio uses the same Khel Vision account and the same restrictions on recordings as the Android app. Google and Firebase handle sign-in. Studio sets secure security and session cookies; a session lasts up to five days unless ended earlier. Signing out ends a session, not your account.
Studio keeps browser entries for upload recovery, interface choices, an upload-permission acknowledgement and work that continues after a reload. These can include an account identifier, file fingerprint, job identifier, source reference or file name. Job or video references may also appear in the page address and browser history. Not all browser entries are removed on sign-out or account deletion, and they have no universal automatic expiry. Clearing site data removes remaining browser entries; it does not delete the account or server-held data. Files you save separately remain under your control.
Depending on the available route, Studio sends a recording, extracted frames, or a link or library selection from which the service obtains a copy. Transfers can go directly to Google Cloud Storage using temporary permissions. Camera recording may include sound when you grant microphone permission. Live capture can send frames while recording. What the service holds as a result is data associated with your account, deleted as section 6 describes. Independent library originals and files you downloaded are not held by us for your account.
Reels built entirely in your browser remain there until you save or share them. For a server-built reel, Studio sends your selections and the service builds and holds the result. Fetching results, playing service-held media and checking jobs also send requests. Ordinary service logs may include network information, request and job identifiers and errors. Android’s Firebase diagnostics disclosure in section 2 does not describe Studio’s browser behavior.
Studio stores an upload-permission acknowledgement in the browser. It is not the Android app’s per-recording record of the exact responsibility statements and their version. The conditions in section 7 still apply to every recording.
10Signing up for app testing
The testing form records the email you enter, your selected platform, your agreement to participate, the notice version and the submission time. We use these to manage the test and contact you about testing. We do not add you to marketing mail. The form does not verify ownership of an entered address.
The form also records which page of this site it was on, without the rest of the address. If the link that brought you to the form carried campaign tags — utm_source, utm_medium, utm_campaign and utm_content, which say where a link was shared — it records those tags too, so we can tell which invitations bring testers. Both are taken from your first visit to the form in a browser tab and kept in that tab's session storage until it is closed, so a later link opened in the same tab does not change them. They are stored with your signup and expire with it.
This site passes the form to our registration service, which also runs on Cloudflare. Cloudflare stores the response in its D1 database. Responses expire 90 days after submission; a daily purge removes expired rows. Short-lived secret-keyed network counters limit repeated submissions; raw IP addresses are not stored in these signup tables. Service providers may retain their own operational logs under their policies. This form sends no verification email and creates no signed-in browser session.
When email copies are enabled, we use Resend to send you a copy of the testing instructions. Resend receives your email address and the message content to deliver the email. You can use the installation steps on the page even if the email does not arrive. This email does not verify address ownership or grant app access.
You complete Google Group membership, Play testing opt-in and TestFlight enrollment on Google's and Apple's pages under their respective policies. Submitting this form does not prove that you joined a group, installed an app or used it, and does not create app analysis permission. To remove a signup response, contact privacy@khelvision.com.