GDPR – General Data Protection Regulation – Today’s the day of deliverance – May 25th. GDPR is finally enacted after MONTHS and MONTHS of agony.

Believe me, to those of us in the field, the GD does NOT stand for General Data – it stands for Gol Danged or something much, MUCH stronger.

And speaking of stronger, when I’m really stressed, I do one of three things:

• Buy a bauble commensurate with my level of misery
• Eat dark chocolate
• Drink

In extreme cases, all three.

Actually, if you know me, you know I don’t drink. So item number 3 is really, REALLY a distant 3^rd- – and I’m on my third bottle of wine this week. Good thing I only like muscato wine, ice wine and my rightful Irish legacy, Guinness.

I actually prefer to quilt, because you can stress-quilt wearing baubles and eating chocolate, but if you drink while quilting, your seams will be crooked as a dog’s hind leg.

So, how do you like my new GDPR-size blue bauble flanked by support “staff”?

Yes, it’s been one horrid, awful, miserable, give-me-a-case-of-wine and buy-chocolate-in-bulk six months or so.

Did I mention that it’s been horrid?

I equate dealing with GDPR to giving birth. Not being pregnant, mind you – just the miserable giving birth part – like being in labor for let’s say – 9 months or so. Then delivering a really ugly 100 pound baby that not even a mother can love. Not to mention, I broke my foot during this time too – and no, it wasn’t kicking anyone or anything. AND I was stone cold sober, at a quilt retreat.

For those of you who don’t know, I have 30+ years of technology consulting experience. While I’m “semi-retired,” I’m not entirely retired and I’ve spent the last many months wrestling with this monster known as GDPR. I’m glad to report that my clients are ready, but no one emerged unscarred. I have crooked-seam quilts that I’m claiming are a new art form, am walking like peg-leg the pirate in a very “special” shoe and I’ve gained 5 “chocolate” pounds.

Wonder why I haven’t been doing many DNA reports? Well – now you know!

I have tried, really tried, to maintain a positive outlook – but as the date has approached and I’ve seen how much we are cumulatively losing in the genetic genealogy community – any semblance of a positive perspective has disappeared.

You can read my GDPR articles:

• GDPR – It’s a Train and It’s a Comin’
• Common Sense and GDPR
• World Families Network, Ysearch and Mitosearch Bite the Dust – Thanks So Much GDPR
• GDPR, DNAeXplain and DNA-Explained.com

Making it even worse are the hollow assurances of individuals on social media saying that “everything will be alright” because GDPR is really no big deal, or worse yet that people are “scaremongering.”

So, let me be extremely candid and not sugarcoat anything, because after being in GDPR-labor for several months, I have absolutely not one shred of patience left whatsoever.

What Is This Behemoth and Why Do I Care?

GDPR, was enacted by 28 EU member countries referred to as “states” to regulate information privacy. In and of itself, there is nothing wrong with that, and given the Facebook Cambridge Analytics fiasco and others, it’s much needed.

However, and this is a huge HOWEVER, the way this regulation was written and implemented is not only a massive overreach in regulation, it’s vague, poorly written and almost impossible to comply with. In many cases, there are no standards or definitions included and where there are, they are often draconian, misinformed or outdated in nature.

Furthermore, GDPR is enforced by the unnamed and unknown commissioners of the 28 different “member states” at their sole discretion – including how to leverage fines up to and including 20 million Euro or 4% of a company’s gross worldwide revenue – whichever is MORE.

And no, there is no, absolutely no indication of how that fine will be decided, the steps or processes, or if the penalty will be imposed based on the severity of the infraction or the size of the organization or individual.

How, you wonder, is the process of an investigation set in motion? By a malcontent complaining.

Now that malcontent may well be justified (read about Equifax breach here and here, and the Facebook fiasco here) or the malcontent might be someone who is simply vindictive – or someplace inbetween. Regardless, the person or company on the receiving end of the complaint is then obligated to defend themselves, to PROVE the malcontent is inaccurate or the fines can be levied at the discretion of the unnamed commissioner. Yes, the burden of proof is on the company, not the complainer.

There is no court involved, no appeal process – nothing.

Are these regulators going to make examples of people or companies? Is this a cash grab by the EU member states? Will there be GDPR chasers, like ambulance chasers? Who knows? I don’t, but it’s clearly a huge risk with zero, zip case law yet. Which is exactly why smaller entities are folding.

