Privacy Policy
Effective: September 27, 2026
Overview
FRD Drive Automation is a privately operated automation application used by its owner for authorized Google Drive and Google Docs workflows. It is not offered as a public consumer service and does not sell access to users.
Google user data accessed
The application's baseline Google Drive authorization is https://www.googleapis.com/auth/drive.file. Under that authorization, the application may access file metadata and file or Google Docs content for files it creates, opens, or is explicitly granted access to through Google.
How data is used
Google user data is used only to perform user-authorized automation, including creating, reading, validating, updating, and recovering project files and their associated metadata. Data may also be used to verify integrity, destination identity, and transaction/recovery state where required by the authorized workflow.
Storage and retention
Private Google Drive content and OAuth credentials are not stored in this public website or public source repository. Google Drive files remain in the authorized Google account unless the user or an authorized workflow changes or deletes them. OAuth credentials are retained only in private operational credential storage for as long as needed to provide authorized access, and may be rotated or revoked.
Authorized automation may temporarily process file content or retain non-secret operational metadata needed for integrity, recovery, and audit. Such material is kept outside this public site and is not used for advertising or unrelated profiling.
Sharing and disclosure
Google user data is not sold, rented, or shared with advertisers. Data may be processed by infrastructure providers only when necessary to execute an authorized workflow or provide the underlying Google/API or compute service, subject to their applicable terms and security controls.
Security
The application is designed to minimize requested permissions, keep credentials outside public repositories and synced public workspaces, use explicit project/object boundaries, and fail closed when authorization or destination identity cannot be established.
User control
The authorized Google account owner can revoke the application's Google access through Google Account security/third-party access settings. Revocation prevents future API access until the application is authorized again.
Changes
If the application's data access, use, or sharing practices materially change, this policy will be updated before those changes are deployed where required.
Contact
Privacy questions may be directed to the operator through the public GitHub owner profile. Do not send credentials, tokens, or private Google Drive content through public GitHub issues.