Data practices
Privacy policy
This policy describes Webnomous Encrypted Mail Backup, a private utility operated by the owner for the owner's mail server. It is not a public email or backup service.
Information handled
The utility prepares mail-server archives and integrity checksums. Archives may contain personal emails, mailbox data and server configuration. Archive contents are encrypted locally before they are uploaded to Google Drive. The recovery key is kept separately and is not included with the uploaded archives.
Google can see stored-file metadata, such as file names, sizes, ownership and upload times, and processes service and connection information under its own policies. Encryption of archive contents does not hide this metadata.
Google authorization and use
The app requests only the Google Drive https://www.googleapis.com/auth/drive.file scope. The backup workflow is confined to app-created backup files and the existing dedicated folder selected by the owner. It does not request the Gmail API or permission to read the owner's entire Drive.
Drive access is used to create and upload encrypted backup files, inspect their metadata and download those files for integrity and recovery checks. Account access remains subject to Google's rules and any policies applied by the account's organization.
Purpose and disclosure
Data is handled for the owner's backup, integrity verification and recovery. The operator does not sell it or use it for advertising. Google Drive is the storage destination. The utility is not intended to share archives publicly or give unrelated people access to them.
Local credentials and protection
Authorization credentials remain in private local files with restricted permissions. Restricted file access is an access control, not a claim that those credential files are encrypted at rest. The recovery key must remain separate from the encrypted backups. Recovery depends on preserving that key and verifying a usable backup.
Retention, deletion and revocation
The workflow does not automatically delete remote backups. Existing files remain in Google Drive until the owner deletes them through Drive or an explicitly authorized process. Provider retention or recovery behavior may still apply after deletion.
The owner may revoke the app through Google Account connections. Revocation stops future authorized access and may interrupt backups. It does not delete files already stored in Drive or remove local copies.
This information website
The authored pages have no signup or data-entry forms and do not ask visitors to provide mail or backup data. The hosting platform adds its own supporting script and may process ordinary connection and request information to serve the pages. Mail, archives, credentials and recovery keys are not published on this website.
Contact and updates
For existing contact information, visit Webnomous. This link does not promise a support service or response time. Material changes to this utility's practices will be reflected here with an updated effective date.