Application information

Privacy policy

Last updated: 13 September 2026

This policy covers shanting, a personal backup integration operated by the owner of shanting.cloud, including its Family Backup desktop OAuth client and this documentation website. The integration is for the operator’s own use, not public enrollment.

Google data accessed and why

The installed rclone client uses Google authorization to upload, list, check, update, remove, and download backup files in the configured Google Drive backup location. This supports scheduled synchronization, verification, and restoration.

Processing includes backup file contents and the file or folder metadata needed to manage them, such as names, identifiers, sizes, and modification times. Drive permissions may permit access beyond the configured folder; folder targeting is an operational setting, not a restriction on the OAuth grant itself.

Storage and security

OAuth tokens are kept in private configuration on the operator-controlled host so scheduled backups can run. They are not included in these public website files.

The configured rclone crypt remote encrypts backup contents before uploading them to Google Drive. Encryption credentials are held separately. Working files and restored copies on the operator’s machines may be unencrypted and rely on local access controls. Encryption does not prevent an authorized operator holding the keys from reading restored data.

Use and sharing

Google API data is used for the backup, verification, and recovery functions described here. Google Drive stores the remote backup; the operator’s host processes it. The integration does not sell this data, use it for advertising, or transfer it to data brokers. It does not publish backup contents through this website.

Use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Retention, deletion, and revocation

The operator controls backup retention and deletion. Synchronization may replace or remove remote files to reflect the selected source; Google Drive trash and version retention may keep additional copies under the account’s settings. Local recovery copies must be managed separately.

The account owner can revoke authorization through Google Account connections. Revocation stops future authorized access once effective; it does not itself erase existing backups or local files. Delete those copies separately where they are stored.

This website

These static documentation pages do not request Google authorization or collect backup files. They contain no application forms, site-authored analytics scripts, or site-authored tracking cookies. Cloudflare, the hosting provider, may process technical request information such as IP addresses and browser details to deliver and protect the website, as described in Cloudflare’s privacy policy.

Contact and changes

For privacy questions or requests, contact the operator using the support email displayed on the Google consent screen for shanting. Material changes to these practices will be reflected on this page with an updated date.