Last updated November 2, 2026

Privacy policy

This policy describes the planned Google Drive integration used by the owner-operated LinkPoint Backup Service. The automated workflow is under configuration and will be operated according to this policy when enabled.

Purpose

The service creates recovery copies of LinkPoint application records and document attachments stored in Supabase. It uses Google Drive as a private destination for encrypted backup archives.

Google data accessed

After the Google account owner authorizes the connection, the service requests the https://www.googleapis.com/auth/drive.file scope. This allows it to create and manage files and folders used by this integration, including filenames, metadata, and stored content. It does not request permission to browse unrelated files already present in the owner's Google Drive.

How data is used and stored

The integration will upload, verify, retrieve, and delete its own encrypted backup archives for backup maintenance and recovery. The archives can contain LinkPoint tasks, customer and project records, notes, and uploaded attachments. Backups are intended to be encrypted before transfer to Google Drive. Decryption keys will be managed separately from the Drive account.

Temporary processing may occur in GitHub Actions, which is used to run scheduled workflows. Google Drive stores the encrypted output. No backups are hosted on this public website.

Sharing

Google account information and backup files are not sold or used for advertising. Information is processed only as required to operate the backup workflow through its infrastructure providers, including Google Drive and GitHub Actions. The account owner controls authorization and access.

Retention and deletion

The intended policy is to retain the four most recent successful weekly backup sets. This retention schedule is not yet active while the workflow is being configured. Once implemented, older backups will be deleted as part of rotation. The account owner can also remove backup files directly in Google Drive.

Revoking authorization

The Google account owner can revoke the integration's access at Google Account — Third-party connections. Authorization revocation stops future Drive API access but does not automatically delete backups already stored in Drive.

Changes and contact

This policy will be updated if the backup workflow or its data-handling practices change. For questions, use the user-support email displayed on the Google authorization consent screen for the LinkPoint Backup Service.

This is an informational privacy disclosure for a private, single-operator integration, not an offer of public backup services.