Delete your Omni Remote account

How deletion works

Open the account-deletion page at omniremote.app/account/delete in a browser; you do not need to install the app. To send a request, sign in to your own account with a verified email address and complete a full sign-in within the previous five minutes, including two-factor authentication if enabled. The page asks you to confirm the consequences and shows the recorded request date and status. Sending the same request again does not create another request.

Your request waits for an administrator's approval. Until approval, sending a request alone does not delete your account or stop its access. Once an administrator starts deletion, account sessions and cloud device credentials are blocked, and the account's cloud connections are disconnected. The workflow then performs external cleanup and removes associated live server records. A request awaiting external cleanup or an administrator retry is not completed deletion. Processing is manual and we do not promise a fixed completion time.

Current availability on 10 October 2026: the web request page is published, but final automated erasure is awaiting configuration and verification of subscription-provider cleanup. Do not treat a submitted request as proof that your data have been deleted. Use the web page to record and track an account-deletion request.

The deletion workflow covers the cloud account's profile and email, password and linked sign-in identities, two-factor secret and recovery codes, sessions and temporary authentication records, registered cloud devices, access grants, subscription state and the deletion request. It also addresses linked RevenueCat customer data and Mailgun bounce, complaint and unsubscribe entries that can be identified as belonging to the account. RevenueCat cleanup is asynchronous; external errors or a profile shared with another named account prevent completion and require an administrator's follow-up. The workflow must avoid deleting another person's data.

Account deletion does not itself remove personal files on your PC, local preferences or diagnostic files on your devices, operating-system backups, delivered emails, Mailgun delivery logs, or Google Play's own transaction records. An anonymous RevenueCat profile that has never been linked to your account cannot always be identified from that account alone. Local direct connections are independent of your cloud account. Hosting logs, backups and support correspondence have the retention limits described above.

After supported cleanup succeeds, only a minimal completion receipt remains: a random request identifier and completion time, without the account ID, email, profile or authentication secrets. Deleting an account does not permanently reserve its former email or sign-in identity; a later explicit registration can create a new account.

Deleting an Omni Remote account does not automatically cancel a Google Play subscription. Manage or cancel it in Google Play separately. For privacy questions or requests concerning other personal data, the published contact is [email protected].

You can use direct control without creating a cloud account, disconnect a PC, disable its cloud connection, revoke a registered cloud device, sign out, or clear saved mobile preferences. These actions do not by themselves delete your cloud account.

Data covered by your request

There is currently no published fixed retention period for hosting logs, backups or support correspondence. RevenueCat, Google Play and Mailgun have their own retention practices. For a deletion request, we explain any records that must be retained, the reason and the applicable period; this policy does not promise an unverified universal deletion deadline or backup-erasure schedule.

Deletion requests retain the account identifier, random request identifier, date and processing status while approval or cleanup is incomplete. Successful supported cleanup removes the account-linked request. A minimal receipt containing only its random request identifier and completion time remains so a repeated confirmation can return the same result. The receipt contains no account ID, email, profile or secrets and has no automatic expiry configured.

Local settings and diagnostic files on your own devices, operating-system backups and Google Play's own transaction records are separate. See the full privacy policy for storage details and your local controls.