Privacy Policy
This policy explains how privately operated David Google Integrations may access, use, store, and protect Google account information when the account owner expressly authorizes an integration.
1. Scope
This public site provides information only. It has no sign-in form, does not request Google API tokens from visitors, and intentionally uses no advertising or analytics scripts. The separate private tools, including rclone, operate only when configured and authorized by the account owner.
2. Google data that may be accessed
Google Drive (current primary purpose): file contents, names, folders, IDs, metadata, and permissions needed to perform owner-directed backups or file operations. A broad Drive permission may allow reading, modifying, creating, or deleting files; access is not restricted automatically to one backup folder.
Optional future integrations: Google Calendar events and calendar details; Sheets spreadsheet content; Docs document content; YouTube channel, video, and analytics data. These are not automatically accessed merely because their APIs are enabled. Each workflow must be separately configured and authorized, and this notice should be revised if processing materially changes.
3. Purposes of processing
Google information is used solely to carry out owner-requested backups, restore procedures, permitted file management, reporting, scheduling, and other specifically authorized operations. It is not sold, used for targeted advertising, or used to build advertising profiles.
4. Storage, service providers, and sharing
For the rclone workflow, authorized files are transferred between the owner's server and the owner's chosen Google Drive account. OAuth credentials and operational logs may be stored on the owner's controlled server under access restrictions. Google, the selected hosting providers, and explicitly configured service providers may process data as necessary to deliver those services. Google user data is not shared with unrelated parties for advertising or sale.
This information website itself does not expose private Google data or OAuth tokens.
5. Security
Operational controls are intended to include least-privilege account access where available, restricted server file permissions, HTTPS for the public website, protection of OAuth credentials, and review of logs. No security mechanism can guarantee absolute protection. Backups and access rights must be validated independently.
6. Retention and deletion
Backup retention, file deletion, and operational-log retention follow the owner's configured backup policies; no universal retention period is claimed. The account owner can revoke application access through Google Account connections. Revoking an OAuth token does not itself delete backups already stored in Google Drive or local copies; those must be removed separately if requested.
7. Limited use and changes
Access to Google user data is intended to comply with the Google API Services User Data Policy, including applicable Limited Use requirements. This policy will be updated if new integrations, data purposes, or processors are introduced.
Contact: davidhandoko0121@gmail.com. Effective date: 17 November 2026.