Privacy Policy
Last updated: July 11, 2026
Threadmark analyzes your genealogy data (GEDCOM files) against the Genealogical Proof Standard. It is a read-only analysis tool — it never edits your tree. This policy explains what we collect, who we share it with, and how long we keep it.
What we collect
- Your GEDCOM file — processed in memory to run the scan. For large files we briefly store it during the scan and request deletion as soon as the scan finishes. Deletion retries automatically after transient failures. We do not keep a copy.
- Tree details used by AI — only when you use an AI feature. Depending on the feature, this can include names, dates, places, spouse names, family labels, and issue evidence for relevant people (up to 32 for Roadmap). See “Who we share it with” below.
- IP address and browser type — standard hosting and abuse-prevention data, plus page analytics on our informational pages only.
- Place names — only when you view the Places map, sent to our geocoding provider to look up coordinates.
Who we share it with (sub-processors)
| Vendor | What they receive | Purpose |
|---|---|---|
| OpenAI (US) | Names, dates, places, spouse names, family labels, and issue evidence needed for the AI feature you choose. | AI analysis only. OpenAI does not use API data to train its models by default and may retain API content for up to 30 days for abuse monitoring. |
| Vercel (US) | Hosting traffic, page analytics on informational pages only (not the upload page or results workspace), and brief GEDCOM storage during scans. | Hosting and performance monitoring. |
| Neon (US) | Your account record from Google sign-in. | Database hosting for signed-in accounts. |
| OpenStreetMap Foundation / Nominatim (UK) | Place names when you view the Places map. | Geocoding (turning place names into map coordinates). |
Before the first AI request in a browser, Threadmark shows a data-sharing notice and asks for consent. Roadmap removes details for likely-living relatives; Conflict Resolver may include names needed for the selected task. AI features are available on paid plans only, so Free users’ data is never sent to OpenAI.
How long we keep it
- Your GEDCOM file: not kept — deletion is requested when the scan finishes, with automatic retries after transient failures.
- AI responses: cached on our servers for up to 30 days so repeat clicks don’t burn your daily quota.
- OpenAI API content: may be retained by OpenAI for up to 30 days for abuse monitoring.
- Session cookie: 30 days (remembers your plan).
- Browser storage (scan history, theme preference): stays on your device until you clear it.
Your rights
To remove browser-held Threadmark data, clear your cookies and local storage. Threadmark does not host share links or persist scan artifacts for sharing. Cached AI responses expire within 30 days. OpenAI abuse-monitoring records age out under OpenAI’s retention terms and cannot currently be deleted through Threadmark. A self-serve Threadmark cache-delete option is planned.
How to contact us
Questions about your data or this policy? Email privacy@threadmarkapp.com.