How does someone even defend themselves? They would hire a lawyer, of course. Know what lawyers that understand GDPR are charging right now?

I can tell you, from direct, personal experience. $1000/per hour, billable by the minute. So if you do manage to avoid the fines, your legal defense will bankrupt you instead. Well, that’s certainly a win!

Now you understand why several small businesses have closed their electronic doors, blogs have disappeared and some sites are blocking all EU IP addresses. Better safe than sorry, but not terribly conducive to genealogical sharing.

Not only that, the GDPR regulation is not just moving forward from May 25^th into the future, it’s retroactive, meaning it applies not just to new sales but to any database worldwide that contains data of an EU resident. The more information, or the more openly they shared, the more difficult GDPR was to implement. Hence, many have closed.

How can you tell if someone is an EU resident from a gmail address, for example? You can’t. So as a business or even a blogger, you are left in the position of not knowing which individuals this regulation might apply to – so if you want to stay in business, or stay safe and NOT attract the notice of the EU commissioners who have the ability to function as GDPR fine-levying Gods – you must comply.

For those of you thinking that GDPR can’t be enforced in the US – maybe, and maybe not. How would we know before lawsuits are filed? And at $1000 an hour, who among us can afford to find out.

Raise your hands please…

Waiting….

Waiting…

I see no hands.

But GDPR created a solution for that too – because non-EU companies that function in Europe MUST appoint a European Representative – who absorbs some of the risk of non-compliance so that the EU commissioners know who to reach out to in order to get their hands on you.

Care to guess how much this service costs? Well, just start running that attorney’s per hour meter rapidly – and this has to be paid YEARLY – forever.

Now, care to guess ultimately who will pay for all of this?

Yes, YOU, the consumer – whether you live in the EU or not.

Sometimes I try to spare my readers from the under-the-hood nitty gritty – but this time, you really do need to know so that you can appreciate what vendors have dealt with to revamp their businesses and internal processes. Otherwise, we as a community stood to lose genetic genealogy and that would have been a mind-numbing tragedy.

What Does Comply Mean?

Some people are being very dismissive of GDPR, or hyper-critical of companies who are trying to change their products, features and websites to become compliant. It’s worth noting here that none of the major companies or vendors are EU companies.

Here’s an example of an e-mail update I received today from a US company:

After nearly two years of hard work and preparation, we are ready for May 25 — the start of “GDPR” in Europe. More than 500 employees from across our company have helped meet more than 1,500 project milestones.

The General Data Protection Regulation is a sweeping set of new and enhanced rules in the European Union. It covers how companies treat the personal data of customers and employees. Specifically, it makes sure an individual’s rights are enforced, personal data is inventoried, breaches are reported promptly, and privacy is baked into all products.

If someone tries to convince you that GDPR compliance is no big deal, they are either grossly uninformed about GDPR itself or don’t have any idea about the magnitude of the ramifications of GDPR on entities from large corporations down to (some) volunteers. Some people have opined that if the companies were “taking care of their customers’ data,” they wouldn’t have to do anything and “would have nothing to worry about in the first place.” That’s blatantly wrong.

For starters, every company had to undergo a specific compliance evaluation process, which was far from easy because GDPR doesn’t just tell you THAT you have to protect information, in some cases they specify how – keeping e-mails in a separate database for example. Data bases aren’t necessarily designed in that manner, nor is that the best solution for security or performance – not to mention genetic genealogy is about sharing.

However, if a company doesn’t comply and someone complains,they have to undergo an audit. If found out of compliance, they’re liable for a potentially astronomical fine by an unknown commissioner (each country has their own) who may or may not have a clue about technology or in this case, genetic genealogy and how it’s utilized.

I’ve made a list of a FEW of the GDPR requirements. Also, keep in mind, many of the requirements tell you in general terms what they want, but there are no examples of what they consider adequate, so you just have to guess and if an issue arises, the data commissioner gets to decide if you guessed correctly.

If not, you’ll get to pay up!

I have included the GDPR citation in the table below, so you can check for yourself if you think I’ve just made this up and am, well, scaremongering. In fact you can read the entire document here and here with the added schedules AND, if that’s not enough, you can then read the UK version here with explanatory notes available separately. Yes, it’s hundreds of pages of pure misery but if you have insomnia, it, guaranteed, will cure you immediately. Hey, there has to be a silver lining someplace.

