Your account.
Your choice.

Delete a self-created cloud account

1. Open Delete your account at the existing service. The service may still be named AI Smart Screen.
2. Sign in again with the account you want to remove. Signing in for deletion does not create a new account.
3. Review the account shown and the deletion consequences. Nothing is deleted merely by opening the page.
4. Choose Delete my account to confirm. The confirmation is single-use and requires a recent sign-in made for deletion.

Once recorded, deletion ends the account's and its screens' access to that cloud service immediately. It removes all screens in that account and cannot be undone. Connected AI clients also lose that account's access and cannot recreate it automatically. The service allows a new, empty account from 24 hours after self-deletion by explicitly approving a screen again.

If the reply is lost or says deletion is unconfirmed, reopen the account page and sign in again to check whether an account still exists. A recorded deletion finishes its cleanup without needing a repeated confirmation. If the daily service budget is exhausted, follow its notice to retry after 00:00 UTC, or contact the operator.

Invited accounts or help with deletion

Accounts set up by invitation are deleted by the operator. Email contact@duellab.org and say that you want to delete your Screen for AI service account. Gábor Eifert, an individual in Dunaharaszti, Hungary, operates the service and handles these requests. Authority over the account must be checked; do not email passwords, access tokens or pairing codes.

What is removed, and when

Remaining application-controlled account and screen data is removed within 24 hours after deletion is recorded. Deleted internal account/screen IDs and deletion times may remain for up to seven days to prevent deleted data returning. The ordinary service also keeps a keyed deleted-identity hash in memory for one day to limit immediate re-signup.

Cloudflare's built-in 30-day recovery history can still contain older service data. The application does not expose or use restoration, and provider-controlled residual copies follow their own policies. These periods do not promise physical erasure of every copy everywhere.

Remove phone-local content and access

Cloud-account deletion does not erase the pages or values kept on an offline phone. Use the phone's native Clear remote content control to remove app-managed remote pages and state. Returning to the clock alone does not clear that data.

A page can also save information in the embedded browser, separately from app-managed state. Clear remote content is not a complete wipe of that browser data. For a broader app-data reset, use Android Settings to clear the app's storage. This also removes app setup and saved approvals, so you will need to set it up again. It does not delete cloud or other providers' data.

Independent Wi-Fi approvals are separate from the cloud account. Open Connected agents on the phone and remove the relevant access if you want that local client to stop. The local clock and locally approved Wi-Fi mode do not require a cloud account; they have no cloud account to delete unless you separately connected one.

Delete an Auth0 profile separately

Service-account deletion does not delete the Auth0 login profile or the sign-in records Auth0 holds. Email the operator at the contact above if you also want that profile removed, and state whether you want both operations. Auth0's published guidance describes 14 months of encrypted offline backups of deleted identity data; this is separate from active service-data removal.

Deleting this service account does not delete an account or data held by your AI provider, Google or another separate provider. Use that provider's own account/privacy process for those requests.

Website example choices

Use Reset example on the homepage to clear the active example, or reload the page to reset all three. The website code keeps those choices in memory only, with no browser storage or transmission to the product service.

Last updated 18 October 2026.

Read the privacy notice ↗