Privacy Policy

This Privacy Policy explains what personal information and email content we collect, how we use and share it, how long we keep it, and what choices you have. It applies when you:

This policy does not cover third-party websites, email providers, or integrations you choose to connect outside of Envoy's control (for example, Google's own privacy practices for Gmail).

To provide the service, Envoy may:

During onboarding and calibration, Envoy may scan a bounded window of your sent mail to infer communication patterns and persona assignments. Optional integrations (for example Linear notifications, outbound webhooks) process only data needed for those features.

4.1 Account and identity information

When you register (via our authentication provider or local-edition setup), we may collect:

4.2 Connected mailbox data

When you authorize Envoy to access your email account, we access data permitted by the OAuth scopes you approve. For Gmail, these currently include:

Email content and metadata we process may include:

Envoy processes mail only for accounts you connect and only to deliver the features you enable.

4.3 Data you configure in Envoy

4.4 Automatically collected technical data

Where enabled, server and pipeline logs apply PII redaction by default (see Section 8).

4.5 Support and communications

If you contact us, we collect the information you provide (email content, screenshots, logs you choose to share).

We use the information above to:

We do not sell your personal information. We do not use your mailbox content to train generalized third-party AI models for unrelated products. Email content is sent to our AI sub-processor only to provide classification, drafting, screening, briefing summaries, and related features for your account (see Section 6).

Envoy uses Anthropic's Claude API to classify messages, screen commercial mail, generate draft replies, synthesize voice-learning updates, and produce briefing summaries.

What is sent to Anthropic: User-role prompts may include email subject lines, message bodies, sender/recipient context, persona instructions, and your configured standing rules. Structured identifiers such as Social Security numbers, payment card numbers, and phone numbers are masked in user messages before the API call (replaced with placeholders such as [ssn], [card], [phone]). Email addresses are generally retained in prompts because they are needed for accurate classification and reply context.

What Anthropic does with it: Processing is governed by Anthropic's terms and privacy policy. We configure API usage for production inference; we do not authorize Anthropic to use your content to train their public models unless their product terms explicitly state otherwise for your account tier.

Your responsibility: Mailbox content may include personal information about your contacts, employees, clients, and other third parties. By connecting a mailbox, you represent that you have authority to allow Envoy and its sub-processors to process that content for the purposes described in this policy.

Envoy is operated from Canada (primary timezone: America/Toronto). We apply the following frameworks depending on your location and relationship to us:

Canada (PIPEDA and applicable provincial law)

We rely primarily on:

United States

Where U.S. state privacy laws apply (for example the California Consumer Privacy Act, as amended), we process personal information for the business purposes described above. We do not "sell" or "share" personal information for cross-context behavioral advertising as those terms are defined under applicable state laws.

If you are a California resident, you may have rights to know, delete, correct, and obtain a portable copy of certain personal information, and to opt out of sale/sharing (not applicable here as we do not sell data). See Section 11.

We implement technical and organizational measures appropriate to the sensitivity of mailbox data, including:

No method of transmission or storage is completely secure. If you believe your account has been compromised, contact us at privacy@jaipteam.com and revoke Envoy's access in your Google Account security settings.

We do not currently hold formal third-party security certifications (for example SOC 2 or ISO 27001). If that changes, we will update this policy and our Trust Center.

We use trusted service providers who process data on our behalf. This list reflects the intended production stack; the local edition may omit some providers.

We may update this list as infrastructure changes (for example migration to Railway in Phase 5). Material additions will be reflected here and in the in-product Trust Center when available.

Command Center integration: Envoy may send optional outbound webhook payloads to a separate product ("Command Center") over HTTPS. That integration is HTTP-only; the systems do not share a database. Webhook delivery requires explicit configuration and shared secrets on both sides. If enabled, effort-update summaries derived from your email processing may be transmitted to your Command Center instance.

We retain information only as long as needed to provide the service, comply with legal obligations, resolve disputes, and enforce agreements.

When you delete your account or disconnect a mailbox, we delete or de-identify associated data within a reasonable period, subject to backup cycles and legal holds. Specific retention schedules will be published in the Envoy Trust Center as they are finalized.

You may request an export of your data (JSON bundle) through account settings when that feature is available, or by contacting privacy@jaipteam.com.

Depending on your jurisdiction, you may have the right to:

To exercise these rights, use in-app controls (Connections, Settings, Trust Center) when available, or email privacy@jaipteam.com. We may verify your identity before fulfilling a request. We will respond within the timeframe required by applicable law.

Disconnect a mailbox: You can remove an account in Envoy and revoke access at Google Account Permissions. Revocation stops new processing; deletion timing is described in Section 10.

Marketing: If we send product updates or marketing email, you may opt out via the unsubscribe link. Transactional and service-related messages (for example security alerts, billing) may still be sent.

You may delete your Envoy account through the Trust Center / Settings (when available) or by contacting privacy@jaipteam.com.

Backups and audit logs may persist for a limited period per Section 10 before being purged or anonymized. Deletion does not remove copies of emails that remain in your Gmail mailbox or messages already forwarded to third parties (for example accounting inboxes).

Local edition: Self-hosted deployments store data on infrastructure you control. Account deletion behaviors in the local edition may be limited to a single principal user; you are responsible for destroying local database volumes and token files if you decommission a local install.

Envoy is based in Canada. Sub-processors (including Anthropic, Google, Clerk, Stripe, Cloudflare, and planned hosting providers) may process data in the United States and other countries. Where required, we rely on appropriate safeguards (for example contractual clauses and vendor security commitments) for cross-border transfers.

If you require data residency in a specific region, contact us before connecting production mailboxes; the standard SaaS offering does not currently guarantee regional data residency.

Envoy is not directed at children under 16 (or the age of digital consent in your jurisdiction). We do not knowingly collect personal information from children. If you believe a child has provided us personal information, contact privacy@jaipteam.com and we will take steps to delete it.

We may update this Privacy Policy from time to time. When we make material changes, we will post the updated policy at /envoy/privacy and update the "Last updated" date. For significant changes, we may notify you by email or in-app notice. Continued use of Envoy after the effective date constitutes acceptance of the revised policy, to the extent permitted by law.