Work in progress

This page is a work in progress and subject to changes and rewrites. Content here reflects RegentDesk's current intent — language, commitments, and structure may all change before launch.

Compliance Overview

How RegentDesk Works —
and What It Never Does

RegentDesk is a writing and scheduling assistant for independent financial advisors. Every email it helps you draft is reviewed and sent by you. It does not give investment advice. It does not send anything on your behalf. This page explains exactly what that means in practice.

Last updated: May 12, 2026

The one rule that covers everything:

RegentDesk never sends anything. Every draft RegentDesk produces sits in your workspace until you copy it, open your email client, paste it, and click send yourself. There is no send button in RegentDesk. There is no schedule-and-forget. Every communication that reaches a client was personally reviewed and sent by you.

What RegentDesk does

Drafts emails in your voice

RegentDesk generates a first draft based on context you provide — the topic, the client, the tone. You read it, edit it if you want, and send it from your own email client. The draft never leaves your screen without your review.

Maintains client context

RegentDesk stores information you enter about each client — their life stage, relationship notes, upcoming events. It uses that context to make drafts more relevant. You control every field, and you can delete any client's data at any time.

Batch communication for crisis moments

When markets move, you can draft personalized outreach for your entire client list in one workflow. Each draft is individualized — and each one requires your review before you copy and send it.

Manages check-in cadences

RegentDesk tracks when you last contacted each client and surfaces who's overdue. It can remind you to reach out — but it does not schedule meetings, send calendar invites, or communicate with clients on your behalf.

What RegentDesk never does

These are permanent design constraints — not settings, not features to be added later.

Generate investment recommendations

RegentDesk does not analyze portfolios, recommend securities, evaluate allocations, or produce any output that constitutes investment advice. It can include numbers you provide in a draft — it cannot generate, compute, or recommend anything about a client's investments.

Send anything without your explicit approval

There is no auto-send, no scheduled sending, no "send if no response," and no sending triggered by market events. Every email goes through your email client, sent by you. This is a permanent design constraint, not a setting that can be changed.

Access your client accounts or portfolio systems

RegentDesk does not connect to custodians (Schwab, Fidelity, Pershing, etc.), portfolio management systems, or any financial data source. All client context in RegentDesk was entered by you manually.

Communicate directly with your clients

RegentDesk has no email address, no messaging system, and no way to contact any of your clients. It generates drafts that appear in your RegentDesk workspace — nothing is delivered anywhere until you copy it and send it yourself.

Store your email credentials

RegentDesk does not have access to your Gmail or Outlook inbox. Drafts are reviewed and copied from RegentDesk — you paste them into your own email client. No email integration is required.

Regulatory questions

Click a question to expand the answer.

Does RegentDesk require FINRA registration?

No. RegentDesk is a writing and scheduling assistant — the same regulatory category as Grammarly or Calendly. It does not provide investment advice, execute trades, or hold client funds. No FINRA or SEC registration is required to use it.

Does using RegentDesk affect my fiduciary duty?

No. Your fiduciary duty requires that advice and investment decisions come from your professional judgment. RegentDesk handles drafting and scheduling — it does not make, recommend, or influence investment decisions in any way.

Will my compliance officer have concerns?

Most advisors find their compliance officers are satisfied once they review this page and understand that every communication is reviewed and sent by the advisor. RegentDesk produces drafts — the advisor is the author of every email that goes out. This page is written to be forwarded to a compliance officer directly.

Does Anthropic offer a BAA for HIPAA?

Anthropic offers BAAs for HIPAA-covered customers. RegentDesk customers (RIAs) are not HIPAA-covered for client financial data, so a BAA is not generally relevant. If an advisor brings HIPAA-protected information into scope (for example, an estate-planning attorney handling medical directives), email lucas@regentdesk.com — we will evaluate whether a BAA is appropriate.

Is the AI-generated content considered my own communication?

Yes. You review, edit, and personally send every email. RegentDesk is a drafting tool, the same as having an assistant write a first draft for you to review and send. The advisor is the author and the responsible party.

Does RegentDesk store my clients' emails?

Today: no. RegentDesk does not connect to your email inbox. You enter client context manually. When RegentDesk adds optional Gmail and Outlook integration in a future release, any emails processed will be stored in encrypted form in your isolated data store. You will be able to see exactly what was processed, exclude specific senders or domains, revoke access at any time, and delete all synced data.

