One file reference.
A separate observation.

The question the check answers

Was metadata available for this exact file at the recorded time? A manual Drive check reports that observation separately from your backup-plugin result and any restore test. Your archive remains in Drive.

Before you authorize

The requested scope is https://www.googleapis.com/auth/drive.file. Google classifies it as non-sensitive and recommends using it with Google Picker. It permits actions beyond metadata for files shared with this app; the implemented check only reads ID, size, trash status and MIME type. Google Picker itself displays file names and previews. File permissions granted to the same app can remain available across your connected sites until you revoke the grant. Authorization is optional; you can continue using job monitoring without a Drive connection.

The Google application is published for production authorization. Publication does not establish that Google has verified the app’s branding. Read the current consent screen and Google’s displayed status before authorizing. Website signup and subscription approval are separate from Google authorization.

Connect and check

In Archive checks, choose a site and open Google Drive. Read the data-access explanation, authorize selected-file access, and use Google’s chooser to select the actual archive. Use a file rather than a folder. The server verifies access before saving it, then you can explicitly run “Check metadata now”. Cancelling leaves the saved connection unchanged. If Google returns an earlier broad grant, remove the app in your Google Account and authorize again; this can affect other sites using the same grant. No public sharing of the file is required.

The check refreshes authorization and requests metadata. A not-found or access-denied result needs investigation; permissions, a changed reference or trash status can explain it. Metadata availability does not prove archive integrity.

Disconnect, remove history and revoke

“Remove stored connection” deletes this site’s encrypted Drive token and file reference from BackupTool. It keeps earlier check outcomes visible. “Remove this site’s Drive check history” removes those Drive outcomes without deleting other provider or job records.

To withdraw the Google grant, use your Google Account’s third-party connections and remove this app’s access. A Google grant can cover other sites connected through the same app and account. Revoking it can require those sites to reconnect too.

If an access token has expired or a refresh token has been revoked, BackupTool stops before requesting the file and reports that authorization is required. Reconnect only after reviewing the consent screen. Testing grants can expire under Google’s testing rules.

Data and service questions

The Privacy page explains use, storage, retention, service providers and your data requests. The service terms describe account access, subscriptions and the limits of monitoring.

Optional follow-up and scheduled metadata

Incident follow-up stores acknowledgement, investigation notes, review reminders and customer-explained resolution. Reporting resumption does not establish archive integrity or recovery. Each timeline retains its latest 100 entries until the site is removed. Dated handover exports can contain these notes and customer-recorded tests; review them before sharing.

Queued email follow-up, daily digests and scheduled branded HTML summaries require workspace opt-in and use the configured recipient. Optional Slack routing sends site names, current signals, timestamps and workspace links to the channel configured by the customer. Investigation notes, exact archive references and test details are excluded from Slack messages. The webhook URL is encrypted. Transport acceptance is recorded separately from inbox or channel receipt. Terminal delivery records are cleaned after 90 days; incomplete outcomes remain for review and are not automatically retried.

Exact-object metadata schedules require separate per-provider consent and reuse the existing saved provider access. Google metadata checks may also request modifiedTime alongside the file ID, size, trash status and MIME type. Provider-reported modification times and request mode may be retained with the latest 30 metadata observations. Selecting a different object requires new schedule consent. This does not list Drive, find newer archives, read archive contents or create a new Google permission grant. Quiet hours and delivery maintenance windows defer follow-up notifications; they do not stop external backup software.