FamilyRootsOur family. Our stories. Our generations.
Privacy

Privacy Policy

Last updated: November 2026

FamilyRoots is a private family-tree service designed to help families preserve their relationships, history and stories across generations.

Information stored in FamilyRoots

Family information is contributed by approved family members.

Depending on what family members choose to add, FamilyRoots may store:

FamilyRoots is not intended for storing sensitive information such as medical records, financial information, government identification numbers, passwords, or private contact details.

Account information

FamilyRoots uses Google sign-in to authenticate users.

Authentication may involve account information such as your name, email address, Google account identifier and the short-lived access token required to use FamilyRoots with Google Drive. FamilyRoots application code holds access tokens in memory and does not write them into family files or local recovery hints.

FamilyRoots does not operate an account or membership database. Google authenticates the signed-in account and Google Drive enforces access to each family file.

How family information is added

Family information is contributed and maintained by approved members of each family.

Family owners and authorised contributors are responsible for deciding what family-history information is added and for keeping that information appropriate and accurate.

LaunchCraft Web provides and maintains the FamilyRoots technology. LaunchCraft Web does not independently research, verify or routinely review family information entered by family members.

Who can access family information

Family trees are private.

Access is limited to authenticated users who have been approved for that family and who currently have permission to its live file in Google Drive. FamilyRoots checks live Drive ownership and permissions rather than treating editable family-file role labels as authority.

Different access roles may allow approved members to view or contribute to family information. The owner can grant or revoke a person’s Drive access. An invitation code identifies the intended family file, but does not by itself grant access.

Approved members may be able to download, export or otherwise copy family information using FamilyRoots or Google Drive, depending on their permissions and available features. Revoking Drive access does not remove copies a person already made.

Possessing the website address alone does not provide access to the private family tree.

How information is used

Family information is used only to provide and maintain the FamilyRoots service, including displaying the family tree, relationships, family history and related features.

FamilyRoots does not sell family information.

Storage and security

FamilyRoots stores each family’s tree, relationships, Life Stories and Life Milestones in a private FamilyRoots file in the family owner’s Google Drive. Google Drive remains the storage location and applies the file permissions granted by the family owner.

The current FamilyRoots application does not maintain a central FamilyRoots database containing a copy of family-tree content. The application uses the limited Google Drive permission (drive.file) rather than permission to access all files in a user’s Drive.

FamilyRoots stores limited local account and file references on the device to help restore the previous Google account and find families the signed-in account has used. This includes the previous account’s Google identifier and email address, an owned-family identifier, and joined-family Drive file locators. These references do not contain the family tree and do not grant access without a valid Google session and current Drive permission.

For owners, FamilyRoots checks and creates automatic restore points in a private backup folder in the owner’s Google Drive. It also creates a safety backup before restoring an existing live family. These backups can contain the complete family file. FamilyRoots does not promise that a particular backup will be retained indefinitely.

Owners can restore a compatible saved FamilyRoots JSON backup that they explicitly select, and approved users may export a Family Journal PDF. On Android, a Family Journal export is written to the app’s cache and passed to the system share sheet. The cache copy may remain until Android or the user clears it. On the web, the journal is downloaded through the browser. Saved backups and exported journals are under the user’s and chosen recipient’s control and may contain personal family information. Users should store and share them carefully.

Reasonable technical measures are used to protect access to family information, including Google authentication, Google Drive file permissions and role-based controls derived from the live Drive file.

No internet-connected service can guarantee absolute security.

Keeping information accurate

Family information is maintained by the approved members of each family. Contributors and owners with appropriate permissions can update information within FamilyRoots.

LaunchCraft Web does not routinely access, verify or edit family-tree information on behalf of families.

If information about you is inaccurate, please contact the owner of the relevant FamilyRoots family so that an authorised family member can review and update it.

Correcting or removing family information

Family-tree information is managed by the approved members of each family.

If you would like information about you corrected or removed, please contact the owner of the relevant FamilyRoots family. An authorised family owner or contributor can make appropriate changes using FamilyRoots.

LaunchCraft Web does not routinely access or edit individual family-tree records on behalf of families.

The FamilyRoots customer may contact LaunchCraft Web regarding service-level or application questions. Because family content is stored in the family owner’s Google Drive, the owner controls deletion of the live family file and Drive backups. The person who exports a copy controls the copies they retain, but copies already shared with other people may remain with those recipients. Removing a member’s access does not delete that person’s information from the family tree; an authorised owner or contributor must separately correct or remove that content. Removing content from the live family does not remove it from backup files or exported copies that still contain an earlier version.

Children

Family trees may include information about children as part of recording family relationships.

Family members should limit information about children to what is reasonably necessary for the family tree and should avoid entering sensitive or unnecessary private information.

Service providers

FamilyRoots currently relies on Google for authentication, Google Drive storage and file sharing. Static web assets may be delivered by a hosting provider, but no FamilyRoots backend stores account, membership or family metadata. Service providers process information under their own applicable terms and privacy policies. Material future integrations will be reflected in this policy before they are used in production.

Privacy questions or concerns

For questions about how the FamilyRoots service handles information, privacy concerns, or service-level data requests, contact LaunchCraft Web using the contact details available on the LaunchCraft Web website.

Requests to correct or remove individual family-tree information should normally be directed to the owner of the relevant family.

Changes to this policy

This policy may be updated when FamilyRoots features or information-handling practices change.

The latest version will be available on this page.