Privacy

GOOM Family Tree lets you build a family tree and share it with the relatives you invite. This page says what the app stores about you and about the people in your trees, who else handles that data, how long it is kept, and how to have it corrected or removed.

Effective . Questions and requests: privacy@goom.life.

Who can use it

You need to be at least 13 to create an account, with an email address and password or with a Google account. Sign-up asks for your date of birth and refuses anyone younger; the date itself is not stored, only whether you are under 18 and when that was checked. If you are under 18, you need a parent's or guardian's permission to use the app. A younger child can be included as a person in a parent's or guardian's tree.

A password account must confirm its email address through a link the app emails before it can sign in, and each password sign-in also asks for a code sent to that address. A password account whose address is still unconfirmed 14 days after sign-up is deleted.

What the app holds about you

  • Your account. Your email address; a salted hash of your password if you have one, never the password itself; whether your address is confirmed; whether emailed sign-in codes are on; when you signed up; when you last signed in; whether you are under 18; and, when the Terms apply, which version you accepted and when. If you sign in with Google, the app stores the link to your Google account and reads only your email address from Google; your name and Google profile picture are not stored.
  • Your profile picture, if you upload one. Only you see it.
  • Your preferences: which tree you last opened and how you like trees laid out.
  • Your trees and collaborations. The trees you own, the trees shared with you, your role in each, and who shared it and when. If you mark a person in a tree as yourself, that person is linked to your account.
  • Invites you send: the email address you invited (for email invites), the role, and when the invite was created, accepted, revoked or set to expire.

What the app holds about people in your trees

For each person in a tree: name, nickname, date of birth, date of death, birth order, sex, gender, pronouns, an optional photo, and how they are related to the others (parent, child or partner). Each tree also has a name. Sex and gender are separate, and gender is never guessed from sex. The only free text is pronouns and, when gender is self-described, a short description of it, up to 100 characters; there are no notes, places or biographies.

Photos are kept in private storage that is not reachable from the internet, and the app serves them only to signed-in people who can open that tree. A photo is stored exactly as uploaded, so information a camera or phone embeds in the file, such as where it was taken, stays in it.

The tree's owner chooses which of these details collaborators see, separately for living and deceased people. Dates can be shown in full, as the year only, or hidden; birth order, sex, gender with pronouns, nickname and photo can be shown or hidden. Unless the owner changes it, a living person's date of birth shows as the year only and their gender, pronouns and photo are hidden. Editors see everything unless the owner applies the same limits to them. Anyone under 18 who is alive shows to everyone except the owner without dates, nickname, gender, pronouns or photo, whatever the settings. Hidden details are removed by the server before a page is sent, not just hidden on screen.

If you are in someone's tree

Trees are built by their owners, who can add relatives who do not use the app. No tree is public and nobody can search for people or trees: a tree is visible only to its owner and to the people the owner invites. The app does not notify people when they are added to a tree. The owner decides which of your details the people they invite can see, and if you are under 18 they never see your dates, nickname, gender, pronouns or photo.

To have your details corrected, or your entry or photo removed, email privacy@goom.life. Tell us your name as it might appear and, if you know it, whose tree you are in. We check that the request comes from you or someone entitled to act for you, tell the tree's owner, and reply within 30 days.

Sharing

  • Only a tree's owner can share it, change collaborators' roles or remove them. An Editor can add, change and remove people; a Readonly collaborator can only view.
  • An email invite works only for an account with the address it was sent to. The email shows the inviter's email address and the tree's name.
  • A link invite works for anyone who has the link and signs in, until the owner revokes it or it expires. Link invites expire within 14 days of being created (7 unless the owner picks a shorter time). Whoever opens one sees the tree's name and the role, and confirms before joining.
  • The owner sees collaborators' email addresses on the sharing page. Collaborators do not see each other's.
  • A collaborator cannot leave a tree on their own; ask the owner, or email us.

Why the app uses this data

Your account data is used to provide the service you signed up for. Details of relatives who do not use the app are held because family history is the purpose of the service, and the safeguards on this page (no public trees, no notes or biographies, owner-controlled visibility, access only by invitation, removal on request) protect them. Logs and telemetry are used to keep the app secure and working.

Who else handles the data

  • Amazon Web Services hosts the app and its database on an Amazon EC2 server in the United States. Photos are stored in Amazon S3, and a nightly backup of the database is copied to Amazon S3 and deleted after 30 days.
  • Amazon Simple Email Service sends the app's emails: address confirmation, password reset, sign-in codes, tree invites, the link to confirm a new email address with a notice to the old one, and the confirmation that you deleted your account.
  • Google handles sign-in if you choose to sign in with Google, and tells the app your email address.
  • New Relic receives the app's logs, traces and metrics, used to find errors and slow pages.

Your data is never sold, rented or used for advertising. The app shows no ads and runs no analytics or tracking scripts; every script and stylesheet comes from the app itself.

Logs and telemetry

  • The app writes a log file on its server each day and keeps the last 28. The same lines also go to the server's system journal, which keeps them until its size limit pushes them out.
  • New Relic keeps logs for 30 days and traces for 8 days.
  • The web server in front of the app keeps a standard access log (IP address, time, the address requested and the browser) for 14 days.
  • Logs and traces identify you by an internal account number. When the app logs an email it sent, the recipient address is encrypted.
  • Logs and traces record the addresses of pages requested, which for an invite link include its code. Traces of database queries keep numbers and dates as they are and replace text values, such as names and email addresses, with a one-way hash.

