Khel Vision
Delete your account
How to delete your Khel Vision account and its data, and how that differs from signing out or removing the account from one phone.
The privacy policy says what we keep and why, and the terms of use cover the rest of using Khel Vision.
1What this page covers
This page is for Khel Vision, including the Android app (com.khelvision.app) and Khel Vision Studio. Deleting your Khel Vision account affects that account and its data across both.
It does not delete your Google account. You sign in to Khel Vision with Google, but the Google account is yours and stays as it is.
2Request deletion without the Android app
Write to hello@khelvision.com with the subject Khel Vision account deletion. Send it from the email address you sign in with, and tell us you want your Khel Vision account and its associated data deleted.
Do not send your password, a sign-in code, an access token or a copy of your recordings. We never need any of them. We may need to check that the account is yours before we delete it.
If you no longer have access to that email address, say so in your request, and we will explain what is needed to confirm the account is yours. Sending the email does not by itself mean deletion has happened; we will write back to confirm the outcome.
You can also open Khel Vision Studio, sign in, choose Delete account in the account controls, and follow the confirmation and sign-in prompts.
3Delete from the Android app
Open Settings → Account → Delete account, read the confirmation, and complete the sign-in prompt.
Not every version of the app has this action yet. If the version on your phone does not have it, use Studio or the email request above.
4What deletion removes
Deleting your account removes your Khel Vision account and all data associated with it: the information we hold for that account, 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 only exceptions are the limited records in section 6, each with its reason and how long it is kept.
Once we accept the request, the account is blocked while any remaining cleanup on our side finishes. Accepting the request and finishing it are separate steps, so do not assume that a network error means the request did not reach us.
On Android, when the app confirms that we accepted the request, it clears that account’s data held by the app on the phone. If that is interrupted, the app tries again the next time it starts.
Deletion cannot remotely erase offline copies on another device, the originals in your photo library, reels you exported, or copies you shared to other services. Remove those yourself, on the device or service that holds them.
5Signing out, and removing data from one phone
Settings has four account actions. Only the last one deletes your account.
- Sign out ends your signed-in session on this phone and keeps the account’s data on it.
- Sign out everywhere, if you signed in with Google, asks you to confirm your identity with Google, ends your account’s sessions on every device, and then signs this phone out. Like Sign out, it keeps the data on this phone. Your account and the data we hold for it remain.
- Remove from this phone, in versions that have it, removes that account’s data held by the app from this phone, and works offline. Your account and the data we hold for it remain.
- Delete account asks us to permanently delete your Khel Vision account and its associated data, and then clears it from this phone. It does not delete your Google account, and it cannot reach other devices or copies already exported or shared (section 4).
6What we keep, and for how long
Accepting your request closes the account and starts cleanup immediately. We aim to finish deleting all data associated with your account within seven days, apart from the exceptions below, and most of it finishes much sooner — nothing waits out the seven days on purpose.
Seven days is the target we work to, not a guarantee. We have not yet verified that every system enforces it, and some of the cleanup is still being built. We would rather tell you that than publish a deadline we cannot keep, and we will say so here when it becomes a promise we can stand behind.
| What | Why it is still there | For how long |
|---|---|---|
| All data associated with your account | This is what deletion removes, including copies our service providers hold on our behalf. Cleanup runs in the background once we accept the request, rather than all at once, and your access ends immediately either way. The rows below are the exceptions. | We aim to finish within seven days of accepting the request, and usually much sooner. This is our target: no automatic rule on our storage enforces it yet. |
| Backups of our service’s own state | Recovering the service if something goes wrong. A backup taken before your deletion may still contain your data until it is cleaned up or replaced. | No maximum is established yet. The automatic clean-up of backups is still being built, and we will not state a period we cannot keep. |
| Server logs that can be linked to your account | Security, and diagnosing faults after the fact. | Our default Cloud Logging buckets retain entries for 30 days, and required Cloud Audit Logs for 400 days. No maximum has been established for VM journals or other logging destinations; these settings are not a limit for every server log. |
| Diagnostics and crash reports held by Google | Finding faults without asking you to reproduce them. Our diagnostic events omit the Khel Vision account identifier, but Google’s installation identifiers are pseudonymous data, not anonymous data. Turning collection off does not erase reports already sent. | Google documents 90 days for Crashlytics traces and associated identifiers before removal from live and backup systems begins. Our Google Analytics properties are set to retain event data for 2 months and user data for 14 months, with user retention reset by new activity. Those controls do not limit standard aggregated reports. Account deletion does not erase prior diagnostics. |
| Authentication information held by Firebase | Signing you in, securing the service and preventing abuse. | After we request deletion of your Firebase user, Google documents removal of other authentication information from live and backup systems within 180 days. Logged IP addresses are retained for a few weeks. This does not keep your Khel Vision account open. |
| A one-way record that the account was deleted, and a status-only receipt | Refusing a late attempt to restore deleted data, and letting an app that lost our reply find out what happened. Neither is a kept account, and neither holds your recordings. | The status-only recovery capability expires 30 days after we accept the request. The one-way anti-resurrection record expires 30 days after cleanup completes. Neither clock is a limit for recordings, backups, logs or other provider records. |
| Planned restricted deletion history: a one-way digest of the internal account identifier, a keyed fingerprint of its verified email address, an opaque deletion request identifier and the cleanup-completion time | Confirming that an account existed, recording its deletion, and preventing deleted data from being restored. It holds no recordings or other content, and it cannot be used to recover your account or its content. | Not enabled in the production service we inspected on 3 October 2026. The proposed history has no automatic expiry; its status-recovery digest expires 30 days after acceptance. We will update this page when the history is enabled. It contains no raw email address, creation timestamp or restorable profile. |
The logs, the diagnostics, the deletion record and the account-history record are not a kept account and not recoverable media. None of them can be used to bring your account, your recordings or your analyses back, by us or by anyone else.