Built for firms that take data seriously.

Data isolation

Every broker on your team gets a structurally isolated workspace. Threads, learned skills, memory, and credentials are scoped to one broker's identity at the database level — enforced by Postgres Row-Level Security, not just by application code.

This is defense in depth: even if a developer (us, or a future hire) accidentally writes a query without the right scoping, the database rejects it. It's not policy — it's structure.

Encryption

• In transit: all traffic uses TLS 1.3 with HTTPS enforced site-wide. No HTTP fallback. HSTS preloaded.
• At rest: database storage is encrypted at the disk level by Supabase (AES-256). Backups are encrypted with separate keys.
• Third-party credentials: when you connect Gmail, Zillow, or other tools, the OAuth tokens and API keys are encrypted with libsodium-style authenticated encryption before being stored. Decryption only happens server-side at the moment of use.

Zero data retention with model providers

We route AI model calls through the Vercel AI Gateway, which has zero-data-retention agreementswith OpenAI and Anthropic. Your conversations are not used to train any model — neither ours nor the underlying provider's.

Access controls

• Per-broker: each broker can only see their own conversations and learned data. Org admins manage members and billing but don't see other brokers' agent threads.
• Per-agent: brokers control which agents have access to which connectors. The Marketing agent can use Higgsfield; the Accounting agent doesn't need to.
• Approval gates: agents draft, brokers approve. Anything that touches the outside world (sending email, signing documents) requires explicit broker approval.

Authentication

Authentication is powered by Supabase Auth. Sessions use HTTP-only, signed cookies. Magic-link and password flows both supported. We don't store passwords directly — Supabase handles that with bcrypt + their own salting.

Two-factor authentication is on the roadmap and will be required for owner accounts.

Infrastructure

• Web: hosted on Vercel (SOC 2 Type II certified).
• Database: Supabase Postgres (SOC 2 Type II certified, GDPR-compliant). Hosted in US-East-1.
• Email: transactional email via Resend (SOC 2 Type II) using your verified domain.
• Payments: card data never touches our servers — handled entirely by Stripe (PCI DSS Level 1).

Backups & recovery

The production database is backed up daily with 7-day point-in-time recovery. We can restore your data to any point within the last 7 days within minutes. Backups are encrypted and stored in a separate region from primary storage.

Incident response

If we detect or are notified of a security incident affecting your data, we will notify you within 72 hours of confirmed exposure with a clear description of what happened, what data was involved, and what we're doing about it. See our status page for current service health.

Reporting a vulnerability

If you discover a security issue, please email us at bendanzim@gmail.com with the subject line “Security report”. We respond to all security reports within one business day. We don't currently run a paid bug-bounty program but are happy to publicly credit researchers who help us keep the platform safe.

Compliance

MyAgentEstate is built on infrastructure with SOC 2 Type II compliance (Vercel, Supabase, Stripe, Resend). We don't hold our own SOC 2 certification yet — that's on the roadmap as we scale to larger firms. For real-estate-specific compliance (state RESPA rules, fair housing language, MLS terms), you're responsible for ensuring agent outputs meet your jurisdiction's rules; we recommend keeping the Filing agent in human-approval mode for any regulated document.

Questions about security? Email us— we'll get back to you within one business day.