Privacy policy

Mastermind Backup Verifier · Design Intelligence

Last updated: October 16, 2026

Under development. Live authorization is disabled. These rules define the permitted handling when the application is enabled. They describe the intended design, not a security certification or a claim that live integration has been tested.

Purpose and scope

Mastermind Backup Verifier is an internal Windows application for comparing one approved Google Drive backup item’s metadata with an expected record. Its permitted purpose is account verification, that comparison and reporting whether the check matched, differed or could not be completed. It is not a general project-analysis service. A metadata match does not prove full backup integrity or restoration.

These informational pages do not sign users in, accept files, handle authorization callbacks or connect visitors to Drive. Viewing them grants no access to Google data.

Information used

Account identity information includes the Google subject identifier, email address and email-verification status. Signed identity information is checked for the intended application, issuer, validity period and authorization context. The account must match the privately approved identity before a metadata check.

The metadata request is limited to the approved item’s identifier, parent identifier, drive identifier where applicable, binary file type, trash status, size, version, modification time and SHA-256 checksum when available. File names, owners, sharing lists, links, previews and contents are outside this request. Missing checksum is reported as unavailable; it does not permit content access.

Private configuration includes approved account and item identifiers, expected metadata and authorization records needed to maintain the connection. Ordinary local reports contain categorical outcomes and limited timing or diagnostic categories, excluding tokens, private identifiers, file names, project details and raw Google responses.

Google permissions and their limits

The permissions are OpenID account identity, email information and read-only Drive metadata access: openid, email and drive.metadata.readonly.

Drive metadata access is account-wide, not confined by Google to one folder or item. The account can have access to working projects as well as backups, and their metadata may be sensitive. The application must restrict its own requests to the approved item. That restriction does not narrow the underlying grant: a stolen usable access token could permit other metadata requests within the account’s access.

The application must not download or inspect contents, list, search or discover files, upload, modify items or change permissions. Read-only access does not make credential compromise harmless or establish backup-only account visibility.

Processing, storage and retention

The comparison is designed to run on the operator’s Windows computer. Metadata responses and short-lived authorization data are processed transiently during the operation, not retained as raw-response reports. This rule does not promise immediate or guaranteed secure memory erasure.

The planned protected storage uses the existing Doppler-backed credential resolver for approved credentials and private configuration. Its integration and protections require review before use. Credentials must not enter the public website or ordinary reports. This policy makes no encryption, hardware-isolation or completed-audit claim.

Necessary private configuration and stored credential records are retained while the owner maintains the connection, until the owner removes or replaces them during disconnection or retirement. Categorical local reports remain until the owner removes them through local record management. No fixed automatic-deletion period is promised. Retained provider copies require the corresponding provider removal process; deletion timing and completion must be confirmed for the records involved.

Providers and human access

Google handles authorization and supplies the requested metadata. The approved secret service, currently planned as Doppler, holds the credential and private-configuration values assigned to it. The authorized operator uses the local application and can review its results. No other recipient of Google user data is permitted without review and an updated disclosure before use.

Framer hosts these public documentation pages separately. Google tokens, account identities, private configuration, metadata responses and project details must not be sent to them. Support messages are used to respond to the request; do not include confidential records or credentials.

Limits on use and transfer

Information received through Google APIs is restricted to the purposes described here and handling in accordance with the Google API Services User Data Policy, including its Limited Use requirements. Google user data must not be sold, used for advertising or used to train artificial-intelligence models. This is the application’s intended data-use commitment, not Google endorsement or a compliance certification.

Revocation and deletion

Google Account third-party connections settings allow you to review or remove an application’s access. Revocation withdraws Google’s authorization; it does not undo past requests or automatically erase records elsewhere. Immediate invalidation timing is not promised here.

Disconnection also requires stopping the local verifier and removing associated stored credentials and private configuration through approved administration. Reports are removed separately when no longer needed. There is no account-management or deletion form on this website.

For assistance or deletion of support information held by Design Intelligence, contact jonathan@designintelstudio.com. Describe the request without tokens, authorization codes, file identifiers or private project files. Identity and scope may need private confirmation before action. No unverified response deadline or automatic provider-system erasure is promised.

Website visits and policy changes

Website visits are separate from verifier use. Framer and configured website providers may process ordinary request information, including IP address, browser information and pages requested. Cookies, analytics and retention depend on the actual site configuration and provider practices. This policy makes no zero-cookie or zero-tracking claim.

The page’s update date will change when the policy changes. Material changes to data use must be disclosed before the changed use begins. Live access remains disabled until the required authorization and security reviews are completed.

Product and privacy contact: jonathan@designintelstudio.com.