EQHO services and connected AI apps

This section covers EQHO account data processed through our services, APIs, and connected AI apps, including the EQHO plugin for ChatGPT and other Model Context Protocol (MCP) clients. It supplements the website and Google API disclosures below. Connecting an app allows it to request EQHO data and actions within the connected account's permissions. Only connect an account and request records you are authorized to use.

Data collected and why we use it

• Account and authorization data: account and organization identifiers, user identity and permissions, and authorization/session information let us authenticate requests and select the account in which an action runs. OAuth tokens are exchanged through the sign-in flow; do not paste passwords, API keys, or verification codes into a chat or tool input.
• Tool requests and configuration: the selected tool, record identifiers, search terms, date ranges, filters, and information supplied to create or update agents, prompts, campaigns, lead lists, phone-number settings, and workflows are used to carry out the requested operation. EQHO receives the arguments the connected client sends, not automatic access to the client's entire conversation history.
• Contacts and communications: requested records can contain names, phone numbers, email addresses, lead fields, message content, call audio or recording links, transcripts, summaries, dispositions, and call scores. We process these to provide communication services, retrieve records, summarize outcomes, and analyze performance. A recording or transcript may include personal information spoken or supplied by a participant.
• Operational and reporting data: campaign activity, call times and duration, delivery status, usage and credit metrics, and aggregated performance are used to produce requested reports. Request and session identifiers, IP addresses, timestamps, tool names, errors, and response timings may also be processed for authentication, security, abuse prevention, troubleshooting, and service reliability. Tool-use analytics can include organization/session identifiers and may be processed by PostHog when enabled.

Who receives the data

When you use EQHO through ChatGPT, tool results are sent to OpenAI so ChatGPT can answer your request. Other connected MCP clients receive results in the same way. Depending on the tool and requested detail, a result can contain the account records, contact details, transcripts, recording links, or reports described above. Review what you request before sharing it with a connected app. Its provider handles information it receives under its own terms, privacy policy, and your account settings; EQHO does not control that provider's separate retention or use. See OpenAI's privacy policy for its practices.

EQHO also uses infrastructure, storage, authentication, monitoring and analytics providers, and AI, speech-processing, and telecommunications providers to deliver the relevant features. For example, OpenAI may process content used for AI responses, and telephony or messaging providers process destination numbers and communication content to deliver calls or messages. The providers involved depend on the feature and account configuration. Authorized members of your EQHO organization may access records according to their roles.

Actions you request or workflows your organization configures can send content to call or message recipients, calendars, CRMs, webhooks, and other integration destinations. These actions can disclose information beyond EQHO and the connected AI app. Use only destinations and recipients you intend to receive that information. We may also disclose information for the legal and security purposes described below.

Retention and deletion

Connecting or disconnecting an AI app does not create or delete the underlying EQHO account records. Recordings, transcripts, messages, leads, agent configurations, and campaign records remain subject to your organization's retention settings and service agreement. Their retention period depends on the record type, the configured service, and any applicable contractual or legal requirements; this notice does not establish a single automatic deletion period for all records.

Authentication sessions and response caches have separate expiration settings; their expiry does not delete account records, operational logs, or copies already returned to a connected app. Security, troubleshooting, and usage records are retained according to their operational purpose and applicable requirements. Backup copies and records required for legal, accounting, dispute-resolution, or security purposes may remain after an active record is deleted.

Contact [email protected] or your organization administrator for the retention schedule applicable to your records, including log and backup periods, or to request deletion. Deleting data in EQHO does not remove copies from ChatGPT, another client, or a recipient of a prior communication; use that provider's controls or contact the recipient separately.

Your choices and controls

• Choose which EQHO account to connect and limit requests to the records and fields needed for your task. Organization administrators manage membership, roles, and enabled integrations.
• Disconnect EQHO in the connected client to stop using that connection. Ask your administrator or EQHO support to revoke access if you cannot do so through the client. Disconnecting does not undo completed actions or erase previously shared information.
• Request access, correction, export, deletion, or withdrawal of consent through your organization administrator or [email protected]. We may need to verify your identity and authority over the records. If your data was provided by an EQHO customer, that customer may need to authorize or handle the request. Ask support about limiting optional analytics; some processing remains necessary to provide and secure the service.
• Use the connected provider's privacy controls for its conversation history and data use. Avoid retrieving full transcripts or recordings when a summary or aggregate report is enough.

Restricted and sensitive information

Do not use the EQHO plugin or MCP tools to collect, request, upload, or retrieve payment-card data, protected health information, government identifiers such as Social Security numbers, or authentication secrets. Do not include these in agent instructions, lead fields, messages, transcripts, attachments, or other tool content. Use the designated OAuth sign-in flow for authorization and the separate billing interface for payments.

Do not use the plugin to create biometric identifiers or voiceprints, or submit biometric templates. Call audio is used for communication and speech-processing features; it can still contain sensitive personal information. Other legally sensitive or special-category data may only be used where strictly necessary for a permitted feature, with legally adequate consent and a clear disclosure before collection. Consent does not override the restricted-data prohibitions above.

You and your organization must have authority to share other people's information and provide required notices and consents for recording, transcription, AI processing, and communications. If restricted information is included accidentally, stop sharing it and contact EQHO support and the receiving provider to request removal. Do not send the sensitive content itself in a support email. These usage restrictions are not a claim that all sensitive content is automatically detected or removed.