Privacy Policy
Effective November 3, 2026
This policy describes the intended data handling of Digital Operations AI, a privately operated automation project. It should be updated if the integrations, storage arrangements, or data practices change.
Information accessed
When authorized through Google OAuth, the automation may access file metadata and selected content in Google Drive and spreadsheet content in Google Sheets. Depending on the workflow, this can include file identifiers, filenames, image links, media content, descriptions, and content scheduling records. Only permissions granted through the connected Google account are available to the automation.
How information is used
Authorized data is used to maintain media libraries, organize and retrieve workflow content, detect new files, prevent duplicate entries, prepare content drafts, and update spreadsheets. Selected content may be processed by locally hosted AI tools as configured by the operator.
Storage and security
Workflow definitions and processing data may be stored in the operator's self-hosted automation environment and in connected Google Drive and Google Sheets accounts. Security controls, backups, access permissions, and retention settings are managed by the operator and the respective service providers. Do not connect sensitive information without confirming that the environment is secured appropriately.
Sharing and disclosure
Connected Google data is used for the configured automation workflows. When the operator explicitly enables integrations for content publication, selected media or text may be transmitted to the designated social platforms. Data may also be processed by the cloud services used to operate these integrations. The project does not use Google user data for advertising targeting or sell Google user data.
Google API data
Access to Google user data is limited to purposes described in this policy. The project does not use Google user data to train generalized artificial intelligence models. If future functionality involves additional processing or third parties, this policy must be updated before enabling it.
Retention and deletion
Data may remain in connected Google accounts and the self-hosted workflow environment until deleted by the operator or according to the applicable service's retention settings. The operator can remove connected content and revoke access via Google Account permissions. Removing an integration does not necessarily delete previously stored copies; those must be reviewed separately.
Your choices
Access can be reviewed or revoked in Google Account settings at Google Account connections. For questions or requests about the project, contact digitaloperations.hq@gmail.com.
Changes
Material changes in data access or use will be reflected in an updated version of this policy.