CrewLaunch Google Integration Privacy Notice

Effective date: October 1, 2026.

What this connection is for

CrewLaunch uses a private Google connection for owner-authorized business administration. It supports email organization and response preparation, scheduling, and working with business files and documents. This connection is not a public customer sign-up service. This notice applies to the Google connection, not to purchases from the separate AI Skills storefront.

Information and permissions

Google asks the account owner to authorize access. Depending on the permissions granted, the connection can access email messages, attachments and labels; calendars and events; Drive files and their contents; Google Docs and Sheets; and contact information.

The current requested permissions include reading, sending and managing email; managing calendars; broad Drive access; creating and editing documents and spreadsheets; and reading contacts. Some permissions allow changes or deletion of data. These permissions are not technically limited to a single Drive folder. A granted permission does not mean every available item is read or every permitted action is performed. Availability also depends on which Google services are enabled.

How information is used

Information is used to carry out the owner's requested business tasks, prepare drafts and summaries, organize records, support scheduling and document work, and check that the connection is functioning. Permission to connect does not by itself approve a particular external message, destructive action or public publication; those actions remain subject to the owner's approval rules.

Processing, storage and service providers

Relevant information may be processed by automation and AI services used for an authorized task. This is not a local-only processing promise. Task content and results may be retained in working files, conversation history, operational records and backups. Authorization credentials are stored separately from the public website and permit access without storing the account owner's Google password in this integration.

Before a workflow sends Google data to an external processor or delivery service, that workflow must identify its recipients and purpose and use settings and terms consistent with the restrictions below. A workflow must not send Google data to a provider whose use of that data has not been checked for compatibility.

Restrictions on use

Google user data must not be sold, used for advertising or creditworthiness decisions, or used to train or improve generalized AI or machine-learning models. Transfers and human access must be limited to the purposes and exceptions permitted by the Google API Services User Data Policy. CrewLaunch's use and transfer of information received from Google APIs will adhere to that policy, including its Limited Use requirements.

Disconnecting and deleting retained information

The account owner can remove the connection through the Google Account third-party connections settings at https://myaccount.google.com/connections. Revocation stops further authorized access but does not automatically remove copies already retained outside Google or reverse actions already completed.

To request access to, correction of or deletion of retained information, contact CrewLaunch at CrewLaunchAI@gmail.com. Requests are handled manually after confirming authority over the information. A deletion review must cover relevant working files, conversation records, logs, backups and external processors. Any legally necessary retention or backup-related delay must be explained when the request is handled. This notice does not promise immediate deletion from every backup or deletion of another person's independent records.

Changes and contact

Material changes to the connection's data uses or permissions require an updated notice and any necessary consent before the new use begins. Questions: CrewLaunchAI@gmail.com.