Does this replace my compliance archiver (Smarsh, Global Relay, Erado, etc.)?

No. Your compliance archiver remains the books-and-records archive of record. RegentDesk is a productivity layer on top — it helps you generate and manage communications, but it does not replace the archiving obligation. Keep your existing archiver in place.

What about Rule 204-2 / books and records?

RegentDesk stores drafts and interactions in a way that supports your 204-2 record-keeping obligations, but RegentDesk is not the archive of record. You can export all your RegentDesk data as JSON at any time from Settings. If you cancel, you can choose to export before deletion or retain your data for your books-and-records window.

Can I export all my data? Can I delete everything?

Yes to both. Export (available from Settings) returns a complete JSON file of all advisor data — clients, drafts, voice samples, interactions. Delete triggers a 30-day soft-delete window followed by hard-purge from active systems. Backup copies are purged within 90 days of the deletion request.

What happens to my data if I cancel?

Your choice at cancellation: export everything and then delete, or retain your data for the Rule 204-2 books-and-records window (five years). We won't delete unless you ask, and we won't hold it hostage if you want it gone.

Is RegentDesk SOC 2 compliant?

SOC 2 Type II is on the roadmap — we are targeting attestation within 12–18 months of launch. Until then, RegentDesk operates under a written information security program (WISP) and the security controls documented on this page. The controls are real; the third-party audit is the piece that takes time.

Data handling and security

Security controls implemented at the infrastructure layer — not add-ons.

Encryption in transit

TLS 1.2+ for all API calls, webhooks, and data in motion. Enforced by Vercel and Supabase at the infrastructure layer.

Encryption at rest

AES-256 database encryption via Supabase. All client data, drafts, and voice samples are encrypted on disk.

Row-level security

Tenancy isolation is enforced at the database layer via Postgres RLS policies. Advisor A cannot access Advisor B's data — even if a software bug exists at the application layer.

Authentication

Handled by Clerk with MFA support. Multi-factor authentication is enforced for all production accounts.

Secrets management

All API keys (Anthropic, Stripe, etc.) are stored in Vercel environment variables. They are never in source code. Keys are rotated quarterly at minimum and immediately on any suspected compromise.

Automated backups

Supabase automated daily backups with 7-day point-in-time recovery. Data can be restored to any point within the retention window.

Audit logging

Data access events are logged internally with advisor ID, timestamp, and action. Retained for at least two years. Available to support breach investigation and vendor oversight reviews.

Data disposal

On deletion or cancellation, data is purged from active systems within 30 days and from backups within 90 days. Disposal events are recorded in a retention log.

What we log

Every meaningful action in RegentDesk writes one row to your audit log — what happened, when, and (where it matters) who clicked the button. The audit log can't be edited or deleted by anyone, including us.

Sign-in and sign-out

So you and your compliance officer can see exactly when your account was used.

Connections to your email and calendar

Every time you connect, reconnect, or refresh access — and any time a connection fails.

Drafts — created, approved, sent, discarded

The legal-hard-line record: every approved or marked-sent draft carries your user id, proving you reviewed it.

Consent changes

Meeting-notes ingestion, Strict Privacy Mode, PDF ingestion — every toggle is recorded with the old and new value.

Voice library additions and removals

When you approve, reject, swap, or promote a voice sample, so changes to your writing voice are traceable.

Check-in schedules — created and changed

When you set up, pause, resume, or update a cadence on a client.

Sensitive-content flags on incoming email

When the pipeline detects patterns like SSNs or account numbers in an inbound message, so access to that data is auditable.

Account export and delete

Every export request and every deletion — including a durable proof-of-deletion that survives the account being removed.

Your audit log is yours. View it in Settings → Audit Log. Export as CSV any time.

How AI processes your data

The question every compliance officer asks first.

What happens when you generate a draft

When you click Generate Draft, the context you provided — the topic, client notes, and tone preference — is sent to the Anthropic API (Claude) for processing. The draft is returned and displayed in your workspace. Nothing else happens: the content is not forwarded, not stored by Anthropic, and not shared with any other party.

