Owned by one. You.
Sovereignty isn't a privacy policy here - it's the architecture. One is built so that the most private, capable thing in your life answers to a single party, and never sells you out.
It runs on hardware you own
The intelligence lives on your device, iPhone, Mac, or a desktop supercomputer. Your life isn't uploaded to be useful.
Consent is scoped and revocable
Discover, request, approve, read. Outside agents get the smallest scope, for the shortest time, and only after your tap.
A ledger only you can read
Every interaction and consent is written to a ledger only you can read, a perfect, portable memory of what happened and who touched what.
Your data is never the product
We collect only what we must, your platform, who you are, your region, your email. Never rented, shared, or sold. That restraint is the company.
Discover. Request. Approve. Read.
Discover
An outside agent finds the capability - without seeing your data.
Request
It asks for a specific scope, purpose, and duration.
Approvethe gate
You review and approve with one tap. Deny, and nothing moves.
Read
Only that scope, only that window - then it's gone, on your ledger.
What we measure, plainly.
This website uses Google Analytics 4 and, when configured, Google Tag Manager, alongside first-party analytics. We do not claim an independent privacy certification.
Our browser event helpers exclude raw search queries, prompts and answers. They record usage counts, lengths, page paths, interface actions and performance measurements. Some values are bucketed; others are exact counts or rounded timings. Query strings are removed from page paths, with search queries replaced by a redacted marker.
These are not all anonymous aggregate counts. Some app events include a session ID, model or device information. First-party collection can associate events with an authenticated user ID or an anonymous identifier. Google’s collection can also include browser, device and network information. Signing in and submitting a search are separate product operations; first-party search records can contain the search itself.
The Google analytics storage setting defaults to denied and follows your PCHP analytics choice. Loading Google scripts and recording events are still measurement activity; denied storage is not a promise of zero network requests.
Read the machine-readable event schema. It documents the first-party event envelope and representative fields, not a third-party audit or a restrictive allowlist. The source links in the schema show the collection and filtering code.
See consent and your ledger in action.
Approve, deny, revoke: the consent gate
Every outside request stops at your tap. See how to approve, deny, and pull access back.
Watch & read the lesson →Reading your private ledger
A perfect, private record of who touched what - and how to read it.
Watch & read the lesson →The most personal technology you'll ever own.
Reserve a One and see ownership by architecture for yourself, a private transparency log you can read, and an agent that asks before it acts.