Privacy Policy

1. About the application

Creative Hostinger Backup is an internal, privately operated server-backup utility for an authorized administrator. It is not a consumer service and has no public registration or advertising system. Google Drive integration is currently being configured and tested.

2. Google data and permissions accessed

The application is designed to request the https://www.googleapis.com/auth/drive.file permission. With the administrator's authorization, it can create and manage Google Drive files that are created by, or explicitly made available to, the application.

It may handle OAuth access and refresh tokens, backup file identifiers, file names, sizes, and technical metadata required for upload, listing, verification, and restore operations. It does not request permission to browse all files in the user's Google Drive.

3. Why and how data is used

Google Drive access is used solely for storing, checking, managing, and retrieving the administrator's offsite backup repository. Server application data, configuration files, and consistent database exports are prepared outside Google Drive. Once configured, the intended backup workflow encrypts this material on the server before upload.

Data obtained through Google APIs is not used for advertising, profiling, model training, or unrelated analytics.

4. Storage, protection, and sharing

OAuth credentials and configuration are intended to be retained in access-controlled configuration files on the administrator's server. The backup repository uses independently managed encryption; encryption keys are kept separate from Google Drive. Google provides the underlying storage and API platform for the encrypted backup objects.

No Google user data is sold or shared with advertising providers. Access is limited to the administrator and infrastructure providers necessary to operate the authorized backup service.

5. Retention and deletion

Encrypted backup files remain in the authorized Google Drive account until removed according to the administrator's selected backup retention policy or manually deleted. Technical OAuth configuration remains on the controlled server until the connection is removed or credentials are deleted. The retention schedule will be finalized before regular backups are enabled.

The account holder can inspect and delete backup files in Google Drive. Revoking OAuth permission in Google Account Connections stops future authorized access, but does not automatically delete files already stored in Drive.

6. Security and incident response

The application is intended to use HTTPS to connect with Google, narrowly scoped OAuth access, restricted local credentials, and encrypted backup archives. These controls will be verified during commissioning; their description is not a claim that live backups have already started. If the administrator suspects credential exposure, authorization can be revoked and credentials rotated.

7. Changes and contact

This notice may change when the backup workflow or relevant permissions change. The updated notice will be published here with its revision date. For privacy questions or requests, contact [email protected].