TRUST
How Aether's AI features handle client information
What each AI-assisted feature sends to the model provider, when it sends it, what is kept, and how to switch it off.
Updated 19 August 2026
Aether uses an AI model to draft. It never uses one to decide. This page says exactly what leaves Aether, when, and what a firm can switch off — in enough detail for an IT or privacy reviewer, in plain enough language for an adviser explaining it to a client.
The provider is Anthropic PBC, through the Claude API. It is listed with every other third party on the subprocessors page.
Last reviewed: 19 August 2026.
The three rules that bound everything below
- The model has no authority. It never reads the database, never calls a tool, and never writes a record. Aether builds the context in code from queries scoped to one firm and one household, sends it, and parses what comes back into a strict, allow-listed shape. Anything a proposal would change is computed in Aether’s own code and applied only after an adviser confirms it.
- Nothing is sent until a person does something. Every feature below is triggered by an adviser action — a question typed, a transcript pasted, a document selected, a generation requested. The one exception is the morning briefing, which runs on a schedule the firm controls.
- A firm can switch it all off. One setting, described at the end of this page, disables every feature here. With it off, no request leaves Aether.
What each feature sends
| Feature | What triggers it | What is sent to Anthropic | What Aether keeps |
|---|---|---|---|
| Vesper — adviser chat | An adviser types a message | The message, plus context Aether builds in code: household name, status and stage, next review date and fee-consent expiry; each member’s name, role and fact-find date; funds under management; counts of tasks, goals and vault items; recent document titles; open task titles. Optionally the adviser’s own writing samples, if that adviser opted in | The conversation text, a 500-character excerpt in the audit log, and a usage row (tokens and cost — never content) |
| Morning briefing | A scheduled run each morning | The ranked briefing lines, which include household names and task text | The briefing text |
| Meeting copilot | An adviser pastes a meeting transcript and attests that participants consented | The full transcript (200–120,000 characters), with participants labelled by their names | The transcript is not kept by default — only its length and a hash. An adviser can choose to keep it through a separate confirmed step. The extraction summary is kept |
| Fact-find extraction from a document | An adviser selects a stored statement | The extracted page text of that statement (up to 50 pages / 120,000 characters) | A proposal only, until an adviser confirms it |
| Portfolio import | An adviser uploads a holdings file | The uploaded PDF (up to 20 MiB), image (up to 5 MiB), or its extracted text | A proposal only. Nothing is stored |
| Adversarial review | An adviser runs a review of draft advice | The draft plan: strategy codes, strategy names, advice areas, statuses, priority scores and rationale text, plus recommendation titles and the client’s internal id number — no name field, though recommendation titles are free text an adviser types | The review memo and its events |
| Client-portal assistant | A client asks a question in the portal | The question, plus sections of that client’s already-published advice documents | The answer, and only if every citation resolves. Off by default for every firm |
| Document narrative and polish | An adviser requests it for one generation, or runs an opted-in campaign | Structured section data — client names and figures — or template prose | The document |
| Migration mapping suggestions | An operator or admin runs analysis during a data migration | Archive item title and body (up to 4,000 characters), up to three 80-character sample values per source column, candidate client names | The mapping suggestions |
Uploaded files, meeting transcripts and statement text travel as content. That is inherent to what those features do: an extraction feature that did not send the document could not extract anything. It is stated here rather than buried, so a firm can decide which features to use.
What Aether does not send
- Passwords, password hashes, session cookies, API keys or any other credential.
- Bank account numbers, tax file numbers or payment details as a category of their own — though a document a firm chooses to send through extraction may contain them, which is why extraction is per-document and adviser-triggered.
- Any other firm’s data. Context is built under row-level security scoped to the requesting firm.
What Anthropic says it does with it
Quoted from the provider’s own published terms and policies, retrieved 18 August 2026:
- Training. Anthropic’s Commercial Terms of Service (effective 17 June 2025) state: “Anthropic may not train models on Customer Content from Services.” Its privacy centre adds: “By default, we will not use your inputs or outputs from our commercial products (e.g. Claude for Work, Anthropic API, Claude Gov, etc.) to train our models.” The exception it names is content a customer explicitly submits as feedback through Anthropic’s own thumbs-up/down control. Aether sends no such feedback.
- Ownership. “Customer (a) retains all rights to its Inputs, and (b) owns its Outputs.”
- Retention. “For Anthropic API users, we automatically delete inputs and outputs on our backend within 30 days of receipt or generation”, with exceptions for longer-retention services, agreed arrangements, policy enforcement and legal compliance. Where content is flagged by Anthropic’s automated trust and safety systems, it “may retain inputs and outputs for up to 2 years”, and trust-and-safety classification scores for up to 7 years.
- Zero data retention. Anthropic offers a zero-data-retention arrangement on request, per organisation, for eligible API features. Aether has not requested one. The models Aether uses — Claude Haiku 4.5, with a Sonnet 4.6 fallback — are not among those Anthropic excludes from the arrangement. If a firm’s obligations require zero retention, say so before signing: it is a change Aether would pursue with the provider, not a setting in the product.
Sources: Commercial Terms · How long do you store my organization’s data? · Is my data used for model training? · API and data retention
Anthropic is a United States provider. Aether does not pin a processing region for these calls.
What Aether has not done yet
Stated plainly, because a reviewer will find it either way:
- Client names are not yet pseudonymised before they are sent. A firm should read the table above as “these names go to the provider”. Replacing names with role tokens in the context Aether builds in code is hardening item SEC-6b.
- Adviser chat transcripts are kept without a purge window. A retention window for them is hardening item SEC-7a.
- Numeric grounding of chat answers is audited, not enforced. Figures in a Vesper chat answer are checked against the context and the mismatch is logged; they are not yet blocked. Every figure that reaches a document is gated: the document layer reverts any polished string whose numbers changed.
The controls a firm has
The master switch. Settings → AI assistance turns every feature on this page off for the whole firm. A firm administrator sets it, and Aether records who acknowledged this disclosure and when. With the switch off, features that can work without a model fall back to their deterministic behaviour and the rest are unavailable — no request leaves Aether.
Per-feature controls, on top of the switch.
- The client-portal assistant is off by default and must be turned on per firm.
- Document narrative is off unless requested for a specific generation.
- Adviser writing-style learning is per-adviser opt-in.
- Meeting copilot requires an explicit attestation that participants consented, and does not keep the transcript unless the adviser separately chooses to.
- Portfolio-import AI, adversarial review and voice learning each have their own operator-level off switch.
Spend and abuse bounds. Per-user hourly limits apply to every flow (Vesper chat 120, meeting extraction 12, AI document generation 20, portfolio-import AI calls 10), with a per-document call cap and per-request timeouts. Every call writes a usage row recording firm, user, flow, model, token counts and estimated cost — never content.
Disclosure. Each adviser sees a short version of this page inside Vesper before their first conversation and acknowledges it; the acknowledgement is recorded with their name and the time, and the chat endpoint refuses a turn until it exists — so this is a gate, not only a prompt. The meeting copilot carries its own disclosure and consent attestation on the page itself.
Questions
Email reid@aetherforge.au. Aether’s Security Review Brief covers the controls behind this page in full, and is available to a firm’s IT reviewer on request.