Privacy policy

PLX Server Backup · Effective 22 October 2026

PLX Server Backup is a personal, owner-operated backup workflow using rclone on an Oracle-hosted server and Google Drive. This policy describes that intended configuration. It does not represent an audit of the operator's server, rclone settings, encryption, logs, or backup schedule.

1. Operator and scope

The application is maintained by GitHub user plx0 for personal backup use. This policy covers the Google Drive integration and this public information website. It is not a public hosted backup service, and this website does not receive backup files or perform OAuth authorization.

2. Data accessed and purpose

The workflow transfers the server files selected by the owner to the owner's Google Drive. To manage those backups, rclone may process file contents and metadata such as names, folder paths, IDs, sizes, timestamps, checksums, and transfer status. File contents can contain whatever information the owner chooses to back up.

The intended Google OAuth scope is https://www.googleapis.com/auth/drive.file. It allows creation and management of files created by this application, plus files explicitly made available to the application. It does not provide general access to every file in the Google Drive account. In an ordinary rclone setup, files uploaded through a different application may not be visible to this client.

Google authorization is used only to carry out the owner's requested backup, restore, listing, and file-management operations. The operator must keep the actual rclone scope and behavior consistent with this policy.

3. Storage and security

Source files and any local copies reside on the owner's server or devices. Uploaded backups and associated metadata reside in the owner's Google Drive. OAuth access and refresh tokens, along with OAuth client configuration, are normally retained in the owner's rclone configuration on the server and any device used for authorization. Depending on the configured logging, local logs may retain file paths, names, errors, and transfer metadata.

The owner is responsible for restricting access to the server, configuration, logs, and backup destinations and for choosing retention and optional encryption. rclone configuration and backups must not be assumed encrypted unless the relevant protection has been configured. Google API transfers use HTTPS; this does not establish that backup files are encrypted by the application before upload.

4. Sharing and service providers

Google processes the data stored in Google Drive under its terms and privacy practices. Oracle provides the infrastructure hosting the owner's server. People or services the owner authorizes to administer that infrastructure or access the Drive destination may be able to access data according to those permissions.

The application's purpose is personal backup. Google user data is not sold, used for advertising, used to train general-purpose AI models, or intentionally shared for unrelated purposes. The workflow does not deliberately publish backup files. The owner controls any sharing permissions applied separately to the server or Google Drive.

5. Retention and deletion

There is no fixed retention period imposed by this information website. Backups, local copies, configuration, and logs remain until the owner deletes them or a retention rule the owner has configured removes them. To remove data, stop scheduled transfers and delete the relevant Drive files, server copies, and logs. Google Drive trash and provider-managed retention can delay permanent removal.

To disconnect the application, revoke it in Google Account connections and remove its stored authorization from the rclone configuration on each relevant device. Revocation stops future access using the revoked grant; it does not itself delete existing backups. A new authorization may be required to use the integration again.

6. Public website and contact

This static website is hosted by GitHub Pages. It contains no application sign-in, forms, advertising, analytics scripts, or tracking cookies added by this application. Hosting providers may process normal web-request information, including IP addresses and access logs, under their own policies. See the GitHub General Privacy Statement and Google Privacy Policy.

For privacy questions, contact the maintainer through GitHub issues. That channel is public. Submit only a general question; do not post credentials, tokens, backup content, or private account details. The owner can perform deletion directly using the controls described above.

7. Google API data-use commitment and changes

PLX Server Backup's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements where applicable. Access is limited to the disclosed backup and file-management purposes.

If the application's purpose, permissions, or data practices change, this policy must be updated before the changed use begins. The effective date above identifies the current version.