Privacy Policy

Last updated: October 12, 2026

This policy covers Family History Archive (FHA), including Family History Archive Backups, maintained by Ben McCoy. Questions and requests may be sent to bendoesads@gmail.com.

Archive information

FHA stores genealogy information supplied by authorized users, including people, places, events, relationships, sources, citations, external identifiers and edit/import history. Signed-in email addresses are used for access control and attribution. Archive data is available according to the application's family-member and administrator permissions.

Google data we access and why

Connecting Google Drive is optional and restricted to the designated backup administrator. FHA requests the https://www.googleapis.com/auth/drive.file scope. This permits access to app-created files and files explicitly made available to the app, rather than general access to the entire Drive.

FHA reads the connected Google account's email address to confirm it is the designated backup account. It reads the backup folder's identifier, type, sharing status and permissions to check that the folder is suitable. It creates JSON backups and verification reports and reads those files back to check their contents and integrity.

Backup reports contain file and folder identifiers, timestamps, record counts, checksums, verification results and the administrator's email address. FHA uses these details to show where a backup was saved and whether verification succeeded.

Storage and service providers

The private application runs on Cloudflare, with archive records stored in Cloudflare D1. The Drive connection stores an encrypted refresh token and connection details in Cloudflare Workers KV, using a key held separately as an application secret. Short-lived access tokens are used to communicate with Google. FHA does not receive or store your Google password.

Backup files and reports are stored in the connected owner's Google Drive. Their contents pass through the Cloudflare application during export and verification. A temporary secure cookie is used to validate the Google connection flow; access services may also use authentication cookies.

GitHub Pages hosts these public informational pages. These pages include no application analytics, advertising scripts or embedded trackers. Hosting and access providers may process technical request information, such as IP addresses, for delivery, security and operation under their own policies.

Use and disclosure

Google data is used to provide and secure the requested backup and verification functions. FHA does not sell Google user data, use it for advertising, or use it to train general-purpose AI models. Data is processed by Google and Cloudflare as needed to operate these functions. Information may also be disclosed when required by applicable law or necessary to investigate security issues.

FHA's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Human access to Google data is limited to user-authorized assistance, security investigation or legal obligations as permitted by that policy.

Retention, deletion and disconnecting

Archive records are retained for ongoing family research until an administrator removes or corrects them. Contact the maintainer to request review, correction or deletion of information concerning you.

Drive backups and reports remain in your Drive until you delete them. FHA currently has no automatic retention or deletion schedule. Removing an archive record does not remove it from older backups; the Drive owner manages those copies separately.

You can revoke FHA's Google access through your Google Account's third-party connections. Revoking access prevents future authorized Drive operations but does not delete existing backups or automatically erase connection details held by FHA. Contact the maintainer to request removal of stored connection information. Reconnecting replaces the stored connection credentials.

Security and changes

FHA uses access controls, encrypted connection storage and HTTPS to protect information. No system can guarantee absolute security. Material changes to Google data use will be disclosed before the new use begins, with renewed consent where required. The date above identifies the latest policy update.