Privacy and Google data use

DynamicMail privacy policy

This policy explains how DynamicMail processes account, tenant, document, Gmail, Google Drive, and support data when organizations use DynamicMail services.

Google OAuth Gmail letters Drive data rooms

Last updated: June 30, 2026. Contact DynamicMail at support@dynamicmail.ai.

1 Who operates DynamicMail DynamicMail is operated by Eregis, Inc. for business tenants and their authorized users.

DynamicMail is operated by Eregis, Inc., 10655 NE 4th St, Suite 630, Bellevue, WA 98004, US. You can contact support at support@dynamicmail.ai or by phone at (608) 818-8777.

DynamicMail provides tenant onboarding, document inboxes, registered and signed mail workflows, data rooms, Google integrations, agent-assisted document workflows, accounting setup surfaces, and related support.

2 Data we process DynamicMail processes only the information needed to provide, secure, support, and audit the service.
  • account identifiers, administrator identity details, contact details, tenant membership, country, language, role, and session information;
  • tenant organization details, onboarding records, KYC and review status, billing or subscription references, and support communications;
  • letters, uploaded documents, attachments, metadata, data-room folder details, sharing settings, processing status, and audit events;
  • technical logs such as request paths, redirect outcomes, consent state, integration callback status, error reports, IP-derived security context, and browser metadata.

When a tenant user connects Gmail or Google Drive, DynamicMail accesses, collects, stores, and processes only the Google user data needed for the connected workflow described below.

3 Google Sign-In DynamicMail uses Google Sign-In to authenticate invited users and workspace administrators.

When you sign in with Google, DynamicMail requests the Google Sign-In scopes openid, email, and profile.

DynamicMail uses this data to confirm the Google account identity, match the email address to an invite or tenant user, establish a secure session, display basic account information, and protect against unauthorized tenant access.

DynamicMail does not use Google Sign-In profile data for advertising, and it does not sell Google user data.

4 Gmail letter loading DynamicMail can load document-bearing Gmail messages into a tenant inbox after an authorized administrator connects a mailbox.

For Gmail inbound sources, DynamicMail requests https://www.googleapis.com/auth/gmail.readonly plus the Google identity scopes needed to identify the connected account.

DynamicMail uses Gmail data to read selected mailbox messages, message metadata, sender and recipient details, dates, subjects, document-bearing content, and attachments so they can be imported as DynamicMail letters or inbox items for the tenant.

DynamicMail does not send email from the connected Gmail account, modify Gmail messages, delete Gmail messages, or use Gmail content for advertising. Access is used to provide the letter loading and document import workflow requested by the tenant.

5 Google Drive data-room sync, upload, and sharing DynamicMail can connect Google Drive to data rooms so authorized users can sync, upload, organize, and share files as part of a tenant workflow.

For Google Drive data-room workflows, DynamicMail requests https://www.googleapis.com/auth/drive plus the Google identity scopes needed to identify the connected account.

DynamicMail uses Google Drive data to list and read files selected for data-room sync, upload files generated or stored by the tenant, manage folders used by the tenant workflow, and apply sharing behavior requested by authorized tenant users.

The full Drive scope is used because DynamicMail must preserve selected existing-folder/file sync, download, upload/update, and sharing workflows for tenant data rooms. drive.file does not cover the current existing-file and folder sync model; drive.readonly does not cover upload/update or sharing changes; metadata-only scopes cannot download or process file content.

DynamicMail does not use Google Drive content for advertising and does not sell Google Drive data.

6 Google API limited use DynamicMail handles Google user data according to the Google API Services User Data Policy, including Limited Use requirements.

DynamicMail's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide or improve user-facing DynamicMail features that the tenant has requested, to secure the service, to comply with law, or with the user's affirmative direction.

DynamicMail does not sell Google user data, does not use it for ads, and does not transfer Google user data for unrelated purposes or to data brokers, surveillance services, or creditworthiness or lending eligibility services.

DynamicMail does not use Google user data to create unrelated databases, build user profiles for unrelated services, or derive credit, lending, advertising, or data-broker products.

Google Gmail and Google Drive data is not used to create, train, or improve generalized or non-personalized AI or machine-learning models. AI, OCR, classification, extraction, and summarization are limited to the user-facing DynamicMail workflow requested by the tenant and its authorized users.

Human access to specific Gmail messages, attachments, Drive files, extracted text, or derived Google data is not allowed unless access is needed for security investigation, abuse prevention, legal compliance, or a support request where the tenant or user has explicitly authorized access to the specific data needed for that ticket. Support access is least-privilege, ticket-bound where practical, and logged for auditability.

7 Sharing, retention, and deletion Tenant data is retained only as needed for the service, legal obligations, support, and auditability.
  • tenant administrators control which users can access tenant workspaces, documents, data rooms, Gmail-imported letters, and Drive-connected data-room content;
  • DynamicMail may use subprocessors such as hosting, logging, email, payment, identity, storage, OCR, and AI infrastructure providers only as needed to operate the requested service and subject to the Google data-use limits above;
  • OAuth access and refresh tokens are stored server-side and are deleted or marked revoked when the Gmail or Drive integration is disconnected, except for minimal audit records needed to prove consent and revocation events;
  • Gmail imports, message metadata, attachments, Drive synced files, cached extracts, OCR text, derived document fields, and data-room records are retained only while needed for the tenant workflow, tenant retention settings, auditability, security, legal obligations, or an active support request;
  • security logs and audit records may be retained after content deletion when needed to investigate abuse, maintain accounting and compliance records, or prove integration lifecycle events;
  • backups are retired through the normal backup lifecycle and are not used to continue active Gmail or Drive processing after disconnect;
  • Google tokens can be revoked by disconnecting the integration in DynamicMail or by removing DynamicMail access in the Google account security settings;
  • deletion requests can be sent to support@dynamicmail.ai, subject to tenant administrator controls, contractual retention, audit records, security logs, and legal obligations.
8 Security and rights DynamicMail uses access controls, transport security, secrets management, audit logs, and tenant isolation to protect data.

DynamicMail limits access to authorized tenant users and operational personnel with a need to support, secure, or maintain the service. OAuth client secrets and service credentials are stored in managed secret systems and are not exposed in public pages.

Google-derived data follows the same safeguards, including tenant isolation, transport security, audit logs, least-privilege access controls, and managed secret storage for OAuth client secrets and service credentials.

Depending on your location and relationship to a tenant, you may have rights to request access, correction, deletion, restriction, objection, portability, or withdrawal of consent. Contact support@dynamicmail.ai and include the tenant name, account email, and the request type.

9 Public terms and integration terms Public DynamicMail Terms and Google Workspace data-access terms are available by locale.

Current locale: en-US, United States. These public links are generated from the DynamicMail locale manifest and Google Workspace integration terms manifest.

All published locale terms links