I’ve briefly listed the requirement, summarized unless in quotes, and the reference citation from the first linked document above, published in the “Official Journal of the European Union.” So, your mission, should you choose to accept it, is to correlate the requirements of the first, second and third documents, together, and figure out how to resolve any conflicts. Good luck! Start now and you’ll exit the maze, dazed and confused, sometime around late summer😊

You will quickly see that I’m neither over-reacting nor making this up.

In the following table, a controller is the primary entity working with information. For genetic genealogy, that would be a DNA testing company or a third party vendor. A processor is any other entity, which could be a lab doing the actual processing, a third party working with a vendor or project administrators who also “process” information.

Processing is defined basically as anything you do with someone’s information:

‘Processing’ means any operation or set of operations which is performed on personal data or on sets of personal data, whether or not by automated means, such as collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction;…

A controller is defined in L119/33 article 4.7 and a processor in L119/33 article 4.8.

Over these next few days and weeks, when we’re tempted to be critical or impatient with a genetic genealogy vendor who has made changes instead of closing up shop and throwing in the proverbial towel – let’s try to be patient, grateful and cognizant of their effort. They have collectively been slaving away in the hot kitchen now for many months, trying to get ready to birth this 100 pound baby, while smiling, with as little disruption as possible to the rest of us.

I know we are all frustrated, but until we’ve walked that proverbial mile, we really have no idea what they’ve been through. From my experiences, I can tell you it was bloody painful.

Vendors’ GDPR compliance is much like an iceberg with a smiley face stuck on top. You’re only seeing the tippy top of the effort involved and it’s an entirely different picture underneath where everyone has been rowing like crazy.

Design By Committee

If you are thinking to yourself that this regulation looks a lot like it was designed by a committee, you’re right, it was. That negotiation process took 4 years, and the regulation took effect another 2 years later – meaning today.

Glory halleluiah, the birthing is FINALLY over, and the baby looks a lot like a….camel.

Huh?

What?

A camel?

Have you heard the analogy that a camel is a horse designed by a committee?

The idea was sound, but the outcome was not at all what was intended or expected. Indeed, the law of unintended consequences. GDPR’s effect on genetic genealogy certainly fits that bill.

In fact, here’s our new a-mazing GDPR horse.

For another perspective, head on over and read what Judy Russell, The Legal Genealogist has to say on the matter.

Now, for me, back to genealogy – a much needed respite!

______________________________________________________________

Disclosure

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Transfers

• Family Tree DNA
• MyHeritage DNA only
• MyHeritage DNA plus Health
• MyHeritage FREE DNA file upload
• AncestryDNA
• 23andMe Ancestry
• 23andMe Ancestry Plus Health
• LivingDNA

Genealogy Services

• MyHeritage FREE Tree Builder
• MyHeritage Subscription with Free Trial

Genealogy Research

• Legacy Tree Genealogists for genealogy research

Recently, I wrote an article titled, GDPR – It’s a Train and It’s a Comin’ wherein I discussed exactly what GDPR is, and why companies have to comply or risk massive fines. If you’re thinking of the recent Facebook fiasco right about now, that’s exactly where this type of legislation is focused, and why.

That said, this European legislation affects genetic genealogy in ways that weren’t anticipated and in ways that may require changes on the part of our providers and ourselves. Every company has to comply, meaning all of the companies that provide services if they have any EU or UK clients, so GDPR affects anyone in this industry – vendor, project administrator and/or customer. Needless to say, it affects you too, one way or another.

One of the most difficult aspects of GDPR is that the true effect is unknown. There is no case law yet to unravel the confusion. And yes, there is confusion. Lots of confusion.

There will be life after GDPR, and there will be genetic genealogy too – although it may look a bit different in some ways.

Many vendors have been preparing for some time now, so we have knowingly or unknowingly already seen many changes that were either required or perhaps bumped up the priority list by GDPR legislation.

First and foremost, the companies MUST comply to protect themselves, or we, as their customers who have invested not just in our own tests, but often tests for many family members will suffer greatly. If the companies go out of business – and yes, the GDPR fines are potentially severe enough at 20 million euros to bankrupt companies – we could all be impacted in a devastating fashion.

No matter what pain-in-the-patoot changes the vendors feel required to make, it’s far more preferable to adapt and retain access to our investment and genetic genealogy tools. The alternative isn’t pretty and the vendors aren’t making the changes because they woke up one morning and decided to make our lives (and theirs) difficult – they are making the necessary changes to protect themselves and our investment in their products along with our DNA results.

