Effective October 12, 2026

Make Automation privacy

This policy covers the personal Make integration operated by Yu-Che Lin, shown as “gmail/drive automation” on Google’s consent screen. It explains what access is granted and how the workflows handle data.

Data and permissions

The connection identifies the authorized Google account by email. Its existing permissions include Google Drive access (drive and drive.readonly) and Gmail access (https://mail.google.com/). These are broad permissions: Drive access can cover all Drive files, and the Gmail scope permits reading, sending, and deleting email.

The current workflows using this connection search Drive folders, create folders, and upload generated files. They do not contain Gmail actions. Permissions describe what the connection can do; the owner’s configured workflow determines which actions run.

Purpose and processing

Data is used to carry out the owner’s configured file and document tasks. Make processes connection credentials, file metadata, workflow inputs and outputs, and execution records. Google stores files uploaded to Drive. Related workflows use separate Google connections for Docs and Sheets documents and records, and LINE for configured messages.

Some workflows also use Google Gemini, OpenAI, OpenRouter, or CloudConvert to generate or convert content. Data passed to those steps is determined by the workflow’s configured inputs; granting Google access does not itself send the contents of the account to those providers.

Storage and security

OAuth credentials are managed by Make so it can execute authorized steps. Workflow data may appear in Make’s execution history and in configured destinations. Make and Google apply their respective service security controls. The owner controls access to the Make account and the destination files.

Sharing and limited use

Data is shared with the services needed to perform configured tasks and with recipients selected in the workflows. Google user data is not sold, used for advertising, or used to train general-purpose AI models by this integration. Use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Retention and deletion

Make retains execution records according to the account’s plan and settings. Files and records in Google Drive, Docs, and Sheets remain until deleted; other destinations apply their own retention settings. To stop future access, disable the relevant Make workflows and revoke the integration in Google Account connections. Revocation does not erase previously created files, messages, or execution history.

Contact

For questions or requests about access or deletion, contact Yu-Che Lin at rjsky311@gmail.com. Changes to this policy will appear here with an updated effective date.