Privacy and data
AI Smart Screen beta uses a hosted service to connect your agent and your screen. Sign-up is open: anyone who can sign in with this service's identity provider can create an account, up to a limit for this beta.
Your account
Your account is created when you sign in and approve your first screen. Signing in alone, or connecting an AI client, does not create one. For it, the service stores a random internal account ID, a keyed hash of your sign-in identity (not your name or email address; it can be matched to your identity only with the service's secret key) and the time it was created. Your name and email address never decide what you may do. When the beta reaches its account limit, or the number of new accounts it accepts in one day, new sign-ups pause; accounts that already exist keep working. A self-created account can connect a limited number of screens, at once and in total, and removed screens count toward the total until the account is deleted. It also has a daily allowance of service use; when it is used up, the account is refused until the next day (00:00 UTC) and other accounts are not affected.
Everything the service stores or processes about you
- Account: the random account ID, the keyed hash of your sign-in identity and the creation time, until the account is deleted.
- Each screen you approve: the screen's name as you or the screen gave it (it may contain a person's name), the features the screen reported, its public key, a hash of its sign-in credential, and when it was approved, when its sign-in expires and whether it was removed. These stay until the screen or the account is deleted, also for removed screens. While a code is waiting for approval, the same details of the screen asking, with its Android and app version, are kept for at most ten minutes.
- Screens that use the internet route through this service: the screen's signed approval of this service (its own keys and identifiers), and for each page the service sent: identifiers, a fingerprint, its status and times, never the page itself, which passes through memory only. The service keeps the latest 512 such records and 64 page identifiers per screen. The screen's latest status report (whether it is connected, what it shows, its screen settings, and its Android, app and WebView versions) is kept only with its open connection and in the service's memory, and is shown to your AI clients.
- Screens that use the older relay route (only screens set up by invitation): the pages, values and interactions listed below, the screen's reported name, versions and when it was last connected, and, if the screen enabled wake-up notifications, its Firebase Cloud Messaging push token until the screen is deleted or the token is replaced. For each returned interaction the service keeps its type, the page it came from and its time until the screen is deleted; the values are kept as listed below.
- Your name and shortened email address: in memory only, as described above.
- Your network address: the service processes a keyed hash of it in memory to limit how often one address may use it, and forgets it within about ten minutes. Cloudflare processes the address itself to deliver and protect the service.
- Daily use: for a self-created account, how much of its daily allowance it used today, kept under the account ID for that day only.
- The AI client's self-reported name: passed to your screen with each page so it can show which AI sent it; in memory only.
- After deletion: the deleted account and screen IDs and the deletion time, for seven days, so that deleted data cannot return, and in this service's memory only, for one day, the keyed hash of your sign-in identity, so the same sign-in cannot create a new account again at once.
Who is responsible, and your rights
Gábor Eifert (Hungary) operates this service and decides how this data is used (the data controller); contact: contact@duellab.org.
Why the data is used, and the legal basis: to provide the service you asked for (your account, connecting your screens and AI clients, delivering pages and returning what you tap), because it is necessary for the agreement with you (GDPR Article 6(1)(b)); and to keep the service secure, available and protected from abuse (network-address limits, account and daily limits, the records that stop deleted data from returning), based on the legitimate interest in a safe and working service (Article 6(1)(f)). You do not have to give any of it, but the service cannot work without it. Nothing about you is decided by automated means beyond these technical limits.
Providers: Cloudflare (hosting and the network in front of the service) and Auth0 by Okta (sign-in) process data on the controller's behalf under their data processing terms. If you sign in with Google, Google confirms who you are to Auth0 under Google's own terms. Screens on the older relay route that turn on wake-up notifications also use Google's Firebase Cloud Messaging. These providers may process data outside the European Economic Area, in particular in the United States; where they do, they rely on the EU–US Data Privacy Framework or the European Commission's standard contractual clauses.
Your AI apps: the AI apps you connect (for example Claude or ChatGPT) are separate services under their own terms and privacy notices. What your AI sends to your screen, and what it reads back from it, is also processed by that AI provider.
Cookies: this service sets one cookie, only while you sign in, connect a screen or delete your account (at most 15 minutes), to keep that step secure. Auth0's sign-in pages set their own cookies to keep you signed in there. There are no analytics, advertising or tracking cookies.
Age: you must be at least 16 years old to use the service.
Your rights: you may ask for a copy of your data, to correct it, to delete it, to restrict or object to its processing, or to receive it in a portable form; you can delete your account yourself (see below). You also have the right to complain to a data protection supervisory authority: the Hungarian National Authority for Data Protection and Freedom of Information (NAIH, naih.hu), or the authority in the country where you live or work.
See also the Terms of use. This notice was last updated on 11 October 2026; a change is shown here with its date.
What is shared
The service stores your screen pages (HTML), their latest values and returned interactions. Authorized agents and the service operator can read this content; it is not end-to-end encrypted. Auth0 handles sign-in and identity information. We do not send your screen HTML, state or interactions to Auth0.
When you sign in, Auth0 shares your name and email address with the service. The service shortens the email at once (for example ei…87@gmail.com) and does not store or log the full address. It shows your name and the shortened email on the approval page and sends only those to the screen you approve, so the screen can show which account it uses; anyone near the screen can see them. They are display only and never decide what you may do. The service forgets them when your sign-in session ends (at most 15 minutes) and, for each screen, once that screen has collected them or its pairing code expires.
How long we keep it
- We keep the current page and latest state while the service's accepted screen report identifies it as selected.
- Old or failed pages and state are removed within 24 hours after they are no longer needed for an active delivery.
- Undelivered commands expire within seven days; their remaining payloads are removed within another 24 hours. A page whose selection the service has not confirmed can lose its hosted copy after this window, even if it is visible on an offline phone.
- Returned interaction values are kept for up to seven days from service acceptance, or deleted sooner on request.
- Account and device registrations last until deletion. Deletion revokes access immediately and removes remaining service data within 24 hours. Only deleted internal account/device IDs and deletion times may remain for up to seven days to prevent deleted data returning.
Provider copies
These deadlines apply to data controlled by our application. Hosting and identity providers may keep residual copies under their own policies for longer. Auth0's published guidance dated September 10, 2025 describes 14 months of encrypted offline backups of deleted identity data. This is dated provider guidance, not a measured erasure guarantee. We do not promise a universal deadline for erasing every provider copy.
Cloudflare history and location
Cloudflare provides a built-in 30-day recovery history for this beta's hosted data, including deleted pages, state, interactions, registrations and deletion records. The history can be accessed by deployed code or an operator able to change that code. We do not expose or use application-data restoration, including this history. Active-storage deletion deadlines still apply. Thirty days is a recovery window, not a guarantee that every provider copy is erased within 30 days.
Our Durable Objects execute and store data in the EU. Cloudflare may terminate TLS and process incoming requests globally; object identifiers may be logged outside the EU. We do not promise that every request or log remains in the EU.
Service failure and your phone
This beta does not create additional application backups or restore hosted application data. Irreversible server-storage loss may lose all hosted accounts, commands, state and history. Your phone keeps its local page and values. Reconnecting requires signing in again and pairing; old phone content is not automatically uploaded to the replacement service.
Delete your account
You can delete your account yourself: open Delete your account, sign in again and confirm. Your account and its screens lose access at once, and their remaining service data is removed as described above. An AI client still connected to the deleted account cannot create a new one. From 24 hours after the deletion you can create a new, empty account by approving a screen again. An account set up by invitation is deleted by the service owner on request.
Deleting your AI Smart Screen account does not delete your login profile at Auth0, which holds the profile your sign-in gave it (such as your name and email address) and records of your sign-ins to this service. To have that profile deleted, or for any other question about your data, contact the service owner: contact@duellab.org. Hosted deletion does not clear the page and values kept locally on your phone; use the phone's native clear/reset controls for those.