Privacy Policy

This policy applies to LeadStream websites and the LeadStream application.

Workspace customers control the records they add to LeadStream. Users should contact their workspace admin for questions about a specific workspace invite or record.

LeadStream processes account data such as name, email address, membership, authentication state, and activity needed to run the service.

Workspaces may contain property records, people, contact details, notes, campaigns, calls, SMS conversations, tasks, imports, connected Gmail account metadata, linked email thread history, and follow-up history.

The LeadStream mobile app processes the device push token and app installation identifier needed for notifications and incoming calls. Camera, selected photo, microphone, and document access occurs only when the user invokes the corresponding capture, attachment, calling, or file workflow.

When a user connects Gmail, LeadStream may process Gmail message metadata, message bodies, participants, labels, attachments metadata, and attachment bytes requested on demand so the user can use visible Gmail features inside LeadStream.

When a user connects LeadStream to ChatGPT or Claude, that assistant and its provider (OpenAI or Anthropic) may receive the user's prompts, requested tool inputs, and bounded LeadStream records returned from that user's workspace for the requested action.

When you request document access, document metadata and document content are sent to your connected AI provider (OpenAI for ChatGPT or Anthropic for Claude). Downloads use short-lived links; uploads require file bytes supplied by the host and may be limited by the host's file support.

With SMS read permission, requested tool results may include recipient phone numbers, conversation message text, saved templates and delivery status. With separate SMS send permission and confirmation of the exact recipient and text, LeadStream sends or schedules messages as you through its messaging provider. Fees may apply. OpenAI or Anthropic processes those requested inputs and results. SMS message bodies and recipient phone numbers are excluded from MCP security-audit summaries. Disconnecting stops new assistant actions but does not cancel accepted messages or scheduled sends.

Visual CRM Copilot results may include property addresses and status, contact names and requested contact details, deal status and financial fields, task titles and due dates, tag labels, and short note excerpts. LeadStream sends the richer visual payload only as widget metadata; the conversation-visible result contains a smaller summary, but both are part of the tool result processed by the assistant's provider.

LeadStream uses data to provide the application, authenticate users, deliver transactional account email, secure the service, troubleshoot issues, and maintain reliability.

LeadStream uses device identifiers and push tokens to route account notifications and incoming calls to the signed-in device. LeadStream does not use mobile device data for advertising or cross-app tracking.

LeadStream uses Google Workspace API data only for visible Gmail product features: private mailbox viewing, manual one-to-one sending and replies, owner-controlled mailbox actions, user-controlled lead linking, linked lead read-only history, sync status, and attachment access requested by the user.

LeadStream does not sell personal information.

LeadStream does not use Google Workspace API data for advertising, retargeting, creditworthiness, lending decisions, or training generalized AI or machine learning models.

Connecting ChatGPT or Claude does not start a background export or synchronization. LeadStream sends requested workspace data when the assistant invokes a tool for the connected user. Explicit event subscriptions may also deliver minimal record IDs and event types to the chosen callback; record details require an authorized read.

Separately authorized campaign, sequence and drip commands can create or resume noncalling follow-up that continues in LeadStream after the tool finishes. SMS activation requires explicit confirmation of fees and funding requirements. LeadStream's messaging providers receive the recipient and message data needed to deliver that approved follow-up; calling activation remains excluded.

With separate IRIS research permission, ChatGPT or Claude can read property research reports and sources, start paid investigations, request cancellation, and record action feedback. Before each start or continuation, confirm the exact property and expected cost. Existing billing and budget rules apply; cancellation does not guarantee an immediate stop or refund. Research may add findings, contacts, and notes under existing IRIS policy. Call-note research and calling remain excluded. Research targets, reports, sources, and feedback requested through the connection are shared with the assistant provider.

LeadStream uses service providers for hosting, authentication, email delivery, calling, SMS, storage, logging, and monitoring.

Providers receive data only as needed to operate the service.

When a user connects ChatGPT, OpenAI processes the prompts, tool inputs, and tool results transmitted through ChatGPT under the user's OpenAI account and applicable OpenAI terms and privacy controls. When a user connects Claude, Anthropic does the same under the user's Anthropic account and applicable Anthropic terms and privacy controls.

With explicit call-read consent, a connected AI assistant can request call history, transcript text, recording metadata and linked IRIS call notes. Requested transcripts and notes may be sent to the AI provider, including OpenAI for ChatGPT or Anthropic for Claude. Current call-processing permission still applies. This read access never places, transfers, controls or schedules calls and does not send recording audio or signed recording URLs.

