← Back to Application

Privacy Policy

Last Updated: October 2, 2026

This Privacy Policy describes how Divorce RE Platform (“we”, “us”, or “our”) collects, uses, stores, and protects information when you use our platform and connect third-party services, specifically including Zoom Video Communications, Inc. (“Zoom”).

1. Information We Collect

A. Information You Provide

When registering and managing deals, we collect account details (such as your name, business email address, and brokerage affiliation) as well as transaction-related records (such as property addresses and client contact details).

B. Information Collected via Zoom Integration

When you connect your Zoom account via OAuth, we request the following scopes (user:read, phone:read, phone:write, phone_recording:read):

  • User Profile Data (user:read): Your Zoom User ID, display name, and email address.
  • Zoom Phone Line Information (phone:read): Your assigned business phone number, extension number, and line status.
  • Call Logs & Voicemails (phone:read): Inbound and outbound call metadata (timestamps, caller/callee phone numbers, duration) and voicemail audio transcriptions.
  • SMS Messaging (phone:write): Outbound SMS message text, recipient numbers, and dispatch timestamps sent via the in-app composer.
  • Call Recording Transcripts (phone_recording:read): AI transcripts and reference links for recorded business phone consultations. Raw audio files remain hosted on Zoom and are not stored on our application servers.

C. Information Collected Automatically from Email Recipients

Email open tracking is off unless your organization turns it on. When it is on, emails sent from the Application include a small image, and when a recipient’s mail app loads that image, the Application records the information below automatically. Recipients, such as clients or professionals on a transaction, are usually not users of the Application.

  • Email Open Records: The time the image loaded, the recipient email address the message was sent to, the IP address of the device that loaded it (which can indicate approximate location), and device and mail-app details (user agent).
  • Who sees them: The sending organization’s agents and admins.
  • Purpose: Only to show senders whether a message was likely opened. Open records are not sold and are not used for advertising.
  • Accuracy: Some mail apps load images automatically and others block them, so a record means the email was probably opened, and an email without a record may still have been read.
  • Retention: Open records are kept while the related communication and the organization’s account exist, and are deleted with them.
  • Your choices: Blocking remote images in your mail app prevents a record. A recipient can ask the sender, or our privacy team at the contact email below, to access or delete their open records.

2. How We Use Zoom Data

We use the data obtained through Zoom APIs exclusively for the following purposes:

  • To authenticate and link your official Zoom Phone business line to your user account.
  • To allow licensed agents and transaction coordinators to send outbound SMS messages from their business line directly from within the deal workspace.
  • To log call logs, voicemails, and recording transcripts onto the transaction timeline to maintain an accurate communication history for authorized team members.

Note: We do not use Zoom user data to train machine learning models, nor do we use it for advertising or marketing purposes.

3. Data Sharing, Selling, and Disclosure

  • No Sale of Data: We do not sell, rent, or trade your Zoom data or any personal information to third parties.
  • No Advertising Use: We do not share personal information with advertisers or data brokers.
  • Legal Requirements: We will only disclose information if required to comply with applicable laws, regulations, or enforceable legal requests.

Service Providers (Subprocessors)

We use the following providers to operate the Application. Each processes data only to provide its service to us.

Core infrastructure (always in use):

  • Supabase, Inc. — database, file storage, and user sign-in. Stores all application data, including transaction records, communications, uploaded documents, and connected-account credentials.
  • Railway Corporation — hosting for the web application and its background processing service.
  • Anthropic, PBC — AI processing used to draft messages for your review and to extract information from emails, call transcripts, meeting notes, and uploaded documents (such as purchase contracts and lender pre-approvals). Before message and transcript text is sent, we automatically remove Social Security and taxpayer numbers, bank and wire account details, payment card and driver’s license numbers, personal phone numbers, and lockbox or access codes. Uploaded documents are sent as provided so their fields can be read. Under Anthropic’s commercial terms, data sent through its API is not used to train its models.
  • Google LLC (Google Maps Platform and Google Cloud) — address lookup when you type a property address, and new-mail notifications for connected Gmail mailboxes (these notifications identify a mailbox, not message content).
  • Cloudflare, Inc. — domain name (DNS) service for our website address only; it does not receive application data.

Services you choose to connect:

  • Google (Gmail and Google Calendar) — reads email, sends the messages you approve, and syncs calendar events for the mailbox you connect.
  • Microsoft (Outlook / Microsoft 365 mail and calendar) — the same, for a Microsoft mailbox you connect.
  • Zoom Video Communications, Inc. — Zoom Phone calls, voicemails, SMS, and call recordings (see Section 1), and transcripts of recorded Zoom meetings.
  • Granola — meeting notes, if your organization adds a Granola API key.
  • Your own email provider (IMAP/SMTP) — if you connect a mailbox by server settings instead of Google or Microsoft.

4. Data Storage & Security

We implement technical and organizational measures to safeguard your data:

  • Encryption in Transit: Connections between your browser and the Application, and between the Application and our providers (including Supabase, Anthropic, Zoom, Google, and Microsoft), use TLS 1.2 or TLS 1.3. Connections to your own mail server (IMAP/SMTP) use the encryption configured for that server.
  • Encryption at Rest: All application data is stored in a managed PostgreSQL database and file storage that are encrypted at rest (AES-256).
  • Credential Encryption: Sign-in credentials for connected services (OAuth access and refresh tokens, mailbox passwords, and API keys) are additionally encrypted by the Application before they are stored, using AES-256-GCM with a key held in our hosting environment, separate from the database. They are kept in tables that only our backend service can read, are never sent to your browser, and the database refuses to store them unencrypted.
  • Access Control: Database Row-Level Security (RLS) policies partition data so that only authenticated, authorized members of your organization can access its records.

5. Data Retention & Revocation

You may disconnect the Zoom integration at any time from your Account Profile or Settings page. Disconnecting immediately deletes the stored OAuth access and refresh tokens. To also withdraw the Application’s authorization on Zoom’s side, remove the app from your Zoom account’s installed apps.

You may also request the deletion of your stored communication records by contacting us at the email below. Deletion requests will be fulfilled within 30 days.

6. Contact Us

If you have questions or concerns regarding this Privacy Policy, please contact:

Divorce RE Platform
Email: privacy@truevei.com
Website: https://truevei.com