Skip to content
Genealogy Researcher

Privacy policy

On this page

Last updated: Oct 12, 2026

This policy explains what personal data Genealogy Researcher processes, why, where it is stored, who receives it and how you can control it. It covers the website at genealogy.junowoz.com and the connection that lets ChatGPT, Claude and other AI assistants use your account.

Who is responsible

The controller is Juan Gouvêa, operating as Juno Woz in Brazil (“we”). Contact for any question or request: inbox@junowoz.com.

What we process

Your account

  • Your email address, the display name if you set one, your language and the dates of creation and last sign-in.
  • Sign-in codes. We store only a hash of each code, with the email address it was requested for. A code expires after 10 minutes and allows 5 attempts. We delete the record of a code within 48 hours.
  • Your browser session. We store only a hash of the session token. The session lasts 30 days.
  • We do not use passwords.

Your AI assistant connection

  • The apps you approved (for example ChatGPT or Claude), the permission you gave and the date.
  • The access and refresh tokens that let the app act for you. Access tokens last 1 hour. Refresh tokens last up to 60 days or until you revoke them.

Your family tree files

  • The GEDCOM file you upload, stored as you sent it.
  • The data we read from it: people, families, events, places, notes, sources and citations.
  • A tree can contain data about living people and sensitive data, such as religion, ordinance records, illness or cause of death, adoption and illegitimacy. See “Other people and sensitive data” below.

Your research workspace

  • Projects, their members and roles, and the trees added to each project.
  • Invite links. We store only a hash of the link token.
  • Research entries that you or your assistant save: questions, plans, search logs, notes, hypotheses, tasks, evidence, transcriptions, citations and conclusions.
  • An activity history of project changes: who did what, and when.

Technical data

  • Cloudflare processes the IP address and the details of each request to deliver and protect the service. Its technical request logs are kept for 7 days.
  • Our own log entries contain only an event name, a code and a status. They do not contain emails, tokens, file content or names of people.
  • Short-lived counters limit how often a person can sign in or call the service. They use a hash of the email address or the IP address.
  • When enabled, Cloudflare Web Analytics counts visits to the public pages. It sets no cookies and does not follow people across sites.
  • When enabled, Cloudflare Turnstile checks on the sign-in page that a request comes from a person before we send a code. Cloudflare processes technical data from your browser for that check.

Cookies

The service sets only functional cookies: the sign-in session cookie (30 days); a short-lived cookie (30 minutes) that ties a sign-in code to the browser that asked for it; a language cookie that remembers pt-BR or English (1 year, set only when you use the language switch); a short-lived cookie (10 minutes) that ties an app approval page to your browser; and, only if you connect FamilySearch, a short-lived cookie that protects that connection step. None is used for advertising or tracking.

Why we process it

  • To create your account, sign you in and run the service you asked for. This includes answering your assistant when it calls our tools. The legal basis is the contract with you (LGPD art. 7, V; GDPR art. 6(1)(b)).
  • To keep the service secure and prevent abuse. The legal basis is our legitimate interest (LGPD art. 7, IX; GDPR art. 6(1)(f)).
  • To meet legal obligations (LGPD art. 7, II; GDPR art. 6(1)(c)).
  • For sensitive data in the files you upload, the legal basis is your consent, which you give when you upload the file and can withdraw by deleting the data (LGPD art. 11, I; GDPR art. 9(2)(a)).

We do not sell personal data. We do not show advertising. We do not use your data to train AI models, and we do not call any AI model ourselves.

Other people and sensitive data

A family tree describes people other than you. You decide what to upload. You are responsible for having the right to upload it and to share it with the people you invite. For data about other people that you upload, we process it only to run the service for you.

When we read a GEDCOM file, we mark people who are probably living, using their dates. This mark is an estimate and can be wrong. Treat every person with recent dates as living.

If you appear in someone else’s tree and want your data removed, write to inbox@junowoz.com. We will act on a request that identifies the person and the tree.

Who receives your data

  • Cloudflare provides hosting, the database, file storage, key storage, email delivery and network protection.
  • Your AI assistant provider. When you use a tool through ChatGPT (OpenAI) or Claude (Anthropic), the tool results become part of your conversation with that provider. Its terms and privacy policy apply to that conversation. We do not control it.
  • Open sources. When you ask the assistant to search outside records, the search terms (names, places and years) go to the source: WikiTree, the Internet Archive, the Library of Congress (Chronicling America), Open Archives and Wikidata. Each source has its own privacy policy. Links to other sites, such as FamilySearch, Find a Grave or national archives, open in your browser, and your visit is between you and that site.
  • People you invite to a project. Members can read the trees and entries of the project according to their role.
  • Authorities, when the law requires it.

Where data is stored

Data is stored with Cloudflare in the Cloudflare Workers platform: a D1 database, R2 file storage and KV key storage. Cloudflare can process data in several countries, including outside Brazil and the European Economic Area. For international transfers we rely on the safeguards that the LGPD and the GDPR allow.

How long we keep data

  • Sign-in codes expire after 10 minutes. We delete the record of a code, with the email address it was requested for, within 48 hours, even if you never sign in. Sessions end after 30 days. Invite links end when they expire or reach their use limit.
  • Trees, files, projects and entries stay until you delete them or delete your account.
  • You can delete a tree in the account area or by asking your assistant to use the delete tool. This removes the parsed data and the original file.
  • You can delete your account in the account area. This removes your profile, your trees and files, the projects you own and their entries, and your assistant connections.
  • Entries you wrote in a project that belongs to another person stay in that project. Delete them first if you want them gone, or ask the owner.
  • The database keeps a point-in-time history for 30 days for disaster recovery. Deleted data can remain in that history for up to 30 days. If we restore the database from that history, we delete again what you had already asked us to delete. Uploaded files are removed when you delete them. We keep no longer-term copies of uploaded files.

Your rights

Under the LGPD (art. 18) and, where it applies, the GDPR, you can ask us to confirm that we process your data, to give you access, to correct it, to anonymize, block or delete it, to give you a copy in a portable format, to tell you with whom we share it, and to withdraw consent. You can also object to processing based on legitimate interest.

  • Self-service: in the account area, export your workspace data as JSON, download your original GEDCOM files, disconnect apps, and delete trees and your account.
  • By email: write to inbox@junowoz.com. We answer within 15 days.
  • Complaints: in Brazil, to the data protection authority (ANPD). In the European Union, to your national authority.

Children

The service is for people who are at least 16 years old. We do not knowingly collect data from younger people. If you think a child has an account, write to inbox@junowoz.com and we will delete it.

Security

All traffic uses HTTPS. Sign-in codes, sessions and invite tokens are stored as hashes. Each account can read only its own trees and the trees shared with it through a project. Cloudflare encrypts stored data at rest. No system is perfectly secure. To report a vulnerability, use GitHub security advisories and do not include personal data.

FamilySearch

Genealogy Researcher has no connection to FamilySearch and does not receive FamilySearch data. FamilySearch support is planned. It stays off until FamilySearch gives written permission. If we ever turn it on, we will update this policy and ask for your permission before you connect an account.

Changes

When this policy changes, we update the date above. For a material change we also notify account holders by email.

Contact

inbox@junowoz.com. For terms of use see the terms. For help see the support page.