Last updated: 16 October 2026
This policy describes the planned and currently tested Google Drive integration for HSENexa Backup Manager, a private backup utility operated by HSENexa. It is separate from the public HSENexa platform.
When the operator explicitly authorizes the utility, it requests the Google Drive drive.file permission, intended for files the application creates or that the operator selects for application use. It does not request permission to scan the operator's entire Google Drive.
The utility is designed to upload encrypted backup archives and technical integrity/status reports to a dedicated operator-controlled Google Drive location. Backups may contain personal information originating in HSENexa services. Archives must be encrypted before upload; the private recovery key must be kept separately. The current integration has been tested with dummy data only; scheduled production backups are not yet active.
OAuth tokens are security credentials used for authorized access. In a future unattended deployment, access must be restricted to a secured automation environment; credentials must not be published in application code or logs. Tokens may be revoked by the account owner in Google Account third-party access settings.
Encrypted backup files will be stored in the operator's Drive under a documented retention policy once automation is approved. The proposed retention is seven daily, four weekly and six monthly copies; no claim is made that this policy is currently active. Google Drive storage and account access remain under the account owner's control.
The utility is not intended to share Google Drive data with advertisers or sell it. Automated monitoring reports should contain backup metadata only, not user records or unencrypted file content.
For questions, contact support@hsenexa.com.