Features How it works
Now in early access

Your inbox,
finally
under control.

Regent reads your emails, drafts your replies, surfaces what's urgent, and makes sure you never miss a lead again.

See how it works ↓
Follow-up ready
Sarah Kim
Ready to send
Reminder set
4 Oak Ave docs
Due tomorrow 9am
Regent app home screen
What Regent does

Built for agents who are
always in motion

Every feature is designed to reduce your mental load — not add to it.

Voice Agent

Command your inbox hands-free. Driving between showings? Say it — Regent drafts, flags, and files while you focus on the road.

Listening

"Flag the Torres offer as urgent and schedule a follow-up for tomorrow morning."

Never miss a hot lead again

Regent ranks every email by deal importance. Urgent leads surface first — your inbox becomes a revenue-generating tool, not a distraction.

Replies that sound exactly like you

Regent learns from your sent history and generates drafts indistinguishable from your own voice. Approve in one tap — sent in seconds.

No lead ever goes cold

Regent monitors every thread. When a client goes quiet, you're alerted immediately — with a suggested follow-up ready to send.

Start every day with clarity

A prioritized morning briefing tells you exactly what needs attention before you open a single email. Less overwhelm, more momentum.

Works inside your existing inbox

Connect Gmail or Outlook in under 60 seconds. No migration, no new apps — Regent works inside the tools you already use every day.

Works with your tools

Plugs into the inbox
you already use

Connect in seconds. No developer, no IT ticket.

Gmail
Outlook
How it works

Up and running in minutes

1
Connect your inbox

Securely link your email in one click via OAuth. Regent reads your threads — nothing is stored or shared.

2
Regent gets to work

Every email is triaged, deadlines extracted, follow-ups tracked, and drafts prepared in seconds.

3
You stay in control

Review, edit, and send. Every action requires your approval — Regent never sends on its own.

Stop letting deals slip through the cracks.

Join the waitlist for early access. We'll reach out when your spot is ready — no spam, ever.

No credit card. We'll only email when Regent is ready.

✓ You're on the list

We'll reach out with your beta invite soon.

Legal

We take your
privacy seriously.

Last updated: May 2026Effective immediately

The short version

We don't store your emailsEmails are read, processed, and immediately discarded after analysis.
TLS 1.3 + AES-256-GCM encryptionYour credentials and data are encrypted at every layer.
You approve everything sentRegent never sends an email without your explicit tap of Send.
Currently in betaThe product is under active development. See Section 7 for details.
01

What data we access

Regent connects to your email account via two independent secure pathways to ensure redundancy and service reliability.

Direct Gmail Integration

When you connect your Gmail account, Regent uses Google's OAuth 2.0 protocol to read your inbox with your explicit permission. You grant access — we never see or store your Google password.

  • Email subject lines and body text — read in real time to generate summaries and draft replies
  • Sender and recipient information — used to identify contacts and track follow-ups
  • Message timestamps and thread structure — used to detect deadlines and unanswered conversations
  • Attachment metadata (filenames, sizes) — scanned to extract tasks and deadlines, then immediately discarded

Unipile Unified Email Layer

Regent also connects through Unipile, a third-party email abstraction layer, to normalize email data across multiple providers and improve service resilience. Unipile receives the same scope of email data as our direct Gmail connection.

  • Email messages are processed through Unipile's infrastructure
  • Unipile normalizes email format and structure for consistent processing
  • Unipile does not store your messages beyond real-time processing
  • Unipile is subject to its own privacy terms (see Section 5)
Read-only by default

Write access is only enabled when you explicitly approve a draft for sending. There are no auto-send features. Emails are never sent without your direct approval.

02

What we store — and what we don't

We are explicit about data retention because this is where trust lives.

Email content: Never stored

Your emails are processed in memory in real time. Once analysis is complete, all email body text, attachment content, and full message threads are permanently discarded. We do not store archives of your email.

Task summaries: Briefly retained

The only persistent data we retain is a lightweight task summary — for example: "Follow up with Sarah Kim — no reply in 4 days." These summaries contain no email body text, no sensitive client information, no attachment content, and no message history.

  • Contact name (if present)
  • Action item (what needs to be done)
  • Deadline or context (if applicable)

Retention windows

Data typeRetention periodDeletion trigger
Email content (in memory)Minutes (real time)Automatic after processing
Task summariesUntil complete or 90 daysUser action or automatic expiry
Processing logs30 daysAutomatic rotation
API call records90 daysAutomatic purge
Your inbox
Email arrives
In-memory only
AI processes
Saved briefly
Summary stored
Email content
Permanently wiped
03

Encryption & infrastructure security

In transit

  • TLS 1.3 — All data between your device and Regent servers
  • TLS 1.3 — All data between Regent and Google (Gmail API)
  • TLS 1.3 — All data between Regent and Unipile
  • TLS 1.3 — All data between Regent and Google Gemini API

