Privacy policy

Purpose and Google permission

The utility verifies whether one designated Google Drive file matches an owner-held local reference. It requests only https://www.googleapis.com/auth/drive.readonly for Google Drive access.

That permission can read metadata and download files accessible to the authorized Google account. It does not permit Drive uploads, edits, renames or deletions. OAuth itself is not restricted to a single file: the utility’s file-ID rule and a dedicated identity’s Viewer sharing arrangement provide that operational boundary. Additional files later shared with that identity could broaden what the account can access.

Data accessed and used

Verification uses the designated file’s complete contents and metadata, such as its identifier, name, size, modification information and available checksums. It calculates a SHA-256 fingerprint locally and compares it with the reference. During setup, the authenticated identity and accessible file metadata may also be checked to confirm the intended access boundary.

Google API data is used only for this verification and its access/safety checks. It is not used for advertising, profiling, sale, or training generalized AI models. Its use follows the Google API Services User Data Policy, including the Limited Use requirements.

Local processing and credentials

The installed rclone client communicates with Google over HTTPS and performs readback on the owner’s computer. Downloaded verification copies may be kept locally. Verification records can include identifiers, sizes, hashes, timestamps and diagnostic results; credentials and file contents are not intended for diagnostic logs.

OAuth client credentials and renewable authorization state are kept in an encrypted local rclone configuration. Its unlock value is protected using Windows user-bound data protection and restrictive local file permissions. Authorized local processes decrypt the necessary values in memory while running. This does not make the computer immune to malware or access by its administrator.

The public website does not receive Google authorization codes, credentials or Drive file contents. Owner-managed file synchronization and backups are separate from this read-only connection and remain under the owner’s control.

Retention and owner control

Authorization state remains stored locally until owner-approved cleanup. Verification records and downloaded copies may be retained for troubleshooting and evidence. No fixed automatic deletion schedule is currently configured; retention and cleanup require owner control.

The owner can revoke the application’s access in Google Account permissions. Revocation stops future authorized access but does not automatically erase local authorization state, records or copies. Local cleanup and any owner-managed backup retention are separate actions.

Sharing and service providers

The utility does not routinely disclose Google Drive contents or credentials to other third parties. Google processes authorized API requests under its own terms. The verification path does not use a separate hosted file-processing service, and Drive data is not published on these pages.

The owner may choose to share verification metadata or diagnostic records with authorized support tools. Such sharing is under the owner’s control and should exclude credentials and file contents.

These static pages contain no forms, application sign-in, analytics scripts or advertising trackers. The website hosting provider, Vercel, may process ordinary request data such as IP addresses, request times and browser information for delivery, security and operations under its privacy policy. This website traffic is separate from the local Drive verification process.

Questions and policy changes

For privacy questions or requests, contact the application owner using the user-support email displayed in the Google authorization screen for SCC Canonical Drive Readback. Do not send passwords, authorization codes, tokens or private file contents in a support request.

If the purpose, requested permissions or handling of Google data changes, the owner will update this policy before adopting the new practice and obtain new consent when required.