The file
What West holds on you is one file: your conversations across every channel, his case notes on them, the assignments you took on, and any notes he made from what you brought him. It lives in a database in the United States, scoped to your identity. Alongside the file the practice keeps operational records: usage metering (tokens, voice characters, avatar seconds), subscription state, and the bindings for channels you opened yourself.
Sealed rooms — the honest version
No code path in this product lets one client's file reach another client's session. That guarantee is enforced in the application: every read is scoped to your identity, and the operator's ledger is mechanically prevented from selecting file content — it sees counts and costs, never words. It is an operational guarantee, not yet a cryptographic one: the practice does not read client files, and the code does not serve them, but per-client encryption is future work, not present fact. We would rather tell you that than claim otherwise.
Who else touches the words
West thinks with Anthropic's models, speaks with ElevenLabs' voices, and appears through Runway's avatar. The site runs on Vercel, the database on Neon, sign-in through Privy, payments through Stripe, and mail through AgentMail. Your messages transit the providers needed to answer them — that is what “an AI you can talk to” means in practice. Your file is not used to train models: our model provider does not train on this API traffic under its terms, and we never hand your file to anyone for training, advertising, or sale. There are no ads here and never will be.
One narrow exception, stated in full. If you arrived from an advertisement we placed and then wrote a letter or paid, we tell the ad platform that its click led somewhere: the click's own identifier and a one-way hash of your address — never your name, never a word you wrote, and never for a letter the crisis line answered. Someone who found the door on their own is never reported to anyone.
Intake: referral packet, never filing cabinet
When you bring West a document, a page with an application, or an archive, he reads it and writes his case notes in his own hand. The honest sentence, in full: West does not store your source material. Each excerpt is processed by Anthropic, which may retain API inputs and outputs for up to 30 days under its terms. West stores only the notes you approve. An archive is opened in your browser — the raw file never uploads — and what leaves your machine is the text he reads, one bundle at a time, discarded when the request completes. His working notes during a reading are destroyed when you decide what to keep; the case history he writes enters your file only after you have read it and said so, and you can burn it instead — no copy, no record of what it said, no note that you declined it.
A filed archive history can later be removed: its notes are hard-deleted from your file and scrubbed from his working memory in one action, or the removal fails and tells you so.
The Shelf: the one place he keeps a page
There is one deliberate exception to the rule above, and it is yours to invoke, never his. A page you put on the Shelf is kept word for word — that is the point of it: he can quote back what you actually wrote, not his summary of it. The line: what he gathers (an archive, a calendar) is distilled and discarded; what you hand him for keeping is held as you gave it. He does not carry shelf pages into every conversation — one comes down only when what you're saying touches it, and passages he reads that way pass through Anthropic under the same up-to-30-day terms as anything else he reads. Taking a page back deletes it entirely: it was never copied into his notes, so removal leaves nothing behind. The Shelf, like the rest of your file, dies with your file if you delete it. If other people speak in a page you shelve — a session transcript, someone else's letter — you tell him so when you hand it over, and that marking is kept with the page.
Retention
A free sitting you walk away from is purged, file and all, after seven days. A client file is kept until you delete it. Two records are retained by design and survive deletion: the crisis log (safety referrals) and the audit log (the record that things happened — including the record of your deletion).
Taking it back
From your file page you can export everything — conversations, notes, assignments, channel bindings, usage totals, subscription state, your application, and your own crisis-referral records — as one document. You can correct what he believes by telling him, or drop any assignment he wrote down wrongly.
Deletion is one action and it is transactional: conversations, case notes, your letter's words, assignments, channel links, metering, and the voice line provisioned for you all go together, or the deletion fails and tells you so. Any live subscription is cancelled with it. What remains: the crisis and audit logs, the bare fact of your admission (your seat, not your words), a closed billing marker — so deleting can't mint fresh free sittings — payment records held at Stripe, and mail already sent to you in the mail provider's archive. On email, STOP always works; on Telegram, /unlink closes the line and the unprompted knock together.
Questions
Write to sol@drwest.ai. A machine reads it in character; the practice's operator reads the operational records only.