Privacy

Backup component

Yonca Backup creates encrypted AES-256 DMG archives and checksum sidecars. It can copy them to local external storage and a separate Monster PNY copy.

If the owner enables the direct Google Drive adapter, the component uses Google OAuth to list and verify existing archives and transfer approved backup objects.

Google Drive permission and operation

The current OAuth permission allows Yonca Backup to view and manage all files in the connected Google Drive. The implementation uses the owner-approved folder as its operational root. Historical archive verification requires access to archives that were not created by this OAuth app.

OAuth credentials and refresh state are kept in private configuration on the owner device. Google consent happens in the owner’s browser.

Where information goes

The current backup component does not send archive contents to a Yonca-hosted backend and does not use archive contents for advertising or AI training. A direct Drive transfer sends the encrypted archive and its checksum sidecar to the owner-approved Google Drive folder.

This static site

This static site is intended to be hosted by Cloudflare. Cloudflare may process normal website request metadata needed to serve the site, such as network and request information. This is separate from the backup application’s OAuth credentials and archives, which remain on the owner machine or in the owner-approved Google Drive folder.

The site author does not set analytics or advertising cookies. Cloudflare may use necessary cookies for security or service operation.

Choices and limits

The owner may revoke the Google connection through Google and may separately delete stored archives. Automatic pruning is disabled, so no retention period is promised until a retention policy is configured.

Checksum verification checks integrity. This notice does not promise zero access, end-to-end encryption, or a specific key-management model.

Contact

For this private owner-fleet service, contact to@ate.sh.