Agent Stack Backups privacy policy

Last updated: 11 October 2026.

Operator and purpose

Agent Stack Backups is operated by the owner of amandianeze@gmail.com for personal VPS backup and recovery. This policy describes the Google Drive backup integration. Contact the operator at amandianeze@gmail.com with questions about its access or stored backups.

Google data and permissions

When authorized, the integration uses Google OAuth credentials to access Google Drive. Its backup operations use the selected folder's identifier, backup file names and metadata, and encrypted backup file contents. Account information may be checked to confirm that the connected account is the intended backup account.

The requested Drive permission permits broader account access. The application configuration directs routine backup operations to the selected backup folder. A folder setting is not a restriction on the OAuth permission itself.

Use of data

The integration uses Google Drive data to store encrypted backups, confirm transfers, and retrieve recovery copies. Google data obtained through this integration is not used for advertising, sold, or used to train AI models. The backup transport does not send retrieved Drive content to the agent models.

The recovery archives themselves can contain private VPS configuration, credentials, and agent records. The local backup process encrypts archives with AES-256 before any planned upload to Drive. The recovery passphrase is excluded from those archives and must be stored independently by the owner.

Storage, access, and service providers

Local archives and integration credentials are stored on the owner's Hostinger VPS. Google Drive stores any uploaded encrypted archives. Google and Hostinger process data as the service providers for storage and hosting. The operator and anyone the operator authorizes to administer these accounts or the VPS can access the corresponding stored data and credentials.

Integration credentials are stored in private files on the VPS. The web server does not enable request access logging for these information pages. Operational error logs may contain request details. These pages do not provide access to backup archives or credentials.

Retention and deletion

Local archives follow the configured backup retention policy. Drive copies remain until the owner removes them or an enabled retention process removes them. The owner can delete Drive copies through Google Drive and remove local copies through VPS administration. Removing one copy does not remove other backup copies.

The owner can revoke the application's Google access through Google Account settings and remove the locally stored OAuth credentials. Revoking access prevents future authorized Drive operations; it does not delete existing archives.

Google API use

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

Changes and contact

Update this policy when the integration's data practices change. The date above identifies this version. Questions and deletion requests can be sent to amandianeze@gmail.com.