LeadStream uses Twilio for calling and recordings. Call transcription and IRIS notes are off until a workspace administrator explicitly opts in to the current provider disclosure for the whole organization. Members are never asked individually. A disclosure change requires renewed admin permission. When enabled, recorded conversation and voicemail audio is sent to AWS Transcribe. Conversation transcripts and linked contact and property context are sent to OpenAI to create IRIS call notes. Voicemail does not create IRIS notes. This automated call workflow is separate from connecting ChatGPT or Claude.

Administrators can turn processing off in Settings > Calling on the web or Settings > Transcription & IRIS notes on mobile. Members can view the organization setting. Turning it off stops new provider dispatch, including queued work. Calling and recordings remain available, and existing transcripts and notes remain workspace records. Data already sent cannot be recalled. Enabling processing does not replay historical calls or voicemail.

LeadStream stores the resulting transcripts and notes as workspace records and disables OpenAI Responses storage for IRIS call-note requests. Provider security and abuse-monitoring retention can still apply; this is not a zero-retention promise. Workspace retention and account/privacy requests are handled under the applicable customer agreement and this policy. Google Workspace API data remains excluded from AI-provider inputs as described below.

LeadStream discloses Google Workspace API data only to the connected Gmail account owner and, when that owner manually links a Gmail thread to a lead, to authenticated users in the same LeadStream workspace who are authorized to view that lead. Unlinked mailbox data is not shared with workspace admins or teammates.

LeadStream may provide Google Workspace API data to infrastructure service providers that host, store, secure, log, or monitor the LeadStream service, but only as needed to provide those services under contractual confidentiality and security obligations. LeadStream may also disclose data when required by law or to protect users, the service, or the public.

LeadStream does not sell Google Workspace API data or transfer it to advertising networks, data brokers, information resellers, or AI model providers. Google Workspace API data is not included in LeadStream tool results sent to ChatGPT, Claude, OpenAI, or Anthropic.

LeadStream uses authenticated access, organization-scoped data, and operational safeguards.

ChatGPT and Claude connections use OAuth scopes for read and explicitly authorized write access. LeadStream resolves organization access from the authenticated user's active membership rather than accepting a tenant identifier from the assistant.

Google OAuth tokens are stored server-side only, encrypted before persistence, and are not returned to the browser.

Google Workspace API data is transmitted over HTTPS and protected with access controls that keep unlinked Gmail mailbox data private to the connected account owner.

LeadStream keeps redacted audit records for Gmail security review and incident investigation. These records document service actions without storing Gmail subjects, bodies, recipients, attachment filenames, raw headers, OAuth tokens, token ciphertext, raw provider payloads, or authorization codes.

Every LeadStream data or view tool call from ChatGPT or Claude creates one bounded security-audit record linked to the connected account and workspace. It records the tool, access type, outcome, time, duration, target category, safe record identifiers, and bounded counts needed for security review and troubleshooting.

These security-audit records do not store raw searches, email addresses, phone numbers, mailing addresses, note text, nested update values, prompts, OAuth tokens, or full tool results. A scheduled cleanup deletes these records after 90 days.

Users should protect their credentials and report suspected unauthorized access to their workspace admin.

Google OAuth tokens are retained only while the Gmail account remains connected. Disconnecting Gmail revokes Google access when possible, permanently deletes stored token material, stops Gmail sync and watch renewal, and deletes all unlinked private mailbox cache from LeadStream.

While Gmail remains connected, unlinked private mailbox cache is retained for a rolling 90 days. Attachment metadata follows the same mailbox or linked-snapshot retention, and attachment bytes are fetched on demand rather than stored by default.

A Gmail thread that the account owner manually links to a lead is retained as CRM history for as long as that linked snapshot remains in the workspace. The Gmail account owner can end this retention at any time by unlinking the thread or deleting the linked snapshot. Disconnecting Gmail alone does not delete a snapshot the owner deliberately shared with a lead.

Gmail account connection metadata may remain as a workspace account record until the workspace data is deleted under the customer agreement or an applicable privacy request. Redacted Gmail security-audit records may be retained for security, legal, and compliance purposes after disconnect; they do not contain Gmail subjects, bodies, recipients, attachment filenames, raw headers, OAuth tokens, token ciphertext, raw provider payloads, or authorization codes.

Unexpected account invites can be ignored. Invite links expire automatically.

Workspace admins control workspace membership and workspace data requests.

Users can disconnect LeadStream in ChatGPT or Claude, or in LeadStream Settings, to stop future tool access. LeadStream supports OAuth token revocation and does not ask users to share LeadStream passwords with either assistant.

Disconnecting stops new assistant tool calls and new audit records. Existing bounded security-audit records are not deleted immediately on disconnect; scheduled cleanup deletes them after 90 days. Contact team@oxctech.com for an account or privacy request.

LeadStream's use and transfer of information received from Google Workspace APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.