A clear view
of privacy.

Who to contact

For privacy questions or a data request, email contact@duellab.org. Gábor Eifert is the data controller for the service. Screen for AI is its product name, formerly AI Smart Screen; the older name can still appear in the existing service and sign-in flow.

The current hosted-service privacy notice remains at the existing service address. It applies to that connection; this website and phone-only use have the separate scope described below.

What this website does

The examples use synthetic content. Choices are kept in the page's memory, reset on reload and are not sent to an AI, phone or mailing-list provider. The website code does not write cookies or browser storage.

The website includes no analytics, advertising, tracking pixels, external fonts, account creation or submission form. Its scripts, styles and illustrations are local files.

Cloudflare hosts this website. To deliver and protect it, Cloudflare processes visitors' network and request information, such as IP addresses and the pages requested. The website runs no server code of its own, and the operator does not enable visitor logging or analytics for it. Cloudflare's own security and operational records follow Cloudflare's policies.

If you choose to email support, your email address and message go through your email provider and the operator's existing Proton mailbox so the operator can respond. They are not added to a beta-updates list. Support-message retention still needs its final public review; you can ask the operator about access or removal.

On your phone and over Wi-Fi

The phone-owned mode keeps pages, page values, returned interactions, approvals and screen settings on the phone. The clock and a locally approved Wi-Fi client do not require a Screen for AI cloud account. You approve or remove local clients in the phone's native controls.

The page state managed by the app belongs to a retained page revision. A replacement revision starts with fresh app-managed state; an unused page can be removed when space is needed. Clear remote content removes app-managed pages and state. A page can also save data separately in the embedded browser; this control is not a complete browser-data wipe. Interaction history is bounded, with seven-day availability where the phone can establish its age; cleanup runs when the app runs. This is not indefinite storage, a cloud backup or a promise to erase an offline phone by a fixed time.

When you use the internet service

A self-created service account is made when you sign in and approve your first screen. Signing in alone or connecting an AI client does not create one. The service keeps a random account ID, a keyed hash of the sign-in identity and its creation time. It also holds approved-screen names, keys and credential hashes, approval and expiry details, removal status and bounded usage/security records. These identify an account or screen even though they are not the person's full email address.

On the phone-owned internet route, page content passes through the service's memory. The service retains delivery identifiers, fingerprints, status and times rather than the page itself, bounded to the latest 512 operation records and 64 page identifiers per screen. The connected screen's latest status, settings and software-version report is held with its live connection in memory.

The older hosted relay route, available to invited installations, can store the pages' HTML, latest values and returned interactions. It also holds screen registration and connection information, and an optional Firebase Cloud Messaging token if wake-up notifications are enabled. Authorized AI clients and the operator can access content handled by the service; this is not an end-to-end encrypted path.

Sign-in, AI providers and cookies

Auth0 by Okta handles the internet service's sign-in. It gives the service your name and email address; the service immediately shortens the email, does not store or log the full address, and uses only the sanitized name and shortened address for display. They can appear on the approval page and the phone you approve, where people nearby can see them. These display values stay in bounded memory sessions, not permanent service storage, and never decide access.

The service stores one necessary browser-session cookie while signing in, approving a screen or deleting an account, for at most 15 minutes. Auth0 sets its own sign-in cookies. The service does not use analytics, advertising or tracking cookies. This website does not set this service cookie.

Cloudflare supplies the hosted service and network protection. Auth0 supplies identity; Google may participate in Google sign-in or older relay wake-up notifications. Providers may process information outside the European Economic Area, including in the United States, under their applicable processing and transfer arrangements. EU storage of the service's Durable Object does not mean every incoming request or provider log stays in the EU.

The AI apps you connect are separate services under their own terms and privacy notices. Their providers process the pages they send and the answers they retrieve. Screen HTML, page values and interactions are not sent to Auth0 by this service. Support email uses Proton separately from sign-in and page delivery.

How long service data remains

• Accounts and screens: registration records remain until deletion, including removed-screen records. Details of a screen waiting for pairing approval remain for at most ten minutes.
• Older hosted-relay content: the service keeps selected page content and latest state according to the screen report it has accepted. Unneeded or failed pages and state are removed within 24 hours after active-delivery protection ends. An offline phone may show a page whose selection the service has not confirmed.
• Undelivered commands: they expire within seven days; remaining payloads are removed within another 24 hours. An unconfirmed page can lose its hosted copy even while still visible offline.
• Returned relay interaction values: up to seven days from service acceptance, or sooner on an accepted deletion request; replay metadata has a separate registration lifetime.
• Account deletion: access ends immediately once deletion is recorded, and remaining application-controlled data is removed within 24 hours. Deleted internal account/screen IDs and deletion times may remain up to seven days to stop deleted data returning.

The ordinary service also uses short-lived security and daily-usage records: a keyed network-address hash in memory for about ten minutes, a day's account usage for that day, and a deleted identity's keyed hash in memory for one day to limit immediate re-signup. They do not contain page answers. Cloudflare processes the network address itself for delivery and protection.

Provider history and residual copies

Cloudflare's built-in 30-day recovery history can contain deleted service data and can be accessed by deployed code or an operator able to change it. The application does not expose or use restoration and creates no additional application-data backups. Thirty days is a recovery window, not a guarantee that every provider copy is erased then.

Deleting a service account does not delete its Auth0 login profile. Auth0's published guidance, originally recorded on 10 September 2025 and rechecked for this notice, describes 14 months of encrypted offline backups of deleted identity data. Provider-controlled residual copies follow provider policies and can outlast active application deletion; no universal physical-erasure deadline is promised.

Purposes and your rights

Account, connection, delivery and answer-retrieval data is used to provide the service you request, on the contractual basis described in the existing service notice. Security, abuse limits and deletion-suppression records support the legitimate interest in a safe, available service. The connected service cannot work without its required technical data; the local clock and independently approved Wi-Fi mode remain separate.

You can ask the operator for access, correction, deletion, restriction, objection or portability where applicable. You can also complain to the Hungarian National Authority for Data Protection and Freedom of Information (NAIH), or the relevant authority where you live or work. Use the contact above; do not include passwords or tokens in a request.

Beta updates

The beta will be open to everyone, with no invitation or waiting list. An optional email list to announce its start is being prepared and is not open yet; this website collects no email addresses. Before the list opens, this notice will be updated with the email provider, what is kept, for how long and how to unsubscribe.

Deleting an account

A self-created cloud account can be deleted after signing in again and confirming on the service's account page. Invited accounts and Auth0 profile requests need operator assistance. Cloud-account deletion does not remotely erase phone-local pages or independent Wi-Fi approvals; use the native phone controls for those.

Read the account-deletion guide ↗

Last updated 18 October 2026. The connected service's own notice remains in force at its existing address.