GK Monitor Backup
Privacy policy
Updated: 15 October 2026
1. Scope
This policy applies to GK Monitor Backup, Vladimir Izhukov’s utility (GardenKlad project) for backing up his own systems. It covers the Google Drive connection and does not replace policies for other services.
2. Data and permissions
With user consent, the application receives OAuth tokens for drive.file access. It processes encrypted archives and metadata of accessible files and folders: identifiers, names, sizes, dates and checksums. Access is limited to files created by the application or explicitly shared with it by the user.
3. Use
Data is used to upload, verify, find and retrieve backups, and to delete copies at the owner’s instruction or under owner-configured retention rules. Google data is not used for advertising, data sales or AI model training.
4. Storage and transfer
Archives are encrypted before transfer over HTTPS to the owner’s Google Drive. The owner keeps the private key separately from the upload server. OAuth tokens are stored on the server with restricted administrative access. Operational logs may include dates, operation status and file metadata. Google provides cloud storage; the server administrator maintains the application. Public archive links are not created automatically.
5. Retention, revocation and deletion
Copies remain until deleted by the owner or under retention rules configured by the owner; there is no single fixed retention period for all copies. Access can be revoked in Google Account connection settings. This stops further connection activity but does not delete existing archives. Delete those separately in Google Drive, including Trash if permanent deletion is required. Contact the application owner to remove server-side tokens, local copies and related logs.
6. Contact and changes
Data and deletion requests: vv@gardenklad.ru. If the purpose or requested data changes, this policy will be updated before those changes take effect; additional permissions will be requested separately.