At rest

  • AES-256-GCM encryption — Your OAuth credentials and API tokens are encrypted at rest
  • Credentials never logged — Tokens do not appear in application logs or error reports
  • Google Cloud Platform — Infrastructure-level encryption at rest (default GCP KMS)
  • SOC 2 Type II certified — GCP meets rigorous compliance and security standards

Database access

  • Database not publicly accessible — isolated to private VPC
  • Access logs enabled — all database access is audited
  • IP whitelisting — only authorized Regent infrastructure can connect
Beta security notice

Regent is in beta. While we take security seriously, our internal access controls are not yet production-hardened. A small number of authorized team members have technical access to infrastructure for debugging and operation. As we scale, we will implement RBAC, mandatory code review, and third-party security audits.

04

Sending emails — always explicit approval

Regent will never send an email on your behalf without your direct, explicit approval. No exceptions.

The approval workflow

  • Regent analyzes your email and drafts a reply based on conversation context and your communication style
  • The draft is presented to you for review — you can edit, reject, or approve it
  • Only when you tap "Send" does Regent transmit the email via Gmail

No auto-send, no background sends

There are no scheduled sends, delayed sends, or automatic transmissions of any kind. Every email requires your explicit tap or click before leaving your account.

05

Third-party services & data processors

Regent relies on third-party services to operate. Here is exactly what each one does and what data it accesses:

  • Google OAuth 2.0 — Authentication and email access. You grant explicit permission via Google's consent screen. Google handles your credentials; we never see your password.
  • Gmail API — Direct access to your inbox for real-time email reading. Read-only by default; write access only on explicit approval.
  • Unipile — Email abstraction layer that normalizes email data across providers. Processes email content in real time; does not store messages beyond processing window. Regent has a Data Processing Agreement with Unipile.
  • Google Gemini API (paid tier) — Powers real-time email summarization and draft generation. Your data is not used to train Google's AI models.
  • ElevenLabs — Voice agent for in-app dictation and voice replies. Voice input is processed in real time. Regent has a Data Processing Agreement with ElevenLabs.
  • Google Cloud Platform — Infrastructure hosting. Task summaries, user accounts, and system logs stored on GCP. SOC 2 Type II certified. All data encrypted at rest via GCP KMS.
Our data use commitment

We do not sell your data. We do not share it with advertisers or marketers. We do not use it for behavioral tracking. This will never change without explicit notice and your consent.

06

Your rights & how to exercise them

  • Access — Request a summary of all data Regent holds about you, including task summaries, account metadata, and activity logs.
  • Deletion — Delete your account and all associated data at any time. Deletion is permanent and processed within 30 days.
  • Revocation — Revoke Regent's Gmail access at any time through your Google Account settings. All processing stops immediately; cached data purged within 24 hours.
  • Correction — Request correction or removal of any stored task summary, contact information, or user profile data.
  • Portability — Request your data in a portable, machine-readable format (CSV or JSON) within 30 days of request.

How to submit a request

R
Regent Privacy Teamprivacy@regentapp.ca · regentapp.ca
Send message

Include your request type (access, deletion, revocation, correction, or portability) and your email address or account ID. We respond within 5 business days.

Legal jurisdiction

If you are located in Canada, your rights are protected under PIPEDA (Personal Information Protection and Electronic Documents Act) and applicable provincial privacy laws. If you are located in the European Union or EEA, your rights are protected under the GDPR. We comply with all applicable requirements including consent, accuracy, security, and individual access rights.

07

Beta disclaimer & liability

Beta status

Regent is currently in beta. The product is provided as-is without warranties. While we work hard to protect your data and provide reliable service, we make no guarantees about uninterrupted or error-free service, complete protection against data breaches, or recovery of data in case of catastrophic failure. By using Regent during beta, you acknowledge the product is under active development and accept the inherent risks of beta software.

Limitations of liability

To the fullest extent permitted by law, Regent is not liable for indirect, incidental, or consequential damages arising from use of the service, data loss or corruption due to user error or third-party service outages, or lost revenue, lost data, or business interruption. Our maximum aggregate liability for any claim shall not exceed the subscription fees paid by you in the 12 months prior to the claim.

No warranty against breaches

While we implement industry-standard security measures, no service is immune to breaches. If a breach occurs, we will notify affected users within 72 hours and cooperate with regulatory authorities as required by law.

08

Changes to this policy

We may update this privacy policy as our product evolves. Material changes will be communicated to you by email at least 14 days before taking effect. Material changes include: new third-party services that process your data, changes to data retention policies, new uses of your data, or changes to encryption or security practices. You can delete your account at any time if you do not agree.

Policy history

  • May 2026 — Added Unipile integration details, expanded third-party processor language, added data retention table, enhanced encryption details, added jurisdiction/compliance notes.
  • January 2026 — Initial privacy policy (Gmail direct integration).

Contact

privacy@regentapp.ca · regentapp.ca · We respond to privacy requests within 5 business days.

© 2026 Regent. A Canadian software company based in Toronto, Ontario. This policy is governed by the laws of Ontario, Canada, and PIPEDA.