Greg's Mail Backup

Data practices

Privacy policy

This policy describes the personal desktop application Greg's Mail Backup and this public information website. The operator and contact is Greg Burns at gregburns1@gmail.com.

Google data accessed

With the account owner's explicit OAuth consent, the backup connection uses the Gmail read-only permission to access message contents, headers, attachments, drafts, message and thread identifiers, dates, labels and other mailbox metadata. This includes Spam and Trash until messages are permanently deleted in Gmail.

Purpose and use

The data is used to create, check, maintain and recover the owner's personal email backups. It is not sold or used for advertising, profiling or training general-purpose AI or machine-learning models.

The application's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Storage and sharing

Processing takes place on the owner's computer. Message files and ZIP archives are staged locally and copied to the owner's Microsoft OneDrive folder. Verified published copies allow local staging files to be released. Working SQLite metadata, logs and OAuth credentials remain on the local computer; the application does not publish credentials to OneDrive or this website.

Microsoft receives the backed-up email data through the owner's chosen OneDrive storage and sync service. Google receives OAuth and Gmail API requests. There is no separate application-operated server collecting email data, and no other intentional sharing beyond these services and owner-directed recovery/export. Provider security and retention policies apply to data held by those providers.

OAuth credentials have restricted local file permissions. The owner controls access to the computer, OneDrive account and exported backup copies.

Retention and deletion

Current captured messages are retained while present in Gmail. The configured application policy removes managed backup message content after permanent source deletion is confirmed on a successful run. Moving a message to Spam or Trash is not permanent deletion.

The application keeps the latest seven metadata snapshots. Earlier retained metadata snapshots can still describe a deleted message even after its managed email content has been removed. Cloud-provider version history, recycle bins and independently exported copies are governed separately by the provider's settings and the owner's actions.

Revoking access or deleting backups

The owner can revoke the application's connection in Google Account settings. This stops future access but does not automatically erase backups already created. The owner can remove stored backups from the computer and OneDrive, and delete local credentials when no longer needed. Questions about access or deletion can be sent to the contact above.

This website

These static pages contain no analytics scripts, advertising, forms or Google sign-in. They do not receive messages, backup files or OAuth tokens. GitHub Pages hosts the website and may keep standard request/security logs, including visitors' IP addresses, under the GitHub Privacy Statement.

Changes

The operator will update this policy if the application's data practices change, and will show the update date on these pages.