Privacy policy

Data accessed and purpose

The utility uploads compressed archive contents and verification records. It reads the contents and metadata of its Drive files, including file names, identifiers, sizes, and hashes, to locate archives, verify uploads, and restore selected data. The transfer tool may also read account storage quota information to report available capacity.

The app requests the Google Drive drive.file permission. This permits access to files created by the app or explicitly made available to it. The current backup workflow uses files and folders it creates. It does not request access to Gmail, contacts, or all existing Drive files.

Google issues authorization tokens after the owner grants consent. The utility stores those tokens to perform unattended transfers; it does not receive the owner's Google password.

Storage and access

Archives and verification records are stored in the owner's Google Drive. Source data, temporary archive copies, restored files, transfer logs, verification receipts, and authorization credentials may be stored on the owner's computer or server, including infrastructure hosted by Amazon Web Services.

Transfers to Google use HTTPS. Authorization credentials are stored with restricted filesystem permissions, separately from this website and its source repository. The utility does not publish archives or create public sharing links.

The owner and people the owner authorizes to administer the backup system can access its data. Google and the infrastructure provider process data as needed to provide their services. This public website does not receive archive contents or authorization tokens.

Use and sharing

The archive utility uses Google user data to store, locate, verify, manage, and restore the owner's archives. It does not sell Google user data or use it for advertising.

Manifold Archives' use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Retention, deletion, and revoking access

Remote archives remain in the owner's Drive until the owner deletes them. The current automatic workflow retains remote archives. Eligible local source and temporary files are removed according to the configured retention and verification checks; recovery data and records may remain until the owner removes them.

The owner can revoke the app's access through Google Account connections and remove stored credentials from the backup system. Revoking access stops future authorized transfers; it does not itself delete existing Drive archives or local copies. Those can be deleted separately, including from Drive's trash where applicable.

This website

This informational site includes no analytics scripts, advertising, forms, or application cookies. It is hosted on Cloudflare Pages. Cloudflare processes visitors' IP addresses and request information to deliver and protect the website, as described in its privacy policy.

Contact and updates

Contact Christian Neisler at christian.neisler@gmail.com with questions about data handling or deletion. This policy will be updated if the utility's data practices change; new uses requiring consent will be disclosed before that use begins.