Privacy Policy
Effective November 2, 2026
Family Tree Explorer (“we”, “the site”) is run by Mitchell United, LLC. This page explains what the site does with your information. Questions and requests: use the contact form, or write to support (at) explorefamilytree (dot) com.
The short version
- You can use the site without an account. A GEDCOM file you open is read in your browser and is not sent to us.
- If you make an account and choose “Save to my account”, that file is stored on our servers, encrypted.
- The DNA views read a raw DNA file you choose, in your browser only. The file is not sent to us, not saved to your account and not kept: reloading the page forgets it.
- The AI Query view works only if you add your own API key from Claude, ChatGPT or Gemini. Your questions and what it looks up in your tree are then sent from your browser to that provider, not through us, and, only if you choose it and confirm, so is a compact copy of your tree, or of the part of it each question is about. Your key is held in memory only, and people who may be living are left out unless you choose otherwise.
- With an account, your place definitions, dismissed data-quality issues and favorite views follow you to every device, encrypted in the same way.
- If you buy the unlock or poster printing, Stripe takes the payment. We keep a record of what you bought, never your card number.
- Posters and their previews are drawn in your browser from your file. They are not sent to us, and the poster files you make are not kept by us.
- We count, for each view, how many posters are made, how many times a poster file is asked for without poster printing, and how many files are made. Not who, and not what was in them.
- We count how often each view is opened. Without an account that is a daily total, tied to no one. With an account, we also keep which views you open, how many times and when.
- If you write to us through the contact form, the message is emailed to us and kept in our mailbox. It is not stored by the site.
- We do not sell your information, and we do not run advertising. Cloudflare’s Web Analytics counts visits to the site’s pages, without cookies.
- If you share a file with a link, an encrypted copy is kept for 14 days. The key is only in the link, which we never receive, so we cannot read the copy.
- You can delete your account, and your saved files with it, whenever you like.
Without an account
Your GEDCOM file is opened and drawn entirely in your browser. A copy of the parsed tree is kept in your browser’s own storage (IndexedDB) so you do not have to upload it again, and the “Clear data” button removes it. Your color-mode choice, your choice of kilometers or miles and which home-page sections you folded are kept in your browser’s local storage, and so are the place definitions you enter, the data-quality issues you dismiss and the views you star. None of this is sent to us unless you sign in, as described below.
A raw DNA file, such as a download from AncestryDNA or 23andMe, can be opened in the views in the DNA and Genetics section. It is read and analyzed entirely in your browser and held in memory only: it is not sent to us, not stored in your browser’s storage, and not saved to an account. Reloading the page, choosing “Remove it from this page”, signing out or clearing your data forgets it. The comparison and family views open several such files at once (up to ten), and hold every one the same way.
When you open a view, the site adds one to a daily count for that view. The count is kept without your name, your address on the network, a cookie or anything about your file, so it cannot be traced to you.
The same is done for posters: when a poster is made on screen, when someone without poster printing asks for a poster file, and when a poster file is made, the site adds one to a daily count for that view and that step. These counts are kept in the same way, tied to no one, whether or not you are signed in, and hold nothing from your file or the poster. They are for seeing how far people get with posters.
Cloudflare, which hosts the site, also measures visits to its pages with Cloudflare Web Analytics. When a page opens, a small script from Cloudflare records the address of the page, where the visitor came from, the type of browser and device, the country, and how quickly the page loaded. Cloudflare describes this as working without cookies and without following visitors from one site to another, and we see only totals, not what any one visitor did. It runs whether or not you are signed in, and it is separate from the counts of views opened described above.
If something goes wrong, the site keeps a short technical note of what failed and where, with the time, for up to thirty days, so that it can be fixed. It names no one and contains nothing from your file.
With an account
We collect, and store on our servers:
- Account details. Your name and email address. If you sign up with a password, a salted hash of it (never the password itself). If you sign in with Google, your Google account identifier, name, email address and profile picture address, which Google provides to us. We use Google only to sign you in.
- Sign-in records. Each session records when it was created, and the IP address and browser description it came from. Request counts per IP address are kept briefly to slow down password guessing.
- Purchase records. If you buy the unlock or poster printing: what you bought, the amount, the date, whether it was refunded, and the reference numbers Stripe gives the payment, and any promotion code you used and how much it took off. Not your card number, which goes to Stripe and never to us.
- Settings that follow your account. The place definitions you have entered (the text of a place as it appears in your file, and how you read it), the data-quality issues you have dismissed (listed by the name of the file they came from), and your favorite views. They are encrypted before they are stored, and they are the same on every device you sign in on.
- Views opened. Which views you have opened, how many times, and when you first and last opened each. This is so we can see which views are used. It does not include anything from your file.
- Saved files. Only if you choose to save one. The file’s contents and its name are encrypted before they are stored. Its size and the time it was saved are stored unencrypted.
The site sets one cookie, a sign-in session cookie that is necessary for the account to work. We do not use cookies to track you. The payment form, which Stripe supplies, may set cookies of its own (see below).
The site’s operator, and anyone the operator makes an administrator, can see this information for every account on an administration page, and can give an account access to the paid views or poster printing or take it away, or make another account an administrator. Each such change is logged, naming the account it concerned.
Sharing a file with a link
If you are signed in you can share the file you have open by making a link. Your browser encrypts the file, and its name, with a new key that is put into the link and nowhere else, and sends us only the encrypted copy. The part of a link after the “#” is never sent to a website by your browser, so we never receive the key and cannot read the copy, even if asked to. We keep, for each link: the encrypted copy; the name of the file, sealed with your account’s own key like the names of saved files, so that your list of links can show it; its size; which account made it; when it was made and when it ends, and how many times it has been opened. We do not keep who opened it. A link works for 14 days; after that, or when you stop sharing it, or when you delete your account, the copy and the record are removed. Anyone who has the whole link can open the file, so give it only to people you trust. A GEDCOM file often includes living people, and you are responsible for sharing it only where you may. Because the key exists only in the link, we cannot show a link again, or recover one that is lost. If you use “Email the link”, your own email program writes the message: we do not send it, and we do not see the address you send it to.
How saved files are protected
Each account has its own encryption key, and that key is itself encrypted with a master key held as a secret in our hosting account. Files are stored encrypted and travel over HTTPS. This protects your files if the storage were ever copied or leaked.
Be aware: this is encryption at rest, not end-to-end encryption. Our server decrypts a file when you open it, so whoever operates the service could technically read saved files. We do not look at the contents of saved files, except as needed to keep the service running, to investigate abuse or a security problem, or when the law requires it. If that is not acceptable for a file, do not save it to an account; you can still explore it without one. The same holds for the settings that follow your account: they are encrypted in storage, and could be read in the same way.
Place definitions and dismissed issues name places and files from your tree, so if that matters to you, do not sign in on a computer you do not trust.
Posters
Many views can make a poster of what they show. The poster and its preview are drawn in your browser from the file you have open, and nothing about them is sent to us: not the file, not the people in it, not the poster. The preview is a small picture shown on the page; with poster printing the PDF, SVG or PNG is written in your browser too, and saved to your own device. To write those files your browser fetches a program from us, and we check that your account has poster printing before we send it, in the same way as for the paid views. Poster files can contain names, dates and places of people who are alive, so take care where you share or display them.
AI Query
The AI Query view answers questions about your tree using an AI model that you connect with your own API key from Anthropic (Claude), OpenAI (ChatGPT) or Google (Gemini). It does nothing until you add a key. The key is typed into the page and held in memory only: it is not sent to us, not stored in your browser’s storage and not saved to an account, and reloading the page forgets it. By default the model does not receive your file. When you ask a question, the view sends the question, and then the results of the lookups the model chooses to run on your file in your browser, such as a list of people and their dates, straight from your browser to the provider you chose. If you choose “My family line” or “Whole tree” in the view, and confirm after seeing its size, it also sends a compact text copy of those people with every question: their names, dates, places and family links, but not the file itself, notes or sources. If you choose “Relevant part” instead, each question sends only the people it is about, picked in your browser from the names, places and years in the question and from the last answer, with their parents, children, spouses and siblings, in the same compact form and up to a size you choose. Nothing is sent in either way unless you confirm it, and changing the choice asks again. They do not pass through our servers, and we do not receive or keep your questions, the answers or the results. By default, anyone who may be alive (with no death recorded and born within the last 110 years, or with no dates to tell) is sent as “Living person” and an id only, with no name, dates or places, and their name is filled in on your screen when the answer is shown. You can turn this off in the view, and then names, dates and places of living people can be sent. What the provider does with what it receives, and what it charges you, are set by your agreement with it, such as Anthropic’s, OpenAI’s or Google’s privacy policy. Only use the view with a tree you have the right to share with that provider.
Contacting us
The contact form asks for your email address, a message and what it is about, and your name if you wish to give it. These are emailed to us through our email service and kept in our mailbox so that we can reply and keep a record of what was agreed, such as a refund. They are not written to the site’s database, and the message is not recorded in the site’s logs. Do not put a GEDCOM file, or the names of living people, in a message. To have a message deleted from our mailbox, write to us and ask.
Information about other people
A GEDCOM file often contains names, dates and places of people who are alive. Only save a file you have the right to keep and process. We do not use the people in your files for anything other than showing them back to you.
Who else handles information
- Cloudflare hosts the site and stores account data and encrypted files. It sees ordinary web request data, such as IP addresses, and measures visits with Web Analytics, as described above. It also runs Turnstile, the check on the contact form that tells a person from a program: the form loads a script from Cloudflare, which sees details of your browser and device to make that check, under its own privacy policy.
- Google, if you choose to sign in with Google.
- Anthropic, OpenAI or Google, only if you add your own key to the AI Query view and ask a question. The view then sends them your question and the results of lookups on your tree, directly from your browser, as described under AI Query.
- Stripe takes payments, if you buy the unlock or poster printing. The payment form is drawn by code your browser loads from Stripe only when you open it, so Stripe sees your card details, your email address and details of your browser and device, which it uses to take the payment and prevent fraud, under its own privacy policy. We receive a record of the payment, not the card details.
- An email service sends the messages for verifying your address and resetting your password. It receives your email address and the message.
We do not sell or rent personal information, and we do not share it for advertising. We may disclose information if the law requires it.
Keeping and deleting
Account details and saved files stay until you delete them. Delete a file, or your whole account, from the account page. Deleting your account removes your account details, your purchase records, your record of views opened, your settings that follow your account, your saved files, your share links and the encrypted copies behind them, and your encryption key, which also ends what you bought. The daily counts keep no trace of you, and the log of an administrator’s changes keeps what was done but no longer your email address. Stripe keeps its own record of a payment for as long as the law and its own rules require. Backups kept by our hosting provider may hold deleted records for a limited time before they expire.
Your rights
Depending on where you live, you may have the right to ask what we hold about you, to correct it, to have it deleted, or to take a copy. Most of this you can do yourself from the account page; for the rest, use the contact form (choose “A privacy request”) or write to support (at) explorefamilytree (dot) com. We will not treat you differently for asking.
Children
The site is not meant for children under 13, and we do not knowingly collect their information. Contact us if you think a child has made an account.
Where information is processed
Cloudflare runs its network worldwide, and Stripe processes payments in the United States and elsewhere, so your information may be processed in countries other than your own.
Changes
If we add advertising, analytics other than Cloudflare’s or other paid products, or change how files are stored, we will update this page before it takes effect and change the date at the top.