Frequently asked questions

No. The project is in Phase 1 of 4 (Foundation) and has shipped zero releases. Installers are a Phase 4 deliverable — the downloads page explains exactly what will be true when they exist. Anything claiming to be an ITISYOU download today is not from this project.

A real repository, a processed design system, a decided and pinned engine (CEF 144 / Chromium 144.0.7559.261, SHA1-verified on disk), and the Phase 1 browser foundation in active development on Windows. The progress page renders the live milestone data; the development story gives the narrative.

The source is not published yet — it is private during early development, and commits are local until the project has a remote. The policy will be revisited before release. We won't call the project "open source" until a repository is actually public.

There isn't one, on purpose. Milestones ship when they have implementation, tests, and verification — the roadmap commits to order and scope, never to quarters.

The codebase contains no telemetry endpoints and no crash-upload path — there is nowhere for a "silent ping home" to go. Because the product hasn't shipped or been independently audited, we phrase this as a property of the current code that is re-verified at every milestone, not as a marketing guarantee. See the privacy approach.

Today: the AI runtime exists only as disabled interfaces — no provider configured, no API keys, zero provider calls. It cannot read your browsing because nothing AI-shaped runs. Future AI (Phase 3) will be opt-in with explicit, per-action, auditable access. Full detail on the AI philosophy page.

No. There is no account system and no sync service. All data — history, sessions, workspaces, permission decisions — lives in separate local datasets on your machine. If an optional sync feature ever exists, it will be opt-in and documented, and local-first stays the default.

Chromium 144.0.7559.261 via the CEF binary distribution (CEF 144.0.34), Chrome runtime style, Views framework — chosen in ADR-001 after a full environment audit ruled out a source fork for now. Chromium's process model, sandbox, and Site Isolation stay at upstream defaults. Details on the architecture page.

No — Electron is explicitly disallowed as the permanent runtime, and it isn't used even as a stopgap. ITISYOU is C++/CMake embedding CEF directly, with the sandbox preserved (on Windows, via the bootstrap.exe + application-DLL pattern). Electron documents itself as unsuitable as a security boundary for arbitrary untrusted content; a browser is exactly that case.

The browser chrome is trusted HTML served over the internal itisyou:// scheme in a privileged view. Web content runs in separate sandboxed views with no privileged bindings, and the one JS-to-native bridge is denied to web content at three independent layers. See the security model.

Windows, Linux, and macOS from one CMake project. Windows is the active, in-development target; Linux and macOS are architecture-ready (wired in the build system) but honestly labeled unverified until those environments are available.

Not yet, and we won't imply otherwise. Phase 1 implements standard networking only, behind a network-mode abstraction designed so Tor and proxy modes can be added in Phase 2/3 without rearchitecting. Until a Tor mode is built and verified, ITISYOU makes zero anonymity claims — if you need Tor today, use Tor Browser.

Nothing of the sort is committed. If a network mode beyond standard/proxy/ Tor is ever proposed, it will appear on the roadmap first, with its threat model stated — not as a marketing checkbox.