Your files. A defined purpose.

This policy distinguishes the public information website from the personal desktop preservation application operated by its owner.

The public website

This site has no application login, archive-upload form, advertising, embedded analytics or application-set tracking cookies. Cloudflare hosts and delivers the site and may process technical request data, such as IP addresses, request times and browser information, for delivery and security under its Privacy Policy. This site is not a portal to private project archives.

The desktop application

The local application processes explicitly approved project documents, source files and related preservation metadata. Its records can include relative filenames, file sizes, hashes, version identifiers, processing status and timestamps. These support backup, integrity checks, version tracking and recovery. Local working files and metadata are not all encrypted merely because archive payloads are encrypted.

Google user data and access

The optional Drive API integration requests https://www.googleapis.com/auth/drive.file only. It accesses files created by or explicitly opened with the application, and the owner-selected destination folder. It uses folder identity, type, permissions and file metadata to check the destination, uploads encrypted archive objects, and downloads those objects for verification and recovery. It does not request Gmail, contacts, calendar or broad Drive access.

Google authentication is performed through Google's authorization flow. The desktop configuration uses a system-browser flow with PKCE and state validation. OAuth credentials are protected locally using Windows CurrentUser DPAPI; they are not published on this website or in source control. The site does not receive authorization codes, access tokens or refresh tokens.

Purpose and sharing

Google API data is used only to provide the owner-requested preservation and recovery features. It is not sold, used for advertising, used to train generalized AI models, or shared for unrelated purposes. The app's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Encrypted archive content is transmitted to the owner's authorized Google Drive destination. Google can still process storage metadata such as object size and upload time. Separately reviewed, sanitized project-status reports may be published to an owner-authorized private GitHub repository; this is distinct from publishing archive contents or Google authorization credentials. The public site repository contains only website materials.

Encryption and recovery

Archive payloads use authenticated AES-GCM encryption before upload. The local application key is protected with Windows DPAPI. An optional recovery envelope protects that key using an owner-chosen passphrase with scrypt and AES-GCM. The owner must retain the recovery envelope and passphrase separately. Losing the necessary recovery materials can make archives unrecoverable. These controls do not guarantee protection against compromise of an unlocked device or account.

Retention, deletion and revocation

Versioned backups and local preservation records are retained until the owner deliberately removes them; the current backup transport does not automatically delete remote versions. Removing a source file does not erase prior backups. The owner can remove archive objects in Google Drive and corresponding local copies, subject to those services' trash and retention behavior.

Access can be revoked in Google Account connections. Revocation stops further authorized API access but does not automatically delete existing archives. The owner must separately remove local authorization material when retiring the application. Reauthorization may be necessary after expiry or revocation; indefinite token validity is not promised.

Separate optional services

Google Drive for desktop has its own authorization and synchronization behavior. It is not the custom drive.file OAuth client. Any separately authorized review using third-party tools is outside this website's data collection and must follow its own permission boundaries.

Contact and changes

Use the contact page for privacy questions. Never submit passwords, tokens, private keys or archive contents through public channels. Material changes to these practices will be reflected here with an updated date.