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 4, 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 development architecture uses a relay between your desktop and phone. The relay can process page previews, tab information, commands, and AI request context. The current connection is not end-to-end encrypted. Do not assume a relay operator is unable to see the information passing through it.

The current browser documentation describes request and reply history expiring after 30 days. That is not a guarantee that every server log, database journal, or backup has the same retention. This website does not provision or operate your pairing relay.

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 verified download entry means the release maintainer has checked the public artifact and supplied its version and checksum. 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.

Development pairing can use a temporary HTTPS address. That address may change after a restart or recovery, so you may need to pair again. A permanent website domain does not, by itself, create a permanent phone relay.

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.