Trust roadmap

Here is exactly what we can prove about your privacy today, per hosting option — and what we can't yet. We'd rather show you the gap than word around it.

Last reviewed 9 July 2026

How to read this

This is the trust-claim ladder we hold ourselves to internally, published in full. Every privacy claim alwyse makes, the hosting option it applies to, and its honest status — shipped, or not. The rule behind it is one line: no sentence on this site may run ahead of what's actually shipped on the tier it describes. Publishing the ladder is how we keep that rule — public copy can't quietly outrun a public table. You'll see gaps below. Showing them is the point.

The three hosting options

Managed beta

The hosted beta most people use during early access. It runs on the same industry-standard isolation as typical cloud software — a real protection, but not the operator-blind guarantee. We don't claim operator-blindness here.

Self-host

You run alwyse on your own hardware. No one at alwyse and no cloud administrator can reach your content — because there is no one but you in the loop. The strongest guarantee available today.

Confidential cloud

The tier we're building toward: hosted, but sealed inside confidential-computing hardware so that not even we can read your content — and your device can verify it. Not available yet.

Statuses, not dates

We don't publish target quarters. A slipped date on a trust page is just a broken promise, which costs a trust brand more than never promising. Each cell says where the guarantee actually is:

  • Shipped Real today — rely on it now.
  • Building Actively in progress.
  • Designed The approach is specified; the build hasn't shipped.
  • Not started A committed goal we haven't begun.
  • Not offered Not part of this tier — by design, or because it doesn't apply.

The ladder at a glance

Each claim, per hosting option, with today's honest status. The plain-language detail — and where each guarantee stops — is spelled out claim by claim below.

alwyse trust claims by hosting option and current status, as of 9 July 2026
Claim Managed betaStandard isolation Self-hostOperator-blind today Confidential cloudAttested — building
No alwyse employee or cloud admin can read your content Not offeredStandard cloud isolation ShippedYou run it DesignedBoundary specified, not built
Your device can cryptographically verify that blindness Not offeredNothing to attest Not offeredYou hold the keys DesignedShips with the tier
Your content never reaches an outside model vendor Not offeredUses your vendor key ShippedWith local models DesignedIn-enclave inference
You can take everything out (export) ShippedServed by your instance ShippedFull local takeout DesignedPath built, arrives with tier
You can delete anything (deletion) DesignedNot user-reachable yet DesignedNot user-reachable yet DesignedArrives with the tier

Claim by claim

No alwyse employee or cloud admin can read your content

  • Managed betaNot offered
  • Self-hostShipped
  • Confidential cloudDesigned

On self-host this is simply true: you run alwyse, you hold the keys, and no one at alwyse is in the loop — there's nothing to trust us about. On the managed beta it is not true, and we won't pretend otherwise: the beta uses standard cloud isolation, the same kind most software you already rely on uses. That's a reasonable protection, but a determined operator with infrastructure access could reach your data — so we don't call the beta operator-blind. Confidential cloud is where we close that gap without asking you to run anything: your content sealed inside confidential-computing hardware. That build isn't shipped yet — the boundary is designed, not delivered.

Your device can cryptographically verify that blindness

  • Managed betaNot offered
  • Self-hostNot offered
  • Confidential cloudDesigned

A promise you can't check is just a promise. Attestation is the proof: your device asks the hardware to show it's running the exact sealed software we published, before it trusts anything to it. On self-host there's nothing to attest — you already hold the keys and run the code, so the question doesn't arise. On the managed beta there's nothing to attest either, because the beta isn't operator-blind to begin with. Attestation is the defining feature of the confidential cloud tier, and it ships when that tier does. Until then, we don't claim it.

Your content never reaches an outside model vendor

  • Managed betaNot offered
  • Self-hostShipped
  • Confidential cloudDesigned

AI needs a model to run, and where that model runs decides who sees your content. Self-host with local models — like Ollama — keeps everything on your machine; nothing leaves. Self-host with your own cloud model keys is your call, but then your content goes to that vendor under their terms, and we say so plainly rather than blur it. The managed beta runs inference through your own vendor key today, so the same egress applies there. Confidential cloud is designed to run inference inside the sealed enclave, so your content never leaves it — that arrives with the tier.

You can take everything out

  • Managed betaShipped
  • Self-hostShipped
  • Confidential cloudDesigned

Ownership means you can leave with everything. Full export ships today: a complete takeout of your observations, the cognition alwyse derived from them, your media, and your preferences — served directly by your own instance, never passing through our servers. On self-host and the managed beta you can do this now. On confidential cloud the same content-blind export path is already built; it becomes available the moment that tier does.

You can delete anything

  • Managed betaDesigned
  • Self-hostDesigned
  • Confidential cloudDesigned

Ownership also means you can erase. The deletion path — remove a single memory, or everything derived from a connected source, and have it cascade through what the system inferred — is designed and partly built, but not yet wired to a control you can reach. So today we mark it designed, not shipped, on every tier. It's a pre-broad-launch commitment, and it's the first row here that will move to shipped as it lands.

What these guarantees don't cover

Operator-blindness is a strong claim, so here is exactly where it stops — stating the edges is the point, not the fine print hidden at the bottom. Even where alwyse is operator-blind, the guarantee is about software and administrative access to your content. It does not defeat a valid legal order for data you hold; it does not claim immunity from someone with your unlocked hardware in hand; and it rests on the limits of the secure-enclave hardware we build on, which has documented failure modes of its own.

Some metadata — that a request happened, its rough size and timing — stays visible so the service can run, even on tiers where its content is not. We'd rather you know the shape of the guarantee than discover its edges later.

"We'd rather show you the gap than word around it."

The rule this page exists to keep

Why publish the gaps at all?

Because a transparency page that only shows the wins isn't transparent. Putting the whole ladder in public makes it self-enforcing: no marketing sentence can quietly claim more than this table admits. If you ever catch one that does, it's a bug — tell us.

Where this is going

The destination is simple to state and hard to earn: a version of alwyse where no one but you can read your life-log — on every tier, verifiable by your own device — and where you can take it all out, or delete it, whenever you want. We're not there yet. This page is the honest scoreboard of how far we've gotten, and it changes in the same breath the product does.

Privacy & Trust How it works Join the waitlist