Privacy

Last updated 6 October 2026. TempleKit is in a free beta and has no accounts yet.

The short version

• Your card PDF is sent to our server only to read it and build your printed pages. It isn't stored there, and it isn't used for anything else.
• Your work (labels, stories, how to say each name, printer settings, and any family tree you build in our tools) is saved in this browser on this device. It is not on our server. Clearing your browser data, or pressing “Start over”, erases it.
• The genealogy tools (relationship calculator, family tree, charts, date tools, Soundex) run in your browser. A GEDCOM file you open is read on your device and is never uploaded.
• Names, places, dates and stories are never sent to analytics.
• TempleKit never signs in to FamilySearch or Ancestry, never reserves names, never collects records from those sites, and never asks for your FamilySearch, Ancestry or Church account password.

What our server sees, and for how long

• Card pages. One page at a time goes to our card engine to be read, stamped and checked, then comes straight back to you. It's held in memory for that request only.
• The QR check. Before any stamped page is offered for download, our server checks that every QR code on it still scans, and scans to the number printed on its own card. This happens in the same request, in memory. Nothing is kept.
• How to say each name. To print a pronunciation line under each name, the individual name words on your cards (for example “Roelof” and “Fleer”) and the countries they came from are sent to our server. They're looked up in our own word list first. Dates, full places, relationships and anything about you are not sent.
• Request logs. Our host, Vercel, keeps standard request logs (time, page, status, approximate location from the IP address) for a short time to keep the service secure and working. Our own code doesn't log card contents.

Services we use

• Vercel hosts the site and runs the card engine.
• OpenStreetMap Nominatim turns a place printed on a card (for example “Follega, Friesland, Netherlands”) into a map location for the card back. Only the place text is sent, never a name.
• Anthropic (Claude), only when AI help is turned on: (1) to draft a card back, it receives the facts printed on that one card (names, the event, the date and place, the parents printed on the card); (2) to respell a name we don't have in our word list, it receives only that name word and the country it came from. Anthropic doesn't use data sent through its commercial API to train its models. You can edit or delete anything it suggests before you print.
• Analytics: Vercel Analytics and Speed Insights today, and, when we turn them on, Google Analytics and PostHog. They see page visits and counts (like “50 cards uploaded”), never card contents, names or tree data. PostHog session replays, if we use them, mask anything marked as family data.

Living people

FamilySearch only prints family name cards for deceased people, but your own name, city and phone or email go on the cards you print. That stays in your browser and in the PDF you download. A family tree you build in our tools may include living relatives. It stays in your browser; if you export it as a GEDCOM to share, we suggest leaving living people out or marking them private first.

Children

TempleKit isn't directed to children under 13, and we don't knowingly collect information from them.

Your choices

• Turn off “Print how to say each name” on the Fronts step and no name words are sent for it.
• Press “Start over” in the app, or clear this site's data in your browser, to erase everything TempleKit saved on your device.
• When accounts arrive, you'll choose what to save to your account, and you'll be able to delete it. We'll update this page first.

Questions

Email team@templekit.com.