Security
Access you control, revocable any time.
The short version: OAuth only, least privilege, nothing held that doesn't need to be.
We never ask for or store your passwords
Every connection to your tools uses OAuth with least-privilege scopes — access limited to exactly what the worker's duties require, nothing broader. We never see or hold your login credentials.
You own your accounts
Every connection can be revoked at any time, from the tool's own settings — no call to us required. Revoking access stops the worker immediately.
Your data stays in your systems
A worker moves data between the tools you already use — your calendar, your CRM, your inbox — it doesn't copy that data into a separate store as its source of truth. Where we do keep records (meeting transcripts, hiring enquiries) that's covered in Data we keep below.
Every worker identifies itself as AI
At the start of every conversation — meeting a worker on this site and every conversation after you hire — before anything else is said.
Data we keep
- Meeting transcripts. Meeting a worker on this site runs on a fictional demo company, not your business. We log those conversations to see what buyers actually ask, so we can improve the product and the worker itself.
- Hiring enquiries. The name, email, and details you submit through a hire form, kept so the team can follow up.
We keep both only as long as we need them to run and improve Milliow. Ask us to delete yours at any time.
Subprocessors
Infrastructure we run on: Supabase (database), Resend (email), Upstash (rate limiting), Cal.com (scheduling), Anthropic (the AI models behind each worker), and Vercel (hosting). None of them see your connected-account credentials — those are held by the OAuth provider, not by us or them.
Who can access what
Access to a client's connected accounts is limited to the engineers who set up and maintain that specific integration — not the whole team, and not by default.