Hermes VPS Drive Backup
Privacy policy
How Hermes VPS Drive Backup accesses, uses, stores and retains Google data, and how the account owner can revoke access or delete backup files.
Scope
Who and what this policy covers
This policy applies to Hermes VPS Drive Backup, an operator-only backup integration maintained by the AI OfficeOS site owner. It does not describe unrelated applications, the operator’s other projects or a public consumer backup service.
Access
Google data accessed and its purpose
The requested Google scope is https://www.googleapis.com/auth/drive.file. The integration accesses the content and metadata of files it creates or that the account owner explicitly opens or shares with it. Relevant metadata may include file and folder identifiers, names, sizes, timestamps and transfer status. It may query the account’s storage quota to avoid failed backups.
This access is used only to store and retrieve selected backup material, verify transfers and perform operator-approved version retention. It is not used to scan unrelated Drive files, read Gmail or access calendars.
Use
No advertising, sale or generalized AI training
Google user data is not sold or used for targeted advertising. This backup integration does not use Google user data to train generalized AI or machine-learning models. Backup content is not sent to a separate analytics or model-training service by this integration.
Hermes VPS Drive Backup’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Storage
Where information is stored and protected
Source material and credentials are handled on the operator-controlled server; backup objects are stored in the operator’s Google Drive. Backup archives must be encrypted before upload. Connectivity tests may use explicitly non-sensitive, generated test files instead of real backup content.
OAuth credentials are kept in access-restricted credential files, not in this public website or its source repository. Encryption keys require separate, protected custody. Encryption does not remove the need to secure the server or the Google account.
Google processes Drive storage and authorization under its own policies. Cloudflare serves these public disclosure pages and may process ordinary website request metadata under its own policies; this website does not receive backup contents. No analytics, advertising scripts, tracking cookies or collection forms are added by these pages.
Retention
Retention, deletion and withdrawal of access
Backup retention is chosen by the operator. Objects remain in Drive until the owner deletes them or an explicitly configured retention process removes them. Local source files and recovery copies are separately controlled by the operator. There is no promise of permanent retention.
To stop further access, disable the backup job and revoke the application’s Google access. To delete existing backups, remove the application’s backup objects in Google Drive and, when permanent deletion is intended, empty the relevant trash. Revoking permission alone does not delete existing Drive files. The operator can remove local credentials, operational records and recovery copies independently.
Contact
Questions and policy updates
For privacy questions or deletion assistance, use the User support email displayed by Google on the consent screen for Hermes VPS Drive Backup. Because this is an operator-only integration, the account owner also controls the backup job and its storage. Never send passwords, authorization codes, access tokens or encryption keys.
The current policy is published at this URL with an update date. A materially different data use or broader scope requires a new review and, where required, new consent; this page does not authorize an expansion.