SECURITY

The security behind your AI Employee.

Built so an AI Employee can join your meetings, read your systems, and speak for your business without ever holding more access, authority, or data than you gave it.

Talk to us about deployment Enterprise deployment

Reviewed before we could ship.

DelegateWorker is approved on the Zoom App Marketplace: our OAuth scopes, data handling, and real-time media access passed Zoom's security review before the listing went live.

Zoom integration

Your cloud, your rules.

For Microsoft Teams, the AI Employee deploys inside your own tenant: behind your firewall, your security policies, and your data boundary. Nothing leaves your cloud.

Enterprise deployment

Always disclosed.

The AI Employee introduces itself as an AI in every conversation: meetings, calls, and messages. Trust with the people it talks to is the product, not a casualty of it.

What we do with your data.

The short version is below. The full version is written in plain words, with no certification claims, on our data handling page.

Live voice

Handled in memory while the call runs, so your AI Employee can keep up with the conversation.

Recordings and transcripts

Stored after the call, encrypted, and owned by you. Read them, download them, or have them deleted.

Your keys

Stored encrypted. Used only by our systems to run the tools you connect. Never visible in conversations, transcripts, or logs.

Always disclosed

Every AI Employee tells people it is an AI assistant. That cannot be turned off.

You can ask us to delete your data at any time. Need a data processing agreement (DPA)? Email hello@delegateworker.com and ask for the DPA.

Compliance

We publish where we actually are. Statuses on this page update as audits complete, not before.

Standard	Status	Coverage	Documentation
Zoom App Marketplace	Approved	Full marketplace security review of OAuth scopes, data handling, and RTMS real-time media access, completed before public listing.	Public marketplace listing.
GDPR	Aligned	EU data protection principles applied across collection, storage, and deletion.	DPA available on request.
CCPA	Aligned	California consumer privacy requirements reflected in our privacy practices.	See privacy policy.
SOC 2	On our roadmap	Controls implementation planned; timeline shared with enterprise customers under evaluation.	Ask us where we are.
ISO 27001	On our roadmap	ISMS scoping planned alongside SOC 2.	Ask us where we are.

What the AI Employee does. What it does not.

Does

Encrypts in transit and at rest
TLS in transit, encrypted storage at rest, secrets in environment vaults.
Scopes access per organization
AI Employees, knowledge bases, memos, and integrations are isolated per customer organization.
Lets you bring your own model keys
Run inference on your own OpenAI or Anthropic API keys under your agreements.
Revokes instantly
Disconnect an integration, pause an AI Employee, or end a session from the dashboard at any time.

Does not

Train on your data
Your conversations, documents, and memos are not used to train models: not ours, and not our inference providers' under their API terms.
Hide what it is
No human impersonation, ever. Disclosure is not configurable off.
Exceed its authority
Observer, Voice, or Proxy: the AI Employee acts at the level you set and escalates anything outside its brief.
Share across customers
No cross-organization access to knowledge, memory, or integrations.

AI Employees introduce new risks. We designed for them.

Prompt injection

Content the AI Employee encounters in meetings and documents is treated as information to reason about, not instructions to follow. High-consequence actions sit behind the authority levels you set.

Authority creep

The Observer / Voice / Proxy dial is a hard product boundary, not a prompt. An AI Employee set to Observer cannot commit your business to anything.

Data boundaries

Each organization's knowledge base is the only memory the AI Employee brings to your conversations. Export or delete it on request.

Credentials

1
OAuth-first integrations with minimal scopes.
2
API keys stored server-side and never exposed in conversation context.
3
Admin-controlled connect and one-click revoke.

Sub-processors

Inference and infrastructure run on named providers. No surprise vendors.

Provider	Role	Note
Anthropic	Language model inference	API traffic is not used to train models.
OpenAI	Language model inference	API traffic is not used to train models.
ElevenLabs	Voice synthesis and conversation runtime	Voice and conversation processing.
Zoom	Meeting media via RTMS	Real-time meeting audio under marketplace-approved scopes.
Twilio	Telephony, SMS, WhatsApp carriage
Stripe	Payments	Card data never touches our servers.
Supabase	Database and storage	Encrypted at rest.
Vercel	Web hosting
Fly.io	AI Employee runtime hosting
Resend	Transactional email (memos)

Responsible disclosure

Found something? Tell us at security@delegateworker.com. We would rather hear it from a researcher than read about it later. Meaningful findings get our thanks and public credit if you want it.

FAQ

Does the AI Employee's model see our API keys?

No. API keys are stored server-side and never exposed in conversation context. You can also bring your own OpenAI or Anthropic keys under your agreements.

Is our data used to train AI models?

Your conversations, documents, and memos are not used to train models: not ours, and not our inference providers' under their API terms.

Can the AI Employee act without our approval?

Only within the authority level you set: Observer, Voice, or Proxy. The dial is a hard product boundary. Anything outside the brief escalates to a human.

How is our organization isolated from others?

AI Employees, knowledge bases, memos, and integrations are isolated per customer organization. There is no cross-organization access to knowledge, memory, or integrations.

Deploying across a department? Bring your security team.

Talk to us