Security
Your clients' words stay yours.
Aevon is built for a business where a compliance officer will ask exactly how it works. This page answers the questions we hear first. The full Security Policy is linked below, and I will answer anything else on a call.
Where the data lives
On Render, on Amazon Web Services, in the United States. Every record carries the firm it belongs to and every query is scoped to that firm, so no advisor or firm can reach another's data. That separation is enforced in the application and covered by tests. It is not a separate database per firm.
Who can see what
An advisor sees their own clients. The firm's owner sees the firm's whole book. Any other role exists only where the firm has asked for it. A sign-in from Claude or ChatGPT sees exactly what the advisor who approved it sees, nothing more, and can be revoked at any time.
In transit
Everything travels over HTTPS with TLS. Plain HTTP connections are refused.
At rest
Two layers. The database disks are encrypted (AES-256). Transcripts, a client's personal details (name, date of birth, contact details) and the most sensitive parts of the file are encrypted again inside the application (AES-256-GCM, a fresh initialization vector per row) with a key the database never holds. A copy of the database on its own is unreadable.
Passwords and sessions
Passwords are hashed with scrypt and a unique salt, never stored or logged in the clear. A session expires after eight hours and requires signing in again.
Recordings
Aevon keeps transcripts, not recordings. When the notetaker joins a Zoom, Teams or Google Meet call it takes the platform's caption text; no audio is recorded or stored. A recording you make or upload in the app is transcribed and then discarded; the audio is not kept.
The AI models
Transcripts and client context go to Anthropic (Claude) for analysis, and to OpenAI for the search index and for transcribing recordings made or uploaded in the app. Both are used through their APIs, which do not use the data to train their models. Aevon does not train models on client data, and it will not connect to an AI app such as Claude.ai or ChatGPT until the advisor confirms that app will not either.
What is claimed
Nothing is said about a client without the sentence and the date behind it. Anything on file without both is counted and held back. The advisor can correct any line, and the original stays on file with the change.
Retention
Meeting transcripts and per-meeting records are kept for seven years so a firm can hold them as part of its books and records, and they can be exported at any time. Whether that satisfies a particular firm's obligations under SEC Rule 204-2 or FINRA Rule 4511 is the firm's determination with its own counsel. Aevon has not obtained a legal opinion on the point and does not claim one. Operational data outside that framework can be deleted within thirty days of a verified request.
Export and deletion
A full export of a firm's data, in a machine-readable format, within thirty days of a written request. On termination, everything outside the books-and-records window is deleted within thirty days.
Logging
An append-only audit log, kept for seven years: sign-ins, password changes, client records created, changed or removed, transcript processing, and administrative actions. Available to your compliance officer on request.
SOC 2
Not yet underway. We will not claim a certification we do not hold, and we will say so plainly here when the audit starts.
Subprocessors
Who else touches the data, and for what.
All in the United States. Each is reviewed for its security and data-protection practices before use. Customers get at least thirty days' notice of a material change to this list.
| Subprocessor | Purpose |
|---|---|
| Anthropic PBC | Language-model analysis of meeting transcripts and client context |
| OpenAI LLC | Text embeddings for the search across a client's file, and transcription of recordings made or uploaded in the app. The audio is transcribed and not kept |
| Recall.ai | Sends the notetaker to Zoom, Microsoft Teams and Google Meet calls and delivers the caption text. No audio is recorded or stored. |
| Render Services Inc | Backend hosting and the managed PostgreSQL database, with AES-256 disk encryption and daily backups |
| Vercel Inc | Frontend hosting and content delivery |
| Stripe Inc | Billing. Stripe receives billing identifiers and amounts; no client meeting content. |
| Resend | Transactional email: sign-in links, password resets, product notices |
| Functional Software Inc (Sentry) | Error reports from the app and the server: stack traces and request metadata, with personal data switched off |
| Google LLC (Google Analytics) | Usage measurement on the website and the app: pages viewed, device, approximate location. No client content |
| Cloudflare Inc | Delivery of the website: DNS and traffic proxy. The app's data goes to Render directly and does not pass through it |
Found something
Report a security issue.
Write to logan@aevonintelligence.com with what you found and how to reproduce it. You will hear back within two business days, and confirmed issues are fixed promptly. Please give us a reasonable chance to fix a problem before publishing it.
Logan Lee, founder
In private development
Send this page to your compliance officer.
If they have a question this page does not answer, I would rather hear it before you sign than after.