DawnOX / PRIVACY & PREVIEW NOTES

A clear view
of what’s connected.

The website preview and the desktop browser are different things. Here is what each one does today.

Updated October 6, 2026.

This website

The DawnOX site is a static product website. Its source contains no advertising scripts, analytics libraries, login, payment form, or email collection form. The tab-switching and approval demonstrations run entirely in your browser, do not connect to your computer, and reset on reload. The demo does not write cookies or local storage.

When the website is served through Cloudflare, the hosting provider processes network requests to deliver and protect it. The site’s lack of analytics does not mean the host has no access to request information such as IP addresses. Any additional hosting-level analytics would need to be reviewed separately.

The desktop browser and phone companion

DawnOX is a Chromium-based desktop browser built with Electron. Its paired phone companion can view page previews and issue commands inside the browser, including opening, switching, and closing tabs, navigating, clicking, scrolling, and typing. Pair only a phone you control and trust.

AI request forwarding is separate from general tab control. Supported website integrations are opt-in and provider-dependent. Provider accounts, subscriptions, and the handling of information on those websites remain subject to the respective provider’s policies.

What passes through the connection

The current development code encrypts paired-phone request and response content between the phone and laptop, including page previews and browser commands. The managed connection service being prepared forwards this encrypted content. It still processes connection metadata, including device identifiers, timing and network addresses. Encryption does not make this a cloud-free service.

The managed account service being prepared uses Supabase for authentication and account/device records, and Cloudflare for connection routing. Account information, device ownership, connection permissions and access-plan status are handled by the service separately from encrypted browser content. No managed public service is announced as live by this website.

The laptop retains request and reply history subject to its retention settings. Those settings do not promise deletion from every log, database journal, backup or filesystem snapshot. Production retention periods, deletion/export support, hosting regions and service-provider arrangements must be finalized before customer launch.

The phone companion is a web application. Its encryption relies on the delivered client code and the security of both devices; an actively compromised client-delivery service or device can defeat that protection. No independent security certification or forward-secrecy guarantee is claimed.

Use development builds carefully

Do not use development builds for passwords, payment details, sensitive customer accounts, or confidential work. Signing, notarization, dependency updates, provider compatibility tests, and further security verification are release tasks, not guarantees implied by this website.

A published download must match signed production release metadata and the final artifact checksum, with the required platform signing checks completed. It does not establish that the application is vulnerability-free. Never bypass operating-system protections simply because a website tells you to.

Connection limits

The laptop must remain awake, online, and running DawnOX. The companion controls website content inside DawnOX, not operating-system dialogs, file pickers, or other desktop applications. Page previews are refreshed snapshots rather than a live video stream.

Private development testing can explicitly enable a temporary tunnel, whose address may change after restart. Public builds require a configured managed connection service, account sign-in and device ownership checks. That service is still being prepared and must be deployed and verified before public phone access is offered.

Before public distribution

These are product and technical notes, not a claim of regulatory compliance or a complete customer privacy policy. Before a hosted service or public browser release launches, the operator’s identity, contact details, service providers, retention settings, user controls, and appropriate privacy terms need to be finalized.