隐私政策

Chengming Backup — Privacy Policy

Effective and updated: October 15, 2026. Maintained by the Chengming Backup project maintainer, reachable at x@aike.si.

Current status. Cloud backup is not active during setup. This notice describes authorization and the planned operating rules; it does not claim Google verification or endorsement. The project supports a private app used by its owner and a small circle of friends. This website provides project and policy information, without collecting or processing application business files. The private application requires its own notices and consent for its separate business features.

Access and collection. A maintainer may authorize the application using Google OAuth. rclone stores the client configuration and access and refresh tokens for unattended operation; Google account passwords are not collected. The planned permission is drive.file, covering files created by or explicitly granted to this application, plus metadata needed to manage them, such as identifiers, names, sizes, timestamps and integrity information. Gmail, contacts and calendar access are not requested.

Project content. Selected backups may contain consistent database exports, application records, authorized saved files, authorization and deletion records, and recovery configuration. Temporary processing content is not automatically archived. Snapshot contents depend on the explicitly selected project backup inventory.

Use and security. Google API data is used only for backup upload, file and snapshot management, integrity checks, restoration and necessary troubleshooting. It is not sold, used for advertising or profiling, or used to train or improve general-purpose AI or machine-learning models. The planned implementation encrypts snapshots with restic before rclone transmits them over HTTPS. Google receives encrypted objects and may process their metadata. Recovery passwords must be stored separately from the backups. Tokens are kept in protected configuration and never embedded in public pages, code or Android packages. Only a local synthetic encryption and restoration drill has passed; Drive upload and restoration remain unverified. Authorized maintainers may access original data during maintenance or restoration; operator-inaccessible end-to-end encryption is not claimed.

Sharing and human access. Google is the account owner's selected storage provider; the hosting provider supplies the server environment. Google user data is transferred or accessed by people only to provide explicitly authorized backup and restoration, for security needs, where required by applicable law, or with explicit consent. Chengming 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.

Website logs. Access logs record IP addresses, time, method, path, status and response size, excluding query strings. Error logs may contain request context needed for diagnosis. No analytics scripts, advertising trackers, external fonts or nonessential cookies are used. Daily rotation retains seven historical log files plus the current log, normally around seven to eight days; operational failures must be addressed by the maintainer. Necessary records may be retained longer for security incidents or applicable legal requirements.

Retention and deletion. The proposed snapshot policy retains seven daily, four weekly and six monthly backups, subject to confirmation before activation. Online deletion does not immediately rewrite historical snapshots; their contents may remain until snapshots expire or the project backup is explicitly removed. Deletion and revocation records must be reapplied on restoration. Contact the maintainer to request access, correction, suspension or deletion of your data. Requests require proportionate identity and ownership checks; do not email sensitive business files or tokens.

Revocation. The account owner can remove the application at Google Account third-party connections. Revocation stops future authorized access but does not itself delete previously uploaded Drive files. The owner can delete the application's backup directory and request removal of related server credentials, caches and deletable copies. Google's own storage and trash retention rules also apply.

Changes. Material changes will be dated here, communicated to affected users before a new purpose or permission takes effect, and require consent where necessary. Contact: x@aike.si.