Privacy Policy

viewfore is built around one promise: we never keep a searchable database of the people in your family tree. This page explains what that means, what little we do store, and the choices you control.

The short version

• Upload a GEDCOM file and we read it to draw your map and charts, then discard it.
• We never keep a searchable database of the people in your tree.
• The only trees we store are ones you choose to save or share, and only as your original file on disk.
• Viewers of a shared tree never sign in and never pay.
• Places are matched using our own copy of public geographic data. We do not send your tree to any outside geocoding service.

Your uploaded family tree

When you upload a GEDCOM file, our server reads it during that request to work out places, dates, names, and relationships. It streams the result back to your browser and then discards the file. We do not copy the people or places from your tree into a searchable database.

There is one exception, and it only happens when you ask for it. If you have an account and you Save a tree (private) or Share a tree (public link or embed), we store your original GEDCOM file plus a small settings file on disk so the tree can be loaded again. A private tree can be opened only by you. A public tree is open to anyone with the link. You can delete a saved or shared tree at any time, which removes the stored file.

Accounts

You only need an account to save or share a tree. To create one we store your email address and a securely hashed password. We use your email to sign you in, to send password resets, and to send you notices about your shares or billing. Viewers of a shared tree do not have accounts.

Payments

Viewing your own tree is free. Publishing a public share or embed is paid. Payments are handled by Stripe. We do not see or store your full card details. Stripe processes the payment and acts as the merchant of record, which means Stripe handles applicable sales tax. We store only what we need to know whether a share is paid and current, such as a subscription status and a Stripe customer reference. Stripe's own privacy policy governs the data it collects.

Email

We send account and billing email (for example password resets and renewal notices) through Mailgun. These are service messages tied to your account, not marketing. We do not sell your email address.

Analytics and cookies

We use privacy-friendly, cookieless analytics to understand basic traffic, such as how many people visit a page. It does not use tracking cookies and does not build a profile of you across other sites. Because it does not use cookies for tracking, viewfore does not show a cookie consent banner. We use only the cookies needed to keep you signed in when you have an account.

Maps

The map draws its background tiles from a map tile provider. Loading those images sends your browser's IP address to that provider, the same as loading any image on the web. The place names in your tree are matched to coordinates using our own copy of public geographic data, so your tree itself is not sent to an outside geocoding service.

Living people

When you publish a public share, you can choose to hide living people, which removes their details before the tree is sent to viewers. You are responsible for the data in the trees you choose to share. Please be thoughtful about sharing information on people who are still living.

Data retention

Uploaded files that you do not save are discarded after the request. Saved and shared files stay on disk until you delete them or delete your account. Account and billing records are kept while your account is open and for as long as needed to meet legal and accounting obligations.

Your choices

• Delete any saved or shared tree from your account, which removes the stored file.
• Close your account, which removes your stored trees and account details.
• Ask us a question about your data using the contact details below.

Children

viewfore is not directed at children and is not intended for use by anyone under 13. We do not knowingly collect personal information from children.

Changes

We may update this policy as the product grows. When we make a meaningful change we will update the date at the top of this page.

Contact

Questions about privacy? See our contact page.