FTDNA Public/Private Settings - Some Notes
New Information as of February 2003
Assuming all parties signed a release form, if a participant in the project matches you, you will get an email from FTDNA (and the information will also appear on your private page at FTDNA). However, if you want to know if you match someone who tested privately (or in another surname project) you must go to your private page and change the code to public. The only problem with that is, if you have a "common" haplotype - you may get misleading matches - and hence not want to go to the public code. But - in my opinion - right now it seems we all would want to be public. (See my Questions to FTDNA and answers below.)
______________________________________
The following extracted from:
Facts & Genes from Family Tree DNA
January 31, 2003 Volume 2, Issue 1
http://www.familytreedna.com/facts_genes.asp
Managing a Surname Project: Public or Private
==============================================
The information below only applies to those who are members of a Surname Project. If you are a member of a Surname Project, understanding the Public/Private setting is important.
A Surname Project can be set as either Public or Private, although by default they begin as Private. A member can override this Group setting, and the individual controls whether they are as Public or Private. [This] is accomplished on the individual [member's] personal page.
All members added to a Surname Project are automatically set as Private when the DNA test kit order is entered. The member can be changed to Public after their DNA test is returned. Members who want to be Public will need to change their Public/Private setting after their DNA test kit is returned.
The Public/Private flag is unrelated to [one's] signing the Family Tree DNA [consent]. This is designed as a dual level privacy option for group members
The Public/Private setting effects how Y DNA Matches works for searching the Family Tree DNA customer database for matches. When a member is set as Private, the Find Y DNA Matches command only searches in the Surname Project for matches. The member is also invisible when others outside the Surname Project Search for Y DNA Matches. A Private member is included in the Recent Ethnic Origins (REO) search.
The Private setting is very beneficial for those with a common Haplotype, who get many matches with other surnames when they are set as Public. By changing their setting to Private, the Find Y DNA Matches command will only search in their Surname Project for matches.
The Public/Private setting also effects whether you get email notification of new matches. If you are set as Private, you will only receive email notification of matches within your Surname Project. A member with a Public setting will receive notice of all matches to those participants set as Public.
To check or change your Public/Private setting:
- go to Update Contact Information on your Personal Page.
- Look below the email address at the line that reads:
"Restrict Match notifications to your surname Project"
If there is a check mark in the box, you are set as Private. If there is no check mark, you are set as Public.
If you are not in a Surname Project, the line for Public/Private will not appear on your Update Contact Information page.
With the implementation of the ability for a member to set their Public/Private status, all members of all Surname Projects were set to Private. Therefore, each participant should now make a decision concerning their setting and change their status to Public, if so desired.
===============================================================
REPRINT POLICY:
We encourage the circulation of "Facts & Genes" by newsletters and lists providing that you credit the author, include our copyright information (Copyright 2003, Family Tree DNA), and cite "Facts & Genes" (http://www.familytreeDNA.com/facts_genes.asp) as the source.
**************************
Note from GKB: Related information
Match requires surname (or a least close locale) to indicate MRCA (can have perfect matches with random people) - see FTDNA's newsletter: September 26, 2002 Volume 1, Issue 3 - http://www.familytreedna.com/facts_genes.asp
**************************
GKB Questions and FTDNA Answers
1. Just read recent Facts & Genes. Mentions "common haplotype" here and there. How do we know if we have a common or uncommon
haplotype (e.g., to make decision about removing Private flag)?
To determine if you have a common Haplotype, set a participant to Public, then do the Find command. If you match others at 12 markers with different surnames, you have a common Haplotype, and want to have your participants set as Private. This would apply for a 12/12, 11/12
and 10/12 match.
2. Are you saying this only applies to 12 marker test comparisons - that the "common" haplotype is a moot point on 25 marker comparisons?
Or put another way, all participants with 25 markers - might as well be on Public (not private)? Is that correct?
Until we have as many people tested 25 marker tests as 12 marker tests we will not really be able to compare the frequency differences,
although as we are showing matches of 24 and 25/25 that will tend to beef up the number of matches, even though the last 13 are more volatile then the first 12.
3. Recent info in F & G indicates if surname project participant changes to public code they will learn of other matches in FTDNA (matches to others not in that surname project - private tests, other surname projects, etc.). The below questions assume all persons signed the release form:
a. Will those just suddenly show up on the participant's private page at FTDNA if/when they change code to public?
Yes, immediately after they change their status
b. Will his results also show up now on the other person's page (e.g., the private tester, or whatever)?
Yes, exactly the same way.
c. I assume that no automatic emails will be sent to each party for any matches prior to the code change?
That is correct.
d. I assume automatic emails would be sent after the code change for any future matches to others not in the project (as well as matches to those in
the project)?
Also correct!