The four guiding principles of GDPR in combination are:

• Transparency
• Simplicity
• Privacy
• Consent

I am very grateful to the testing companies for stepping up and taking care of business, even though the “solution” sometimes makes life more inconvenient for me personally. That’s life right now and we just have to suck it up and get used to the changes.

Therefore, those of us who work in various ways with DNA and genetic genealogy, especially the DNA of others, need to be aware of GDPR requirements. I’ve seen a lot of misinformation fueled by fear circulating, so I’d like to discuss what is required, along with what we do and don’t know.

I’m going to say this now and again at the end of this article, so please, please take special note.

In other words, your mileage may vary. Not to mention, it’s certainly possible that I’ve misinterpreted something. You will see a lot of “weasel words” like “seems to be” and “I think,” because in many cases, we really don’t know.

Yes, change is uncomfortable, but I will get through this and so will you. No need to hit the panic button and the sky is not falling although there is some rumbling.

How Do You Work With DNA?

You may work with DNA in a variety of ways:

• Your own results in any or all of the commercial data bases, or a public database like GedMatch
• Results of family members or friends whose accounts you manage in any of the commercial data bases or at GedMatch
• Results of Family Tree DNA project members as a project administrator at Family Tree DNA
• Results of Family Tree DNA project members on a private or third-party website
• As a search angel helping others as a volunteer
• As a paid researcher or professional in this field in some capacity

Different Situations

GDPR speaks to a variety of situations, so let’s take a look at some of the provisions and how they might affect you and others.

Dead People

Deceased individuals are explicitly exempted from GDPR.

Volunteers

Volunteers and unpaid individuals are explicitly NOT exempted from GDPR regulations simply because they are volunteers or unpaid. GDPR applies to volunteers and unpaid individuals in the same way as those who are compensated unless other exemptions apply.

Attempting to Uniquely Identify a Person

If you are working with your own DNA results, and only your own results, GDPR probably affects you less than others – unless you are trying to uniquely identify a living person.

GDPR contains the following verbiage:

“Processing of personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, and the processing of genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health or data concerning a natural person’s sex life or sexual orientation shall be prohibited.”

To me, the most relevant part of this paragraph is, “for the purpose of uniquely identifying a natural person,” because I feel this relates to people searching for unknown biological parents.

Although GDPR does not apply to deceased people, you don’t know if your parent is deceased until you identify them. If the parent has submitted their own DNA for testing, this wouldn’t seem to be an issue, because the parent(s) intentionally, consensually, tested, entering their DNA into a genetic genealogy data base with the intention of matching and being seen by matches. In other words, you don’t have to “do” anything other than test to identify your parent – because that match is already waiting for you.

However, if an individual tests and then subsequently uses DNA results and other tools and techniques with the intention of uniquely identifying the parent, that seems to be “processing” that is prohibited.

I will not be attempting to track down and personally identify any person who could be living today, meaning certainly no one born within the last 100 years. That doesn’t mean I don’t think people searching for birth family shouldn’t test – I think the process of searching after testing could be problematic under GDPR.

Processors vs Controllers

In the GDPR documentation, controllers are very clearly companies doing the DNA tests and making decisions. Processors, however, are people or companies that perform additional functions as determined by the controllers. The definition and relationship of people who do genetic genealogy work is unclear. Certainly no one working on the GDPR legislation considered genetic genealogy whose intention IS to SHARE information.

If one is working with an individual’s DNA in a professional capacity, the argument that the professional is “processing the information” and making decisions about that processing would seem to be pretty convincing, especially if they were uploading information, or working with matches to identify someone.

You be your own judge, but processors are bound in most cases by the same rules as controllers – and controllers are required to be sure that processors know what is expected of them if they are in any way involved in the transfer of information from the controller to the processor. Another category, “third parties” is largely undefined, as are their responsibilities.

To be safe, I’m presuming worst case here, meaning that all regulations apply, because I don’t want to be caught in an uncomfortable or even ugly situation.

GDPR Does Not Apply To

• GDPR does not apply to “a natural person in the course of a purely personal or household activity and thus with no connection to a commercial activity.”
• Clearly, the verbiage here suggests that individuals working with family data might not be subject to GDPR, but the verbiage about not uniquely identifying individuals would seem to pertain regardless.
• Yes, these two provisions might well be in conflict with each other. I have absolutely no idea which would be determined to be accurate nor under what circumstances. Nor do I know how people administering larger projects, such as regional or haplogroup projects would be viewed since their interest is beyond the “household” but is not connected to a commercial activity.