Cookies and browser storage

Every cookie the app sets is strictly necessary for it to work, and none is used for tracking, so there is no cookie banner.

Cookies
CookiePurpose
.AspNetCore.Identity.ApplicationKeeps you signed in. It ends when you close the browser, unless you tick "Remember me?"; then it lasts 14 days from your last visit.
Identity.TwoFactorUserIdRemembers who is signing in between the password and the emailed code. Lasts 5 minutes.
Identity.TwoFactorRememberMeSet only if you tick "Remember this machine" when entering a sign-in code, so this browser does not need a code for 14 days.
Identity.ExternalOnly when you sign in with Google: carries the sign-in back from Google. Lasts 5 minutes.
.AspNetCore.Correlation.*Only when you sign in with Google: protects the round trip to Google against forgery. Deleted when you return.
.AspNetCore.Antiforgery.*Protects forms against cross-site request forgery. Ends when you close the browser.
.AspNetCore.SessionRemembers which tree you are looking at. Ends after 20 minutes without activity or when you close the browser.
.AspNetCore.Mvc.CookieTempDataProviderCarries a one-time message to the next page, such as "Profile picture updated". Deleted once shown.
ft_signup_holdOnly when a sign-up is refused because of age: stops another sign-up attempt from this browser for 24 hours. Holds no personal details.
ft_reauthOnly when you confirm deleting your account or changing your email address by signing in with Google again: proves that sign-in to this browser for 10 minutes. Deleted once used.

The app keeps one item in your browser's local storage, ft-theme, holding the colour theme you picked. It never leaves your browser. Because nothing tracks you, Do Not Track and Global Privacy Control signals have nothing to switch off.

How long data is kept

  • A password account whose email address is still unconfirmed 14 days after sign-up is deleted, with any empty trees it owns.
  • An account nobody has signed in to for 24 months is deleted, with the trees it owns (their people, relationships and photos) and its profile. Before that, the app emails the account's address 30 days ahead and again 7 days ahead; signing in before the date keeps the account. An account is kept while someone it shares a tree with still uses the app, and the service's own test and administrator accounts are exempt. Other accounts are kept until you delete them under Account settings or ask us to.
  • Link invites stop working within 14 days.
  • A tree is kept until its owner deletes it. Deleting a tree deletes its people, relationships, photos, collaborators and invites. Removing a person deletes their photo.
  • Deleted data drops out of the database backups within 30 days.

Your rights

  • Correct: you can change anything in trees you own or edit, your password and your profile picture yourself.
  • Change your email address: under Account settings you confirm it is you (your password, or signing in with Google again) and give the new address. The change happens only when you open the link sent to the new address, and a notice then goes to the old one. The change unlinks Google sign-in, pending tree invites sent to the old address can no longer be accepted, and your other signed-in browsers are signed out within 30 minutes. An address another account uses cannot be taken, and the form does not say whether one does.
  • Delete: you can delete your account yourself under Account settings in the menu with your picture, even before accepting changed Terms. You confirm it is you (your password, or signing in with Google again) and type your email address. Your account, the trees you own with their people, relationships and photos, your profile and profile picture, and your access to trees shared with you are deleted straight away; a person you marked as yourself in someone else's tree stays in that tree but is no longer linked to you. You are signed out and a confirmation goes to your address. If a tree you own is shared, you also type a confirmation naming how many trees and people it affects, and those people are not told; otherwise remove its collaborators and invites first. The service owner's account, and the only administrator's, cannot delete themselves this way.
  • Copy: Download your data under Account settings, even before accepting changed Terms, gives you a zip of JSON files and photos: your account (email address, whether it is confirmed and uses sign-in codes, when you signed up and last signed in, any idle-deletion notice dates, which Terms version you accepted and when, whether you are under 18 and when that was checked, your sign-in methods and roles), your profile picture and preferences, every tree you own in full (its people with their photos, relationships, visibility settings, collaborators' email addresses and roles, and invites including the addresses you invited), the trees shared with you with your role and when it was granted, and the people linked to you in other people's trees. It leaves out passwords, tokens, invite link codes, account ids, the contents of trees other people own, and photos of you in their trees (privacy@goom.life can send you a copy of those photos). The tree, person and relationship ids it includes (currentFamilyTreeId, fromMemberId, id, memberId, toMemberId, treeId) are internal numbers used only to link records within the file. The file is built in a temporary file on the server that is deleted as soon as the download ends; up to 3 downloads an hour.
  • For anything else, or if you cannot use Account settings, email privacy@goom.life.
  • We reply to every request within 30 days. If you are unhappy with the answer, you can complain to the data protection authority where you live.

Children

Children under 13 cannot have their own account. Sign-up asks for a date of birth without saying what age is needed; if it is refused, that browser cannot try again for 24 hours. Anyone aged 13 to 17 needs a parent's or guardian's permission to use the app.

Trees often include children. Anyone under 18 who is alive shows to everyone except the tree's owner without dates, nickname, gender, pronouns or photo, whatever the owner's other settings. A parent or guardian can ask for a child's entry or account to be corrected or removed by emailing privacy@goom.life.

Security

  • Passwords are stored only as salted hashes, and password sign-ins need a code emailed to the account's address.
  • After 5 wrong passwords or sign-in codes in a row, the account is locked for 15 minutes.
  • The site is served over HTTPS.
  • Photos are private and served only through the app to people with access to the tree.

Changes to this page

When this page changes, the effective date at the top changes with it.