Security & controls
Your advisors sign the advice. They need to see where it came from.
This page is for the compliance and IT people evaluating Kemen. It covers how client data is held, who can see it, what the agents can and can't do without a person, and what your firm can show an examiner. It also lists what isn't in place yet.
Advisor approval
Agents draft, and advisors send. Nothing an agent writes reaches a client, and nothing is written to the CRM, until an advisor approves it. An advisor can also turn a draft down, and the firm keeps the reason. The full list of what runs on its own and what waits.
Every draft records which agent wrote it and why, which advisor approved it, and when.
Grounded, cited figures
The numbers in a draft are calculated in code by the same engines the rest of the product uses, and each carries a citation to the account, holding or transaction behind it. The language model gets finished numbers and writes the prose around them. It isn't asked to do arithmetic an advisor would be accountable for.
Who can see what
- Firm sign-in. Bring your firm's Okta, Microsoft Entra or Google Workspace. Offboarding happens in one place, your directory.
- Roles. Advisors see their book. Firm admins see the firm and run supervision. The IT admin role runs integrations and agents, and sees no client data at all.
- Firm-owned work. Drafts and client files belong to the firm, not the individual advisor, so they stay when someone leaves.
Audit trail and supervision
- Activity log. Who opened which client, what was published, and when it was acknowledged. On screen, and as a CSV export.
- Agent run records. For every agent run: what triggered it, what data it read, and the citations behind its output. Viewing a record is itself logged.
- Supervision. Exceptions across the book, such as allocation outside the firm's model or a client with no review on file. Plus a review of AI activity with a sign-off on each item.
- Exam pack. One download for any period: activity with its sign-offs, everything published to clients, the firm policy in force, and the agent records behind it.
- Retention. The firm sets how long agent records are kept. The default is six years.
Data protection
- Hosted on AWS in the United States (us-east-1). The database is encrypted at rest with a dedicated AWS KMS key, and connection tokens for linked accounts are encrypted with KMS too. All traffic is over TLS.
- Client data never trains a model. Models run on Amazon Bedrock inside Kemen's own AWS account. Bedrock doesn't use prompts or outputs to train models, and doesn't share them with the model's maker.
- Linked accounts are read-only. Kemen can't move money or place trades.
- Advisor notifications go only to the email, Slack and Microsoft Teams workspaces your firm connects.
Service providers
The third parties that process data on Kemen's behalf:
- Amazon Web Services: hosting, database, and AI models through Amazon Bedrock
- Resend: email delivery
- Sentry: error monitoring
- PostHog: product analytics
- Plaid, Tink and Prometeo: only when a client links an account through them
Not in place yet
So you don't have to find these yourself:
- No SOC 2 report yet. We'll walk pilot firms through our controls and answer their security questionnaire directly.
- No archiver connection yet. A books-and-records export to Smarsh and Global Relay is planned. Today, the activity log and exam pack are downloads.
- Client emails come from Kemen's domain. They're sent as “Advisor via Kemen”, and replies go to the advisor's own inbox. Sending from your firm's own domain needs a setup step we haven't built yet.
Kemen is software, not a registered investment adviser. Your advisors remain the advisers of record.
Kemen is in private beta
We're onboarding a small group of independent advisory firms as pilot partners. Leave your work email and we'll reach out.