case: (Default)
Case ([personal profile] case) wrote in [community profile] fandomsecrets2023-04-29 04:52 pm

[ SECRET POST #5958 ]


⌈ Secret Post #5958 ⌋

Warning: Some secrets are NOT worksafe and may contain SPOILERS.


01.



__________________________________________________



02.



__________________________________________________



03.
[Succession, Roman Roy]



__________________________________________________



04.
[minecraft youtube?]



__________________________________________________



05.
[Green Hell]



__________________________________________________



06.
[Lost Ruins]
























Notes:

Secrets Left to Post: 02 pages, 30 secrets from Secret Submission Post #852.
Secrets Not Posted: [ 0 - broken links ], [ 0 - not!secrets ], [ 0 - not!fandom ], [ 0 - too big ], [ 0 - repeat ].
Current Secret Submissions Post: here.
Suggestions, comments, and concerns should go here.

(Anonymous) 2023-04-30 02:51 am (UTC)(link)
There is DOJ policy - police can't quietly upload a fake profile to a genealogy website without first identifying themselves. And the site itself must have informed its users that law enforcement agencies may search their data. It also bars police from using a suspect's DNA profile to look for genes related to disease risks or psychological traits. Another provision attempts to limit situations in which police secretly take a DNA sample from a suspect's relative—from a discarded cup or tissue, for example—to help home in on a suspect. The policy says the person must give their informed consent unless police have obtained a search warrant. But that only applies to DOJ and federally funded agencies.

Some sites forbid law enforcement use (Ancestry, 23andMe, and MyHeritage) and some now have clauses in their agreements or opt-in/opt-out consent (GEDmatch, FamilyTreeDNA).