Loading page appearance…

Privacy and Google data use

DynamicMail privacy policy

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

Google OAuth Gmail letters Drive data rooms reCAPTCHA security

Last updated: October 28, 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, Google Drive, or Google Calendar, DynamicMail accesses, collects, stores, and processes only the Google user data needed for the connected workflow described below.

2a Individual identity verification Individual legal identity verification is separate from account sign-in, organization verification and ordinary room permissions.

Verification is optional for ordinary room access. A first-party invitation requires matching sign-in and explicit acceptance; separate, versioned consent is required before Swedish BankID, Stripe Identity or platform manual review. Email delivery and opening a link are not acceptance, consent or proof of identity.

The selected provider may process the identity information needed for that method. DynamicMail's default local collection excludes identity document files, selfies, raw provider payloads and public evidence links. It retains only the decision, method, necessary times, provider evidence reference, policy/consent version and minimal encrypted claims needed for authorized conflict checks. If no applicable configured evidence policy exists, optional claims are not retained.

Existing purpose-specific security, audit, contractual and legally required retention/deletion schedules below continue to apply; no new blanket duration is introduced. Local revocation and provider redaction are separate outcomes. Authorized deletion respects legal holds and minimized audit tombstones. Removing a tenant membership does not delete a reusable person identity in other tenants.

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 Calendar bookings and meeting links A calendar owner can authorize DynamicMail to check availability and maintain booking events on a selected writable calendar.

Booking connections request openid and https://www.googleapis.com/auth/userinfo.email to identify the connected Google account, https://www.googleapis.com/auth/calendar.calendarlist.readonly to let the owner select a calendar, https://www.googleapis.com/auth/calendar.freebusy to check availability, and https://www.googleapis.com/auth/calendar.events to create and update DynamicMail appointment events, private preparation and wrap-up holds, and Google Meet links. Event access is needed for shared calendars where the connecting owner has permission to write events.

DynamicMail processes the account identity, calendar selection metadata, busy intervals, appointment times and timezone, attendee and guest contact details, booking notes, generated meeting links, and event references needed to provide the requested booking workflow. Calendar operations are limited by the application to its own booking events on the selected calendar. An organization connection is shared within the authorized DynamicMail tenant; it is created through the calendar owner's consent.

DynamicMail sends appointment details, meeting links, and calendar attachments through its email delivery provider to the primary attendee, invited guests, and organizer according to the booking settings. The primary attendee receives the protected management link; guests do not receive that link. Rescheduling, cancellation, and reminders use the same appointment identity. Private preparation and wrap-up holds are not distributed to attendees.

OAuth credentials are encrypted server-side and bound to the tenant and connection owner. Disconnecting Calendar stops future calendar access through that connection and marks the local credentials revoked. To revoke the Google authorization itself, remove DynamicMail in your Google account security settings. Disconnecting does not automatically remove previously created events, sent emails, or meeting links; cancel appointments before disconnecting if those events should be removed.

Booking and calendar records follow the retention, deletion, and security provisions below. Google Calendar data is not sold, used for advertising, or used to train generalized AI models.

7 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, Google Drive, and Google Calendar data is not used to create, train, or improve generalized or non-personalized AI or machine-learning models. This restriction covers raw content, aggregated or anonymized information, extracted text, summaries, embeddings and other derived data. 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.

7a Self-hosted models and Google data Our self-hosted mathematical proof and audio components are separate from customer Google Workspace workflows.

DynamicMail’s production Google Workspace features do not use deepseek-ai/DeepSeek-Prover-V2-7B. This self-hosted mathematical proof component is currently unreleased for customer Google Workspace workflows. It operates within Eregis-controlled infrastructure and does not receive or process Google user data. Google user data is never shared with DeepSeek for training or any secondary purpose.

Our self-hosted Aria (loubb/aria-medium-base) and ACE-Step 1.5 (ACE-Step/Ace-Step1.5) audio components are also separate from customer Google Workspace workflows and do not receive Google user data.

DynamicMail does not use Google user data to create, train or improve foundational or generalized AI or machine-learning models. This restriction covers raw content, aggregated or anonymized information, extracted text, summaries, embeddings and other derived data.

8 reCAPTCHA security and fraud prevention DynamicMail uses Google reCAPTCHA Enterprise for attended human-presence checks on selected sensitive actions.

When an authorized user chooses to continue a protected action, DynamicMail may load Google reCAPTCHA Enterprise and ask Google to assess whether the interaction is likely to be genuine. A challenge may be shown. This check helps prevent fraud, automated abuse, and unauthorized high-risk activity; it does not prove identity, replace multi-factor authentication, approve a transaction, or establish legal consent.

Google may process browser and device information, interaction signals, network information such as IP address, service-generated cookies or similar identifiers, the public site key, the expected action label, and a short-lived response token. DynamicMail sends the response token only to its authenticated verification endpoint, which submits it to Google for assessment. DynamicMail does not put the token in agent messages, chat history, event streams, or user-visible evidence.

For reCAPTCHA Enterprise, Google acts as a processor for customer personal data under the Google Cloud terms from April 2, 2026. Processing is governed by the current Google Cloud Terms and Cloud Data Processing Addendum. Google may process data outside Sweden and the country where the user is located, subject to those terms and their transfer safeguards. DynamicMail does not claim that another product's CASA review covers this processing.

The raw response token and browser-attempt nonce are short-lived verification material and are not retained as business evidence. DynamicMail retains minimized server-side security records such as the request and assessment identifiers, status and reason code, timestamps, policy version, and bound operation or preview references according to configured request, audit, legal, and security retention schedules.

9 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, Drive-connected data-room content, and organization booking profiles;
  • 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, Drive, or Calendar 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, data-room records, and booking/calendar 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, Drive, or Calendar 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.
10 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.

11 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