Location

• While GDPR applies to European residents, you may not be aware that someone is a European resident. I’m going to assume that everyone is a European resident and that way there is no possible mistake.
• GDPR does not appear to apply to European citizens living outside of the EU/UK.

Anonymization

• I would suggest that people not represent to others that they can be anonymous in data bases if or when they test. People are being identified daily based on autosomal tests by comparing the trees and genealogy information of who they match, especially related to parent search cases. That “anonymous” cow left the barn long ago.

Permission

Permission, also termed consent in GDPR, was always important, but is now even more so.

• Do not do anything with anyone’s information, meaning DNA information or other information they have provided without their express WRITTEN permission. I’m viewing e-mail as written permission, but that might not be strong enough, especially not for anyone doing research on behalf of others.
• People can only give consent for their own information, or the information for someone they have legal authority to given consent for (child, etc.) or someone whose permission they have obtained.
• You must inform someone whose information you have access to or that they have provided that they have the right to ask for their data to be corrected or removed and of the relevant address where to complain, and how, if they are not happy with a controller or processor.
• Do not expose anyone’s information, including their GedMatch or Family Tree DNA kit number, on a presentation slide, on Facebook or anyplace else without the person’s explicit permission.

Data

• GDPR says that one can’t continue to hold data longer than necessary to finish the processing for which the person has agreed.
• My personal assumption would be that this means that I would delete client reports when they are complete. However, I have in the past kept reports handy, because many clients have asked for a copy, even years later, after losing the original. This also begs the question, relative to DNA and genealogy projects, when is “done?”
• My interpretation would be that one would need permission to maintain the data or information in any format after you have “finished.” However, as we all know, genealogy is never finished, and our genealogical “best practices” are focused on retaining information, not disposing of it.
• GDPR isn’t about just genetic data. If other information is gathered, such as through a blog or newsletter, be sure that your usages are GDPR compliant, as are any tools that people utilize for your applications such as blogging platforms, website providers, etc.

Rules

• Controllers and processors must store contact information separately from “results.” I’m presuming this means in a separate spreadsheet for project administrators and people working with other people’s (genetic) information.
• Controllers and processors may be required to track when they are “processing” and what they are doing. Fortunately, for Group Project Administrators, Family Tree DNA provides a logging function which will help immensely.
• If a controller/processor receives a request to provide an individual with all of the information the controller/processor holds on the individual, the processor must comply in a reasonable time – mentioned in the GDPR documentation as within 30 days.
• Project administrators may want to post a privacy policy on their project website at FTDNA and/or elsewhere, especially if any project information is posted outside of the FTDNA project structure. Your project members will need to know that your project is separate from Family Tree DNA, and that they need to contact you directly for modification/removal of both posted data and anything they have personally sent you.
• Never release the names or e-mails of project members, or any other individual, without their express consent for every request. I tell the requesting person if they will compose an e-mail, I will simply forward it to the project member they are asking about. That removes the entire issue and leaves it in the hands of the project member.
• If a personal data breach occurs that results in either loss of or exposure of records, the controller or processor must report the breach within 72 hours to the supervisory authority. However, reporting is not required if the breach is “unlikely to result in risk to the rights and freedoms of natural persons.”

Right to Erasure aka Right to be Forgotten

• If an individual asks you to delete any information they have previously provided to you, it should be done within 30 days. There is some leeway, but minimally the person can expect timely communication from you.
• I would think this would be particularly important for project administrators, especially if the project website is maintained outside of the Family Tree DNA structure where the administrator has created a separate website.
• If a project member changes their privacy setting from a public to a project-only setting, that change is reflected in the project display automatically at Family Tree DNA. If an administrator maintains a separate website, they will need to devise a way to routinely coordinate the privacy settings of project members to reflect new changes. I’m very glad that I don’t maintain any projects outside of the Family Tree DNA structure. It’s still possible to miss some text you’ve put on a separate results page perhaps, but the former project member’s results will automatically be deleted from the project and social media feed, both, by Family Tree DNA.
• If a person has provided you with any information, and they request you to remove or correct it, do so quickly and thoroughly, within the 30 day window. This applies to both paper and computer files.
• In GDPR, there is no provision, consideration or discussion of situations where websites become abandoned over time. In my opinion, GDPR never considered a hobby type of environment where someone posting informational content might not have a registered domain name that would disappear if not paid for. Furthermore, information that has been posted to the web in reality cannot be entirely removed given tools like WayBackMachine. Nothing that has been published is ever really “deleted” from the internet or is entirely “forgotten,” regardless of GDPR.
• Be sure when obsoleting your computer to reformat or destroy your disk drive in a manner in which the data cannot be recovered by the next owner.

