PrivacyDesign + current build

Privacy as architecture

Privacy promises are cheap; most browsers make them in a settings page while the architecture does something else. ITISYOU's approach is to make the architecture itself the privacy policy — and to state clearly what is verified today versus designed for tomorrow.

The browser — current development build

What the Phase 1 design does

Separate datasetsIn development

History, sessions, workspace data, and permission decisions are separate local datasets with separate boundaries — not one profile blob. Nothing is synced, uploaded, or shared; there is no account system.

Zero telemetry endpointsIn development

The codebase contains no telemetry or analytics endpoint and no crash-upload path. This is checked as part of milestone verification — a claim we re-earn at every phase, not a slogan.

Deny-by-default permissionsIn development

Camera, microphone, location, notifications: every request routes through one PermissionService whose default answer is no, with a local structured log of decisions.

AI cannot watchIn development

The AI runtime is disabled interfaces only — no provider, no keys, zero calls. See the AI philosophy for exactly what that means.

Status framing

"In development" above means: this is how the Phase 1 build is being constructed, and it has not yet shipped or been independently audited. We will not switch these to present-tense "guarantees" until each has verification evidence behind it.

This website

browse.itisyou.app practices what it preaches

  • No analytics, no trackers, no cookies. The site sets no cookies and loads no third-party scripts.
  • No external requests. Fonts are self-hosted; every script, stylesheet, and image is served from this domain. The Content-Security-Policy header enforces it.
  • No forms, no accounts. Nothing here collects your data, so there is nothing to leak.
  • Static by construction. Pages are pre-rendered files; the only dynamic route, /api/status, serves a static JSON document about the project — it reads nothing about you.

Standard web-server request handling (the hosting platform's operational logs) is the only data processing involved in serving this site.

Formalities

Not yet a legal document

This page describes real behavior, but it is not yet a formal legal privacy policy — there is no shipped product to attach one to. A reviewed policy will be published before the first release (Phase 4), and it will be held to the same standard as everything else here: it must describe what the software verifiably does.