Privacy Policy

About this policy

Radar Backup is the owner's personal, local-first utility for encrypted backups of the owner's local research application. This policy covers the utility's Google data handling and this separate public information website.

Current status: only synthetic test data has been uploaded to Google Drive. The synthetic-data pilot passed upload, integrity verification and isolated restore. Production backup remains inactive; no real research dataset has been uploaded. This describes the tested architecture and does not imply that production backup or automated scheduling is active.

Google data and permissions

The local utility requests only https://www.googleapis.com/auth/drive.file through an owner-controlled Google OAuth Desktop client.

The scope permits access to Drive files created by the application or explicitly opened or shared with it. It is per-file access, not general access to the account's entire Drive. In this backup workflow, access is used for repository files and folders the utility creates. Unrelated pre-existing Drive files are outside this workflow.

Within this access, the utility processes:

• Encrypted repository file content: uploaded for backup and downloaded for integrity verification or restoration.
• Drive file and folder metadata: identifiers, names, parent relationships, sizes, timestamps and available checksums needed to locate, transfer and verify repository files.
• OAuth authorization data: access tokens, refresh tokens and related authorization details used locally to authenticate requests to Google.

Permitted repository operations include creating, listing, reading, updating and deleting app-accessible files when the owner runs backup maintenance. This is write access, not read-only access. The permission is not a guarantee that existing files from another client or upload method will be accessible.

No Gmail, Contacts, Calendar or broad Drive scope is requested. The utility does not request a separate Google profile or email scope.

How data is used and shared

Google data is used to transfer encrypted repository files, check integrity, manage retained backup files and restore data locally. The application does not use an LLM for backup.

Google Drive is the intended off-machine storage provider. Google processes encrypted files, Drive metadata and normal service information, such as request timing, IP addresses and account activity, under its own terms and privacy policy. Google authorization services process OAuth requests and tokens as needed to authorize access.

No separate cloud AI service, analytics provider or external backup processor is configured to receive backup contents. The utility does not sell Google user data or use it for advertising, profiling or training AI models. This statement describes the configured architecture; it is not a claim that a complete network audit has ruled out every other form of service processing.

Encryption and local credentials

restic encrypts backup content locally on the owner's device before the encrypted repository files are transferred to Google Drive. During restore, repository data is downloaded and decrypted locally with the required restic credentials.

Encryption of backup content does not hide all storage metadata. Google Drive can observe repository object names, sizes, timestamps and transfer activity. Repository control and key files may also expose format or key-derivation metadata; a password-protected repository key file is not the plaintext recovery password. Encryption does not guarantee protection against a compromised device, stolen credentials or every security threat.

OAuth credentials are stored in encrypted local configuration on the owner's device and used by the local backup utility to authorize access to Google Drive. The public website contains no OAuth credentials, access tokens, restic passwords or recovery keys and provides no access to them.

Storage, retention and controls

Encrypted backup files and their Drive metadata remain in the owner's Google Drive until removed through the owner's retention or deletion actions, subject to Google's service behavior, trash and retention rules. No fixed retention period is promised here. Restored plaintext, local repository data, caches and any script or tool logs remain under the owner's local control and must be managed locally.

The owner can revoke the utility's access in Google Account third-party connection settings. Revocation stops future authorized access after it takes effect; it does not itself delete existing Drive files, local tokens, logs or restored files. The owner can separately remove those items and empty Drive trash where appropriate. Without valid authorization, network access or the required recovery credentials, backup and recovery may fail.

This information site has no backup storage, account system or data-deletion service.

This public website

This is a static information website. It does not access your Google Drive, initiate OAuth, run backups or receive backup content. It includes no cookies, analytics, advertising, forms, third-party scripts or external font requests. No browser storage is used by the site code.

This public information website is hosted on Cloudflare Pages. Cloudflare may process ordinary HTTP request and security information, including IP addresses, browser information and requested URLs, to deliver and protect the site under Cloudflare's Privacy Policy. This site makes no claim that the hosting provider keeps no logs. The site's no-tracking design must be preserved unless the owner separately approves a change and updates this policy.

The underlying research application is separate from this public information website and is not accessible through it.

Changes to this policy

The owner should update this policy and its date before materially changing the utility's Google data handling, recipients, permissions or the website's behavior. A new use of data must not be assumed from a previously granted permission.

Contact

The public contact address uses Cloudflare Email Routing to forward messages to an inbox chosen by the owner. Cloudflare and the destination email provider will process those messages for delivery; the owner will use them to respond to enquiries.