Guiding Principles

• I am not going to be providing any information to anyone about living people as a result of genetic or genealogy research beyond matches provided by a testing company. People can view their own matches for themselves, so that’s not information I need to provide.
• I am not going to recommend uploading to GedMatch or other “open” platform, should one exist, without a commensurate statement that the data base is open, and anyone whom the person matches and sees their kit number can also see whom they match, along with their ethnicity, etc. I’m personally fine with that scenario, but blanket recommendations to upload to GedMatch don’t take into consideration the informed consent necessary for people unfamiliar with the platform, especially relative to “sensitive information” that can identify someone’s racial makeup or religion.
• Do not change anyone’s anything unless you have explicit consent. This means not restricting what others can see or do and not making decisions for them unless you have been specifically designated/authorized to do so. Family Tree DNA has a methodology for a tester to explicitly grant a project administrator full access in order for that individual to grant an administrator more than read/view access. Ancestry also has provisions to allow others to manage a kit or share additional information.
• Do not share anyone else’s GedMatch kit number, especially not in any public forum.
• Do not add living people to your tree(s) and allow them to be seen publicly without their express consent.
• Never expose a minor’s information.
• I would suggest that it is unethical to attempt to “recreate” an autosomal kit representing the DNA of a living person who has declined to DNA test by utilizing the DNA of their other family members, in particular, their children. This does not apply to recreating the DNA profile of deceased family members – only living people who have exercised their right to refuse DNA testing.
• Do not order, transfer, upgrade or otherwise “process” the DNA of anyone without their permission unless it is your DNA, you are their legal guardian or they have granted you permission to do so.

In essence, kindergarten rules apply – do unto others, treat others respectfully and how you would want to be treated.

There’s a lot we don’t know about how GDPR will be interpreted in the long run. I don’t believe GDPR is targeting people like project administrators, unless they are incredibly negligent or intentionally violate the privacy of others. I suspect that, for the most part, being careful with other people’s information, respectful and perhaps more aware than in the past will keep us all safe.

And yes, I know…all it would really take is that one vindictive bad apple that might make your life miserable – especially given that we really don’t know how genetic genealogists will be viewed under GDPR.

I know the changes within projects at Family Tree DNA have upset some group project administrators, and while I don’t like change any better than the next person, I’m actually grateful that Family Tree DNA has implemented modifications that will prevent me (and others) from making errors in judgement or simply getting too busy to delete someone’s information.

I don’t host any projects outside of the Family Tree DNA framework, and if I did, I would revert at this point to Family Tree DNA hosted projects since they have invested the effort into modifications for GDPR compliance. I think that so long as I stay within their framework, and follow the rules, I should be fine.

If you have personal concerns, I would suggest that you read the GDPR documentation for yourself, view the ISOGGG slide presentation listed below, or contact your own lawyer, because as I said before:

Additional Resources

• ISOGG slide presentation
• www.eugdpr.org
• The EU document: http://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32016R0679&from=EN
• The UK document: https://www.gov.uk/government/collections/data-protection-bill-2017
• Parliament BIll HL Bill 66: https://publications.parliament.uk/pa/bills/lbill/2017-2019/0066/lbill_2017-20190066_en_1.htm
• Information Commissioner’s Office Website: https://ico.org.uk/
• Irish Data Protection Commissioner: https://www.dataprotection.ie/docs/gdpr/1623.htm
• Quick Access Document by intersoft consulting https://gdpr-info.eu/

______________________________________________________________

Disclosure

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Transfers

• Family Tree DNA
• MyHeritage DNA only
• MyHeritage DNA plus Health
• MyHeritage FREE DNA file upload
• AncestryDNA
• 23andMe Ancestry
• 23andMe Ancestry Plus Health
• LivingDNA

Genealogy Services

• MyHeritage FREE Tree Builder
• MyHeritage Subscription with Free Trial

Genealogy Research

• Legacy Tree Genealogists for genealogy research