Privacy Policy

1. Overview and Purpose

This Privacy Policy explains how the Vps application ("the Application", "we", "us") accesses, uses, processes, and protects information when interacting with Google services.

Vps is a strictly personal, non-commercial automation tool designed solely for scheduled disaster recovery and backup of virtual private server (VPS) infrastructure owned and maintained by the developer. The Application is not available to the public and does not provide multi-user accounts or commercial services.

2. Google User Data and Scopes Accessed

The Application requests access strictly to a single, scoped Google OAuth permission:

https://www.googleapis.com/auth/drive.file — "See, edit, create, and delete only the specific Google Drive files that you use with this app."

Under this scope:

• Restricted Scope Access: The Application only has access to files and directories that it has created itself within Google Drive (specifically under the designated backup directory).
• No Access to Personal Documents: The Application has zero access to your emails, Google Docs, photos, contacts, calendars, or any other personal Google Drive files.
• No Profile Harvesting: The Application does not collect, harvest, or process personal user profile information beyond the standard OAuth authentication token handshake required to identify the authorized Google Drive storage quota.

3. Purpose of Google Drive API Integration

The sole purpose of requesting Google Drive API access is to store, retrieve, and synchronize encrypted backup snapshots of server state (system configurations, database dumps, and application volume data) for emergency disaster recovery.

4. How Backups Are Generated and Stored

Backups are generated via automated local system services operating directly on the server:

1. Local Snapshot Creation: On a scheduled basis, automated system workers collect designated system configuration files, database dumps, and container persistent volumes.
2. Client-Side Encryption Pipeline: Before any data leaves the server or touches a network interface, the data stream is processed by Restic, an industry-standard backup tool with native cryptographic protection.
3. Transfer via rclone: The encrypted data chunks are uploaded to the authorized Google Drive storage destination using secure HTTPS protocols.

5. Cryptographic Protection (Restic Encryption)

Security and privacy are enforced at the architectural level through client-side end-to-end encryption:

• Cipher: Authenticated encryption using AES-256 in CTR mode with Poly1305 MAC or HMAC-SHA256.
• Key Derivation: Password hashing and key derivation utilize memory-hard scrypt algorithms.
• Zero Plaintext Exposure: Google Drive acts exclusively as a dumb object storage backend. All file names, directories, metadata, and contents are fully encrypted before transmission. Neither Google nor any unauthorized third party has the capability to inspect or decrypt backup contents.
• Key Storage: Cryptographic passphrases are kept strictly on the local server in root-restricted storage and in the owner's offline secure key storage. Passphrases are never transmitted to Google APIs.

6. Third-Party Sharing and Disclosures

We do not sell, rent, lease, trade, or share any data with third parties.

• No Trackers or Analytics: The Application and its public documentation pages contain zero third-party tracking scripts, cookies, or analytics services.
• No Commercial Data Use: No Google user data or backup contents are ever used for machine learning models, advertising, marketing, or behavioral profiling.
• Direct Transmission: All data transmissions occur strictly between the server host and official Google API endpoints over TLS 1.3 encryption.

7. Data Retention and Deletion Policy

Backup snapshots are maintained according to a defined automated retention schedule (e.g., pruning older snapshots via automated maintenance jobs).

The user maintains complete control over all data:

• Backups can be deleted at any time directly through the Google Drive web or mobile interface.
• Backups can be purged programmatically using local maintenance commands.
• Upon deletion, backup chunks in Google Drive are permanently removed.

8. Storage and Protection of OAuth Tokens

OAuth 2.0 refresh tokens and short-lived access tokens provided by Google are stored strictly in local configuration files on the server:

• Files are stored under root-only permissions (POSIX 0600), accessible only by the root administrative account.
• Tokens are never exposed in logs, public repositories, web frontends, or unencrypted backups.
• Tokens are utilized solely by the backup automation utility to refresh temporary API access tokens when executing scheduled backup jobs.

9. User Rights and Revoking Access

You have full and immediate control over the Application's access to your Google account at all times:

• You can immediately revoke access via the official Google Account Security portal at:
  https://myaccount.google.com/permissions
• Revoking access invalidates all active refresh and access tokens immediately, preventing any further communication between the Application and Google Drive.
• Previously uploaded files will remain in your Google Drive until you decide to delete them.

10. Security Limitations

The Application is intended for private use by its administrator. While industry-standard cryptographic practices (AES-256 client-side encryption) and least-privilege scoping are strictly enforced, users are responsible for safeguarding server root access and the master Restic encryption passphrase.