Anthropic's data handling commitments

  • API inputs are not retained by Anthropic beyond the duration of the API call.
  • API inputs are not used to train Anthropic models.
  • All data is encrypted in transit via TLS.
  • Processing occurs in US-based data centers.
  • Zero Data Retention (ZDR) configuration available on request for advisors whose firms require it — eliminates the standard 30-day API safety-monitoring window. Email lucas@regentdesk.com to enable.

These commitments are documented in Anthropic's API terms and are reflected in our Data Processing Agreement template, available on request.

If something goes wrong

Our incident response commitment

RegentDesk maintains a written incident response plan covering detection, containment, eradication, recovery, and communication. In the event of a confirmed security incident that affects your data, we commit to notifying you within 72 hours of confirmation.

That 72-hour window is deliberate: it gives you the runway to meet your own 30-day customer-notification obligation under SEC Regulation S-P § 248.30(a)(4) (effective 2024).

What the notification covers

  • What happened and when it was detected.
  • Which data was affected and which clients' information may have been involved.
  • What RegentDesk has done to contain and remediate.
  • What you should do next.

The full incident response plan is available to advisors on request and is included in our Data Processing Agreement template.

Who else touches your data

Full subprocessors page →

Every vendor that processes advisor or client data on RegentDesk's behalf is listed here. We commit to giving you at least 30 days' notice before adding any new subprocessor that processes client data.

Subprocessor
Purpose
Data processed
Location
Supabase
Database and storage
All client and draft data
United States
Clerk
User authentication
Advisor identity and session tokens
United States
Anthropic
AI draft generation and context extraction
Email content and client context during processing only — not retained
United States
Vercel
Application hosting and serverless functions
All data flowing through the application
United States
Inngest
Background job queue (batch operations)
Job metadata
United States
Stripe
Payment processing
Billing data only — no client data
United States
Google Cloud Pub/Sub
Gmail push notifications (future integration)
Message IDs and event metadata
United States
Microsoft Graph
Outlook notifications (future integration)
Message IDs and event metadata
United States

Google Cloud Pub/Sub and Microsoft Graph are listed for future Gmail/Outlook integration. They are not active today. View full list with data categories →

Your data

What's stored

Client names, relationship notes, life events, and check-in history — information you enter manually. Voice samples you add to train your writing style. Drafts you generate and their edit history.

What's not stored

Portfolio holdings, account balances, trade history, or any financial data. Email credentials or inbox contents. Any data from custodian systems.

Your controls

Delete any client's data instantly from Settings. Export everything as a JSON file. Revoke any future integration (email, calendar) and all sync stops immediately. Request full account deletion — 30-day soft-delete, then hard-purge.

Where it lives

US-only processing. Supabase-hosted Postgres with daily backups and 7-day point-in-time recovery. Per-advisor data isolation enforced at the database layer via row-level security — not just application logic.

Document Reading

Optional PDF extraction for KYC forms, account opening packets, beneficiary forms, and similar client documents — off by default, advisor-controlled when on.

Some wealth managers want RegentDesk to extract structured information from KYC forms, account opening packets, beneficiary forms, and similar documents attached to client emails. This is off by default. To turn it on, you choose a setting in your account: Off, Allowlist Only, or Allowlist Plus Discover. You also choose which sender addresses RegentDesk is allowed to read PDFs from — your custodian, your attorney, your CPA, or anyone you specify.

When the feature is on:

  • We never read PDFs from senders you haven't approved.
  • We never extract Social Security numbers, full account numbers, routing numbers, or credit card numbers. Our extraction prompt explicitly forbids it, and a redaction step strips any of those patterns from the result before storage.
  • Every extracted fact is paired with a verbatim quote from the document so you can verify what we read.
  • Every PDF parsed is logged in your audit trail with the timestamp, sender, and the count of facts extracted.

You can change your settings or remove specific senders at any time. Your data is yours; you can export everything in machine-readable format or delete your entire account from a single page in settings.

Strict Privacy Mode: separately, you can turn on Strict Privacy Mode at any time. With Strict Mode on, RegentDesk only runs AI on emails with people on your client list and on the email addresses you specifically authorize (Jump, Zocks, etc.). All other email content is never analyzed. Strict Mode is independent of the PDF setting above.

Compliance officer or general questions: email lucas@regentdesk.com. We answer on a call if needed.

Get started