Privacy notice

Who to contact

Privacy questions, and requests to hide or remove a person, go to [email protected].

What Amora Tree stores

• Names, nicknames, gender, and whether someone is marked living or deceased
• Birth and death dates and places, including partial dates such as a year alone
• Family links: parents, partners, and children
• Notes and any extra details the owner adds
• Photos
• Phone, email, and address
• A history of edits, which can include the earlier values
• A sign-in cookie

Who can see it

Anyone with the shared password can see the whole tree, including phone, email, and address. This version has no separate accounts.

Phone, email, address, and any detail marked Personal are labelled so that later members of the tree, and other trees, will not receive them. That label is not a second password today.

AI

Amora Tree is not connected to an AI service of its own. An app you connect can read the tree, and can change it only after you tick Allow changes. What an app can do follows what you can do. If you can only look, the app can only look. That includes life events and a city or village of residence. The map shows cities and villages. A street address is never sent out to be located and is never changed. Merging two people is one of those changes and can be undone. You choose who stays and which differing value to keep or drop. Undo puts both people and their links back. Each change is shown before it is saved. A citation is optional and never required. A note can be hidden from AI even when the person is visible. Personal details already in the tree are never sent to an AI. update_person does not change them. A merge does not move them into a view that is not the owner's. An import can store phone, email, address, and other private details the user chose to send in, and those values are not read back. Contact details you send through an AI are shared with that AI provider. Check your plan's data protection. A connected app can ask for a GEDCOM file for someone else. Personal details stay out of that file. Living people and children are limited to a name, family links, and a birth year. A full export stays in Settings.

Photos

A photo is stored for this tree outside the database once it has been copied. A new photo has its location data removed before it is saved. A photo already on the person stays in the database until that copy has been checked. Deleting a photo here does not change a photo in another tree.

Deleting someone

Deleting a person removes them from the tree. The history of edits can still show the earlier values. Write to [email protected] if a person should be hidden or removed from history and from backups as well.

Backups

Each night the server keeps an encrypted copy for 14 days. When off-site storage is set up, another encrypted copy is kept for 30 days and then deleted. A backup file already saved on a computer is not changed. There is no restore button in the app. Times are Australia/Sydney.

Where it is kept

The tree is stored in a database hosted by Railway. In this version the person who runs Amora Tree can read that database. Amora Tree does not sell the data. No advertising network, SMS provider, or email provider receives it.

Errors and request logs

When error tracking is turned on, a crash report is sent to an error-tracking service. Names, phone numbers, email addresses, addresses, cookies, and anything typed into a page are removed first. When error tracking is not turned on, that report is not sent anywhere.

The server writes a line for each request with the route, the status code, how long it took, and whether someone was signed in. That line does not include names or other details from the tree.

Cookies

One cookie, named kinfolk_session, keeps you signed in on this device for up to 90 days, and longer if you keep using the tree. It is not used to track you across other sites. Logging out ends the session.

Children

The tree may include children. This version has no accounts for children. An adult keeps those records.