Integrations privacy policy

Who and what this policy covers

This policy covers the Empyrean Integrations tools administered by Jacob Jones, including the shared Google application also known as gdrive-mcp. Empyrean Consulting hosts this information and handles integration-support inquiries. Empyrean Ventures Inc., doing business as Ellie Mental Health, is the business operator for the clinic Google Ads reporting integration.

It is not a privacy policy for Ellie corporate, patient treatment, or unrelated websites. Google, hosting services, and any assistant platform you use also have their own privacy policies. Those policies do not expand the uses we permit for Google user data under this policy.

Information accessed and its purpose

Access depends on the connector, permissions granted, and feature you use. Not every connector requests or receives all of the following:

• Drive: file and folder identifiers, names, metadata, document contents, and selected file contents, for finding information, answering questions, preparing documents, and making requested file or folder changes. Local folder restrictions further limit the local Drive connector.
• Gmail: message and thread identifiers, headers, labels, message bodies, and selected attachments where reading is authorized, for correspondence and research workflows. Compose-authorized tools use recipients, subjects, message text, and attachments to create drafts or send explicitly approved messages.
• Google Chat: spaces, memberships, messages, reactions, and read-state information where authorized, for conversation context and communication assistance. Creating messages requires the relevant permission and applicable human approval.
• Google Ads: account and campaign identifiers, campaign status/settings/budgets, and performance statistics, for internal clinic advertising reporting and assessment. The current EIP Ads integration is read-only and does not upload patient records or customer lists.
• Connection and operational information: the account identifiers needed to associate a connection, OAuth authorization tokens, and necessary operation or error records, for maintaining authorized connections and diagnosing problems. Google handles account authentication; these tools do not need your Google password.

Information selected for an assistant workflow may be used to produce summaries, research records, task records, or documents requested by the authorized user. Model-provider authentication and business-application sign-in are separate capabilities; their existence does not grant access to Gmail, Drive, Chat, or Ads.

Use, sharing, and connected assistants

Google user data is used for the authorized, user-facing features described above. It is not sold, used for personalized advertising or retargeting, supplied to data brokers, or used to determine creditworthiness. Gmail, Drive, and Chat content is not used to create advertising audiences.

When you expressly use a connected assistant, selected content may be processed by that assistant's provider, such as OpenAI or Anthropic, to carry out your request. This is a disclosure to that provider, not purely local processing. Only content authorized for that workflow may be transferred. Google user data must not be transferred or used to train generalized artificial-intelligence models.

Transfers are limited to delivering authorized features with your consent, protecting security, complying with law, or an ownership transfer with the required prior consent. Human access to Google-derived content is limited to your affirmative agreement, necessary security or legal handling, or permitted aggregated internal operations. We do not publish private Google content through this website.

Our handling of Google API data, including derived data and permitted transfers, is subject to the Google API Services User Data Policy and its Limited Use requirements.

Storage and protection

Depending on the feature, selected data and derived work products may be stored on operator-managed workstations, in private application storage, or in the user's authorized Drive or research workspace. Assistant workflows can also process and retain content within the selected assistant service according to its account settings and applicable terms.

Connections to Google use HTTPS. Access is limited through Google authorization, application controls, and access controls on the operating environment. The local Drive connector is bound to localhost and uses a bearer credential and a folder allowlist; these controls are specific to that connector and are not claims about every integration.

Authorization tokens are retained to maintain the connections you approve. No system can guarantee complete security. Do not provide patient information, passwords, government identity documents, or unnecessary sensitive information to these workflows.

Retention, disconnection, and deletion

Connection credentials are retained while the authorized connection is needed. Selected source material, derived records, and work products are retained as needed for the user's requested work and applicable business or legal recordkeeping. There is no automatic promise that every connector or assistant service deletes all data after the same number of days.

You can revoke future Google access through your Google Account's third-party connections. Revocation stops future authorized access but does not automatically erase documents, previously copied data, assistant conversations, or records already created.

To request disconnection or deletion of retained integration data, email jacob.jones@empyreanconsulting.com and identify the account and integration, without sending passwords or tokens. We will verify the request, remove credentials and data under our control that are no longer needed, and explain any legally required retention or additional deletion steps for user-owned files, backups, or independent providers. Files in your own Google account remain under your control unless you separately request an authorized change.

Changes and contact

These tools are intended for authorized adult users, not children. We will update this page when data practices change. A new purpose or new category of Google data requires an updated disclosure and the necessary user consent before that use begins.

Questions or privacy requests: Jacob Jones, Empyrean Consulting, jacob.jones@empyreanconsulting.com.