Home› Welcome to the FamilySearch Community!› Suggest an Idea

A clearly deceased person is marked as private…

Sears, Rafaien
Sears, Rafaien ✭
May 1 edited May 1 in Suggest an Idea

This is more of a report of a problem, but I noticed there were at least a couple people I worked on who are clearly deceased, but are still marked as private. One is Louis Nicholas Mavredes (GKJC-TYX). How should this be resolved?

This problem was found on the mobile iOS FamilyTree app.

Louis_N_Mavredes_Confidential_Person_Error.png


Tagged:
  • Family Tree
1
1
Up Down
1 votes

Active · Last Updated May 1

Comments

  • Sears, Rafaien
    Sears, Rafaien ✭
    May 1 edited May 1

    Well, I’ve gone and looked a little harder at the questions page and found several people had the same problem. Should I still keep this page up? (I don’t know if I can take it down, though.)

    0
  • Stephanie Spencer Booth
    Stephanie Spencer Booth ✭✭
    May 1

    I have seen this with every individual I have added that was born in the Middle East, including Egypt, Iran, Turkey and others. I found an article in the help center that says the person may be marked private if the living relatives might be in danger if the public knows they are related to someone from that country. I don't know what militant groups might be using FamilySearch to stalk living people, but it seems like there needs to be a better way to protect the living and be able to share your ancestry.

    When you use FamilySearch, it seems obvious that you are trying to share your family tree with others. If all of your ancestors are marked Private, then you aren't sharing with anyone.

    I agree that this is a problem!

    1
  • Julia Szent-Györgyi
    Julia Szent-Györgyi ✭✭✭✭✭
    May 1

    Of the options in that yellow banner, it's the second one that applies. The problem is the birthplace: Turkey is apparently on the list of places that the confidentiality bot finds objectionable.

    1
  • Sears, Rafaien
    Sears, Rafaien ✭
    May 1

    I see the problem. I’m not a direct-line descendant of this individual, so this problem probably came up while I was attaching record hints and adding people to the tree.

    Thank you both for the insightful answers!

    0
Clear
No Groups Found

Categories

  • 24.7K All Categories
  • 25.8K FamilySearch Help
  • 130 Get Involved
  • 2.8K General Questions
  • 458 FamilySearch Center
  • 485 FamilySearch Account
  • 4.8K Family Tree
  • 3.7K Search
  • 4.9K Indexing
  • 686 Memories
  • 338 Other Languages
  • 34 Community News
  • 6.9K Suggest an Idea
  • Groups